Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1X6eH7-0008D1-0H
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jul 2014 11:18:29 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.180 as permitted sender)
	client-ip=209.85.214.180; envelope-from=mh.in.england@gmail.com;
	helo=mail-ob0-f180.google.com; 
Received: from mail-ob0-f180.google.com ([209.85.214.180])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X6eH6-0000MX-2x
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jul 2014 11:18:28 +0000
Received: by mail-ob0-f180.google.com with SMTP id uy5so3738280obc.39
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 14 Jul 2014 04:18:22 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.182.115.134 with SMTP id jo6mr7280451obb.70.1405336702382;
	Mon, 14 Jul 2014 04:18:22 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.76.35.234 with HTTP; Mon, 14 Jul 2014 04:18:22 -0700 (PDT)
In-Reply-To: <35E6FF51-F9C4-4973-8489-B364E7C27C14@ricmoo.com>
References: <35E6FF51-F9C4-4973-8489-B364E7C27C14@ricmoo.com>
Date: Mon, 14 Jul 2014 13:18:22 +0200
X-Google-Sender-Auth: OFL-aub6sxWQSxVXMKVWkeJbTfc
Message-ID: <CANEZrP3RfYRoiwg_f9K0sf=vvpY=Wx78Q97Qp8uosK1GPV9QRg@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Richard Moore <me@ricmoo.com>
Content-Type: multipart/alternative; boundary=089e0102fb06ef7a0904fe257234
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	0.0 HTML_OBFUSCATE_05_10 BODY: Message is 5% to 10% HTML obfuscation
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1X6eH6-0000MX-2x
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Self-dependency transaction question...
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2014 11:18:29 -0000

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

Conceptually all transactions in the block chain lie on a single timeline.
The fact that we quantise that timeline into blocks is in many ways neither
here nor there - it's still a strict line.

What *can* happen and you must be aware of is duplicated transactions.
Satoshi sort of assumed this could never happen because everything is hash
based, but forgot that duplicating coinbases is possible and at one point
this did happen. It was banned by a rule change afterwards but you still
must be able to process the older parts of the chain that have this. There
is a BIP that covers the new rule.

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>Conceptually all transactions in the block chain lie on a single timeline.=
 The fact that we quantise that timeline into blocks is in many ways neithe=
r here nor there - it&#39;s still a strict line.=C2=A0</div>
<div><br></div><div>What <i>can</i>=C2=A0happen and you must be aware of is=
 duplicated transactions. Satoshi sort of assumed this could never happen b=
ecause everything is hash based, but forgot that duplicating coinbases is p=
ossible and at one point this did happen. It was banned by a rule change af=
terwards but you still must be able to process the older parts of the chain=
 that have this. There is a BIP that covers the new rule.</div>
<div><br></div></div></div></div>

--089e0102fb06ef7a0904fe257234--