mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

Concretize Output Ordering to be less confusing (#876)

Browse Source 
* Clean up output sorting wording to be a sorted list and way more explicit
* Retitle section to not mention input ordering as we do not need it
This commit is contained in:
Matt Corallo 2021-06-21 20:14:27 +00:00 committed by GitHub
parent 381650c7bc
commit bda72c8305
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
03-transactions.md
View File

@ -5,7 +5,7 @@ This details the exact format of on-chain transactions, which both sides need to
# Table of Contents
* [Transactions](#transactions)
* [Transaction Input and Output Ordering](#transaction-input-and-output-ordering)
* [Transaction Output Ordering](#transaction-output-ordering)
* [Use of Segwit](#use-of-segwit)
* [Funding Transaction Output](#funding-transaction-output)
* [Commitment Transaction](#commitment-transaction)
@ -42,9 +42,12 @@ This details the exact format of on-chain transactions, which both sides need to
# Transactions
## Transaction Input and Output Ordering
## Transaction Output Ordering
Lexicographic ordering: see [BIP69](https://github.com/bitcoin/bips/blob/master/bip-0069.mediawiki). In the case of identical HTLC outputs (amount of satoshis as well as the script are the same), the outputs are ordered in increasing `cltv_expiry` order.
Outputs in transactions are always sorted according to:
* first according to their value (in whole satoshis, note that for HTLC outputs, the millisatoshi part must be ignored)
* followed by `scriptpubkey`, comparing the common-length prefix lexicographically as if by `memcmp`, then selecting the shorter script (if they differ in length),
* finally, for HTLC outputs, in increasing `cltv_expiry` order.
## Rationale