Layered TxPool Never evicts local transactions and they should be given priority.

[non-fungible-nelson]

Description

As an user, I want my local transactions to live in my mempool indefinitely, regardless of the size of the executable pool.

Acceptance Criteria

• Local designated transactions are long lived and stay in at least the third tier indefinitely
• Local transactions are given priority if they respect block building rules.

[ahamlat]

This may have an impact on memory usage, not use we can keep indefinitely local transactions, we may need to limit the size of the transaction pool to avoid a besu crash or OOM killer event.

[fab-10]

Indeed the txpool is limited in how much memory it can use, so to keep local txs indefinitely the approach we can take is to save the local tx to a disk based layer instead of dropping it.

[non-fungible-nelson]

Hi @fab-10 - slight update to this issue. We should be giving priority to local transactions in block building if they respect otherwise stated block building rules.

[fab-10]

yes I am already taking in account that priority senders have their transactions prioritized

[fab-10]

With this PR #5959 priority senders have their txs included with priority and dropped from the pool after all the others. I think this is already a good intermediate step, since it is possible to tune the size of the txpool to virtually never expire txs from priority senders.

What is remaining to do is the actual overflow to disk of those txs, but I think it could be less priority now