oasisprotocol / oasisprotocol/oasis-core
Support single-node key manager upgrades
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Currently the upgrade procedure is such that a new key manager enclave must always replicate from a different node. It should be possible to perform the upgrade within the same node, talking to the old enclave.
Given that on-chain registration of nodes and enclaves is required for replication, this may require some consensus-breaking changes.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing upgrade procedure and the on-chain registration and replication requirements for nodes and enclaves. Determine how a new key manager enclave can communicate with the old enclave on the same node, and resolve the consensus implications; done means the single-node upgrade path works without replication from another node.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100