From: Peter <dizzle@pointbiz•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Decentralized BIP 47 payment code directory
Date: Tue, 01 Mar 2022 17:31:53 +0000 [thread overview]
Message-ID: <R3RZz9X_TWvYDZP-k1ZM-li_xpmw9n6DLkd5MDTiDN7Nu-WfFzGPp-Nuy-UFx9z1TOovIvvoQ1riAKOUrLxKUZ3vCIiTWY-ZRR_T4F1qNR8=@pointbiz.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]
Hi,
Regarding to BIP47 there's a newer version (v3 and v4) proposed here:
https://github.com/OpenBitcoinPrivacyProject/rfc/blob/master/obpp-05.mediawiki
This newer version addresses some issues from v1.
Now the notification from Alice to Bob is a transaction from Alice to Alice as a bare 1 of 3 multisig. The other 2 pubkeys represent Alice's payment code and Bob's payment identifier. Eliminating the toxic change issue.
The overhead is a one time 64 byte for the two pubkeys. This overhead would be amortized over the lifetime of the Alice / Bob relationship.
Additionally the first economic payment from Alice to Bob can be included along with the notification transaction.
Payment codes are recoverable from the bip32 seed. No extra backups required.
This new version is in production with Samourai wallet.
This BIP47 v3 allows Alice to receive Bob's address without exposing her IP/identity to Charlie who can watch Alice receive the payment code material from Bob without knowing if Alice acted by sending a payment to Bob.
An xpub doesn't accomplish this because if you have your xpub in a crowdfunding platform the platform or anyone who hacks it can identify your payments. With the payment code you can associate yourself publicly with your payment code and no one (who is not the sender) will know if you received funds as your payment code is not visible in the blockchain.
Regards
Peter
[-- Attachment #2: Type: text/html, Size: 1897 bytes --]
next reply other threads:[~2022-03-01 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-01 17:31 Peter [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-02 4:45 Prayank
2022-02-28 14:56 Prayank
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='R3RZz9X_TWvYDZP-k1ZM-li_xpmw9n6DLkd5MDTiDN7Nu-WfFzGPp-Nuy-UFx9z1TOovIvvoQ1riAKOUrLxKUZ3vCIiTWY-ZRR_T4F1qNR8=@pointbiz.com' \
--to=dizzle@pointbiz$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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