summaryrefslogtreecommitdiff
path: root/b0/2691fe776b6e8849cc7b36a13b9e16b5a2d1e5
blob: 63470b62efaad5999bd1e5dd3849eb22d91583c2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <jgarzik@bitpay.com>) id 1X6WNG-0006Zf-KD
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jul 2014 02:52:18 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 74.125.82.50 as permitted sender)
	client-ip=74.125.82.50; envelope-from=jgarzik@bitpay.com;
	helo=mail-wg0-f50.google.com; 
Received: from mail-wg0-f50.google.com ([74.125.82.50])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1X6WNE-0003yW-PC
	for bitcoin-development@lists.sourceforge.net;
	Mon, 14 Jul 2014 02:52:18 +0000
Received: by mail-wg0-f50.google.com with SMTP id n12so3419573wgh.33
	for <bitcoin-development@lists.sourceforge.net>;
	Sun, 13 Jul 2014 19:52:10 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to:cc:content-type;
	bh=Kf/TiOuPQlqY0kcGfu9lOSpa0jaB9pzObXOVaySMSOk=;
	b=HMHtqSucIwcxDY6TCUuZLk2XhMeQPxHmzg1ZH1MYiKpqjGU7Wz2RSpPSF4t61BKL7o
	0mAel1Nc996TtnBZeWzVkiu1yrDbpJtOXFBaJDKIKT3i/izxTyeYm8ASbN4MJXGaZKLe
	KAnNwgXP0U2nMuEHN4g1rl1Jefw9yj8WZY+WY5cYBUgQZ74jsMQ7SP1Dh9qB/srpqA+N
	e/2RNzmjNDwK350bvX6f06Tru+AkXWUJXlZuWuOE5dYGcsrS8igxpb8xmr8xfrJNq62F
	enG1CugOIA6ulwB2dJFbbK5iSNNUQ0bffGaTN5FL4a9p3XLYWmyKLhnBucw6gjjU6aTG
	0GlA==
X-Gm-Message-State: ALoCoQlsYG6umEt+mXTWb/ge/uDqgn1Zi/+KT6YutQ8c9O7CfV+C/618e+5LyHyI6DmPj5r7tymY
X-Received: by 10.194.90.228 with SMTP id bz4mr15793622wjb.65.1405306330487;
	Sun, 13 Jul 2014 19:52:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.5.67 with HTTP; Sun, 13 Jul 2014 19:51:50 -0700 (PDT)
In-Reply-To: <CACq0ZD6Mo0uVMM8HU3VrYORQgme7z084B45Cap8GYVwi-xs6vA@mail.gmail.com>
References: <35E6FF51-F9C4-4973-8489-B364E7C27C14@ricmoo.com>
	<CACq0ZD6Mo0uVMM8HU3VrYORQgme7z084B45Cap8GYVwi-xs6vA@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Sun, 13 Jul 2014 22:51:50 -0400
Message-ID: <CAJHLa0OOBK8+eiU5jGaaicVzi9L5bY6W1XyfY2Mcv1C1DBCA0A@mail.gmail.com>
To: Aaron Voisine <voisine@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
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 SPF_PASS               SPF: sender matches SPF record
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	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: 1X6WNE-0003yW-PC
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 02:52:18 -0000

On Sun, Jul 13, 2014 at 10:25 PM, Aaron Voisine <voisine@gmail.com> wrote:
> I believe tx have to be ordered sequentially within a block. Also
> since a tx is referenced by it's hash, it's practically impossible to
> make a self referential tx.

Correct.  A TX will not reference a later TX in the same block (or itself).

This would be a good invalid-block test to add to the test suite.  Any
volunteers?

-- 
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc.      https://bitpay.com/