The question is, why would it take one or more days for the first TX to confirm? If several full nodes of Charlie are unable to see both TXs, then Charlie needs to learn how to set fee relay, purge limit etc. Or maybe mempool.space has problems? Or they might have been a target of an eclipse attack, who knows.
If this has already happened, better to share TXids.
Topic: transactions and their distribution via mempools (Read 53 times)
The difference in the mempool size settings can be one of the possible reasons why it isn't visible or visible after a long delay when the fee of the transaction is way lower than the purging rate which means the second TX is queue far away from the tip and nodes uses default mempool size won't relay that transaction to other nodes.
Hi Findingnemo and thanks for your kind feedback. So far I see, both nodes show similar -better said- same settings for their mempool:
Quote
mempoolminfee": 0.00001000,
"maxmempool": 300000000,
"minrelaytxfee": 0.00001000,
"maxmempool": 300000000,
"minrelaytxfee": 0.00001000,
what still puzzles me, that both transactions were initiiated on the same machine but have different effect. Looking forward to more comments, thanks to everyone.
Bob uses a pruned full-node, Charlie an archived full-node with -txindex and neither of them mines blocks.
The difference in the mempool size settings can be one of the possible reasons why it isn't visible or visible after a long delay when the fee of the transaction is way lower than the purging rate which means the second TX is queue far away from the tip and nodes uses default mempool size won't relay that transaction to other nodes.
Other reasons could be network latency but it can be the reason here because mostly it will be delayed a couple of minutes not 2 hours like you said.
Anyway, let's wait for the experts @o_e_l_e_o and @nc50lc who can provide an answer with a clear explanation.
Hello forum,
Bob has made a transaction in bitcoin core. The TXID was immediately visible in https://mempool.space
Bob created another transaction on another day. The TXID was not visible in mempool.space even after several minutes. Only after about 2 hours did the TXID appear there.
Bitcoin core displayed both transactions immediately in the dashboard. Bob finds both transactions in the mempool of its bitcoin core installation and can view its details.
What are the possible reasons why the second transaction only appeared in the mempool hours later? Bitcoin core was continuously connected to the Internet, no connection problems or other warnings/errors in the log.
Charlie operates several full-nodes across the globe. Bob has asked Charlie to give him info on whether Charlie's nodes know these TXIDs. So Charlie also executed the commands shown above. Charlie could not detect either transaction in his mempool.
I would be interested to know what the usual route and process chain of the mempool looks like once a user creates a transaction on his local Bitcoin core. Bob uses a pruned full-node, Charlie an archived full-node with -txindex and neither of them mines blocks.
Who can explain how this process chain works in detail or point me to helpful help pages?
Many thanks
citb0in
Bob has made a transaction in bitcoin core. The TXID was immediately visible in https://mempool.space
Bob created another transaction on another day. The TXID was not visible in mempool.space even after several minutes. Only after about 2 hours did the TXID appear there.
Bitcoin core displayed both transactions immediately in the dashboard. Bob finds both transactions in the mempool of its bitcoin core installation and can view its details.
Quote
bitcoin-cli getrawmempool |grep
bitcoin-cli getrawmempool |grep
bitcoin-cli getmempoolentry
bitcoin-cli getmempoolentry
bitcoin-cli getrawmempool |grep
bitcoin-cli getmempoolentry
bitcoin-cli getmempoolentry
What are the possible reasons why the second transaction only appeared in the mempool hours later? Bitcoin core was continuously connected to the Internet, no connection problems or other warnings/errors in the log.
Charlie operates several full-nodes across the globe. Bob has asked Charlie to give him info on whether Charlie's nodes know these TXIDs. So Charlie also executed the commands shown above. Charlie could not detect either transaction in his mempool.
I would be interested to know what the usual route and process chain of the mempool looks like once a user creates a transaction on his local Bitcoin core. Bob uses a pruned full-node, Charlie an archived full-node with -txindex and neither of them mines blocks.
Who can explain how this process chain works in detail or point me to helpful help pages?
Many thanks
citb0in
Jump to: