oasisprotocol / oasisprotocol/oasis-core
scheduler should allow rescheduling of a contract with a new set of not-yet-allocated workers within an epoch
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
if there is a discrepancy on a committee, and a node is found to be misbehaving, one of the consequences of that consensus finalization is that the committee should dissolve, and the scheduler
should form a new committee for that contract that can pick up the work.
this will add complexity for scheduler, and for compute nodes watching for what committee they're on, but seems needed to make staking work out reasonably.
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 scheduler's committee formation and the compute nodes' committee-tracking logic; the issue names no files or tests. Define how a discrepancy dissolves a contract's committee, how a replacement committee is selected from not-yet-allocated workers within the epoch, and how nodes recognize the new committee.
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
- 32/100