From: Eric Voskuil <eric@voskuil•org>
To: Pieter Wuille <pieter.wuille@gmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>,
Juan Garavaglia <jg@112bit•com>
Subject: Re: [bitcoin-dev] Issolated Bitcoin Nodes
Date: Thu, 23 Mar 2017 18:58:37 -0700 [thread overview]
Message-ID: <cfdd397d-afac-e0c3-b347-558152d7a81b@voskuil.org> (raw)
In-Reply-To: <CAPg+sBjrjUFJZnCtmcvZYs_pc4T3YzU_jtK+eZANyGKSLavrXg@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 03/23/2017 05:20 PM, Pieter Wuille via bitcoin-dev 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.
Juan's statement pertains to incompatibility, not mysterious causation.
Clearly it's a material consideration. Is it an oversight that this is
not documented as an incompatibility in any of the segwit BIPs?
I don't recall any discussion on the importance of segwit bridge
nodes. Is there a plan for bridging mainnet?
e
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBCAAGBQJY1H1AAAoJEDzYwH8LXOFOAk4H/RrJyexvyFKXfY7qC0bGCVwN
2iZ0wR0n/H0Z0qfP5nzDID0RARC3F/KFAAeLTaCIZa5uI0h3MrPbNm7hSi/m0nHJ
mTzfJf0E8g+ETzyDpWjgR25ta6n3VdKp2tnNrY3z/ojnGYBFthpRDWV09K5trX5k
qMyoPDfTP8jVIwihqx3MZLBnfiQKlEjNxCxmnuL7bh37msp6WK+elKudSrDBPiIi
ljQ+u5NyeKWY+qzEzKPShIKnm3wC4K/RiiZIUvz60x6PCHr8OZGTEiKhPLWznVuj
Q9gVtHxFzDpMZbxo4vP4nH+isQgqNa9gQ2E5783OC0/lpxHCoZEsgsD5lTAcp08=
=GyRS
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2017-03-24 1:58 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
2017-03-24 1:58 ` Eric Voskuil [this message]
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=cfdd397d-afac-e0c3-b347-558152d7a81b@voskuil.org \
--to=eric@voskuil$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jg@112bit$(echo .)com \
--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