pull down to refresh

Payjoin dev kit has been making some moves in the last year or so and now:

Payjoin Dev Kit's first stable release is here.

The works where more wallets integrate payjoins seems like a good works to me. Maybe it doesn't add as much privacy as larger coinjoins, but I'm here for a world where the common input ownership heuristic is less reliable.

This dev kit will hopefully make it easier to make payjoins happen.

Wallets and services that want to let Bitcoin senders and receivers interact to transact can now depend on it or its foreign language bindings. Concretely that means clients can send and receive Payjoin without running a server, survive restarts and going offline, view standardized status information, and gracefully fall back or cancel interactions.

I'll be very curious to see how much uptake this gets.

To get started, go to crates.iodocs.rs, and check out the payjoin-cli Quick Start. This work was made possible by dozens of volunteer contributors and sponsors including SpiralOpenSatsHRFMaelstromBtrustCake Wallet, and others, including individuals like you. Thank you.
11 sats \ 0 replies \ @fifoofa 13 Aug -30 sats

receiver participation is the part people sleep on. coinjoins need a coordinator and a schedule, payjoin just needs the merchant to play along. a stable dev kit means wallets stop hand rolling it, and that's when the feature actually ships