summaryrefslogtreecommitdiff
path: root/89/5490100eacc18a33c2a6adfddfea1ffdcef08a
blob: ae7779ba35769e636818aecbe26e061ec2e2786a (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
88
89
90
91
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <gmaxwell@gmail.com>) id 1Uzam2-00068Q-Cq
	for bitcoin-development@lists.sourceforge.net;
	Wed, 17 Jul 2013 23:04:42 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.217.169 as permitted sender)
	client-ip=209.85.217.169; envelope-from=gmaxwell@gmail.com;
	helo=mail-lb0-f169.google.com; 
Received: from mail-lb0-f169.google.com ([209.85.217.169])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1Uzam0-00023H-Em
	for bitcoin-development@lists.sourceforge.net;
	Wed, 17 Jul 2013 23:04:42 +0000
Received: by mail-lb0-f169.google.com with SMTP id d10so2018828lbj.28
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 17 Jul 2013 16:04:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.152.27.169 with SMTP id u9mr3858537lag.8.1374102273727; Wed,
	17 Jul 2013 16:04:33 -0700 (PDT)
Received: by 10.112.160.104 with HTTP; Wed, 17 Jul 2013 16:04:33 -0700 (PDT)
In-Reply-To: <EFFD62F8-8066-4B56-8331-1F1A8D7FF3C2@mac.com>
References: <CANEZrP0_H9+prDSF92q8a4QzP=fzDM6cTDv0+KcfV9NF9thkmw@mail.gmail.com>
	<3E7894A0-06F3-453D-87F8-975A244EBACF@include7.ch>
	<CANEZrP2jmWkDbpJEm0vd2CKF-prFNbz_ZeNJfDWtSCKb8k5ZXA@mail.gmail.com>
	<2BDA0943-22BB-4405-9AF0-86FB41FD04A6@include7.ch>
	<CANEZrP0McSrVzwv=-qimPyX41EEDmyQdYW5QjPr_i+KWyJZSZw@mail.gmail.com>
	<2F20A509-13A9-4C84-86D7-A15C21BACD53@include7.ch>
	<CANEZrP2yQvmvwP_ZULdS2i+X6L9MeZ+DfidiuZPD2EHwLsN2MA@mail.gmail.com>
	<2A1C412D-414E-4C41-8E20-F0D21F801328@grabhive.com>
	<CANEZrP12V_5Ak0f91RsMziuqXysde102rGeSko=qPBjefy3AeA@mail.gmail.com>
	<8EE501AA-1601-4C28-A32E-80F17D219D3A@grabhive.com>
	<20130717105853.GA10083@savin>
	<3DB67FAF-E113-47FE-9043-C22D0F5A4F4A@grabhive.com>
	<16E9C860-51CA-4274-B852-A816D12B6A5B@mac.com>
	<7685FDAE-C584-4FC8-9751-4D5556EC57C7@grabhive.com>
	<CANEZrP3F0Q_NXhhbkh=9CESAAmhntM_uKQEe0CJf=sDuJx2Xmw@mail.gmail.com>
	<EFFD62F8-8066-4B56-8331-1F1A8D7FF3C2@mac.com>
Date: Wed, 17 Jul 2013 16:04:33 -0700
Message-ID: <CAAS2fgSDCOFk=7mVVuTKBHvCP+C+2KiE8sq8+JuSDVRz1hz4cw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Michael Gronager <gronager@mac.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(gmaxwell[at]gmail.com)
	-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: 1Uzam0-00023H-Em
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SPV bitcoind? (was: Introducing
	BitcoinKit.framework)
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: Wed, 17 Jul 2013 23:04:42 -0000

On Wed, Jul 17, 2013 at 3:26 PM, Michael Gronager <gronager@mac.com> wrote:
> However, by having a merkle tree hash of all UTXOs they become downloadab=
le in a trusted manner from any other client - something that enables boots=
trap in minutes, so the old numbers becomes less relevant in this setting.

This, however, reduces the node to SPV security of the past history.
Particularly for a wallet client=E2=80=94 as opposed to a miner or what hav=
e
you=E2=80=94 if you are willing to accept SPV security you could simply be =
an
SPV client.

(I like committed UTXO trees, and I believe I was the first person to
suggest them=E2=80=94 but I think it's good to not over-hype what they do!)