From: Pieter Wuille <pieter.wuille@gmail.com>
To: Juan Garavaglia <jg@112bit.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Issolated Bitcoin Nodes
Date: Thu, 23 Mar 2017 17:20:32 -0700 [thread overview]
Message-ID: <CAPg+sBjrjUFJZnCtmcvZYs_pc4T3YzU_jtK+eZANyGKSLavrXg@mail.gmail.com> (raw)
In-Reply-To: <SC1P152MB1648D0F9DF4279C49D755233F53F0@SC1P152MB1648.LAMP152.PROD.OUTLOOK.COM>
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
next prev parent reply other threads:[~2017-03-24 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 22:37 [bitcoin-dev] Issolated Bitcoin Nodes 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 [this message]
2017-03-24 0:31 ` James Hilliard
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=CAPg+sBjrjUFJZnCtmcvZYs_pc4T3YzU_jtK+eZANyGKSLavrXg@mail.gmail.com \
--to=pieter.wuille@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jg@112bit.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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