From c4a0369e705ad43babee50dd0466f162567e6427 Mon Sep 17 00:00:00 2001 From: Gregory Sanders Date: Thu, 12 May 2022 03:19:21 -0400 Subject: [PATCH] Make generated pubkeys slightly more grep-able (#988) * remotepubkey instead of remote_pubkey * Add a grepable reference of localpubkey usage --- 03-transactions.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/03-transactions.md b/03-transactions.md index fb6de87..6420a2b 100644 --- a/03-transactions.md +++ b/03-transactions.md @@ -128,13 +128,14 @@ If a revoked commitment transaction is published, the other party can spend this If `option_anchors` applies to the commitment transaction, the `to_remote` output is encumbered by a one block csv lock. - OP_CHECKSIGVERIFY 1 OP_CHECKSEQUENCEVERIFY + OP_CHECKSIGVERIFY 1 OP_CHECKSEQUENCEVERIFY The output is spent by an input with `nSequence` field set to `1` and witness: -Otherwise, this output is a simple P2WPKH to `remotepubkey`. +Otherwise, this output is a simple P2WPKH to `remotepubkey`. Note: the remote's commitment transaction uses your `localpubkey` for their +`to_remote` output to yourself. #### `to_local_anchor` and `to_remote_anchor` Output (option_anchors)