From: James Hilliard <james.hilliard1@gmail•com>
To: Pieter Wuille <pieter.wuille@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Issolated Bitcoin Nodes
Date: Thu, 23 Mar 2017 19:31:25 -0500 [thread overview]
Message-ID: <CADvTj4o=_X2OK8YTtRdrY=8tgxg9Km3PBfdPZ=KAFctHk4Ctwg@mail.gmail.com> (raw)
In-Reply-To: <CAPg+sBjrjUFJZnCtmcvZYs_pc4T3YzU_jtK+eZANyGKSLavrXg@mail.gmail.com>
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@lists•linuxfoundation.org> wrote:
> On Thu, Mar 23, 2017 at 3:37 PM, Juan Garavaglia via bitcoin-dev
> <bitcoin-dev@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@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
next prev parent reply other threads:[~2017-03-24 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 22:37 Juan Garavaglia
2017-03-23 23:01 ` Matt Corallo
2017-03-23 23:14 ` Andrew Chow
2017-03-24 3:38 ` Andrew Chow
2017-03-24 0:20 ` Pieter Wuille
2017-03-24 0:31 ` James Hilliard [this message]
2017-03-24 1:58 ` Eric Voskuil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADvTj4o=_X2OK8YTtRdrY=8tgxg9Km3PBfdPZ=KAFctHk4Ctwg@mail.gmail.com' \
--to=james.hilliard1@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pieter.wuille@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox