📅 Original date posted:2017-12-19
📝 Original message: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 at 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 at lists.linuxfoundation.org <
> bitcoin-dev-bounces at lists.linuxfoundation.org> on behalf of Sjors
> Provoost via bitcoin-dev <bitcoin-dev at 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 at 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 at 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 at vt.edu
> > PGP key ID: 26623924
> >
> > _______________________________________________
> > bitcoin-dev mailing list
> > bitcoin-dev at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171219/cbaee39b/attachment-0001.html>;
Hampus Sjöberg [ARCHIVE] /
npub10u…hln8t
2023-06-07 18:08:02
in reply to nevent1q…4sfc
Author Public Key
npub10uzud4rf4636awmfgvarmcfndcmdnv8rfd2y3rx2sqgckv9zur4qahln8tPublished at
2023-06-07 18:08:02Event JSON
{
"id": "866542476d9060d49b0016c3777c2e79da4b2833580fbfb5b2abdeef63ddbde8",
"pubkey": "7f05c6d469aea3aebb69433a3de1336e36d9b0e34b54488cca80118b30a2e0ea",
"created_at": 1686161282,
"kind": 1,
"tags": [
[
"e",
"aa26ac7d2c56b5e93f58d0a4616f8108b14cd88c555a82aa7113c62ff7cbed00",
"",
"root"
],
[
"e",
"daaf4f556e0bd6f59821829e66babcecc7e43cfa4eb3976f0506d6ee2a87a157",
"",
"reply"
],
[
"p",
"807351d851a3c419faea089fe59e0d72175abc5b316d48bfa974b48d83c07fed"
]
],
"content": "📅 Original date posted:2017-12-19\n📝 Original message:Most solutions only work with a single Bitcoin address (terrible for\nprivacy, and also potentially a security risk) or xpubkey (also terrible\nfor privacy).\n\nI think the best solution here is some kind of store-and-forward server,\nwhere you trade a little bit of privacy (to the server, that is), but get\nthe convenience of using (for example) an email address as the account.\nI like for example BIP75 for this, and I hope the community can work\ntowards a solution like this. This could potentially work good with LN as\nwell. https://github.com/bitcoin/bips/blob/master/bip-0075.mediawiki\n\nHampus\n\n2017-12-19 10:05 GMT+01:00 Damian Williamson via bitcoin-dev \u003c\nbitcoin-dev at lists.linuxfoundation.org\u003e:\n\n\u003e There is no reason it should not be easily possible to develop a Bitcoin\n\u003e wallet that has an integrated name to address mapping feature. It might be\n\u003e a good idea for a software product, it could even be based on Bitcoin Core.\n\u003e There is no specific reason that people wanting that sort of feature could\n\u003e not use it. In fact, you could map names, strings, email addresses, it\n\u003e could be very flexible.\n\u003e\n\u003e\n\u003e Relying on an additional service like DNS which is flexible enough to\n\u003e handle the job, does introduce an additional availability risk. There is no\n\u003e additional privacy risk provided each mapped name or address is only used\n\u003e once to send/receive one payment unless you directly use something\n\u003e personally identifiable like an email address which could be used to map\n\u003e bitcoin addresses to an individual. Personally, I am not concerned about\n\u003e privacy so much but can understand that some highly value their privacy.\n\u003e\n\u003e\n\u003e If you get it right it will be a service better than namecoin transacting\n\u003e in Bitcoin. If you think that is valuable, go for it.\n\u003e\n\u003e\n\u003e Regards,\n\u003e\n\u003e Damian Williamson\n\u003e\n\u003e\n\u003e ------------------------------\n\u003e *From:* bitcoin-dev-bounces at lists.linuxfoundation.org \u003c\n\u003e bitcoin-dev-bounces at lists.linuxfoundation.org\u003e on behalf of Sjors\n\u003e Provoost via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\n\u003e *Sent:* Monday, 18 December 2017 10:26 PM\n\u003e *To:* Douglas Roark; Bitcoin Protocol Discussion\n\u003e *Subject:* Re: [bitcoin-dev] A DNS-like decentralized mapping for wallet\n\u003e addresses?\n\u003e\n\u003e Have you thought about combining this with BIP-47? You could associate\n\u003e payment codes with email via DNS.\n\u003e\n\u003e It would be nice if there was a way to get rid of the announcement\n\u003e transaction in BIP-47 and establish a shared secret out of bound. That\n\u003e would simplify things, at the cost of an additional burden of storing more\n\u003e than an HD seed to recover a wallet that received funds this way.\n\u003e\n\u003e Perhaps the sender can email to the recipient the information they need to\n\u003e retrieve the funds. The (first) transaction could have a time locked refund\n\u003e in it, in case the payment code is stale.\n\u003e\n\u003e Sjors\n\u003e\n\u003e \u003e Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e het volgende geschreven:\n\u003e \u003e\n\u003e \u003e On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:\n\u003e \u003e\u003e I was wondering in terms of mass adoption, instead of long wallet\n\u003e \u003e\u003e addresses, maybe there should be a DNS-like decentralized mapping\n\u003e \u003e\u003e service to provide a user at crypto address?\n\u003e \u003e\n\u003e \u003e A few years ago, I was part of an effort with Armory and Verisign to\n\u003e \u003e make something similar to what you're describing.\n\u003e \u003e https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can\n\u003e \u003e find the one and only official draft. I worked on a follow-up with some\n\u003e \u003e changes and some nice appendices, explaining some nice tricks one could\n\u003e \u003e use to make payment management flexible. For various reasons, it never\n\u003e \u003e got published. I think it's an interesting draft that could be turned\n\u003e \u003e into something useful. Among other things, it was able to leverage BIP32\n\u003e \u003e and allow payment requests to be generated that automatically pointed\n\u003e \u003e payees to the correct branch. DNSSEC may have some issues but, AFAIK,\n\u003e \u003e it's as the easiest way to bootstrap identity to a common, reasonably\n\u003e \u003e secure standard.\n\u003e \u003e\n\u003e \u003e --\n\u003e \u003e ---\n\u003e \u003e Douglas Roark\n\u003e \u003e Cryptocurrency, network security, travel, and art.\n\u003e \u003e https://onename.com/droark\n\u003e \u003e joroark at vt.edu\n\u003e \u003e PGP key ID: 26623924\n\u003e \u003e\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171219/cbaee39b/attachment-0001.html\u003e",
"sig": "5810764a5e05749bb6f22e5c9cfb32c241202d7cb29c3707b8549b29159b229a380bde53aa5f5459abadccce54eaeb482deaf17f480116c7416e13981fc7b705"
}