From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <andrewlecody@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id BB76E409
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Aug 2015 12:29:18 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ob0-f179.google.com (mail-ob0-f179.google.com
	[209.85.214.179])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D769563
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Aug 2015 12:29:17 +0000 (UTC)
Received: by obbhe7 with SMTP id he7so110582562obb.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Mon, 17 Aug 2015 05:29:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:references:in-reply-to:from:date:message-id:subject:to
	:content-type; bh=vG/GMbkFmxVDuC5BV/mcXW23PP7Li5B8/YkPkFhjS30=;
	b=tVpHv70N6jWXC6wvlhANjPdfF2sb+XvCnKT2fzOpkKc4IR4wGigqZHaLX2F65Rh435
	B5mR+6Ni5xrHXkXvdvq5v2pK+/Rf2IKg/yb49NA+kH1mikrBCMK2lTYMgBmaxPvNun4e
	n8O9cq/ho69graIrzITeFQrRDdjv5UenGQwZlro1a7SFcrhPHRbf2HILqEYzFd5KYp2/
	Wn3pzRsMiz1KplQLW1jYaWWxnKVM74b31VwCo6aqHt/ERPYitDArIyODyEWfTmEpvpYZ
	ev7PDNgtxkjZFxS4Zks3lJItSyzKpyyg8MTC11aGKA7BOD/ukbKdJdIXwrjiIpexWz8X
	c8IQ==
X-Received: by 10.182.224.194 with SMTP id re2mr971974obc.24.1439814557273;
	Mon, 17 Aug 2015 05:29:17 -0700 (PDT)
MIME-Version: 1.0
References: <CADWuND3EfO6YO3g4H09_mWhrHC4PX4SZpTTuETiX2PyCxSRCsQ@mail.gmail.com>
	<55D1167B.1060107@gmail.com>
	<CAEX2NSfaPv0g07hfT31voGWX05Z6uaBsZOjhMkOwBr4mdHbPQw@mail.gmail.com>
	<55D124D7.4050209@gmail.com>
	<61AD0CE6-014E-44E2-B9C7-00B35D2E09CC@petertodd.org>
In-Reply-To: <61AD0CE6-014E-44E2-B9C7-00B35D2E09CC@petertodd.org>
From: Andrew LeCody <andrewlecody@gmail.com>
Date: Mon, 17 Aug 2015 12:29:07 +0000
Message-ID: <CAEX2NSeAgrN877zAVDrk_J+7EVDPagt8u4+HB7hDMVMPwS6Zng@mail.gmail.com>
To: Peter Todd <pete@petertodd.org>, Cameron Garnham <da2ce7@gmail.com>, 
	Cameron Garnham via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary=089e013a2afa3a9486051d80f3ef
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Bitcoin XT 0.11A
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Aug 2015 12:29:18 -0000

--089e013a2afa3a9486051d80f3ef
Content-Type: text/plain; charset=UTF-8

Wouldn't that require a fork that lasts for more than 100 blocks?

On Mon, Aug 17, 2015, 01:43 Peter Todd <pete@petertodd.org> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
>
>
> On 16 August 2015 17:03:35 GMT-07:00, Cameron Garnham via bitcoin-dev <
> bitcoin-dev@lists.linuxfoundation.org> wrote:
> >There are a few ways: here is my favorite (for the moment).
> >
> >1. Spam the 8mb blocks with 1 Satoshi outputs to the brainwallet
> >'BitcoinXT'
>
> Even more direct: use coinbase outputs of  XT blocks to create those
> outputs, as they can't by definition be on the Bitcoin chain.
>
> If you can't get those, using coinbase outputs of Bitcoin blocks to create
> "definitely Bitcoin-only" outputs, and then spend the inputs to those
> transactions again on the XT chain. This isn't quite as good, as a big
> reorg on the XT chain could in theory spend them, but it's a close second.
> -----BEGIN PGP SIGNATURE-----
>
> iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV0YIS
> AAoJEMCF8hzn9Lnc47AH/R9EaGaa0xmD7qBODGUwX3SsDde7DMgO4t8X5GQ9uoaq
> qcjdnnvdeXjy5S39QdZFJjlH5bGn+BJy2wIxn0lMciKhEGIFOGeCUsMYEbgnOc03
> cLuyYpxdfXe4Amoxf2mqADgBqkAckf4cX6bMm3XXg+v3XAby2llydIGIydTwGWYq
> 2KwXl9U9zm7UV8b5tJ7WmItCAcZAvTcSoX5SerOmPjjrmLtPTHThj8SfLTGAoWfT
> EXsSGkDBJ/9rJMms56FjciWsXHlB9pYK0a1sxh88PJluebqh99imDisJvATCVp2Z
> kZX1keZ1nyfG45jibgt6dlY97wU0n919SmQz0Tg6g90=
> =OD56
> -----END PGP SIGNATURE-----
>
>

--089e013a2afa3a9486051d80f3ef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Wouldn&#39;t that require a fork that lasts for more than 10=
0 blocks?</p>
<br><div class=3D"gmail_quote"><div dir=3D"ltr">On Mon, Aug 17, 2015, 01:43=
=C2=A0Peter Todd &lt;<a href=3D"mailto:pete@petertodd.org">pete@petertodd.o=
rg</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">-----BEGIN PGP SI=
GNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
<br>
<br>
On 16 August 2015 17:03:35 GMT-07:00, Cameron Garnham via bitcoin-dev &lt;<=
a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">b=
itcoin-dev@lists.linuxfoundation.org</a>&gt; wrote:<br>
&gt;There are a few ways: here is my favorite (for the moment).<br>
&gt;<br>
&gt;1. Spam the 8mb blocks with 1 Satoshi outputs to the brainwallet<br>
&gt;&#39;BitcoinXT&#39;<br>
<br>
Even more direct: use coinbase outputs of=C2=A0 XT blocks to create those o=
utputs, as they can&#39;t by definition be on the Bitcoin chain.<br>
<br>
If you can&#39;t get those, using coinbase outputs of Bitcoin blocks to cre=
ate &quot;definitely Bitcoin-only&quot; outputs, and then spend the inputs =
to those transactions again on the XT chain. This isn&#39;t quite as good, =
as a big reorg on the XT chain could in theory spend them, but it&#39;s a c=
lose second.<br>
-----BEGIN PGP SIGNATURE-----<br>
<br>
iQE9BAEBCAAnIBxQZXRlciBUb2RkIDxwZXRlQHBldGVydG9kZC5vcmc+BQJV0YIS<br>
AAoJEMCF8hzn9Lnc47AH/R9EaGaa0xmD7qBODGUwX3SsDde7DMgO4t8X5GQ9uoaq<br>
qcjdnnvdeXjy5S39QdZFJjlH5bGn+BJy2wIxn0lMciKhEGIFOGeCUsMYEbgnOc03<br>
cLuyYpxdfXe4Amoxf2mqADgBqkAckf4cX6bMm3XXg+v3XAby2llydIGIydTwGWYq<br>
2KwXl9U9zm7UV8b5tJ7WmItCAcZAvTcSoX5SerOmPjjrmLtPTHThj8SfLTGAoWfT<br>
EXsSGkDBJ/9rJMms56FjciWsXHlB9pYK0a1sxh88PJluebqh99imDisJvATCVp2Z<br>
kZX1keZ1nyfG45jibgt6dlY97wU0n919SmQz0Tg6g90=3D<br>
=3DOD56<br>
-----END PGP SIGNATURE-----<br>
<br>
</blockquote></div>

--089e013a2afa3a9486051d80f3ef--