marigold-dev / marigold-dev/deku
document usage of produce-block and sign-block
Open
Nobody has claimed this yet.
backlog
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
## Genesis
As `produce-block` requires a state.bin you need to run a node. After this it should be a matter of pointing out to the state.bin.
After the block is produced it will generate a hash, with this hash you can call `sign-block`. If 2/3 sign a block it gets merged
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 locating the documentation or command entry points for `produce-block` and `sign-block`. Document that `produce-block` requires a running node and `state.bin`, then explain how the produced block hash is passed to `sign-block` and when the block is merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- cli, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100