Skip to content
This repository has been archived by the owner on Mar 24, 2023. It is now read-only.

Use a Merkle accumulator for history #29

Open
adlerjohn opened this issue May 14, 2020 · 1 comment
Open

Use a Merkle accumulator for history #29

adlerjohn opened this issue May 14, 2020 · 1 comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request investigation Investigation required.

Comments

@adlerjohn
Copy link
Member

adlerjohn commented May 14, 2020 •
edited by liamsi
Loading

Instead of a linear previous-blockhash, a Merkle accumulator (such as a Merkle mountain range) should be used. This allows for proving inclusion of a block in the chain with a logarithmic number of hashes, which is especially in the context of cross-chain relays.
@adlerjohn adlerjohn added documentation Improvements or additions to documentation enhancement New feature or request labels May 14, 2020
@adlerjohn adlerjohn added this to the Pre-implementation draft milestone May 14, 2020
@adlerjohn adlerjohn self-assigned this May 14, 2020
@adlerjohn adlerjohn added the investigation Investigation required. label Jun 17, 2020
@adlerjohn
Copy link
Member Author

It might be possible to capture all the benefits of an in-protocol history MMR with a history MMR computed entirely client-side (i.e. add a new leaf to a locally-maintained MMR for each new block header).

@adlerjohn adlerjohn removed their assignment Mar 13, 2021
@liamsi liamsi added this to To do in Mainnet and beyond via automation Mar 17, 2021
@liamsi liamsi removed this from the Pre-implementation draft milestone Mar 17, 2021
@liamsi liamsi removed this from To do in Mainnet and beyond Dec 5, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
documentation Improvements or additions to documentation enhancement New feature or request investigation Investigation required.
Projects
No open projects
Celestia Node
Status: TODO
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adlerjohn @liamsi