A DNS-like decentralized mapping for wallet addresses?

A DNS-like decentralized mapping for wallet addresses?
2017-12-01  0:00 ` Tao Effect
                   ` (5 more replies)
  
From: mandar mulherkar @ 2017-11-30 22:20 UTC (permalink / raw)
  To: bitcoin-dev

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

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!

[-- Attachment #2: Type: text/html, Size: 899 bytes --]

 permalink raw reply	[|nested]
2017-12-01  0:00 ` 
                   ` 
  
From: mandar mulherkar @ 2017-11-30 22:20 UTC (permalink / raw)
  To: bitcoin-dev

[-- Attachment #1: Type: text/plain, Size: 641 bytes --]

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!

[-- Attachment #2: Type: text/html, Size: 899 bytes --]

 permalink raw reply	[|nested]
* 
  2017-11-30 22:20 [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses? mandar mulherkar

  2017-12-01  0:10 ` 
                   ` 
  5 siblings, 0 replies; 12+ messages in thread
From: Tao Effect @ 2017-12-01  0:00 UTC (permalink / raw)
  To: mandar mulherkar, Bitcoin Protocol Discussion


[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]

Check out Blockstack, they're doing something like that.

--
Please do not email me anything that you are not comfortable also sharing with the NSA.

> On Nov 30, 2017, at 2:20 PM, mandar mulherkar via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org <mailto:bitcoin-dev@lists•linuxfoundation.org>> 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?
> 
> 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 <mailto:bitcoin-dev@lists•linuxfoundation.org>
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #1.2: Type: text/html, Size: 4407 bytes --]

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

^ permalink raw reply	[|nested] 12+ messages in thread
* 
  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  3:08 ` 
                   ` 
  5 siblings, 0 replies; 12+ messages in thread
From: Justin Newton @ 2017-12-01  0:10 UTC (permalink / raw)
  To: mandar mulherkar, Bitcoin Protocol Discussion


[-- Attachment #1.1: Type: text/plain, Size: 1212 bytes --]

https://www.walletnames.com

Based on a standard that can support blockchain based or traditional ICANN
DNS.



On Fri, Dec 1, 2017 at 6:20 AM, mandar mulherkar via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> 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?
>
> 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
>
>


-- 

Justin W. Newton
Founder/CEO
Netki, Inc.

justin@ <justin@netki•com>netki.com <justin@netki•com>

*+1.818.927.2646*

[-- Attachment #1.2: Type: text/html, Size: 3457 bytes --]

[-- Attachment #2: PastedGraphic-1.tiff --]
[-- Type: image/tiff, Size: 10972 bytes --]

^ permalink raw reply	[|nested] 12+ messages in thread
* 
  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-18 11:26   ` Sjors Provoost
  2017-12-01  3:15 ` 
                   ` 
  5 siblings, 1 reply; 12+ messages in thread
From: Douglas Roark @ 2017-12-01  3:08 UTC (permalink / raw)
  To: bitcoin-dev


[-- Attachment #1.1: Type: text/plain, Size: 1183 bytes --]

On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:
> 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?

A few years ago, I was part of an effort with Armory and Verisign to
make something similar to what you're describing.
https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can
find the one and only official draft. I worked on a follow-up with some
changes and some nice appendices, explaining some nice tricks one could
use to make payment management flexible. For various reasons, it never
got published. I think it's an interesting draft that could be turned
into something useful. Among other things, it was able to leverage BIP32
and allow payment requests to be generated that automatically pointed
payees to the correct branch. DNSSEC may have some issues but, AFAIK,
it's as the easiest way to bootstrap identity to a common, reasonably
secure standard.

-- 
---
Douglas Roark
Cryptocurrency, network security, travel, and art.
https://onename.com/droark
joroark@vt•edu
PGP key ID: 26623924


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 895 bytes --]

^ permalink raw reply	[|nested] 12+ messages in thread
2017-11-30 22:20 [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses? mandar mulherkar
                   ` (3 preceding siblings ...)
  2017-12-01  3:15 ` Lucas Clemente Vella

  2017-12-01 11:07 ` Antonis Anastasiadis
  
From: CANNON @ 2017-12-01  4:12 UTC (permalink / raw)
  To: mandar mulherkar, Bitcoin Protocol Discussion

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).


 permalink raw reply	[|nested]
2017-12-01  3:15 ` Lucas Clemente Vella

  2017-12-01  8:24   ` Jérémie Dubois-Lacoste
  
From: CANNON @ 2017-12-01  4:17 UTC (permalink / raw)
  To: Lucas Clemente Vella, Bitcoin Protocol Discussion, mandar mulherkar

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.


 permalink raw reply	[|nested]
2017-12-01  3:15 ` Lucas Clemente Vella
  2017-12-01  4:17   ` CANNON

  
From: Jérémie Dubois-Lacoste @ 2017-12-01  8:24 UTC (permalink / raw)
  To: Lucas Clemente Vella, Bitcoin Protocol Discussion

[-- Attachment #1: Type: text/plain, Size: 1587 bytes --]

https://openalias.org/


2017-12-01 4:15 GMT+01:00 Lucas Clemente Vella via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org>:

> 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
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

[-- Attachment #2: Type: text/html, Size: 3189 bytes --]

 permalink raw reply	[|nested]
2017-11-30 22:20 [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses? mandar mulherkar
                   ` (4 preceding siblings ...)
  2017-12-01  4:12 ` CANNON

  
From: Antonis Anastasiadis @ 2017-12-01 11:07 UTC ( / )
  To: bitcoin-dev



Also check the Open Alias project. It's based on DNS+DNSSEC but it
offers the usability feature you mention (nice addresses).

https://openalias.org/

On 01/12/2017 00:20, 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?
>
> 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
2017-12-01  3:08 ` Douglas Roark

  2017-12-19  9:05     ` Damian Williamson
  
From: Sjors Provoost @ 2017-12-18 11:26 UTC (permalink / raw)
  To: Douglas Roark, Bitcoin Protocol Discussion

[-- Attachment #1: Type: text/plain, Size: 2147 bytes --]

Have you thought about combining this with BIP-47? You could associate payment codes with email via DNS.

It would be nice if there was a way to get rid of the announcement transaction in BIP-47 and establish a shared secret out of bound. That would simplify things, at the cost of an additional burden of storing more than an HD seed to recover a wallet that received funds this way.

Perhaps the sender can email to the recipient the information they need to retrieve the funds. The (first) transaction could have a time locked refund in it, in case the payment code is stale.

Sjors

> Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> het volgende geschreven:
> 
> On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:
>> 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?
> 
> A few years ago, I was part of an effort with Armory and Verisign to
> make something similar to what you're describing.
> https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can
> find the one and only official draft. I worked on a follow-up with some
> changes and some nice appendices, explaining some nice tricks one could
> use to make payment management flexible. For various reasons, it never
> got published. I think it's an interesting draft that could be turned
> into something useful. Among other things, it was able to leverage BIP32
> and allow payment requests to be generated that automatically pointed
> payees to the correct branch. DNSSEC may have some issues but, AFAIK,
> it's as the easiest way to bootstrap identity to a common, reasonably
> secure standard.
> 
> --
> ---
> Douglas Roark
> Cryptocurrency, network security, travel, and art.
> https://onename.com/droark
> joroark@vt•edu
> PGP key ID: 26623924
> 
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

 permalink raw reply	[|nested]
2017-12-18 11:26   ` Sjors Provoost

  2017-12-19 13:11       ` Hampus Sjöberg
  
From: Damian Williamson @ 2017-12-19  9:05 UTC (permalink / raw)
  To: Douglas Roark, Sjors Provoost, Bitcoin Protocol Discussion

[-- Attachment #1: Type: text/plain, Size: 3614 bytes --]

There is no reason it should not be easily possible to develop a Bitcoin wallet that has an integrated name to address mapping feature. It might be a good idea for a software product, it could even be based on Bitcoin Core. There is no specific reason that people wanting that sort of feature could not use it. In fact, you could map names, strings, email addresses, it could be very flexible.


Relying on an additional service like DNS which is flexible enough to handle the job, does introduce an additional availability risk. There is no additional privacy risk provided each mapped name or address is only used once to send/receive one payment unless you directly use something personally identifiable like an email address which could be used to map bitcoin addresses to an individual. Personally, I am not concerned about privacy so much but can understand that some highly value their privacy.


If you get it right it will be a service better than namecoin transacting in Bitcoin. If you think that is valuable, go for it.


Regards,

Damian Williamson


________________________________
From: bitcoin-dev-bounces@lists•linuxfoundation.org <bitcoin-dev-bounces@lists•linuxfoundation.org> on behalf of Sjors Provoost via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
Sent: Monday, 18 December 2017 10:26 PM
To: Douglas Roark; Bitcoin Protocol Discussion
Subject: Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses?

Have you thought about combining this with BIP-47? You could associate payment codes with email via DNS.

It would be nice if there was a way to get rid of the announcement transaction in BIP-47 and establish a shared secret out of bound. That would simplify things, at the cost of an additional burden of storing more than an HD seed to recover a wallet that received funds this way.

Perhaps the sender can email to the recipient the information they need to retrieve the funds. The (first) transaction could have a time locked refund in it, in case the payment code is stale.

Sjors

> Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> het volgende geschreven:
>
> On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:
>> 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?
>
> A few years ago, I was part of an effort with Armory and Verisign to
> make something similar to what you're describing.
> https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can
> find the one and only official draft. I worked on a follow-up with some
> changes and some nice appendices, explaining some nice tricks one could
> use to make payment management flexible. For various reasons, it never
> got published. I think it's an interesting draft that could be turned
> into something useful. Among other things, it was able to leverage BIP32
> and allow payment requests to be generated that automatically pointed
> payees to the correct branch. DNSSEC may have some issues but, AFAIK,
> it's as the easiest way to bootstrap identity to a common, reasonably
> secure standard.
>
> --
> ---
> Douglas Roark
> Cryptocurrency, network security, travel, and art.
> https://onename.com/droark
> joroark@vt•edu
> PGP key ID: 26623924
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev


[-- Attachment #2: Type: text/html, Size: 5506 bytes --]

 permalink raw reply	[|nested]
2017-12-19  9:05     ` Damian Williamson

  
From: Hampus Sjöberg @ 2017-12-19 13:11 UTC (permalink / raw)
  To: Bitcoin Protocol Discussion

[-- Attachment #1: Type: text/plain, Size: 4601 bytes --]

Most solutions only work with a single Bitcoin address (terrible for
privacy, and also potentially a security risk) or xpubkey (also terrible
for privacy).

I think the best solution here is some kind of store-and-forward server,
where you trade a little bit of privacy (to the server, that is), but get
the convenience of using (for example) an email address as the account.
I like for example BIP75 for this, and I hope the community can work
towards a solution like this. This could potentially work good with LN as
well. https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki

Hampus

2017-12-19 10:05 GMT+01:00 Damian Williamson via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org>:

> There is no reason it should not be easily possible to develop a Bitcoin
> wallet that has an integrated name to address mapping feature. It might be
> a good idea for a software product, it could even be based on Bitcoin Core.
> There is no specific reason that people wanting that sort of feature could
> not use it. In fact, you could map names, strings, email addresses, it
> could be very flexible.
>
>
> Relying on an additional service like DNS which is flexible enough to
> handle the job, does introduce an additional availability risk. There is no
> additional privacy risk provided each mapped name or address is only used
> once to send/receive one payment unless you directly use something
> personally identifiable like an email address which could be used to map
> bitcoin addresses to an individual. Personally, I am not concerned about
> privacy so much but can understand that some highly value their privacy.
>
>
> If you get it right it will be a service better than namecoin transacting
> in Bitcoin. If you think that is valuable, go for it.
>
>
> Regards,
>
> Damian Williamson
>
>
> ------------------------------
> *From:* bitcoin-dev-bounces@lists•linuxfoundation.org <
> bitcoin-dev-bounces@lists•linuxfoundation.org> on behalf of Sjors
> Provoost via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org>
> *Sent:* Monday, 18 December 2017 10:26 PM
> *To:* Douglas Roark; Bitcoin Protocol Discussion
> *Subject:* Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet
> addresses?
>
> Have you thought about combining this with BIP-47? You could associate
> payment codes with email via DNS.
>
> It would be nice if there was a way to get rid of the announcement
> transaction in BIP-47 and establish a shared secret out of bound. That
> would simplify things, at the cost of an additional burden of storing more
> than an HD seed to recover a wallet that received funds this way.
>
> Perhaps the sender can email to the recipient the information they need to
> retrieve the funds. The (first) transaction could have a time locked refund
> in it, in case the payment code is stale.
>
> Sjors
>
> > Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> het volgende geschreven:
> >
> > On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:
> >> 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?
> >
> > A few years ago, I was part of an effort with Armory and Verisign to
> > make something similar to what you're describing.
> > https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can
> > find the one and only official draft. I worked on a follow-up with some
> > changes and some nice appendices, explaining some nice tricks one could
> > use to make payment management flexible. For various reasons, it never
> > got published. I think it's an interesting draft that could be turned
> > into something useful. Among other things, it was able to leverage BIP32
> > and allow payment requests to be generated that automatically pointed
> > payees to the correct branch. DNSSEC may have some issues but, AFAIK,
> > it's as the easiest way to bootstrap identity to a common, reasonably
> > secure standard.
> >
> > --
> > ---
> > Douglas Roark
> > Cryptocurrency, network security, travel, and art.
> > https://onename.com/droark
> > joroark@vt•edu
> > PGP key ID: 26623924
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev@lists•linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

[-- Attachment #2: Type: text/html, Size: 7486 bytes --]

 permalink raw reply	[|nested]