stacks-network / stacks-network/stacks-core
Fix race condition between a block proposal and block responses
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
Currently signers will ignore any block responses received for a block proposal they have never seen. It would be better if block responses included the block being signed/rejected and the receiving signer immediately start processing the received block OR store these orphaned responses on the side and apply them after a block proposal arrives. This is not super important as the system will just propose a new block if not enough rejections/approvals arrive in time from the signers, but it may be worthwhile all the same.
Contributor guide
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 tracing how signers handle block proposals and block responses, focusing on the race where a response arrives before its proposal. The issue presents two possible outcomes—include the block in responses or store orphaned responses—so the desired behavior and completion criteria need to be resolved before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain, distributed-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100