Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Sparse Merkle Trie for Fork-Choice Rule Data Structure #429

Closed
rauljordan opened this issue Aug 22, 2018 · 2 comments
Closed

Use Sparse Merkle Trie for Fork-Choice Rule Data Structure #429

rauljordan opened this issue Aug 22, 2018 · 2 comments
Assignees
Milestone

Comments

@rauljordan
Copy link
Contributor

Hi all,

As part of #422, we are using a DAG to store received blocks at each received slot number. This is implemented naively as a map of slots to slices of blocks, which does not lend itself to light-client friendly proofs. SMT (Sparse Merkle Tries) have been discussed as the path forward. A PR for this would use an SMT instead of the map created in #422's /beacon-chain/blockchain/service.go.

Assigning provisionally to @nisdas.

@nisdas
Copy link
Member

nisdas commented Aug 26, 2018

@rauljordan
Copy link
Contributor Author

rauljordan commented Aug 30, 2018

Closing this as we have decided to persist all processed blocks and purge after proof of custody is over

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants