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