Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1WYNFk-0004P0-BZ for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 22:15:24 +0000 Received: from mail-pd0-f175.google.com ([209.85.192.175]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1WYNFi-0007Re-PS for bitcoin-development@lists.sourceforge.net; Thu, 10 Apr 2014 22:15:24 +0000 Received: by mail-pd0-f175.google.com with SMTP id x10so4428216pdj.20 for ; Thu, 10 Apr 2014 15:15:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=B9v6CAZjj51cfEKOdv/nkWEPEkvDI2PvZDY5wZez2ss=; b=h0HtCCiAnzSM8PGjrFPYOXryJVSwArrpsBg0Mx5j6hDzMNJFKM/+I849QP6eUixxsE ddfALImim4pPKI0En7V32OY/xEYW/+d9gKbxUgvjL6ARP6Ai0mCMEZgmcuVKLLMhmawm S7Lgk7tubuJyQta617+nu++ofP7sy2KtCY5+lgKGXnW/SWFdbEPsu6HotZSJfDPCjCCP Dxdx+pP9GirB9OJzKhkOhe7sBEZmeRAhGOk7NJgO+Z5bQ9/YjklHUafW8EYpEgV62Q7K 82Fh+1l2gaDBGoM+eFumgEUNR2WiGanrSnjehOVZBPCdFRnPke36g5uM6yRxM5tvLl/g rR+Q== X-Gm-Message-State: ALoCoQkT/ZR4WiBa5Q10AAGgO/KgjhxB6FzQ+LFcyQNpXUQxdf0jEbgrmKd4bgKlMyEpIMISAh6z X-Received: by 10.68.252.165 with SMTP id zt5mr22850419pbc.17.1397168116841; Thu, 10 Apr 2014 15:15:16 -0700 (PDT) Received: from [192.168.127.227] (50-0-36-93.dsl.dynamic.sonic.net. [50.0.36.93]) by mx.google.com with ESMTPSA id z3sm26124318pas.15.2014.04.10.15.15.15 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 10 Apr 2014 15:15:16 -0700 (PDT) Message-ID: <534717F3.6@monetize.io> Date: Thu, 10 Apr 2014 15:15:15 -0700 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <53470E65.5080402@jcea.es> In-Reply-To: <53470E65.5080402@jcea.es> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.192.175 listed in list.dnswl.org] X-Headers-End: 1WYNFi-0007Re-PS 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 22:15:24 -0000 Checkpoints will go away, eventually. On 04/10/2014 02:34 PM, Jesus Cea wrote: > 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. > > 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. > > > > ------------------------------------------------------------------------------ > Put Bad Developers to Shame > Dominate Development with Jenkins Continuous Integration > Continuously Automate Build, Test & Deployment > Start a new project now. Try Jenkins in the cloud. > http://p.sf.net/sfu/13600_Cloudbees > > > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >