<div dir="ltr"><div><div><div>Most solutions only work with a single Bitcoin address (terrible for privacy, and also potentially a security risk) or xpubkey (also terrible for privacy).<br><br></div>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.<br></div>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. <a href="https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki">https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki</a><br></div><div><br></div>Hampus <br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-12-19 10:05 GMT+01:00 Damian Williamson via bitcoin-dev <span dir="ltr"><<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.linuxfoundation.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div id="m_2108495040098490071divtagdefaultwrapper" style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif,"EmojiFont","Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols" dir="ltr">
<p style="margin-top:0;margin-bottom:0">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.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">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.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">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.</p>
<p style="margin-top:0;margin-bottom:0"><br>
</p>
<p style="margin-top:0;margin-bottom:0">Regards,</p>
<p style="margin-top:0;margin-bottom:0">Damian Williamson<br>
</p>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr style="display:inline-block;width:98%">
<div id="m_2108495040098490071divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> <a href="mailto:bitcoin-dev-bounces@lists.linuxfoundation.org" target="_blank">bitcoin-dev-bounces@lists.<wbr>linuxfoundation.org</a> <<a href="mailto:bitcoin-dev-bounces@lists.linuxfoundation.org" target="_blank">bitcoin-dev-bounces@lists.<wbr>linuxfoundation.org</a>> on behalf of Sjors Provoost via bitcoin-dev
<<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>><br>
<b>Sent:</b> Monday, 18 December 2017 10:26 PM<br>
<b>To:</b> Douglas Roark; Bitcoin Protocol Discussion<br>
<b>Subject:</b> Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet addresses?</font>
<div> </div>
</div><div><div class="h5">
<div class="m_2108495040098490071BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="m_2108495040098490071PlainText">Have you thought about combining this with BIP-47? You could associate payment codes with email via DNS.<br>
<br>
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.<br>
<br>
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.<br>
<br>
Sjors<br>
<br>
> Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev <<a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a>> het volgende geschreven:<br>
> <br>
> On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:<br>
>> I was wondering in terms of mass adoption, instead of long wallet<br>
>> addresses, maybe there should be a DNS-like decentralized mapping<br>
>> service to provide a user@crypto address?<br>
> <br>
> A few years ago, I was part of an effort with Armory and Verisign to<br>
> make something similar to what you're describing.<br>
> <a href="https://tools.ietf.org/html/draft-wiley-paymentassoc-00" id="m_2108495040098490071LPlnk805993" target="_blank">
https://tools.ietf.org/html/<wbr>draft-wiley-paymentassoc-00</a> is where you can<br>
> find the one and only official draft. I worked on a follow-up with some<br>
> changes and some nice appendices, explaining some nice tricks one could<br>
> use to make payment management flexible. For various reasons, it never<br>
> got published. I think it's an interesting draft that could be turned<br>
> into something useful. Among other things, it was able to leverage BIP32<br>
> and allow payment requests to be generated that automatically pointed<br>
> payees to the correct branch. DNSSEC may have some issues but, AFAIK,<br>
> it's as the easiest way to bootstrap identity to a common, reasonably<br>
> secure standard.<br>
> <br>
> --<br>
> ---<br>
> Douglas Roark<br>
> Cryptocurrency, network security, travel, and art.<br>
> <a href="https://onename.com/droark" id="m_2108495040098490071LPlnk436626" target="_blank">https://onename.com/droark</a><br>
> <a href="mailto:joroark@vt.edu" target="_blank">joroark@vt.edu</a><br>
> PGP key ID: 26623924<br>
> <br>
> ______________________________<wbr>_________________<br>
> bitcoin-dev mailing list<br>
> <a href="mailto:bitcoin-dev@lists.linuxfoundation.org" target="_blank">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
> <a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" id="m_2108495040098490071LPlnk312082" target="_blank">
https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br>
</div>
</span></font></div>
</div></div></div>
</div>
</div>
<br>______________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href="mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.<wbr>linuxfoundation.org</a><br>
<a href="https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" rel="noreferrer" target="_blank">https://lists.linuxfoundation.<wbr>org/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div><br></div>