{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-10-27\n📝 Original message:These nodes are much more likely to just be broken than malicious, but\nwithout any way to diagnose why they are dropping a transaction it's hard\nto find out what's really going on.\n\nAnyway, yes, I need to spend time adding timeouts and all kinds of other\nthings, although of course if the transactions are being rejected due to a\nchange in network rules that won't help either - if the nodes you're\nconnected to are silently eating your transaction, there's no sane UI that\ncan result from that without more explicit error handling.\n\n\nOn Sun, Oct 27, 2013 at 3:39 PM, Luke-Jr \u003cluke at dashjr.org\u003e wrote:\n\n\u003e On Sunday, October 27, 2013 2:32:57 PM Mike Hearn wrote:\n\u003e \u003e Currently bitcoinj gets a small but steady stream of bug reports of the\n\u003e form\n\u003e \u003e \"my transaction did not propagate\". It's flaky because the library picks\n\u003e one\n\u003e \u003e peer to send the transaction to, and then watches it propagate across the\n\u003e \u003e network. But if that selected peer refuses the tx for whatever reason,\n\u003e that\n\u003e \u003e propagation never comes, and there's currently no timeout to make it\n\u003e retry\n\u003e \u003e with a different node.\n\u003e\n\u003e Sounds like the real bug is \"BitcoinJ relies on good/servant behaviour from\n\u003e other nodes\". Don't assume your random node isn't hostile. Handling a peer\n\u003e that doesn't relay your transaction for any reason (including if they lie\n\u003e to\n\u003e you about having done so) should be expected behaviour.\n\u003e\n\u003e Luke\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131027/dfd261cc/attachment.html\u003e"}