Quote from: PepeLapiu on May 20, 2025, 07:00:28 AM

Quote from: nc50lc on May 19, 2025, 04:26:51 AM

It would be best if you can provide actual examples of those past transactions and hopefully, mempool.space still logged its RBF history.

I looked up some of my old tx's from 2 years ago. Doesn't look like mempool.space logs in RBF history that far back.

That's unfortunate, it would've cleared whatever misunderstanding with the previous batch transactions that you used to do.
Since it's not about the fee rate, it has to be calculated precisely from the mentioned values.
There's not even a fee rate in the transaction data, it's calculated by the client (Electrum) on-the-fly based from its size and left-over amount.

One possible case based from the statement above: since it's automated, it might had been failing to broadcast the first few batch txns due to the low additional fee and saved as "local transaction".
The last batching transaction that had high fee caused those to be batched with enough fee. (since Electrum includes local transactions with it)
And since the local transactions aren't in any node's mempool, only the first transaction will subject to RBF's rule.

But since we have no data to analyze, the query can't be resolved.
Just take note that Electrum implemented RBF based from its unchanged standard and falling to do so will cause the transaction to be rejected by nodes.