ETH/AVAX Concurrent Tx Lookup
We've experimented with using daemons on longer links, and in particular this causes issues in ETH/AVAX due to head of line blocking on sequential lookups for TXs in a block, causing them to fall behind enough to rack up intermittent slash. This updates Avalanche and Ethereum clients to perform concurrent lookups for transaction receipts within a block.
Based on my understanding the following are ok, but seeking confirmation:
- Out of order deletes from the signer/meta cache are ok since the same tx hash shouldn't occur multiple times in a block
- Non-deterministic order on the inbound
TxArray
is alright