W3C home > Mailing lists > Public > public-webpayments@w3.org > November 2015

Re: A Decentralized Hashtable for the Web

From: Dave Lampton <dave.lampton@gmail.com>
Date: Tue, 03 Nov 2015 15:43:24 +0000
Message-ID: <CAHbN0ewe6M=_Ni3rVoEpmUF2cunX4xTfEvGVcRLXHYCXV=j4+A@mail.gmail.com>
To: Erik Anderson <eanders@pobox.com>, Web Payments CG <public-webpayments@w3.org>
Re: a new name... how about Hashbrown ?

On Tue, Nov 3, 2015 at 5:57 AM Erik Anderson <eanders@pobox.com> wrote:

> Its called Redis in active-active mode. Plenty of forks of redis out
> there that can accomplish this. I have no proof but I suspect Blockchain
> was originally a fork of Redis.
> Additionally you cant have a decentralized Hashtable until you have a
> "non-forking" trust mechanism.
> I am still not convinced you can decentralize trust. Even 51% attack of
> a proof-of-work majority is centralizing trust.
> 1 bad bug in a new deployment of a decentralized hashtable could destroy
> the entire decentralized hashtable network. But thats what snapshots and
> restore points are, right? Well you still need 51% of the network to
> agree to rollback to a restore point.
> Now spam the network with new hash entries and watch the hashtable bloat
> in size and become un-maintainable.
> Technology is just not there and network/memory/disk resources are still
> expensive so few are willing to maintain this.
> We are still 10 years from seeing something like this from being even
> remotely mature enough to reach adoption.
> Erik Anderson
> Bloomberg
> --

*Dave Lampton*
Twitter: @Dave_Lampton <https://twitter.com/dave_lampton>
Google: +DaveLampton <https://www.google.com/+DaveLampton>
LinkedIn.com/in/DaveLampton/ <https://www.linkedin.com/in/davelampton/>
About.me/DaveLampton <https://about.me/davelampton>
Received on Tuesday, 3 November 2015 15:44:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:07:43 UTC