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 client-settings.md #2741

Merged
merged 1 commit into from
Nov 26, 2021
Merged

Conversation

mkalinin
Copy link
Collaborator

Releasing client software with updated parameters and giving a time for users to upgrade their nodes is going to be default strategy to accelerate the Merge in the case of emergency, see the comment here for details.

Therefore, CLI args doesn't increase the speed of the reaction in emergency cases hence supporting them is anymore not a requisite for a client software. This PR proposes to remove the corresponding document from the set of consensus spec docs.

cc @MicahZoltu @karalabe

@mkalinin mkalinin requested a review from djrtwo November 24, 2021 11:09
Copy link
Contributor

@djrtwo djrtwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

Note to readers that TERMINAL_TOTAL_DIFFUCLTY, TERMINAL_BLOCK_HASH, and TERMINAL_BLOCK_HASH_ACTIVATION_EPOCH are still defined but must be overridden in updated configs in releases rather than on the command line

@djrtwo
Copy link
Contributor

djrtwo commented Nov 24, 2021

leaving this up for 24 hours before merging in case other comments

Copy link
Contributor

@MicahZoltu MicahZoltu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From a specification standpoint, I don't think this should be specified so I think removal of this is a good thing. From a recommendation standpoint for the various client I think there is notable value in providing a CLI override flag to their users, especially enterprise users that may have a fairly onerous upgrade process but a fairly simple configuration process.

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.

None yet

3 participants