<div dir="ltr">I'm working on a proposal called Numerifides. Full working document here: <a href="https://github.com/tyzbit/numerifides">https://github.com/tyzbit/numerifides</a><div><br></div><div>Highlights:<br>- Committed directly to Bitcoin blockchain</div><div>- Seems to solve Zooko's triangle (Decentralized, secure and human meaningful)</div><div>- Can use already existing SPV infrastructure for lookups (like DNS requests).</div><div>- Doesn't have the squatting problems of Namecoin (squatting a name costs you locked up Bitcoin funds)</div><div>- Consensus revocation of names (Someone squatting <a href="http://google.com">google.com</a> but the community knows that's a lie? It's possible to "unseat" that registration)</div><div>- If you registered a name no one cares about (oeJFwlkS) no one will care to try to unseat your name, except to steal your funds you locked up (which need to just be high enough so as to not be dust)</div><div>- Usable for any name->data association such as Lightning nodes, DNS, Certificate Authorities, decentralized identities etc</div><div><br></div><div>Already I know some concerns are in the details of implementation like the hash function used for the transaction puzzle, censorship resistance (though the market effect does play itself well here) and privacy concerns (though the committed data can be encrypted or hashed before being stored as I do envision a "catchall" unadvertised datatype where anyone can commit anything for any purpose such as for document existence or even committing an encrypted key to some piece of data). I also don't like the idea of people committing IP addresses of their websites to the blockchain for all time, but perhaps a 2nd-layer "nameserver"-like configuration can be found for less permanent, more ephemeral data like DNS.<br></div><div><br></div><div>I'd love any feedback the list has to offer.<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Apr 16, 2018 at 6:19 AM Corné Plooy via Lightning-dev <<a href="mailto:lightning-dev@lists.linuxfoundation.org">lightning-dev@lists.linuxfoundation.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Op 10-04-18 om 20:34 schreef Tyler H:<br>
><br>
> I will continue to approach the problem of securely advertising<br>
> human-understandable node names, and I hope someday soon I will have a<br>
> solution Lightning can use that retains the open, decentralized<br>
> properties of the technology and the underlying blockchains.<br>
><br>
Two of my favorite approaches:<br>
* Namecoin-style: Register your name first-come-first-serve on a block<br>
chain.<br>
-> Provides no protection against name squatting and attackers<br>
registering similarly-looking names.<br>
* Web of Trust: I tell you I believe this pubkey really corresponds to<br>
this name; someone else might tell you something else. DNS is<br>
essentially a special case of this, where the WoT has a centralized star<br>
shape. TLS is another case, where there is dozens of signing parties<br>
(CAs), and everyone typically gets their keys signed by only one of<br>
them, so anyone verifying keys has to trust all these CAs. More<br>
generally, a WoT can have any shape though.<br>
-> Provides little to no protection against trusted parties lying to you.<br>
<br>
CJP<br>
<br>
<br>
_______________________________________________<br>
Lightning-dev mailing list<br>
<a href="mailto:Lightning-dev@lists.linuxfoundation.org" target="_blank">Lightning-dev@lists.linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev</a><br>
</blockquote></div>