📅 Original date posted:2017-03-23
📝 Original message:There were bridge nodes being run on testnet at one point to prevent
forks https://github.com/jl2012/bitcoin/commit/9717d856e72baa939d4b273f0a56e6009978e11b
On Thu, Mar 23, 2017 at 7:20 PM, Pieter Wuille via bitcoin-dev
<bitcoin-dev at lists.linuxfoundation.org> wrote:
> On Thu, Mar 23, 2017 at 3:37 PM, Juan Garavaglia via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>> Long story short, when nodes 0.13+ receive blocks from 0.13+ nodes all is
>> ok, and those blocks propagate to older nodes with no issues. But when a
>> block tries to be propagated from bitcoind 0.12.+ to newer ones those blocks
>> are NOT being propagated to the peers with newer versions while these newer
>> blocks are being propagated to peers with older versions with no issues.
>>
>> My conclusion is that we have a backward compatibility issue between 0.13.X+
>> and older versions.
>
> Hello Juan,
>
> this is expected behaviour. Nodes with segwit active only download
> blocks from other segwit peers, as old peers cannot provide the
> witness data they need to verify the blocks.
>
> --
> Pieter
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
James Hilliard [ARCHIVE] /
npub10r…kgk2d
2023-06-07 17:57:43
in reply to nevent1q…2uvj
Author Public Key
npub10r9d6edmnrljk59wsf06zqp494l3qtjpa3w245hy6t5euqxlzw2qdkgk2dSeen on
wss://relay.nostr.bandPublished at
2023-06-07 17:57:43Event JSON
{
"id": "cfbc7589acb711de147f2b0b00fb388f736958a9acb4acf3900be4787e45adf9",
"pubkey": "78cadd65bb98ff2b50ae825fa100352d7f102e41ec5caad2e4d2e99e00df1394",
"created_at": 1686160663,
"kind": 1,
"tags": [
[
"e",
"a77672c0bec72cf6c744f58f911e3b4b495fa3bf41bc9de349fa803c65967858",
"",
"root"
],
[
"e",
"bdf981eb0c42e42230872c69a36203c5dbd8ab6907d79fdd1ef98249e1e2360a",
"",
"reply"
],
[
"p",
"5cb21bf5d7f25a9d46879713cbd32433bbc10e40ef813a3c28fe7355f49854d6"
]
],
"content": "📅 Original date posted:2017-03-23\n📝 Original message:There were bridge nodes being run on testnet at one point to prevent\nforks https://github.com/jl2012/bitcoin/commit/9717d856e72baa939d4b273f0a56e6009978e11b\n\nOn Thu, Mar 23, 2017 at 7:20 PM, Pieter Wuille via bitcoin-dev\n\u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e On Thu, Mar 23, 2017 at 3:37 PM, Juan Garavaglia via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e Long story short, when nodes 0.13+ receive blocks from 0.13+ nodes all is\n\u003e\u003e ok, and those blocks propagate to older nodes with no issues. But when a\n\u003e\u003e block tries to be propagated from bitcoind 0.12.+ to newer ones those blocks\n\u003e\u003e are NOT being propagated to the peers with newer versions while these newer\n\u003e\u003e blocks are being propagated to peers with older versions with no issues.\n\u003e\u003e\n\u003e\u003e My conclusion is that we have a backward compatibility issue between 0.13.X+\n\u003e\u003e and older versions.\n\u003e\n\u003e Hello Juan,\n\u003e\n\u003e this is expected behaviour. Nodes with segwit active only download\n\u003e blocks from other segwit peers, as old peers cannot provide the\n\u003e witness data they need to verify the blocks.\n\u003e\n\u003e --\n\u003e Pieter\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev",
"sig": "db44f3d060532011ac060d9248dd6c4b468764357d6ccd7f26302a503c877851d7ad55b55973b0cf79c2dae213eb9916be10190bfe0c62f14e52e12a7ac8db63"
}