Open andll opened 1 year ago
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/core