Difference between revisions of "Merkle proof"
Todd Price (talk | contribs) |
Todd Price (talk | contribs) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
The data element is hashed to create its [[leaf (node)|leaf node]] value, and then hashed with a provided set of the adjunct node values along the [[Merkle path]] back to the root. | The data element is hashed to create its [[leaf (node)|leaf node]] value, and then hashed with a provided set of the adjunct node values along the [[Merkle path]] back to the root. | ||
| − | If the same Merkle root is created as has been published previous, then it stands that the data element is be guaranteed to come from the same index in the same data set as in the earlier published instance. | + | If the same Merkle root is created as has been published previous, then it stands that the data element is be guaranteed to come from the same [[index]] in the same data set as in the earlier published instance. |
| + | |||
| + | For more information on the Standardised format for a Merkle proof see the published standard by the Technical Standards Committee here: https://tsc.bitcoinassociation.net/standards/merkle-proof-standardised-format/ | ||
Latest revision as of 05:48, 25 April 2022
A Merkle proof is the act of verifying an element exists within a set summarised by the Merkle root.
The data element is hashed to create its leaf node value, and then hashed with a provided set of the adjunct node values along the Merkle path back to the root.
If the same Merkle root is created as has been published previous, then it stands that the data element is be guaranteed to come from the same index in the same data set as in the earlier published instance.
For more information on the Standardised format for a Merkle proof see the published standard by the Technical Standards Committee here: https://tsc.bitcoinassociation.net/standards/merkle-proof-standardised-format/