Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Conversation

@gguoss
Copy link
Contributor

@gguoss gguoss commented May 20, 2019

Thank you for your Pull Request!

Before you submitting, please check that:

  • You added a brief description of the PR, e.g.:
    • What does it do?
    • What important points reviewers should know?
    • Is there something left for follow-up PRs?
  • You labeled the PR with appropriate labels if you have permissions to do so.
  • You mentioned a related issue if this PR related to it, e.g. Fixes #228 or Related #1337.
  • You asked any particular reviewers to review. If you aren't sure, start with GH suggestions.
  • Your PR adheres the style guide
    • In particular, mind the maximal line length.
    • There is no commented code checked in unless necessary.
    • Any panickers have a proof or removed.
  • You bumped the runtime version if there are breaking changes in the runtime.
  • You updated any rustdocs which may have changed

After you've read this notice feel free to remove it.
Thank you!

✄ -----------------------------------------------------------------------------

@gavofyork
Copy link
Member

what bug is this meant to fix?

@gguoss
Copy link
Contributor Author

gguoss commented May 29, 2019

what bug is this meant to fix?

Validator (A, B ).

  • A: AuthorityKey ( authA )
  • B: also set AuthorityKey ( authA), then B can't run a node.

Validator's key will be two same AuthorityKey.

@gavofyork
Copy link
Member

please explain further.

@bkchr
Copy link
Member

bkchr commented Jun 3, 2019

@gguoss ping

@bkchr bkchr added the A5-stale Pull request did not receive any updates in a long time. No review needed at this stage. Close it. label Jun 3, 2019
@gguoss
Copy link
Contributor Author

gguoss commented Jun 3, 2019

Registering the authority node does not require any physical machine to run the node. Because I just need to set my authority key to the existing authority key of the running node. This way I can get dividends as usual.

@gguoss
Copy link
Contributor Author

gguoss commented Jun 3, 2019

Registering the authority node does not require any physical machine to run the node. Because I just need to set my authority key to the existing authority key of the running node. This way I can get dividends as usual.

The reason for doing evil is: A duplicate authority key can be added to the aura consensus.

/// Sets the session key of a validator (function caller) to `key`.
/// This doesn't take effect until the next session.
fn set_key(origin, key: T::SessionKey) {
let who = ensure_signed(origin)?;
Copy link
Member

Choose a reason for hiding this comment

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

it should remove the current entry for NextKeyFor(who) in KeyFilterMap.

@gavofyork
Copy link
Member

so this is to prevent two validators assigning themselves the same session key?

@gguoss
Copy link
Contributor Author

gguoss commented Jun 5, 2019

so this is to prevent two validators assigning themselves the same session key?

yes

@gavofyork
Copy link
Member

This is superseded now.

@gavofyork gavofyork closed this Jun 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

A5-stale Pull request did not receive any updates in a long time. No review needed at this stage. Close it.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants