-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 PeerDAS Feature Flag #13865
Add PeerDAS Feature Flag #13865
Conversation
@@ -254,6 +256,12 @@ func ConfigureBeaconChain(ctx *cli.Context) error { | |||
logEnabled(BlobSaveFsync) | |||
cfg.BlobSaveFsync = true | |||
} | |||
// For the p.o.c we enable it by default. | |||
cfg.EnablePeerDAS = true |
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.
Might want to be careful with this one. Don't merge everything to develop later thinking it's feature-flag gated but forget this line still exists.
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.
Oh yeah definitely, in any case even if we merge to develop a node with this enabled will immediately stall since all the topics are non-existent in mainnet or any of the testnets
What type of PR is this?
Feature
What does this PR do? Why is it needed?
This PR implements a feature flag so that all peer das related changes to core code can be put behind a flag. Doing this allows us to be able to experiment on this in an easier fashion along with making this much simpler to modify for any future forks.
Which issues(s) does this PR fix?
N.A
Other notes for review