public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: CANNON <cannon@cannon-ciota.info>
To: mandar mulherkar <mandar.mulherkar@gmail.com>,
	Bitcoin Protocol Discussion
	<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses?
Date: Fri, 1 Dec 2017 04:12:24 +0000	[thread overview]
Message-ID: <88db7e18-e290-a81a-7f71-a9a66e564464@cannon-ciota.info> (raw)
In-Reply-To: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>

On 11/30/2017 10:20 PM, mandar mulherkar via bitcoin-dev wrote:
> Hello,
> 
> I am new, so apologies if this has been asked before.
> 
> Here are a few questions to start with -
> 
> I was wondering in terms of mass adoption, instead of long wallet
> addresses, maybe there should be a DNS-like decentralized mapping service
> to provide a user@crypto address?

Check out namecoin, there is also blockstack as someone mentioned, but I personally feel namecoin is technologically better.

If do not want a static bitcoin address mapped to a username, could use a stealth address (we need more
support for stealth addresses in bitcoin wallets).


  parent reply	other threads:[~2017-12-01  4:12 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
2017-12-01  8:24   ` Jérémie Dubois-Lacoste
2017-12-01  4:12 ` CANNON [this message]
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=88db7e18-e290-a81a-7f71-a9a66e564464@cannon-ciota.info \
    --to=cannon@cannon-ciota.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --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