Luke-Jr [ARCHIVE] on Nostr: 📅 Original date posted:2013-10-27 📝 Original message:On Sunday, October 27, ...
📅 Original date posted:2013-10-27
📝 Original message:On Sunday, October 27, 2013 2:32:57 PM Mike Hearn wrote:
> Currently bitcoinj gets a small but steady stream of bug reports of the form
> "my transaction did not propagate". It's flaky because the library picks one
> peer to send the transaction to, and then watches it propagate across the
> network. But if that selected peer refuses the tx for whatever reason, that
> propagation never comes, and there's currently no timeout to make it retry
> with a different node.
Sounds like the real bug is "BitcoinJ relies on good/servant behaviour from
other nodes". Don't assume your random node isn't hostile. Handling a peer
that doesn't relay your transaction for any reason (including if they lie to
you about having done so) should be expected behaviour.
Luke
📝 Original message:On Sunday, October 27, 2013 2:32:57 PM Mike Hearn wrote:
> Currently bitcoinj gets a small but steady stream of bug reports of the form
> "my transaction did not propagate". It's flaky because the library picks one
> peer to send the transaction to, and then watches it propagate across the
> network. But if that selected peer refuses the tx for whatever reason, that
> propagation never comes, and there's currently no timeout to make it retry
> with a different node.
Sounds like the real bug is "BitcoinJ relies on good/servant behaviour from
other nodes". Don't assume your random node isn't hostile. Handling a peer
that doesn't relay your transaction for any reason (including if they lie to
you about having done so) should be expected behaviour.
Luke