mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 09:46:12 +00:00
Dev Docs: Change MerkleBlock To Merkle Block (But Not P2P Message Form)
This commit is contained in:
parent
6edf496a5b
commit
b9ee23615a
5 changed files with 11 additions and 10 deletions
|
@ -140,7 +140,7 @@ message header:
|
|||
message headers: message header
|
||||
message payload:
|
||||
'`merchant_data`': pp merchant data
|
||||
merkleblock: merkleblock message
|
||||
merkle block:
|
||||
'`merkleblock` message': merkleblock message
|
||||
'`merkleblock` messages': merkleblock message
|
||||
merkle root:
|
||||
|
|
|
@ -77,6 +77,7 @@
|
|||
[mempool message]: /en/developer-reference#mempool "A P2P protocol message used to request one or more inv messages with currently-unconfirmed transactions"
|
||||
[merge]: /en/developer-guide#term-merge "Spending, in the same transaction, multiple outputs which can be traced back to different previous spenders, leaking information about how many satoshis you control"
|
||||
[merge avoidance]: /en/developer-guide#term-merge-avoidance "A strategy for selecting which outputs to spend that avoids merging outputs with different histories that could leak private information"
|
||||
[merkle block]: /en/developer-reference#merkleblock "A partial merkle tree connecting transactions matching a bloom filter to the merkle root of a block"
|
||||
[merkle root]: /en/developer-guide#term-merkle-root "The root node of a merkle tree descended from all the hashed pairs in the tree"
|
||||
[merkle tree]: /en/developer-guide#term-merkle-tree "A tree constructed by hashing paired data, then pairing and hashing the results until a single hash remains, the merkle root"
|
||||
[merkleblock message]: /en/developer-reference#merkleblock "A P2P protocol message used to request a filtered block useful for SPV proofs"
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue