Friday, November 22, 2024

community – Globally offline node goes on-line however txs that had been broadcast to it whereas off the online should not broadcast when it goes totally on-line


I’ve a Bitcoin Core node that I disconnected from the web whereas protecting it on a hub with a laptop computer. I despatched a transaction to that node from my laptop computer (through a neighborhood Electrum server). Now I put the node totally on-line with the web (after disconnected my laptop computer…) anticipating this one new transaction to get despatched to the Bitcoin community after my node synced up (which took simply seconds, it was offline only some minutes).

Nonetheless: This new Tx did not get broadcast to the community. A mempool explorer related to solely that node confirmed the Tx, however a mempool explorer related to a node on this planet at massive didn’t. Waited quarter-hour.

I needed to go to my node, dump the Tx in hex, then ship it (from that node, totally on-line) through sendrawtransaction earlier than it confirmed up on the community.

(So I assume that is the anticipated conduct. Is it?)

Query: Is there any technique to “kick” my node, when it goes again on-line to the world and is synced once more, to ship its “new” transactions?

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles