MIME-Version: 1.0
In-Reply-To: <CALC81CNMTWhAQ8VSxToGcSPeJmfFJrANrdXONseTq1=WKm4=7w@mail.gmail.com>
References: <CALC81CNMTWhAQ8VSxToGcSPeJmfFJrANrdXONseTq1=WKm4=7w@mail.gmail.com>
Date: Thu, 16 May 2013 11:47:07 -0400
Message-ID: <CA+8xBpdY9Vi+K0Cxr_AJ25Y2ieB=0EueiPHq92pdr5QdBnNj_A@mail.gmail.com>
From: Jeff Garzik <jgarzik@exmulti.com>
To: Ricardo Filipe <ricardojdfilipe@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Service bits for pruned nodes
Precedence: list

On Thu, May 16, 2013 at 7:26 AM, Ricardo Filipe
<ricardojdfilipe@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.
jgarzik@exmulti.com