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

BLS: Not a blocker: Sign new key with removed members #322

Open
jeanphilippeD opened this issue Jun 6, 2019 · 0 comments
Open

BLS: Not a blocker: Sign new key with removed members #322

jeanphilippeD opened this issue Jun 6, 2019 · 0 comments

Comments

@jeanphilippeD
Copy link
Contributor

For Future reference.
We don't need to solve this now, I think.

Updating the keys

Whenever the DKG is complete and a new set of keys is generated, the Elders SHALL use their old keys to sign the new aggregate public key - in case of splits, both of the new public keys. This is a requirement of RFC 56. The signature shares SHALL be input into PARSEC, and only once enough shares reach consensus for the signature to be constructed, will the Elders discard their old BLS keys.

The signature along with the new section's public key SHALL be appended to the SectionProofChain in the shared state (see RFC 56).

Removed elder will generally not be faulty, they may be relocated or another older node joined in. How will these removed elder do "The signature shares SHALL be input into PARSEC"?

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

No branches or pull requests

1 participant