EVM/node: bypass tx container (pool or queue) when forwarding tx
Checklist
- [ ] Provide automatic testing.
- [ ] Add an item in the changelog
What
This MR get rids of the forward mode of the tx_pool. The forward mode of the TX_pool was added to forward as soon as received transaction to the upstream node. There is a possibility to get rid of that by forwarding txs as soon as receiving them.
Also for the RPC mode, when the tx_container is not activated (i.e. private_rpc_endpoint) is defined then also forward keys RPC to the local r/w node : find_transaction_by_hash get_transaction_count`.
Why
To simplify the use of the tx_queue by the proxy and the rpc mode, in following MRs and to have a more predictable behavior for RPCs.
How
Add a first class module to services.dispatch_request that wraps the tx containers logic.
Manually testing the MR
This si a NOOP operationnaly, CI should be green
Summary by CodeRabbit
-
New Features
- Introduced new API endpoints for querying Ethereum transaction counts and fetching transaction details by hash.
-
Refactor
- Consolidated transaction management across components for improved modularity, error handling, and configurability.
- Streamlined the integration between transaction processing and RPC server interactions.