@@ -26,7 +26,7 @@ sure the transaction is really made up, and you can't prove it
26
26
compactly to someone who doesn't know every transaction: "you can't
27
27
prove a negative".
28
28
29
- ### Pettycoin's Solution # ##
29
+ ## Pettycoin's Solution ##
30
30
31
31
The miner inserts an index for each input into the block alongside the
32
32
transaction: this says where the input transaction is. This
@@ -38,7 +38,7 @@ transaction, the input refs (both with proof that they're in the
38
38
block), and the transaction where the input ref said it would be (with proof).
39
39
You still need to detect double-spends in the traditional way, though.
40
40
41
- ### The UTXO Committment Solution # ##
41
+ ## The UTXO Committment Solution ##
42
42
43
43
This is a bit more complicated, but it does more. The scheme has
44
44
several parts, the first of which is UTXO Committments; a seemingly
@@ -50,7 +50,7 @@ standard part of bitcoin-wizard lore which has several variants
50
50
and
51
51
[ Peter Todd has an implementation] ( https://github.com/petertodd/python-merbinnertree ) ).
52
52
53
- #### Background: UTXO Commitments in A Nutshell # ###
53
+ ### Background: UTXO Commitments in A Nutshell ###
54
54
55
55
The important part of bitcoin is the Unspent Transaction Outputs
56
56
(UTXO): stuff which can still be used. As you go through the blocks,
@@ -94,7 +94,7 @@ incorrectly and that can be proven.
94
94
The UTXO commitment scheme opens the door to "assisted transactions"
95
95
where you supply a transaction along with UTXO proofs that all its
96
96
inputs are unspent as of the last block. A recipient which knows
97
- only the block headers[ ^ utxo-not-in-hdrs ] can confidently accept this as an
97
+ only the block headers< sup > [ 1 ] ( #footnote-1 ) </ sup > can confidently accept this as an
98
98
unconfirmed transaction.
99
99
100
100
In fact, a miner can actually mine this without any extra checks:
@@ -110,7 +110,7 @@ Corollaries of this include (1) Gregory Maxwell is smarter than I am,
110
110
and (2) if you can get the attention of the right bitcoin wizards,
111
111
your own sidechain project will be greatly improved :)
112
112
113
- [ ^ utxo-not-in-hdrs ] Bitcoin is unlikely to add the UTXO hash to the
113
+ < a name = " footnote-1 " > [ 1 ] </ a > Bitcoin is unlikely to add the UTXO hash to the
114
114
80-byte header. Instead, it would become a compulsory part of the
115
115
coinbase, is the order of 100 bytes long, and you need
116
116
log2(num-transactions) 32 byte hashes to attach it to the header. But
0 commit comments