stacks-network / stacks-network/stacks-core
Cache transactions that exceed cost limits
Open
Nobody has claimed this yet.
mempool
optimization
performance-optimizations
- Dominant language
- Rust
- Stars
- 3.1k
- Forks
- 762
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 76
Description
In Nakamoto, it would be useful to cache transactions that have been attempted and found to exceed the block limits. This would allow the miner to quickly skip those transactions on the next mempool walk.
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 locating Nakamoto’s miner mempool walk and the path that detects transactions exceeding block limits. Trace how those transactions are revisited, then determine the cache’s lifetime and invalidation behavior; done means later walks skip previously rejected transactions without changing handling for transactions that can fit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100