Skip to content

Make it explicit witness must conform to MINIMALIF #764

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

Merged
t-bast merged 1 commit into from
Apr 27, 2020
Merged

Make it explicit witness must conform to MINIMALIF #764

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 1 addition & 0 deletions .aspell.en.pws
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -378,3 +378,4 @@ IRC
bitmasks
CSPRNG
lexicographically
MINIMALIF
8 changes: 5 additions & 3 deletions 03-transactions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,6 +56,8 @@ thus the two peers must agree on the canonical ordering for this case.

Most transaction outputs used here are pay-to-witness-script-hash<sup>[BIP141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#witness-program)</sup> (P2WSH) outputs: the Segwit version of P2SH. To spend such outputs, the last item on the witness stack must be the actual script that was used to generate the P2WSH output that is being spent. This last item has been omitted for brevity in the rest of this document.

A `<>` designates an empty vector as required for compliance with MINIMALIF-standard rule.<sup>[MINIMALIF](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-August/013014.html)</sup>

## Funding Transaction Output

* The funding output script is a P2WSH to:
Expand Down Expand Up @@ -109,7 +111,7 @@ This output sends funds back to the owner of this commitment transaction and thu

The output is spent by a transaction with `nSequence` field set to `to_self_delay` (which can only be valid after that duration has passed) and witness:

<local_delayedsig> 0
<local_delayedsig> <>

If a revoked commitment transaction is published, the other party can spend this output immediately with the following witness:

Expand Down Expand Up @@ -172,7 +174,7 @@ This output sends funds to either the remote node after the HTLC-timeout or usin

To timeout the HTLC, the remote node spends it with the witness:

<remotehtlcsig> 0
<remotehtlcsig> <>

If a revoked commitment transaction is published, the remote node can spend this output immediately with the following witness:

Expand Down Expand Up @@ -232,7 +234,7 @@ These HTLC transactions are almost identical, except the HTLC-timeout transactio
* `txin[0]` outpoint: `txid` of the commitment transaction and `output_index` of the matching HTLC output for the HTLC transaction
* `txin[0]` sequence: `0`
* `txin[0]` script bytes: `0`
* `txin[0]` witness stack: `0 <remotehtlcsig> <localhtlcsig> <payment_preimage>` for HTLC-success, `0 <remotehtlcsig> <localhtlcsig> 0` for HTLC-timeout
* `txin[0]` witness stack: `0 <remotehtlcsig> <localhtlcsig> <payment_preimage>` for HTLC-success, `0 <remotehtlcsig> <localhtlcsig> <>` for HTLC-timeout
* txout count: 1
* `txout[0]` amount: the HTLC amount minus fees (see [Fee Calculation](#fee-calculation))
* `txout[0]` script: version-0 P2WSH with witness script as shown below
Expand Down