BitcoinCash/specification
1
Fork 0
Code Issues Pull Requests Releases Activity

Merge pull request #14 from BitcoinUnlimited/dagurval-patch-1

Browse Source 
Update transaction-ordering.md
This commit is contained in:
dagurval
2020-02-25 20:12:10 +01:00
committed by GitHub
parent dbf0f71b0b bf0afffa37
commit e6659104a9
1 changed files with 7 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
protocol/blockchain/block/transaction-ordering.md
+6 -3
View File
@@ -7,9 +7,10 @@ For historic blocks, see [Topological Transaction Ordering](#legacy-transaction-
## Canonical Transaction Ordering ## Canonical Transaction Ordering
With canonical transaction ordering (CTOR), the Transactions after the Coinbase Transaction are required to be sorted in lexicographical order by Transaction Hash. With canonical transaction ordering (CTOR), the transactions after the coinbase transaction are required to be sorted in lexicographical order by transaction hash. The transaction hash is interpreted as little endian during sort. CTOR was scheduled to activate at median-time-past time 1542300000 and activated at block height 556766 (inclusive) on mainnet.
New Blocks will not be accepted by the network unless they follow this constraint. After activation, blocks that do not follow this constraint will be rejected by the network.
CTOR went into effect at 1542300000 unix time (November 15, 2018 4:40:00 PM GMT).
CTOR is also sometimes referred to as LTOR (lexicographical transaction ordering).
See [HF20181115](/protocol/forks/HF20181115) for more information on this change. See [HF20181115](/protocol/forks/HF20181115) for more information on this change.
@@ -17,3 +18,5 @@ See [HF20181115](/protocol/forks/HF20181115) for more information on this change
With topological transaction ordering, Transactions after the Coinbase Transaction were required to abide by the following constraint: if a transaction B spends outputs created by transaction A, transaction B must appear after transaction A in the block. With topological transaction ordering, Transactions after the Coinbase Transaction were required to abide by the following constraint: if a transaction B spends outputs created by transaction A, transaction B must appear after transaction A in the block.
Otherwise, transactions could appear in any order. Otherwise, transactions could appear in any order.
Before CTOR activated (block height < 556766) this was the required transaction order.