Skip to content
This repository has been archived by the owner on Feb 1, 2019. It is now read-only.

Shard state/data local storage #33

Open
jamesray1 opened this issue Apr 17, 2018 · 3 comments
Open

Shard state/data local storage #33

jamesray1 opened this issue Apr 17, 2018 · 3 comments
Assignees
@ChosunOne
Labels
A3: in progress Pull request is in progress. No review needed at this stage. M4: core Core client code / Rust. P5: some time soon The issue is worth doing soon. phase 1 Refer to https://ethresear.ch/t/sharding-phase-1-spec/1407

Comments

@jamesray1
Copy link
Member

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
@jamesray1 jamesray1 added the phase 1 Refer to https://ethresear.ch/t/sharding-phase-1-spec/1407 label Apr 17, 2018
@jamesray1 jamesray1 self-assigned this Apr 17, 2018
@jamesray1 jamesray1 changed the title Shard state local storage Shard state/data local storage Apr 18, 2018
@jamesray1 jamesray1 removed their assignment Apr 18, 2018
@jamesray1 jamesray1 added the help wanted Extra attention is needed label Apr 18, 2018
@jamesray1 jamesray1 mentioned this issue Apr 27, 2018
Open
@timxor
Copy link
Contributor

timxor commented Apr 27, 2018

@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
Copy link
Contributor

timxor commented Apr 27, 2018 •
edited
Loading

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

@jamesray1
Copy link
Member Author

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.

@ChosunOne ChosunOne self-assigned this May 5, 2018
@ChosunOne ChosunOne added WIP and removed help wanted Extra attention is needed labels May 5, 2018
@jamesray1 jamesray1 added M4: core Core client code / Rust. A3: in progress Pull request is in progress. No review needed at this stage. P5: some time soon The issue is worth doing soon. and removed M4: core Core client code / Rust. WIP labels May 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ChosunOne ChosunOne

Labels
A3: in progress Pull request is in progress. No review needed at this stage. M4: core Core client code / Rust. P5: some time soon The issue is worth doing soon. phase 1 Refer to https://ethresear.ch/t/sharding-phase-1-spec/1407
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@timxor @ChosunOne @jamesray1