oasisprotocol / oasisprotocol/oasis-core
security: Split up the node key and allow key rotation etc
Open
Nobody has claimed this yet.
c:breaking/consensus
c:consensus/cometbft
c:key management
c:runtime/compute
c:security
golang
p:1
s:needs adr
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Right now (especially with #1498), each node's NodeKey is used for multiple things, that should likely all be separate, support for expiry, an offline master/subkey type configuration, and rotation.
- The ekiden node signing key.
- The Tendermint (private) validator signing key.
- The Tendermint P2P link key.
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 locating NodeKey and reviewing its uses for the three listed roles, then read the context from issue #1498. Map the requirements for separate keys, expiry, offline master/subkey configuration, and rotation before defining the scope and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100