-
Notifications
You must be signed in to change notification settings - Fork 207
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
[CIP-50] optional replay protection #1748
[CIP-50] optional replay protection #1748
Conversation
Coverage from tests in coverage: 44.6% of statements across all listed packagescoverage: 54.1% of statements in consensus/istanbul coverage: 44.8% of statements in consensus/istanbul/backend coverage: 0.0% of statements in consensus/istanbul/backend/backendtest coverage: 43.3% of statements in consensus/istanbul/backend/internal/db coverage: 24.1% of statements in consensus/istanbul/backend/internal/enodes coverage: 22.4% of statements in consensus/istanbul/backend/internal/replica coverage: 64.2% of statements in consensus/istanbul/core coverage: 0.0% of statements in consensus/istanbul/proxy coverage: 75.3% of statements in consensus/istanbul/uptime coverage: 100.0% of statements in consensus/istanbul/uptime/store coverage: 51.8% of statements in consensus/istanbul/validator coverage: 79.2% of statements in consensus/istanbul/validator/randomCommentID: 09775b3d7b |
32ddca7
to
192e3c2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Blockchain side LGTM. Will need to update CIP-35 e2e test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update around espresso name in tests
Depends on #1695
Description
Implementation of the CIP 50, that makes the replay protection optional
Related issues
Backwards compatibility
No. Part of the Expresso hard fork