Date: Wed, 2 Mar 2022 05:45:58 +0100 (CET)
From: Prayank <prayank@tutanota.de>
To: dizzle@pointbiz.com
Message-ID: <Mx7wjMe--3-2@tutanota.de>
MIME-Version: 1.0
Content-Type: multipart/alternative; 
 boundary="----=_Part_71095_1499491547.1646196358193"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Decentralized BIP 47 payment code directory
Precedence: list

------=_Part_71095_1499491547.1646196358193
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Peter,

> Regarding to BIP47 there's a newer version (v3 and v4) proposed here: https://github.com/OpenBitcoinPrivacyProject/rfc/blob/master/obpp-05.mediawiki

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

Thanks for sharing the link. Removing toxic change sounds good and certainly an improvement.

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

Crowdfunding platform can also be self hosted like BTCPay server. In this case XPUB is not shared with anyone as long as machine running BTCPay is secure. Problem with this setup is users need to setup BTCPay, running all the time and manage gap limit. No such thing is required in using BIP 47 payment codes.

There is also a [rust library][1] to use BIP 47 and I found the link on twitter yesterday. I think this can be helpful for application developers to implement BIP 47 payment codes in different bitcoin projects.

[1]: https://github.com/rust-bitcoin/rust-bip47


-- 
Prayank

A3B1 E430 2298 178F

------=_Part_71095_1499491547.1646196358193
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
<div>Hi Peter,<br></div><div dir="auto"><br></div><div dir="auto"><div>&gt; Regarding to BIP47 there's a newer version (v3 and v4) proposed here: https://github.com/OpenBitcoinPrivacyProject/rfc/blob/master/obpp-05.mediawiki<br></div><div><br></div><div>&gt; 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.<br></div><div><br></div></div><div dir="auto">Thanks for sharing the link. Removing toxic change sounds good and certainly an improvement.<br></div><div dir="auto"><br></div><div dir="auto">&gt; 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.<br></div><div dir="auto"><br></div><div dir="auto">Crowdfunding platform can also be self hosted like BTCPay server. In this case XPUB is not shared with anyone as long as machine running BTCPay is secure. Problem with this setup is users need to setup BTCPay, running all the time and manage gap limit. No such thing is required in using BIP 47 payment codes.<br></div><div dir="auto"><br></div><div dir="auto">There is also a [rust library][1] to use BIP 47 and I found the link on twitter yesterday. I think this can be helpful for application developers to implement BIP 47 payment codes in different bitcoin projects.<br></div><div dir="auto"><br></div><div dir="auto">[1]: https://github.com/rust-bitcoin/rust-bip47<br></div><div><br></div><div dir="auto"><br></div><div dir="auto">-- <br></div><div>Prayank<br></div><div><br></div><div dir="auto">A3B1 E430 2298 178F<br></div>  </body>
</html>

------=_Part_71095_1499491547.1646196358193--