CodeChain-io / CodeChain-io/foundry
Handle invalid transactions.
Open
- Dominant language
- Rust
- Stars
- 36
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
We have no proper rule for transactions that are tested to be valid by TxSorter, but not accepted by the actual owner module.
They will just reside in the mempool forever, in current implementation.
Contributor guide
Research direction
Start by tracing the transaction path from TxSorter through the owner module and into the mempool. Determine the expected handling for transactions that pass TxSorter but are rejected by the owner module, then define completion through tests showing that such transactions no longer remain in the mempool indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100