marigold-dev / marigold-dev/deku
delay verify hash of snapshot
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Even if we don't verify the hash of a snapshot on time, and do it late, no problem will happen because deku will never get in sync as the published hash on Tezos will not match the hash that is calculated locally after a couple blocks.
Concerning case, the validators list must be checked to ensure that future signatures match.
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
No files, tests, or entry points are named. Locate the snapshot hash verification and validator-list handling, then clarify how delayed verification should work and how future signatures must be checked; done means the intended synchronization behavior and validator-signature safety are covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100