marigold-dev / marigold-dev/deku
Chain stops if nodes' clocks get out of sync
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
@EduardoRFS and I have discovered in issue during testing where nodes seem to get out of sync with each other and start proposing mutually unsignable blocks, which halts the chain's progress.
We have a hyptothesis that it's related to our main-chain operations - we suspect that operations from Taquito are some how coming out of order.
The bug rarely occurs when using the start script (we suspect this is because the nodes are started at exactly the same time), but seems to occur more frequently if starting the nodes by hand (where the delay between starting each node is longer).
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 reproducing the failure with nodes launched manually at different times, then compare it with the start script. Investigate whether Taquito main-chain operations arrive out of order; done means staggered node startup no longer produces mutually unsignable blocks or halts chain progress.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100