Who here has set their mempool max size larger than the default (300MB)? Why?
Are mining pool nodes known for running way above the default? Any reliable sources on that?
I had a 1sat/vbyte transaction that was purged from my mempool over 2 weeks ago. Is it safe to assume it was purged everywhere else? If you were me would you bother broadcasting a high fee transaction with the same input to sweep it back?
I run > 300MB, pretty sure miners would too since it makes economical sense to have as full of a picture of pending txs as possible.
if you don't care about urgency of the tx I'd just rebroadcast it in a while
i tried that for awhile. cpu load was getting way up there, lightning crashing, ssh responsiveness slowing to crawl, requiring daily reboot of node. increasing zram didnt help. searched web, found sthg suggesting mempool > 300 could br cause. put back to 300 and problem has largely gone away.
Interesting, I though it wouldn't be an issue if one has RAM to spare but I guess there's extra CPU and network load associated with that.
If you no longer want the transaction to play, then I would create a new transaction to sweep that UTXO. You can never be sure the old transaction is gone and wont be mined in later.
There's no harm in trying to rebroadcast, only one can get through properly anyways and it's much more likely the high fee one will and the other will be discarded as a double spend.
I run my node with 1G mempool, probably increasing soon because I have the resources to spare so might as well!
Even if the transaction has been forgotten by most nodes and doesn't appear anymore on blockexplorers, it is still a valid transaction and might have stayed in the mempool of a node somewhere. So it's better to use one of the inputs in another transaction to invalidate the original, "stuck" transaction otherwise you risk it to be re-broadcast and be confirmed when you already forgot about it.
It's a 5 USD tx so at this point I think I would spend it all on fees on rebroadcasting 😂😂😂
