Flexible service identity rotation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 876
- Forks
- 260
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 157
Description
Came out of #7848.
End goal: rotate identities in live network and distribute them correctly.
Pitfalls, as on top of author's head:
* consensus problem
* putting private keys on ledger is a security downgrade
* keeping them in mem-only needs ordered distribution and has to survive elections
* only primary can do that, as the corresponding public part has to be committed
* has to survive rollbacks
* endorsement chains from one-per-service -> flexible
* snapshot-recovery endorsement lookup
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 reading the originating issue #7848 and tracing the existing service-identity, endorsement-chain, snapshot-recovery, and election-related entry points. No files or tests are named, so the work is not ready to start until the consensus, key-handling, rollback, and distribution design is agreed and concrete acceptance tests are identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100