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

Remove feature flags for beta #7509

Closed
terencechain opened this issue Oct 12, 2020 · 5 comments
Closed

Remove feature flags for beta #7509

terencechain opened this issue Oct 12, 2020 · 5 comments
Assignees
Milestone

Comments

@terencechain
Copy link
Member

terencechain commented Oct 12, 2020

This issue tracks the follow of the following + rationales:

@terencechain terencechain self-assigned this Oct 12, 2020
@terencechain
Copy link
Member Author

Questions for @rkapka

Can I delete these two flags?
* disable-finalized-deposits-cache
* enable-eth1-data-majority-vote

@prestonvanloon prestonvanloon added this to the v1.0.0-beta milestone Oct 12, 2020
@rkapka
Copy link
Contributor

rkapka commented Oct 12, 2020

disable-finalized-deposits-cache

Yes

enable-eth1-data-majority-vote

No - please see #7362. It requires an optimization PR that @nisdas is working on. We might be able to invert the flag without the optimization, but it might result in a lot of BlockExists calls, possibly causing many ETH1 block requests if blocks are not present in the cache.

@terencechain
Copy link
Member Author

Questions for @nisdas, can i delete the following flags?

  • enable-att-broadcast-discovery-attempts
  • disable-dynamic-committee-subnets
  • disable-noise

@terencechain
Copy link
Member Author

disable-finalized-deposits-cache was removed in #7533

@kwood
Copy link
Contributor

kwood commented Dec 15, 2020

I'm confused as to why disable-broadcast-slashings was removed? Broadcasting currently removes all incentive to run a slasher, as 100% of the whistleblower reward currently goes to the proposer. The explanation above The node should broadcast slashing by default doesn't really make sense, that already was the default. Is there something else unsafe about not broadcasting slashings?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants