Consider being able to replace one transaction with a higher fee #2334
Labels
priority:low
optional label to track the relative priority of planned items
proposal
item is not yet actionable and is suggesting a change that must first be agreed upon
WS: BestTxs
Reliable and seamless transaction flow
Currently, users have to wait for their txs to be pruned from the mempool before an account can have the option of submitting another transaction. There are a few ways to that we could add the ability to submit more than one tx at once per user, notably cosmos/cosmos-sdk#13009, discussions in #1939, and #1910. In addition to those, it might be useful to include an antehandler and mempool logic that would allow for a transaction to be replaced before it gets pruned if there is a higher gas price for the new transaction.
The text was updated successfully, but these errors were encountered: