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

Support "commitments" in Home and Replica #55

Closed
asaj opened this issue Jan 31, 2022 · 0 comments
Closed

Support "commitments" in Home and Replica #55

asaj opened this issue Jan 31, 2022 · 0 comments

Comments

@asaj
Copy link
Contributor

asaj commented Jan 31, 2022

This issue is to replace the existing "update" model for synchronizing Home and Replica contracts.

The Home contract will no longer keep a queue of merkle roots. Instead, upon calls to an external function snapshot, it will store a mapping(root -> leaf index).

The updater will wait the appropriate confirmation time and then sign a commitment to (root, leaf index). Replicas will accept this commitment iff the leaf index is greater than the greatest leaf index that they've already committed.

Updaters are slashable iff they've signed a commitment to a snapshot that is not present in the mapping on Home.

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