📅 Original date posted:2013-05-16
📝 Original message: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 <jgarzik at exmulti.com>:
> On Thu, May 16, 2013 at 7:26 AM, Ricardo Filipe
> <ricardojdfilipe at 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 at exmulti.com
Ricardo Filipe [ARCHIVE] /
npub14f…hksaj
2023-06-07 15:01:12
in reply to nevent1q…5p9v
Author Public Key
npub14fwd2yh320mh4ge46ute8ukdyx2kjxy2ak4a05prjwrtzlmh9rvq8hksajPublished at
2023-06-07 15:01:12Event JSON
{
"id": "b9199974594e895df8d69c6904807df61788e38feb9b6e562be894f7b372e71c",
"pubkey": "aa5cd512f153f77aa335d71793f2cd219569188aedabd7d0239386b17f7728d8",
"created_at": 1686150072,
"kind": 1,
"tags": [
[
"e",
"1092d5ea64142286a0cd5c2b3aebd8da882fcd6a0c7a755bcf6c68f75e2e26e6",
"",
"root"
],
[
"e",
"fa8bc0cb344e399e5ff220bb7c53af33586250e5bb8ab40a7ec3f3522848ff1a",
"",
"reply"
],
[
"p",
"b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11"
]
],
"content": "📅 Original date posted:2013-05-16\n📝 Original message:Of course.\nMy proposal was just for the pruned nodes.\nI.e. You would have a majority (maybe not even a majority required) of\nnodes storing the whole blockchain and pruned nodes would store\n\"random\" parts of the blockchain, according to the resources they\nhave, which would be organized as a DHT.\n\n2013/5/16 Jeff Garzik \u003cjgarzik at exmulti.com\u003e:\n\u003e On Thu, May 16, 2013 at 7:26 AM, Ricardo Filipe\n\u003e \u003cricardojdfilipe at gmail.com\u003e wrote:\n\u003e\u003e We would only end up with few copies of the historic data if users\n\u003e\u003e could choose what parts of the blockchain to store. Simply store\n\u003e\u003e chunks randomly, according to users available space, and give priority\n\u003e\u003e to the \"N most recent\" chunks to have more replicas in the network.\n\u003e\u003e\n\u003e\u003e You don't need bittorrent specifically for a DHT, if publicity is a\n\u003e\u003e problem. There are many DHT proposals and implementations, and i bet\n\u003e\u003e one of them should be more suitable to the bitcoin network than\n\u003e\u003e bittorrent's.\n\u003e\n\u003e That's just about the worst thing you could do for bitcoin. DoS one\n\u003e part of the DHT, you DoS the entire blockchain by breaking the chain.\n\u003e\n\u003e --\n\u003e Jeff Garzik\n\u003e exMULTI, Inc.\n\u003e jgarzik at exmulti.com",
"sig": "a792c70cc8da72cc7f683270b2e3ad54a5fbb22436b10bb9371064fb110ee9890ad1da68df509345cb7e199f6f3dd3c944a6c7d1aae2079d4173d8c2b3fae120"
}