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 > <https://bitcointalk.org/index.php?topic=194078.0>. > > 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 >
------------------------------------------------------------------------------ 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
