pull down to refresh
It has always been the case that transactions are not final until multiple confs. The protocol never gives any assurances of confirmation for any transaction in the mempool. Relying on 0conf will also expose you to purge risk, like we saw last week.
For example, f2pool mined two full-rbf double spends earlier today. I don't think they're running with mempoolfullrbf enabled. I think they just restarted a node or something similar and cleared their mempool.
deleted by author
Other than transactions relevant to your wallet, no. Bitcoin Core doesn't need that information for normal operation as double spends of mempool transactions are perfectly normal.
This is how you say it without the strawman.
My node, my policy.
If you disagree, keep the first seen policy.
Non sequitur, but anyway.
Cool! Do your thing.
"the delusion that you cannot double spend on the mempool."
Strawman