marigold-dev / marigold-dev/deku
Move async state hashing into consensus library
Open
Nobody has claimed this yet.
backlog
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
We should define the logic for async state hashing in the new consensus library (#675):
- async state hashing is trigger on a separate thread via an Effect (probably uses `Lwt_domain`)
- async state hashing finishes and triggers a Consensus event.
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 issue #675 and the new consensus library to locate the existing state-hashing and event-flow entry points. Check how Effects and Lwt_domain are used for work on a separate thread. Done means async state hashing is defined in the consensus library, completes, and triggers a Consensus event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100