search

Drops-of-Diamond / diamond_drops

WIP on sharding and Ethereum 2.0 with enshrined-in-consensus data availability and Rust: a fast, safe, concurrent and practical programming language
The Unlicense
57 stars 14 forks source link

Shard state/data local storage #33

Open jamesray1 opened 6 years ago

jamesray1 commented 6 years ago

I think we want to use sparse merkle trees https://ethresear.ch/t/data-availability-proof-friendly-state-tree-transitions/1453/6 https://github.com/ethereum/research/blob/master/trie_research/bintrie2/new_bintrie.py

https://gitter.im/ethereum/sharding?at=5ad49182102fac7b7b19334c

timxor commented 6 years ago

@jamesray1 so the db should store collation roots (defined in src/collation/header.rs and src/collation/collation.rs) for just up to 100 separate shard collation roots?

timxor commented 6 years ago

And implemented with a sparse binary merkle tree data structure, yea?

jamesray1 commented 6 years ago

Sorry @tcsiwula, I only just saw this, I tend to see Gitter comments faster.

We may use one shard p2p network as per #34.

But yes, it should store collation bodies and headers, but the current R&D direction is to use a sparse merkle binary tree to store this data.