![\"\"](\"https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2026\/08\/image-27.png\")
<\/figure>\n\n\n\nAugust 12, 2026 \u00b7 3 min read<\/p>\n\n\n\n
Dan Gould<\/a><\/p>\n\n\n\n Three years after inception<\/a>, Payjoin Dev Kit’s first stable release is here. The Rust library for BIP 77<\/a> and BIP 78<\/a> Payjoin is published as 1.0.0<\/a>. Wallets and services that want to let Bitcoin senders and receivers interact to transact can now depend on it or its foreign language bindings<\/a>. 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.<\/p>\n\n\n\n Payjoin is the base case for interactive transaction construction where both sender and receiver contribute. It creates an opportunity to save blockspace fees with multi-contributor batching, secure transaction cut-through settlement, and preserve privacy by breaking the assumption Satoshi left in the whitepaper<\/a> that transaction inputs all come from the same owner.<\/p>\n\n\n\n There is much more to do. This release commits to the core This API was hard earned through pilot integrations with Bull Bitcoin Mobile<\/a> and Cake Wallet<\/a>, which are compatible with the payjoin-cli reference. A number of other integrations are in flight and in review. 1.0 stability allows us to focus efforts on multiplying integrations from here.<\/p>\n\n\n\n To get started, go to crates.io<\/a>, docs.rs<\/a>, and check out the Development on Payjoin which allows transactions that obfuscate amount and payee giving some privacy to transactions that support it. Basically, both parties contribute funds to a transaction so it’s not clear who was paid, concealing the refund, kind of like a mini coinjoin and can be a feature of normal transactions giving some privacy and […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-18454","post","type-post","status-publish","format-standard","hentry","category-tech"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"featured_image_src":null,"author_info":{"display_name":"Jason","author_link":"https:\/\/jasonsblog.ddns.net\/index.php\/author\/jturning\/"},"_links":{"self":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/18454","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/comments?post=18454"}],"version-history":[{"count":1,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/18454\/revisions"}],"predecessor-version":[{"id":18456,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/18454\/revisions\/18456"}],"wp:attachment":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/media?parent=18454"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/categories?post=18454"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/tags?post=18454"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}payjoin<\/code><\/a> state machine API including the persisted session format so that sessions written today replay in future versions. Other Payjoin Dev Kit software is not yet stable, including our payjoin-ffi<\/code><\/a> bindings library, the payjoin-cli<\/code><\/a> end-to-end reference implementation, and the payjoin-mailroom<\/code><\/a> server that anyone can host so that clients don’t have to; nor is the BIP 77 spec<\/a>, though its Draft status is nearing graduation to Complete.<\/p>\n\n\n\npayjoin-cli<\/code> Quick Start<\/a>. This work was made possible by dozens of volunteer contributors and sponsors including Spiral<\/a>, OpenSats<\/a>, HRF<\/a>, Maelstrom<\/a>, Btrust<\/a>, Cake Wallet<\/a>, and others, including individuals like you. Thank you.<\/p>\n","protected":false},"excerpt":{"rendered":"