Problem: Transaction ordering #84
Description
Current issue:
- When an account broadcast many transactions at a time (with nonce increament), there is high chance that most of the txs will be failed to execute due to nonce check, that caused by un-ordered by sequence when executing txs.
- When trace transaction, the data is not accurate if there is Cosmos Txs before or in the middle of the txs that modified store and trace tx can not simulate that.
That caused by the reason that current Tendermint/CometBFT version we are using, does not support re-order the transactions.
Possible solution:
- ABCI 2.0. As I understood,
PrepareProposalwould help us with the ability to modify the txs bytes, that we can used to re-order the txs as the following orders:- EVM txs first
- Within EVM txs, follow Ethereum's order.
- Any others if applicable