marigold-dev / marigold-dev/deku
Partially signed block
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
A block may contain invalid operations, but not necessarily this block needs to be rejected as that adds latency to the network, another option is to allow signatures over part of a block, and only the part that has enough signatures will be included.
This will happens both in the case of unknown consensus operations or unknown Tezos operations,
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating block validation and signature handling, then clarify how unknown operations, partial signatures, inclusion thresholds, and latency should behave. Done requires an agreed design and tests covering partially signed blocks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100