Expand description
Merkle Trees used by the protocol.
Every tree hashes its inner nodes with its own key, so a node of one tree can’t be interpreted as a node of another tree. Trees with a number of leaves that isn’t known at compile time also commit to it.
Type Aliases§
- Beacon
Chain Body Merkle Tree - Beacon chain block body
- Beacon
Chain Header Merkle Tree - Beacon chain block header fields, its root is the block root
- Block
Merkle Mountain Range - Beacon chain block roots.
- Child
Intermediate Shard Blocks Merkle Tree - Child intermediate shard block roots of a beacon chain block
- Child
Leaf Shard Blocks Merkle Tree - Child leaf shard block roots of an intermediate shard block
- Intermediate
Shard Body Merkle Tree - Intermediate shard block body
- Intermediate
Shard Header Merkle Tree - Intermediate shard block header fields, its root is the block root
- Intermediate
Shards Segments Merkle Tree - Segments of child intermediate shard blocks of a beacon chain block
- Leaf
Shard Body Merkle Tree - Leaf shard block body
- Leaf
Shard Header Merkle Tree - Leaf shard block header fields, its root is the block root
- Leaf
Shards Segments Merkle Tree - Own segments of child leaf shard blocks of an intermediate shard block
- OwnSegments
Merkle Tree - Own segments of a shard
- Segment
Roots Merkle Tree - Segment roots of own segments of a shard
- Shard
OwnSegments Merkle Tree - Own segments of a leaf shard
- State
Owner Contracts Sparse Merkle Tree - State of one owner: hashes of contents of slots by the address of the managing contract
- State
Owners Sparse Merkle Tree - Global state: state roots of owners by owner address
- Super
Segment Merkle Tree - Segment roots with their positions in a super segment
- Transactions
Merkle Tree - Transactions of a leaf shard block