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.

Sign up for GitHub

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

Jump to bottom

Add key manager policy document submission #2516

Closed
kostko opened this issue Jan 6, 2020 · 2 comments
Closed

Add key manager policy document submission #2516

kostko opened this issue Jan 6, 2020 · 2 comments
Assignees
@Yawning
Labels
c:consensus/cometbft Category: CometBFT c:key management Category: key management

Comments

@kostko
Copy link
Member

kostko commented Jan 6, 2020

As noted in #1846 we need to add key manager policy document submission to the consensus layer in order to support upgrades without going through a dump/restore cycle.
@kostko kostko added c:key management Category: key management c:consensus/cometbft Category: CometBFT labels Jan 6, 2020
@kostko kostko mentioned this issue Jan 6, 2020
Closed
@Yawning
Copy link
Contributor

Yawning commented Jan 6, 2020

This needs policy decisions about who can submit the new policy document, and if end-users can run their own key manager instance for their own runtimes, how the consensus layer is supposed to enforce policy signature validation.

@kostko kostko mentioned this issue Feb 4, 2020
Closed
15 tasks
@tjanez
Copy link
Member

tjanez commented Feb 6, 2020

This has been implemented in #2636.

@tjanez tjanez closed this as completed Feb 6, 2020
@kostko kostko mentioned this issue Apr 13, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Yawning Yawning

Labels
c:consensus/cometbft Category: CometBFT c:key management Category: key management
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@kostko @tjanez @Yawning