{"type":"rich","version":"1.0","author_name":"npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu","author_url":"https://nostr.ae/npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcu","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2017-03-23\n📝 Original message:I haven't investigated, but you may be seeing segwit-invalid blocks...0.13.0+ nodes will enforce segwit as it activated some time ago on testnet, 0.12.X nodes will not.\n\nOn March 23, 2017 3:37:34 PM PDT, Juan Garavaglia via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003eWe notice some reorgs in Bitcoin testnet, while reorgs in testnet are\n\u003ecommon and may be part of different tests and experiments, it seems the\n\u003eforks are not created by a single user and multiple blocks were mined\n\u003eby different users in each chain.  My first impression was that the\n\u003eproblem was related to network issues but some Bitcoin explorers were\n\u003efollowing one chain while others follow the other one.  Nonetheless,\n\u003ewell established explorers like blocktrail.com or blockr.io were\n\u003efollowing different chains at different heights which led to me to\n\u003ebelieve that it was not a network issue. After some time, a reorg\n\u003eoccurs and it all comes to normal state as a single chain.\n\u003eWe started investigating more and we identified that the fork occurs\n\u003ewith nodes 0.12; in some situations, nodes 0.12 has longer/different\n\u003echains. The blocks in both chains are valid so something must be\n\u003eoccurring in the communication between nodes but not related with the\n\u003enetwork itself.\n\u003eLong story short, when nodes 0.13+ receive blocks from 0.13+ nodes all\n\u003eis ok, and those blocks propagate to older nodes with no issues. But\n\u003ewhen a block tries to be propagated from bitcoind 0.12.+ to newer ones\n\u003ethose blocks are NOT being propagated to the peers with newer versions\n\u003ewhile these newer blocks are being propagated to peers with older\n\u003eversions with no issues.\n\u003eMy conclusion is that we have a backward compatibility issue between\n\u003e0.13.X+ and older versions.\n\u003eThe issue is simple to replicate, first, get latest version of\n\u003ebitcoind, complete the IBD after is at current height, then force it to\n\u003euse exclusively one or more peers of versions 0.12.X and older, and you\n\u003ewill notice that the latest version node will never receive a new\n\u003eblock.\n\u003eProbably some alternative bitcoin implementations act as bridges\n\u003ebetween these two versions and facilitate the chain reorgs.\n\u003eI have not yet found any way where/how it can be used in a malicious\n\u003eway or be exploited by a miner but in theory Bitcoin 0.13.X+ should\n\u003eremain compatible with older ones, but a 0.13+ node may become isolated\n\u003eby 0.12 peers, and there is not notice for the node owner.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170323/f7be920b/attachment.html\u003e"}