[DEFUNCT] Post-clustermempool Package RBF

[instagibbs]

How does minrelay fit into this paradigm?

@sipa

Pre-eviction: remove from PKG any chunk whose feerate is below mempoolminfee or below incremental_relay_feerate. [DoS protection]

I think this links back to our conversation yesterday. If you have two same-unit-size txs, A and B, where A is 0-fee, B is 1 fee, and mempoolminfee is 1, then B would be accepted when submitted by itself, but rejected as a package A+B. In this scenario of course, we’re only considering “chunks” since we’re not connecting the package to the mempool clusters.

Once this check is run, we know everything in these chunks “pays for itself”, and can continue on safely, even if A+B ends up with a chunk score less than minrelay.

@sipa

Verification: verify all transactions in PKG using policy/standardness rules, against UTXOs gathered from chain, mempool, and PKG itself.

I assume this is where scripts are being run as well?

@sipa

Addition One by one, add the transactions of PKG to mempool performing consensus validation.

What kind of failures are possible here if any?

I assume TimeToSize is another step we want, after 12.

edit: misunderstood the Q2 scenario, deleted