Categories: Bitcoin Latest News

Implementing Reusable Payment Codes In Bitcoin Wallets To Improve User Privacy

The Bitcoin Development Kit is planning to implement BIP47 which would allow users to receive via a static payment code and interact with more privacy.

The below is a direct excerpt of Marty’s Bent Issue #1182: “BDK plans to add BIP47 support.” Sign up for the newsletter here.

Source

This is very encouraging to see; the team working on the Bitcoin Development Kit (BDK) seem as if they are going to merge in support for BIP47, which would allow wallet developers who are building their wallets leveraging the BDK to easily implement reusable payment codes. This would allow bitcoin users to interact with each other in a more private way by enabling users to receive via a static payment code that does not reveal the actual address a UTXO ends up in.

To date (and to the best of my knowledge), the only popular wallet to enable BIP47 has been Samourai Wallet. Recently, there has been a surge in interest for more wallets to begin implementing this feature. Historically, BIP47 has been controversial because many developers think that if BIP47 gets wide adoption it will bloat the chain and drive fees higher due to the amount of data needed to create the payment codes via OP_RETURN. As fees have remained low for an extended period of time and bitcoiners seek out better privacy tools as authoritarian governments like Canada seem keen on using their financial systems to execute political witch hunts, it seems that many are more than comfortable with this tradeoff that comes with BIP47.

The beauty of the BDK team adding BIP47 support is that it should make it easier for a number of wallets to implement the payment codes without having to build it from scratch. It will be interesting to see how many wallets begin implementing BIP47 once support is officially merged into the BDK. And whether or not they do it quickly. At the very least, the market will get some very intriguing insight into how this feature affects the chain at scale if it gets material adoption. Best case scenario is that it significantly increases the ability for users to transact more privately using many different wallets and it doesn’t affect the chain state too much due to the fee market acting as a forcing function (as fees go higher individuals become less incentivized to create transactions with OP_RETURN data included).

We will keep you freaks updated as this progresses.

Read More

The Bitcoin Development Kit is planning to implement BIP47 which would allow users to receive via a static payment code and interact with more privacy.

Author:

Marty Bent

Publish date:

Mar 23, 2022

The Bitcoin Development Kit is planning to implement BIP47 which would allow users to receive via a static payment code and interact with more privacy.

The below is a direct excerpt of Marty’s Bent Issue #1182: “BDK plans to add BIP47 support.”Sign up for the newsletter here.

This is very encouraging to see; the team working on the Bitcoin Development Kit (BDK) seem as if they are going to merge in support for BIP47, which would allow wallet developers who are building their wallets leveraging the BDK to easily implement reusable payment codes. This would allow bitcoin users to interact with each other in a more private way by enabling users to receive via a static payment code that does not reveal the actual address a UTXO ends up in.

To date (and to the best of my knowledge), the only popular wallet to enable BIP47 has been Samourai Wallet. Recently, there has been a surge in interest for more wallets to begin implementing this feature. Historically, BIP47 has been controversial because many developers think that if BIP47 gets wide adoption it will bloat the chain and drive fees higher due to the amount of data needed to create the payment codes via OP_RETURN. As fees have remained low for an extended period of time and bitcoiners seek out better privacy tools as authoritarian governments like Canada seem keen on using their financial systems to execute political witch hunts, it seems that many are more than comfortable with this tradeoff that comes with BIP47.

The beauty of the BDK team adding BIP47 support is that it should make it easier for a number of wallets to implement the payment codes without having to build it from scratch. It will be interesting to see how many wallets begin implementing BIP47 once support is officially merged into the BDK. And whether or not they do it quickly. At the very least, the market will get some very intriguing insight into how this feature affects the chain at scale if it gets material adoption. Best case scenario is that it significantly increases the ability for users to transact more privately using many different wallets and it doesn’t affect the chain state too much due to the fee market acting as a forcing function (as fees go higher individuals become less incentivized to create transactions with OP_RETURN data included).

We will keep you freaks updated as this progresses.

Feedzy

Recent Posts

Bitcoin ETFs crushed by billions in outflows as Treasuries stifle interest-rate cut hopes

Your day-ahead look for May 26, 2026Read MoreCoinDesk: Bitcoin, Ethereum, Crypto News and Price Data[#item_full_content]

52 minutes ago

Bitcoin risks another lower high as stocks rally, AI tokens outperform

The bitcoin price chart is forming a potential lower high while ether languishes in a…

2 hours ago

Bitcoin caught between critical onchain support and an options showdown

Heavy supply concentration and large options positioning continue to suppress volatility and keep bitcoin range-bound.Read…

3 hours ago

Bitcoin At A Crossroads: Two Key Levels Will Define BTC’s Next Major Move, Analyst Says

As Bitcoin (BTC) recovers from its recent drop below the $75,000 support, some market observers…

6 hours ago

Bitcoin Fake Breakdown Could Be Setting Up Next Major Rally

Bitcoin’s recent drop below key support may have been more than just a bearish breakdown.…

7 hours ago

Bitcoin stalls near $76,500 as muted trading points to macro wait-and-see

Enflux says “the bid is there” but no one is adding size, while Glassnode data…

8 hours ago