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

Add Network Flags to Slashing Protection Export Command #9907

Merged
merged 1 commit into from
Nov 15, 2021

Conversation

rauljordan
Copy link
Contributor

@rauljordan rauljordan commented Nov 15, 2021

Fixes #9905 by adding the --prater, --pyrmont, --mainnet flags to slashing protection exports. A user was mentioning that adding --prater to the slashing protection export command still logs "Running on Ethereum consensus mainnet" instead of prater. This is scary to a user.

Copy link
Contributor

@potuz potuz left a comment

Choose a reason for hiding this comment

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

LGTM, can´t believe this was the issue with exports.

Copy link
Member

@prestonvanloon prestonvanloon left a comment

Choose a reason for hiding this comment

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

lgtm, i wish there was a better way to handle this though

@prylabs-bulldozer prylabs-bulldozer bot merged commit b5ca09b into develop Nov 15, 2021
@delete-merged-branch delete-merged-branch bot deleted the slashing-protection-right-network branch November 15, 2021 19:21
@rauljordan
Copy link
Contributor Author

rauljordan commented Nov 15, 2021

@potuz issue with exports is different. The user was storing the validator.db in one directory and the wallet keystores in another. They were then trying to export from the wallet directory, which in turn did not contain their validator.db. Addressing that now in another PR

lgtm, i wish there was a better way to handle this though

There should be a way to create a "flag registration hook" or some higher-order function that applies common flags to all Prysm commands. I'll create a tracking issue for this one,

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.

Slashing protection export gives wrong warn-message
3 participants