Date: Wed, 19 Aug 2015 16:23:23 -0700
From: Peter Todd <pete@petertodd.org>
To: Adam Back <adam@cypherspace.org>
Message-ID: <20150819232323.GE27857@muck>
References: <55D1167B.1060107@gmail.com>
	<CAEX2NSfaPv0g07hfT31voGWX05Z6uaBsZOjhMkOwBr4mdHbPQw@mail.gmail.com>
	<55D124D7.4050209@gmail.com>
	<61AD0CE6-014E-44E2-B9C7-00B35D2E09CC@petertodd.org>
	<CAEX2NSeAgrN877zAVDrk_J+7EVDPagt8u4+HB7hDMVMPwS6Zng@mail.gmail.com>
	<F99FFEE6-6D10-480D-B96D-960B84092C88@gmail.com>
	<CABm2gDoEVmqiOpPcf1wUsNt4pmU=oVawq2-0YwrEjm1W1YBmeg@mail.gmail.com>
	<55D4A3BD.2060706@sky-ip.org>
	<CABm2gDo-jgE7ow5eNTp70YwQKNL3OfDMT=uU9H6G09MS_J2k-Q@mail.gmail.com>
	<CALqxMTGUtRm4nW1TTVwr0i+NYD93f-i9d9=nkJnPQdPEw8Zy0g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="l+goss899txtYvYf"
Content-Disposition: inline
In-Reply-To: <CALqxMTGUtRm4nW1TTVwr0i+NYD93f-i9d9=nkJnPQdPEw8Zy0g@mail.gmail.com>
Cc: Cameron Garnham via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
Precedence: list


--l+goss899txtYvYf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Aug 19, 2015 at 03:45:48PM -0700, Adam Back via bitcoin-dev wrote:
> Wouldnt the experience for SPV nodes be chaotic?  If the full nodes
> are 50:50 XT and bitcoin core, then SPV clients would connect at
> random and because XT and core will diverge immediately after
> activation.

Actually not necessarily!

To my knowledge there aren't any SPV implementations that do address
caching; they all use the peer servers in a centralized fashion every
time they connect. If those peer servers are setup to only return nodes
on one side of the fork or the other, that's all they'll connect too and
they'll never see another chain.

--=20
'peter'[:-1]@petertodd.org
00000000000000000402fe6fb9ad613c93e12bddfc6ec02a2bd92f002050594d

--l+goss899txtYvYf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJV1Q/oXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwNDAyZmU2ZmI5YWQ2MTNjOTNlMTJiZGRmYzZlYzAyYTJi
ZDkyZjAwMjA1MDU5NGQvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udyPqgf+NUpK0nadAMo9aYiYPfT0RGHR
bitQdh1Gr1bmkbg2Hx0SCa4GI5BzwwHP2zeNnnrePp+ixpXRIIk6E0oMBs49TXo/
1hBTs/wJ+vD7kOmqjQVYV7W0X2GDX4s6kF+05wEx7katv7BTtHDIjaCcGMgvTvfq
geswmJ/3j4szxxHLih6Z1QJf+iB6OOPPdP8m7BKyOC9K944+i5Z5LM196+eofvEL
JXsvgALjiDu0nKifABM7UZaYEv5MlOo41GJ6x/dSWK0DCOJ3e6SfbQvl3Jghk8Eg
NAFcf9KlnX/NTyWVubPGYJUtQvVma6PIHwftgnzN1qENojJ8e2+Xb132NY3oQQ==
=7cJp
-----END PGP SIGNATURE-----

--l+goss899txtYvYf--