Of course. My proposal was just for the pruned nodes. I.e. You would have a majority (maybe not even a majority required) of nodes storing the whole blockchain and pruned nodes would store "random" parts of the blockchain, according to the resources they have, which would be organized as a DHT.
2013/5/16 Jeff Garzik <jgar...@exmulti.com>: > On Thu, May 16, 2013 at 7:26 AM, Ricardo Filipe > <ricardojdfil...@gmail.com> wrote: >> We would only end up with few copies of the historic data if users >> could choose what parts of the blockchain to store. Simply store >> chunks randomly, according to users available space, and give priority >> to the "N most recent" chunks to have more replicas in the network. >> >> You don't need bittorrent specifically for a DHT, if publicity is a >> problem. There are many DHT proposals and implementations, and i bet >> one of them should be more suitable to the bitcoin network than >> bittorrent's. > > That's just about the worst thing you could do for bitcoin. DoS one > part of the DHT, you DoS the entire blockchain by breaking the chain. > > -- > Jeff Garzik > exMULTI, Inc. > jgar...@exmulti.com ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
