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

Signer computes what to sign on its own #1925

Closed
5 tasks done
Tracked by #1777
jpraynaud opened this issue Sep 9, 2024 · 0 comments · Fixed by #1972
Closed
5 tasks done
Tracked by #1777

Signer computes what to sign on its own #1925

jpraynaud opened this issue Sep 9, 2024 · 0 comments · Fixed by #1972
Assignees
Labels
feature 🚀 New implemented feature

Comments

@jpraynaud
Copy link
Member

jpraynaud commented Sep 9, 2024

Why

The signer needs to compute the next message to sign independently and without relying on the pending certificate of the aggregator.

What

Replace the usage of the Pending Certificate in the signer with its own computation of which is the next message to sign.

How

  • Adapt the mechanism of the aggregator to compute the next signed entity type to sign
  • Store the signed entity type signed persistently when it has been successfully (when signature is sent)
  • Prune or keep last 2 epochs in the store?
  • Remove all pending certificate code in the signer
  • Deprecate the /pending-certificate route in OpenAPI
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🚀 New implemented feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants