marigold-dev / marigold-dev/deku
use index for validators on consensus.mligo
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
## Problem
Currently we rely on the ordering of validators present in the consensus contract to decide who is the next validator, the idea is to have a map from `int -> validator` so that there is no way to commit a mistake and accidentally change the order as happened in the past already.
Contributor guide
No contributing guide indexed for this repository
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 consensus.mligo and trace how the contract currently orders validators and selects the next one. Replace the ordering-dependent representation with an index-to-validator map, and verify that validator selection no longer depends on accidental ordering changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100