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

[orchestrator] [Future request] Populate key pairs #5

Open
andll opened this issue Jul 11, 2023 · 2 comments
Open

[orchestrator] [Future request] Populate key pairs #5

andll opened this issue Jul 11, 2023 · 2 comments

Comments

@andll
Copy link
Collaborator

andll commented Jul 11, 2023

Core::signer and Committee::authorities are currently populated with a dummy keypair even for production. We want to generate unique keys and pass it to committee/core

@asonnino
Copy link
Collaborator

This is not strictly related to the orchestrator, right? It is more of a genesis issue where we should be able to accommodate both benchmark and production keys

@andll
Copy link
Collaborator Author

andll commented Jul 13, 2023

I am not sure what production genesis ceremony will look like, but ideally we want to use different keys in test setup, just in case it will surface any issues (unlikely, but still possible)

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

2 participants