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

Keep the signed merkle root of the Ethereum bridge pool updated #423

Closed
4 of 5 tasks
Tracked by #420
batconjurer opened this issue Sep 2, 2022 · 1 comment
Closed
4 of 5 tasks
Tracked by #420

Comments

@batconjurer
Copy link
Member

batconjurer commented Sep 2, 2022

This will have two implementations: one for vote extensions and one for without.

For vote extensions:

  • Each validator signs the latest root and adds to their vote extensions
  • At every block, these signatures are aggregated and included in the block proposal to be included in storage.

Without vote extensions:

  • Each validator signs the latest root and broadcasts it as a protocol tx
  • These signatures appear on chain and we keep a tally of partial proofs of different merkle tree roots in storage.
  • We maintain the latest root which has reached a quorum of signatures.
@cwgoes
Copy link
Collaborator

cwgoes commented Jan 13, 2023

@batconjurer is this up-to-date?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Tested in Devnet
Development

No branches or pull requests

2 participants