-
Notifications
You must be signed in to change notification settings - Fork 792
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
Deprecate eth1
and dummy-eth1
flags
#6566
Conversation
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.
nit
lighthouse/beacon_node/src/config.rs
Lines 285 to 294 in d10e81a
// Always follow the deposit contract when there is an execution endpoint. | |
// | |
// This is wasteful for non-staking nodes as they have no need to process deposit contract | |
// logs and build an "eth1" cache. The alternative is to explicitly require the `--eth1` or | |
// `--staking` flags, however that poses a risk to stakers since they cannot produce blocks | |
// without "eth1". | |
// | |
// The waste for non-staking nodes is relatively small so we err on the side of safety for | |
// stakers. The merge is already complicated enough. | |
client_config.sync_eth1_chain = true; |
since sync_eth1_chain
is now true
by default, I think this line is redundant. Also the comments about the deprecated --eth-1
flag might no longer be relevant.
EDIT:
also this line here may be redundant
lighthouse/beacon_node/src/config.rs
Line 124 in d10e81a
client_config.sync_eth1_chain = true; |
Nice catch, thanks @eserilev. I've removed that redundant code and also added a |
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.
LGTM!
@mergify queue |
✅ The pull request has been merged automaticallyThe pull request has been merged automatically at c5007ea |
Proposed Changes
Deprecate the following beacon node flags:
--eth1
: No longer required because it is enabled by default. The deposit contract sync can be disabled via a separate flag--disable-deposit-contract-sync
, which has existed since the merge.--dummy-eth1
: Very rarely used and of limited utility.