Payjoin DevKit ships, and Bitcoin privacy gets a little less fake
Payjoin is moving from clever theory to usable Bitcoin software. Dan Gould’s Payjoin DevKit now ships with an async protocol and oblivious HTTP relay support that make it much more practical for mobile wallets, while also making common chain-tracing assumptions harder to lean on.
- Privacy: breaks the common input ownership heuristic
- Mobile: async Payjoin works better on phones
- Live use: Bull Bitcoin has shipped support; Cake Wallet is also referenced
- Efficiency: can reduce on-chain waste in some cases
- Roadmap: multi-party Payjoin is next
For years, Bitcoin privacy tools have had a nasty habit of being brilliant and inconvenient at the same time. Payjoin is trying to fix that. Instead of a payment looking like a plain one-way transfer from sender to recipient, the receiver helps construct the transaction. That matters because it disrupts common input ownership, the old blockchain-analysis trick that assumes multiple inputs in one transaction usually belong to the same wallet owner.
That assumption is one of the main ways analysts cluster wallets and trace spending patterns. Payjoin doesn’t make Bitcoin invisible. It does, though, make lazy surveillance a lot less reliable. And in Bitcoin privacy, making the enemy work harder is often the whole point.
What changed with the DevKit
The big technical update is the move to an async protocol paired with an oblivious HTTP relay. In plain English, the sender and receiver no longer need to be online at the exact same moment for the payment handshake to work. That’s a big deal for mobile wallets, where apps sleep, connections drop, and users are not sitting there babysitting a terminal like it’s 2013.
Oblivious HTTP also helps limit metadata leakage during coordination. Payjoin still uses HTTP-based messaging to exchange the details needed to build the transaction, but the relay layer is designed so the service handling the request is not trivially able to tie the request to the sender’s IP address. That is not magic anonymity sauce. It is just a decent privacy layer, which is more than enough to be useful.
Bull Bitcoin’s own announcement gives the clearest public confirmation of the newer model. It says the company has shipped serverless asynchronous Payjoin (BIP77) in its mobile wallet, and it credits Dan Gould and the Payjoin Dev Kit project for the design.
That BIP number matters. The newer asynchronous flow is associated with BIP77, while the earlier interactive Payjoin setup is commonly referred to as BIP78. If you mix those up in front of Bitcoin nerds, they will notice immediately. They always do.
Why mobile support is the real breakthrough
Older Payjoin setups were awkward because the receiver often had to be online and reachable at the right moment. That was fine for some merchant setups, but it was a lousy fit for ordinary wallet users. Bull Bitcoin says the newer model removes that pain by using a Payjoin Directory and an Oblivious HTTP server so the receiver does not need to run their own always-on server.
That is what “serverless” means here. Not “no servers exist, ” because that would be nonsense. It means the wallet user does not need to maintain their own public-facing coordination server just to receive a private Payjoin payment. A transaction can also be paused and resumed later if one side is offline, which makes the whole thing much more realistic on phones.
That usability shift is the difference between a protocol people admire and a protocol people actually ship. The crypto graveyard is full of beautiful ideas that died because the workflow was a pain in the ass.
Where it is live today
Bull Bitcoin is the clearest confirmed deployment in the material provided. The company says it has implemented Payjoin V2, or BIP77, in its mobile wallet. Cake Wallet is also referenced as an adopter, but the supporting details are thinner here, so Bull Bitcoin is the one to treat as confirmed and Cake Wallet as mentioned rather than exhaustively documented in the available material.
That distinction matters because deployment claims in crypto can get sloppy fast. “Supported somewhere” and “shipped in a live wallet” are not the same thing. One is a roadmap bullet. The other is software people can use.
For readers who want the base definition, the Bitcoin Wiki page on PayJoin is the old-school reference point, while the newer design discussion in From Two-Party Protocol to Multiparty Framework shows where the protocol is heading next.
Privacy gains without the fairy dust
Payjoin is appealing because it improves privacy without asking users to do anything exotic. It can also improve fee efficiency in some cases by adjusting the transaction so the final on-chain result is less revealing and the net amount settled on-chain is smaller than a plain one-way payment would be.
But let’s not turn that into another crypto miracle story. Payjoin does not guarantee big fee savings every time. The actual outcome depends on the transaction shape, wallet behavior, and network conditions. Anyone promising precise savings here with a straight face is probably selling something.
It also does not solve every fingerprinting problem. Breaking common input ownership is useful, but chain analysis firms have more than one trick in the bag. That is why the caution around remaining fingerprinting heuristics is healthy. Better privacy is not the same thing as solved privacy.
Why developers should care
The point of the Payjoin DevKit is not just to make a neat protocol easier to talk about. It is to make it easier to ship. According to the episode framing, developers can integrate the library in under ten thousand lines of code. That is an attractive claim, but it should be treated as a rough integration pitch unless independently verified.
Still, the underlying message is solid: privacy tools win when wallet teams can implement them without wrecking their codebase or their weekends. A brilliant protocol that is too painful to integrate usually ends up admired from a distance and ignored in practice.
That is why this update matters. It is not merely about cryptographic elegance. It is about deployment, mobile usability, and reducing the friction that has kept Payjoin from becoming a default Bitcoin behavior.
What comes next
The roadmap points toward multi-party Payjoin, which would extend the model beyond a simple two-party payment flow. If that becomes practical, the privacy and efficiency benefits could grow further. If it stalls, well, the crypto world has a long and distinguished history of “next steps” that never leave the whiteboard.
For now, the important part is simpler: Payjoin is shipping. That makes it one of the more meaningful Bitcoin privacy developments in play right now, not because it promises utopia, but because it quietly makes the network more private, more usable, and a little less obedient to chain-surveillance laziness.
Related reporting
Bitcoin privacy is under pressure from more than just chain analytics. In a separate development, OpenAI Robotics Chief Resigns Over AI Surveillance in Military Deal showed how surveillance creep is not some abstract paranoia fantasy. It is a live political and technical problem. And when the state comes knocking, crypto privacy advocates tend to get very short on patience, for good reason.
That same pressure is why the crackdown on wallet developers has sparked so much outrage. Bitcoin Privacy Shock: Samourai Wallet’s Keonne Rodriguez and Samourai Wallet Founders Face 5 Years: Bitcoin Privacy Tools Targeted by Feds are part of the broader warning shot: privacy software is increasingly treated like contraband by people who would prefer Bitcoin behave like a surveillance-friendly bank ledger with better branding.
Key takeaways
-
Why does Payjoin matter for Bitcoin privacy?
It breaks the common input ownership heuristic, which makes transaction clustering less reliable. That does not make Bitcoin anonymous, but it does make tracing harder. -
What changed to make Payjoin better on mobile?
The async protocol lets payments be paused and resumed when users are back online, and oblivious HTTP helps reduce metadata leakage during coordination. -
Where is Payjoin already live?
Bull Bitcoin has publicly announced support for serverless asynchronous Payjoin in its mobile wallet. Cake Wallet is also referenced, but the confirmation is thinner in the available material. -
Does Payjoin solve all fingerprinting issues?
No. It breaks one major heuristic, but blockchain analysis has other ways to infer patterns. Privacy improves, but it is not finished. -
Is Payjoin only about privacy?
No. It can also improve fee efficiency in some cases by reducing on-chain waste through collaborative transaction construction.
Bitcoin does not usually advance through fireworks. It advances through tools that leak less, work better, and give users one fewer reason to trust nosy middlemen. Payjoin DevKit is pushing in exactly that direction.
