Skip to content

Remove ambiguous note about use of localpubkey in to_remote #1299

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Remove ambiguous note about use of localpubkey in to_remote #1299

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
747e005
03: remove note that remote uses your `localpubkey` in their `to_remote`
carlaKC Nov 17, 2025
992b7a2
03: specify htlc pubkey in test vectors for local/remote_htlcpubkey
carlaKC Oct 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 9 additions & 10 deletions 03-transactions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,8 +139,7 @@ The output is spent by an input with `nSequence` field set to `1` and witness:

<remote_sig>

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.
Otherwise, this output is a simple P2WPKH to `remotepubkey`.

#### `to_local_anchor` and `to_remote_anchor` Output (option_anchors)

Expand Down Expand Up @@ -1036,8 +1035,8 @@ The *expected weight* of an HTLC transaction is calculated as follows:
- OP_IF: 1 byte
- OP_CHECKSIG: 1 byte
- OP_ELSE: 1 byte
- OP_DATA: 1 byte (remotepubkey length)
- remotepubkey: 33 bytes
- OP_DATA: 1 byte (remote_htlcpubkey length)
- remote_htlcpubkey: 33 bytes
- OP_SWAP: 1 byte
- OP_SIZE: 1 byte
- OP_DATA: 1 byte (32 length)
Expand All @@ -1050,8 +1049,8 @@ The *expected weight* of an HTLC transaction is calculated as follows:
- OP_EQUALVERIFY: 1 byte
- 2: 1 byte
- OP_SWAP: 1 byte
- OP_DATA: 1 byte (localpubkey length)
- localpubkey: 33 bytes
- OP_DATA: 1 byte (local_htlcpubkey length)
- local_htlcpubkey: 33 bytes
- 2: 1 byte
- OP_CHECKMULTISIG: 1 byte
- OP_ELSE: 1 byte
Expand All @@ -1076,8 +1075,8 @@ The *expected weight* of an HTLC transaction is calculated as follows:
- OP_IF: 1 byte
- OP_CHECKSIG: 1 byte
- OP_ELSE: 1 byte
- OP_DATA: 1 byte (remotepubkey length)
- remotepubkey: 33 bytes
- OP_DATA: 1 byte (remote_htlcpubkey length)
- remote_htlcpubkey: 33 bytes
- OP_SWAP: 1 byte
- OP_SIZE: 1 byte
- OP_DATA: 1 byte (32 length)
Expand All @@ -1087,8 +1086,8 @@ The *expected weight* of an HTLC transaction is calculated as follows:
- OP_DROP: 1 byte
- 2: 1 byte
- OP_SWAP: 1 byte
- OP_DATA: 1 byte (localpubkey length)
- localpubkey: 33 bytes
- OP_DATA: 1 byte (local_htlcpubkey length)
- local_htlcpubkey: 33 bytes
- 2: 1 byte
- OP_CHECKMULTISIG: 1 byte
- OP_ELSE: 1 byte
Expand Down