From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WYMcJ-0004Os-TA for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 21:34:39 +0000 X-ACL-Warn: Received: from babylon5.jcea.es ([94.23.84.75] helo=smtp.jcea.es) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1WYMcI-0005DA-6C for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 21:34:39 +0000 Received: from [10.8.0.6] (ks27448.kimsufi.com [91.121.85.130]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.jcea.es (Postfix) with ESMTPSA id 3g4bGb0YWSzjQ for ; Thu, 10 Apr 2014 23:34:31 +0200 (CEST) Message-ID: <53470E65.5080402@jcea.es> Date: Thu, 10 Apr 2014 23:34:29 +0200 From: Jesus Cea User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="e5xqQTnI34g4V5lIfVSkMPbANEBg52bqO" X-Spam-Probability-jcea: Ham (0.0%) rz: False [12d313498efc52dac64136124c726113] (None) X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1WYMcI-0005DA-6C Subject: Re: [Bitcoin-development] Chain pruning 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: Thu, 10 Apr 2014 21:34:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --e5xqQTnI34g4V5lIfVSkMPbANEBg52bqO Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable On 10/04/14 18:59, Pieter Wuille wrote: > It's important to > note that this is a strict reduction in security: we're now trusting > that the longest chain (with most proof of work) commits to a valid > UTXO set (at some point in the past). AFAIK, current bitcoin code code already set blockchain checkpoints from time to time. It is a garanteed that a longer chain starting before the checkpoint is not going to be accepted suddently. See . Could be perfectly valid to store only unspend wallets before last checkpoint, if during the blockchain download the node did all the checks= =2E Would be interesting, of course, to be able to verify "unspend wallet accounting" having only that checkpoint data (the merkle tree can do that, I guess). So you could detect a data corruption or manipulation in your local harddisk. --=20 Jes=FAs Cea Avi=F3n _/_/ _/_/_/ _/_/_= / jcea@jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea@jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz --e5xqQTnI34g4V5lIfVSkMPbANEBg52bqO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJTRw5mAAoJEGjgN61Khv5D8tsH/iXF38P3V4L9SlFI5UQhrKuS B7AAA7klhXSRIlsMHU6+k1yhY/K7vVnjdp32l9bBOP3dclAHPo2dsS4Wg4jth8Yv 4o4naOrjmvXwofB84FlQWYGSNkMKcviJePMNLI+1wDAkyMjvC5yhGNUQTuHJ4PUY ovSKCrSX7vwFsXpurNQLqC11SNpWD8iU0wj4Ht1/oG8fiGQ8UwvvOP4rrBuV9ud1 +5SnNi7pGLN/r8HUCI49qJFRfVD+epsOZrdxHK6NpDQbzpP+craDY0dxckSYNJKR ISC8H6KORwancs6VxxCGrkzUHskOXKUS2XyMEDWpFfL7hdTCkq3xP7yySEm5X9w= =e+RR -----END PGP SIGNATURE----- --e5xqQTnI34g4V5lIfVSkMPbANEBg52bqO--