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

[Merged by Bors] - Strict slashing protection by default #1750

Closed
wants to merge 4 commits into from

Conversation

michaelsproul
Copy link
Member

Proposed Changes

Replace --strict-slashing-protection by --init-slashing-protection and remove mentions of --auto-register

@michaelsproul michaelsproul added ready-for-review The code is ready for review v0.3.0 For inclusion in v0.3.0 labels Oct 9, 2020
@michaelsproul
Copy link
Member Author

Ready for review.

Now includes a tasty fail-fast feature that causes the VC to bail out early if the slashing protection database is misconfigured.

🤞 that all the tests pass

Copy link
Member

@paulhauner paulhauner 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, only one question.

@@ -32,8 +32,8 @@ pub struct Config {
pub delete_lockfiles: bool,
/// If true, don't scan the validators dir for new keystores.
pub disable_auto_discover: bool,
/// If true, don't re-register existing validators in definitions.yml for slashing protection.
pub strict_slashing_protection: bool,
/// If true, re-register existing validators in definitions.yml for slashing protection.
Copy link
Member

Choose a reason for hiding this comment

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

Does this also register validators that didn't exist originally? Just checking this is worded accurately.

Copy link
Member Author

Choose a reason for hiding this comment

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

It's a little bit clunky, but I think it will register all validators from the validator definitions YAML, I'll earmark it for improvement in a subsequent PR, seeing as we're tight for time

@michaelsproul
Copy link
Member Author

Batch merging with #1743

bors r+

bors bot pushed a commit that referenced this pull request Oct 9, 2020
## Proposed Changes

Replace `--strict-slashing-protection` by `--init-slashing-protection` and remove mentions of `--auto-register`
@bors bors bot changed the title Strict slashing protection by default [Merged by Bors] - Strict slashing protection by default Oct 9, 2020
@bors bors bot closed this Oct 9, 2020
@michaelsproul michaelsproul deleted the init-slashing-protection branch October 9, 2020 03:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-review The code is ready for review v0.3.0 For inclusion in v0.3.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants