mirror of https://github.com/zcash/zips.git
Rework paragraph to eliminate incomplete sentence
This commit is contained in:
parent
f503789adf
commit
7b98f97f5d
|
@ -571,9 +571,9 @@ reduce the memory requirements for managing and updating the commitment trees.
|
||||||
In leaf nodes, some information is repeated. We chose to do this so that leaf nodes could
|
In leaf nodes, some information is repeated. We chose to do this so that leaf nodes could
|
||||||
be treated identically to internal and root nodes for all algorithms and (de)serializers.
|
be treated identically to internal and root nodes for all algorithms and (de)serializers.
|
||||||
Leaf nodes are easily identifiable, as they will show proof of work in the
|
Leaf nodes are easily identifiable, as they will show proof of work in the
|
||||||
``hashSubtreeCommitment`` field, and their block range (calculated as
|
``hashSubtreeCommitment`` field (which commits to the block hash for leaf nodes), and
|
||||||
``nLatestHeight - (nEarliestHeight - 1)``) will be precisely 1. For the same reason, we
|
their block range (calculated as ``nLatestHeight - (nEarliestHeight - 1)``) will be
|
||||||
change the semantics of ``hashSubtreeCommitment`` in leaf nodes to commit
|
precisely 1.
|
||||||
|
|
||||||
Personalized BLAKE2b-256 was selected to match existing Zcash conventions. Adding the
|
Personalized BLAKE2b-256 was selected to match existing Zcash conventions. Adding the
|
||||||
consensus branch ID to the hash personalization string ensures that valid nodes from one
|
consensus branch ID to the hash personalization string ensures that valid nodes from one
|
||||||
|
|
Loading…
Reference in New Issue