-
Notifications
You must be signed in to change notification settings - Fork 118
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
Add feature flags for backwards compatibility #521
Conversation
Codecov Report
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. @@ Coverage Diff @@
## main #521 +/- ##
==========================================
- Coverage 33.23% 33.19% -0.04%
==========================================
Files 24 24
Lines 5079 5097 +18
==========================================
+ Hits 1688 1692 +4
- Misses 3173 3186 +13
- Partials 218 219 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
📢 Have feedback on the report? Share it here. |
3b1ad6a
to
10010d7
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.
nice!
* Add feature flags for backwards compatibility * improve readability of flags * renaming flags * remove fork schedule checks and flag
📝 Summary
Adds two feature flags to maintain backwards compatibility with older CL clients.
⛱ Motivation and Context
New features were recently added which breaks compatibility with older clients. This PR adds feature flags allowing toggling via env vars to switch between the features:
USE_V2_PUBLISH_BLOCK_ENDPOINT
- this toggles using the v2 endpoint on CL clients to publish blocks. This endpoint includes equivocation checks to prevent equivocation attacks. The latest prysm and lighthouse releases has not been tested thoroughly for the v2 endpoint, so the default for this flag is using the v1 endpoint.📚 References
✅ I have run these commands
make lint
make test-race
go mod tidy
CONTRIBUTING.md