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

Prune old Bridge pool merkle trees #2110

Closed
Tracked by #2023
sug0 opened this issue Nov 7, 2023 · 0 comments · Fixed by #2206
Closed
Tracked by #2023

Prune old Bridge pool merkle trees #2110

sug0 opened this issue Nov 7, 2023 · 0 comments · Fixed by #2206
Labels
enhancement New feature or request ethereum-bridge has-a-pr The issue has been solved by a PR that has yet to be merged

Comments

@sug0
Copy link
Collaborator

sug0 commented Nov 7, 2023

we might be able to withgo storing multiple bridge pool merkle trees, as well. we only need to keep trees from the latest root that has been signed with a quorum signature onward. so, suppose the latest merkle tree nonce is $5$, but the latest signed root's nonce is $3$; then, we can delete all the trees signed with a nonce of $0$ through $2$, whilst upholding the liveness of the bridge.

Originally posted by @sug0 in #2043 (comment)

@sug0 sug0 added enhancement New feature or request ethereum-bridge labels Nov 7, 2023
@sug0 sug0 added the has-a-pr The issue has been solved by a PR that has yet to be merged label Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ethereum-bridge has-a-pr The issue has been solved by a PR that has yet to be merged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant