Problem: transaction ordering

[VictorTrustyDev]

Context

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, PrepareProposal would 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

Problem may occurs with the above solution, need to aware:

• Needed core Cosmos txs might not be able to be executed like IBC messages,...

Expected

[linear]

ENG-2466 Issue 2263

[hanchon]

With ABCI2.0 we can fix it 🚀

[github-actions]

This issue is stale because it has been open 45 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.

[MalteHerrmann]

SDK v0.50 and ABCI++ are on the way

[mikebraver]

Did the latest version available of SDK and ABCI already solved this problem?