Expand description

Replacing Transactions

When queue limits are reached, a new transaction may replace one already in the pool. The decision whether to reject, replace or retain both is delegated to an implementation of ShouldReplace.

Here we decide based on the sender, the nonce and gas price, and finally on the Readiness of the transactions when comparing them

Structs

Choose whether to replace based on the sender, the score, the Readiness, and finally the Validity of the transactions being compared.