anyway, any kind of compression that comes to the blockchain is orthogonal to pruning.
I agree that you will probably want some kind of replication on more recent nodes than on older ones. However, nodes with older blocks don't need to be "static", get the block distribution algorithm to sort it out. 2014-04-10 17:28 GMT+01:00 Mike Hearn <m...@plan99.net>: > Suggestions always welcome! > > The main problem with this is that the block chain is mostly random bytes > (hashes, keys) so it doesn't compress that well. It compresses a bit, but > not enough to change the fundamental physics. > > However, that does not mean the entire chain has to be stored on expensive > rotating platters. I've suggested that in some star trek future where the > chain really is gigantic, it could be stored on tape and spooled off at high > speed. Literally a direct DMA from tape drive to NIC. But we're not there > yet :) > > ------------------------------------------------------------------------------ > 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
