feature: support transactions with unmined inputs in the mempool #8777
Labels
A-mempool
Area: Memory pool transactions
A-rpc
Area: Remote Procedure Call interfaces
C-enhancement
Category: This is an improvement
P-Medium ⚡
Motivation
We don't allow txs with unmined inputs in the mempool. However, supporting them can be useful, in particular for the tex address support which creates two transactions, one z->t and another t->t and submits them sequentially. Currently the second one is rejected in zebrad because of the unknown input since the first one wasn't mined yet.
Specifications
No spec for the mempool 🥲
Complex Code or Requirements
We need to consider that this changes the mempool criteria from "any txs that could be mined on their own" to "a collection of txs that possibly need to be mined together" and check if this has unintended consequences. (In particular I think this will stop #5674 from being implementable)
Testing
Probably trying to submit two txs where the second spends something from the first
Related Work
See discussion in https://discord.com/channels/809218587167293450/809251029673312267/1275193366740602993
The text was updated successfully, but these errors were encountered: