You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
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)
Core::signer
andCommittee::authorities
are currently populated with a dummy keypair even for production. We want to generate unique keys and pass it to committee/coreThe text was updated successfully, but these errors were encountered: