summaryrefslogtreecommitdiff
path: root/24/846491e163d540e3a98144db2eb984dc20eb25
blob: 1199e29764ffbc19847600e4b92d9f26b10ca7d5 (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
86
87
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
	id 1RhqID-0007Sw-8h for bitcoin-development@lists.sourceforge.net;
	Mon, 02 Jan 2012 22:23:45 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of m.gmane.org
	designates 80.91.229.12 as permitted sender)
	client-ip=80.91.229.12;
	envelope-from=gcbd-bitcoin-development@m.gmane.org;
	helo=lo.gmane.org; 
Received: from lo.gmane.org ([80.91.229.12])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1RhqIC-0006bU-02 for bitcoin-development@lists.sourceforge.net;
	Mon, 02 Jan 2012 22:23:45 +0000
Received: from list by lo.gmane.org with local (Exim 4.69)
	(envelope-from <gcbd-bitcoin-development@m.gmane.org>)
	id 1RhqHz-0001Xx-OA for bitcoin-development@lists.sourceforge.net;
	Mon, 02 Jan 2012 23:23:31 +0100
Received: from 70-36-134-180.dsl.dynamic.sonic.net ([70.36.134.180])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00 for <bitcoin-development@lists.sourceforge.net>;
	Mon, 02 Jan 2012 23:23:31 +0100
Received: from tyrell.elden by 70-36-134-180.dsl.dynamic.sonic.net with local
	(Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <bitcoin-development@lists.sourceforge.net>;
	Mon, 02 Jan 2012 23:23:31 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: bitcoin-development@lists.sourceforge.net
From: Elden Tyrell <tyrell.elden@gmail.com>
Date: Mon, 2 Jan 2012 14:23:16 -0800
Message-ID: <jdtaol$3ku$1@dough.gmane.org>
References: <jdrds3$3tf$1@dough.gmane.org>
	<CALxbBHU7f1m+p45RHLhN-VGBoXJEi62x5mZUiAe_d5D-5Ga7yA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Complaints-To: usenet@dough.gmane.org
X-Gmane-NNTP-Posting-Host: 70-36-134-180.dsl.dynamic.sonic.net
User-Agent: Unison/2.1.6
X-Spam-Score: -1.8 (-)
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
	(tyrell.elden[at]gmail.com)
	-0.0 SPF_HELO_PASS          SPF: HELO matches SPF record
	0.0 DKIM_ADSP_CUSTOM_MED   No valid author signature, adsp_override is
	CUSTOM_MED
	-0.0 SPF_PASS               SPF: sender matches SPF record
	-1.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay
	domain 1.2 NML_ADSP_CUSTOM_MED    ADSP custom_med hit,
	and not from a mailing list
	-0.2 AWL AWL: From: address is in the auto white-list
X-Headers-End: 1RhqIC-0006bU-02
Subject: Re: [Bitcoin-development] does "stubbing" off Merkle trees reduce
	initial download bandwidth?
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, 02 Jan 2012 22:23:45 -0000

On 2012-01-02 05:31:19 -0800, Christian Decker said:
> Later full blocks would be required to detect usable inputs for future 
> outgoing transactions.

Er, yes, this is what I meant; I guess I should have been more specific.

So, a paranoid client cannot confirm reciept of coins until it has an 
unstubbed copy of the entire chain.  It can do other things (like send 
coins) using a stubbed chain, but it needs the whole unstubbed chain in 
order to be sure that incoming coins haven't already been spent.

Thanks for confirming this.