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

cmd/geth: rename --whitelist to --eth.requiredblocks #24505

Merged
merged 3 commits into from
Mar 15, 2022

Conversation

ryanschneider
Copy link
Contributor

For awhile now I've wanted to rename the "whitelist" option I introduced in #18028 to something both more descriptive (the current flag does not convey what is being whitelisted) and more inclusive.

IMO --peer.requiredblocks is much more self-documenting, though I'm totally open to having a discussion around other argument names (and will make the required changes to this PR if we decide on a different name).

@fjl
Copy link
Contributor

fjl commented Mar 6, 2022

requiredblocks is a very good name. I don't really agree with the peer. prefix because we don't have any other flag like that.

@ryanschneider
Copy link
Contributor Author

ryanschneider commented Mar 6, 2022 via email

@holiman
Copy link
Contributor

holiman commented Mar 9, 2022

I think it's good to have peer in there -- because the current implementation just 'shields' it on the peer-level, not in any deeper level. E.g. if a peer lies in the initial checks, it can still serve us those blocks.
However, one could argue that the peer-part is an implementation detail, and the 'intention' is to require certain hashes.

@fjl
Copy link
Contributor

fjl commented Mar 9, 2022

I just want something other than peer. as prefix because it's getting a bit out of hand with those flag prefixes. If we invent a new one for every flag, the value of the prefix system is lost.

@holiman
Copy link
Contributor

holiman commented Mar 15, 2022

Yeah I'm fine with skipping the peer. prefix

@fjl
Copy link
Contributor

fjl commented Mar 15, 2022

We have now settled on --eth.requiredblocks.

@fjl fjl changed the title cmd, eth: Rename whitelist argument to peer.requiredblocks cmd/geth: rename --whitelist to --eth.requiredblocks Mar 15, 2022
@fjl fjl merged commit dbfd397 into ethereum:master Mar 15, 2022
@fjl fjl added this to the 1.10.17 milestone Mar 15, 2022
sidhujag pushed a commit to syscoin/go-ethereum that referenced this pull request Mar 16, 2022
* cmd, eth: Rename whitelist argument to peer.requiredblocks

* eth/ethconfig: document PeerRequiredBlocks better

* cmd/utils: rename new flag to --eth.requiredblocks

Co-authored-by: Felix Lange <fjl@twurst.com>
JacekGlen pushed a commit to JacekGlen/go-ethereum that referenced this pull request May 26, 2022
* cmd, eth: Rename whitelist argument to peer.requiredblocks

* eth/ethconfig: document PeerRequiredBlocks better

* cmd/utils: rename new flag to --eth.requiredblocks

Co-authored-by: Felix Lange <fjl@twurst.com>
cp-wjhan pushed a commit to cp-yoonjin/go-wemix that referenced this pull request Nov 16, 2022
* cmd, eth: Rename whitelist argument to peer.requiredblocks

* eth/ethconfig: document PeerRequiredBlocks better

* cmd/utils: rename new flag to --eth.requiredblocks

Co-authored-by: Felix Lange <fjl@twurst.com>
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

Successfully merging this pull request may close these issues.

3 participants