{"type":"rich","version":"1.0","author_name":"npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","author_url":"https://nostr.ae/npub1dtr22xd42nv07un2xq0rmtkqkjylgsmexau0anxxafa9xmmn2ncshu7wrs","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-10-27\n📝 Original message:On Sunday, October 27, 2013 2:32:57 PM Mike Hearn wrote:\n\u003e Currently bitcoinj gets a small but steady stream of bug reports of the form\n\u003e \"my transaction did not propagate\". It's flaky because the library picks one\n\u003e peer to send the transaction to, and then watches it propagate across the\n\u003e network. But if that selected peer refuses the tx for whatever reason, that\n\u003e propagation never comes, and there's currently no timeout to make it retry\n\u003e with a different node.\n\nSounds like the real bug is \"BitcoinJ relies on good/servant behaviour from \nother nodes\". Don't assume your random node isn't hostile. Handling a peer \nthat doesn't relay your transaction for any reason (including if they lie to \nyou about having done so) should be expected behaviour.\n\nLuke"}