From: Lucas Clemente Vella <lvella@gmail•com>
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 01:15:00 -0200 [thread overview]
Message-ID: <CAGCathwjmj_f0TWZF=BhdCq=dSZ_R53Frd3A9b2SgFtus-AH=g@mail.gmail.com> (raw)
In-Reply-To: <CAHneDF3qH9OUxqLthY6hEzzFr21QJFLV5wOP8jw+p5eOtpb2oQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
The original altcoin, Namecoin, aimed a building a bitcoin-like, blockchain
based decentralized DNS system. Unfortunately it didn't catch, but it would
be the most logical choice for the name registry database.
2017-11-30 20:20 GMT-02:00 mandar mulherkar via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org>:
> 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?
>
> This address translation can happen with confirmations from the network.
> So instead of providing a long string, or a QR code that needs an app, you
> simply type in a human readable address, and the wallet software converts
> it to a wallet address.
>
> Please let me know where I can research this more - if there already is
> literature about this somewhere.
>
> thanks!
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
--
Lucas Clemente Vella
lvella@gmail•com
[-- Attachment #2: Type: text/html, Size: 2115 bytes --]
next prev parent reply other threads:[~2017-12-01 3:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 22:20 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 [this message]
2017-12-01 4:17 ` CANNON
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='CAGCathwjmj_f0TWZF=BhdCq=dSZ_R53Frd3A9b2SgFtus-AH=g@mail.gmail.com' \
--to=lvella@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=mandar.mulherkar@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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