📅 Original date posted:2017-12-18
📝 Original message: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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171218/376f96f6/attachment.sig>;
Sjors Provoost [ARCHIVE] /
npub1ux…7wq7p
2023-06-07 18:08:02
in reply to nevent1q…6xaj
Author Public Key
npub1uxks6rvrzqljyfp92sffgqypf8fpts0pv2dshvmmnrse76v0avlqy7wq7pPublished at
2023-06-07 18:08:02Event JSON
{
"id": "135b2d584d5299243e282d9575892c469bd0ab5c4c75cb7241f163f44cd19fd4",
"pubkey": "e1ad0d0d83103f222425541294008149d215c1e1629b0bb37b98e19f698feb3e",
"created_at": 1686161282,
"kind": 1,
"tags": [
[
"e",
"aa26ac7d2c56b5e93f58d0a4616f8108b14cd88c555a82aa7113c62ff7cbed00",
"",
"root"
],
[
"e",
"52c0cbefcd57b7155dd3a3187b880096b222f29bcda9221d7f927a8a4bace4f6",
"",
"reply"
],
[
"p",
"533e45ffeb94bc88c14af70b25994838170e7910c1273994b63bce468eac2230"
]
],
"content": "📅 Original date posted:2017-12-18\n📝 Original message:Have you thought about combining this with BIP-47? You could associate payment codes with email via DNS.\n\nIt 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.\n\nPerhaps 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.\n\nSjors\n\n\u003e Op 1 dec. 2017, om 04:08 heeft Douglas Roark via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e het volgende geschreven:\n\u003e \n\u003e On 2017/11/30 14:20, mandar mulherkar via bitcoin-dev wrote:\n\u003e\u003e I was wondering in terms of mass adoption, instead of long wallet\n\u003e\u003e addresses, maybe there should be a DNS-like decentralized mapping\n\u003e\u003e service to provide a user at crypto address?\n\u003e \n\u003e A few years ago, I was part of an effort with Armory and Verisign to\n\u003e make something similar to what you're describing.\n\u003e https://tools.ietf.org/html/draft-wiley-paymentassoc-00 is where you can\n\u003e find the one and only official draft. I worked on a follow-up with some\n\u003e changes and some nice appendices, explaining some nice tricks one could\n\u003e use to make payment management flexible. For various reasons, it never\n\u003e got published. I think it's an interesting draft that could be turned\n\u003e into something useful. Among other things, it was able to leverage BIP32\n\u003e and allow payment requests to be generated that automatically pointed\n\u003e payees to the correct branch. DNSSEC may have some issues but, AFAIK,\n\u003e it's as the easiest way to bootstrap identity to a common, reasonably\n\u003e secure standard.\n\u003e \n\u003e --\n\u003e ---\n\u003e Douglas Roark\n\u003e Cryptocurrency, network security, travel, and art.\n\u003e https://onename.com/droark\n\u003e joroark at vt.edu\n\u003e PGP key ID: 26623924\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\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: Message signed with OpenPGP\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171218/376f96f6/attachment.sig\u003e",
"sig": "9161c7e4a75fa9b240680f2b353a0e61e17528d78d22ddf7bc0d38d20a710501b45ddaf24514022ea3d689adaab1bfd0fd0c21bcf67e645bf1cd42255c1a3177"
}