public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: CANNON <cannon@cannon-ciota.info>
To: Lucas Clemente Vella <lvella@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>,
	mandar mulherkar <mandar.mulherkar@gmail.com>
Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses?
Date: Fri, 1 Dec 2017 04:17:37 +0000	[thread overview]
Message-ID: <143c8bc4-77a7-a097-fbc1-75a1210e60ca@cannon-ciota.info> (raw)
In-Reply-To: <CAGCathwjmj_f0TWZF=BhdCq=dSZ_R53Frd3A9b2SgFtus-AH=g@mail.gmail.com>

On 12/01/2017 03:15 AM, Lucas Clemente Vella via bitcoin-dev wrote:
> Unfortunately it didn't catch, but it would

Interesting, I just mentioned namecoin literally seconds before this email arrived.
Saying "it did not catch" is not accurate I'd say. It still works great, and namecoin
has actually made great progress this year 2017. I'd say that namecoin has great potential
but just not widely adopted yet.

Would be real nice to have namecion support in major bitcoin wallets for name to data mapping.


  reply	other threads:[~2017-12-01  4:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 22:20 [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses? mandar mulherkar
2017-12-01  0:00 ` Tao Effect
2017-12-01  0:10 ` Justin Newton
2017-12-01  3:08 ` Douglas Roark
2017-12-18 11:26   ` Sjors Provoost
2017-12-19  9:05     ` Damian Williamson
2017-12-19 13:11       ` Hampus Sjöberg
2017-12-01  3:15 ` Lucas Clemente Vella
2017-12-01  4:17   ` CANNON [this message]
2017-12-01  8:24   ` Jérémie Dubois-Lacoste
2017-12-01  4:12 ` CANNON
2017-12-01 11:07 ` Antonis Anastasiadis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=143c8bc4-77a7-a097-fbc1-75a1210e60ca@cannon-ciota.info \
    --to=cannon@cannon-ciota.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=lvella@gmail.com \
    --cc=mandar.mulherkar@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox