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 ) 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 ; 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: References: <3E7894A0-06F3-453D-87F8-975A244EBACF@include7.ch> <2BDA0943-22BB-4405-9AF0-86FB41FD04A6@include7.ch> <2F20A509-13A9-4C84-86D7-A15C21BACD53@include7.ch> <2A1C412D-414E-4C41-8E20-F0D21F801328@grabhive.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> Date: Wed, 17 Jul 2013 16:04:33 -0700 Message-ID: From: Gregory Maxwell To: Michael Gronager 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 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 23:04:42 -0000 On Wed, Jul 17, 2013 at 3:26 PM, Michael Gronager 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!)