Gregory Maxwell [ARCHIVE] on Nostr: 📅 Original date posted:2013-10-30 📝 Original message:On Sun, Oct 27, 2013 at ...
📅 Original date posted:2013-10-30
📝 Original message:On Sun, Oct 27, 2013 at 7:32 AM, Mike Hearn <mike at plan99.net> wrote:
> I'm really looking forward to this. 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
Actually, we'll probably need to explicitly document that a failure to
reject is by no means a promise to forward.
If a node is using priority queued rate limiting for its relaying then
it might "accept" a transaction from you, but have it fall out of its
memory pool (due to higher priority txn arriving, or getting
restarted, etc.) before it ever gets a chance to send it on to any
other peers.
Finding out that it rejected is still useful information, but even
assuming all nodes are honest and well behaved I don't think you could
count on its absence to be sure of forwarding.
📝 Original message:On Sun, Oct 27, 2013 at 7:32 AM, Mike Hearn <mike at plan99.net> wrote:
> I'm really looking forward to this. 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
Actually, we'll probably need to explicitly document that a failure to
reject is by no means a promise to forward.
If a node is using priority queued rate limiting for its relaying then
it might "accept" a transaction from you, but have it fall out of its
memory pool (due to higher priority txn arriving, or getting
restarted, etc.) before it ever gets a chance to send it on to any
other peers.
Finding out that it rejected is still useful information, but even
assuming all nodes are honest and well behaved I don't think you could
count on its absence to be sure of forwarding.