On Mon, May 16, 2016 at 4:41 PM, Melvin Carvalho <melvincarvalho@gmail.com> wrote: > OK so you want to store public keys associated with an (unnamed) > identifier using a block chain. Such as namecoin, bitcoin or ethereum. > > This is already sounding like a bad idea. > No. We are not storing public keys on a blockchain. Read the white papers, or come to the design workshop. > Or is there some other block chain. Now what happens when it gets 51% > attacked? Or someone claims someone else's identifier. > > I store my public key on my homepage. Surely this is a HUGELY simpler, > cheaper and more secure way to do it? > If your public key is compromised, or you do prudent key rotation, using a key as an identifier is bad. Putting a public key on a web page is vulnerable to the centralities of domain systems. — Christopher Allen
Received on Monday, 16 May 2016 21:59:20 UTC