oasisprotocol / oasisprotocol/oasis-core
Leader fault detection and rotation within primary execution committee
Open
Nobody has claimed this yet.
c:runtime/compute
p:1
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Any worker can act maliciously in an execution committee. The most problematic is the leader, who drives 1. transaction ordering/batching, 2. forwarding to other workers 3. coordinating commit-reveal, 4. storing states to storage.
Any of these steps can be mishandled. We need ways to
- Detect faulty leaders
- Prove the consensus layer of its faults
- Rotate leaders to satisfy liveness
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 reviewing the consensus layer and execution committee components involved in transaction ordering, forwarding, commit-reveal coordination, and state storage. Done means the project has defined and implemented faulty-leader detection, consensus-level fault proof, and leader rotation sufficient for liveness.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100