Topic: Mempool Memory (Read 260 times)
If there's anyone with more technical knowledge that can lend any useful information to any of the above questions, I'd be grateful to learn something new. It seems this post very much runs the risk of being burried into oblivion on this busy board.
During this time of increased network congestion (seems more the norm now than ever) and the backlog of unconfirmed transactions, I'm trying to figure out how the mempool retains unconfirmed transactions. It seems that unconfirmed transactions used to drop out after a time, in my experience, around a week of being unconfirmed. . Recently, I had a transaction remain unconfirmed for 6 weeks, and it just recently confirmed as the backlog of unconfirmed transactions in the mempool was mostly eliminated. (It's currently rebuilding though).
So a couple questions:
1) has something changed recently to cause the mempool to retain unconfirmed transactions longer than it used to?
2) I'm assuming the mempool is decentralized, so what exactly determines what unconfirmed transactions are in or out?
My simplistic understanding is that my wallet broadcasts my transaction which is picked up by a node (all nodes?), and the node broadcasts it until it is bundled into a block, and unconfirmed transactions are generally sorted by highest fee/byte. Please correct anywhere this is incorrect. But are the collective nodes what constitute the mempool then, or is the mempool distinct from the nodes? And along that line, can we force the mempool to forget unconfirmed transactions of a certain age?
So a couple questions:
1) has something changed recently to cause the mempool to retain unconfirmed transactions longer than it used to?
2) I'm assuming the mempool is decentralized, so what exactly determines what unconfirmed transactions are in or out?
My simplistic understanding is that my wallet broadcasts my transaction which is picked up by a node (all nodes?), and the node broadcasts it until it is bundled into a block, and unconfirmed transactions are generally sorted by highest fee/byte. Please correct anywhere this is incorrect. But are the collective nodes what constitute the mempool then, or is the mempool distinct from the nodes? And along that line, can we force the mempool to forget unconfirmed transactions of a certain age?
Jump to: