Stoked to announce the launch of Payjoin Dev Kit to ship Payjoin into every piece of Bitcoin software. Scale Bitcoin, save fees, and preserve privacy today. https://payjoindevkit.org/blog/pdk-an-sdk-for-payjoin-transactions/
They are all delicious ๐๐
Gm #coffeechain
Hand delivered proof of work from nostr:npub1a6zkqnuwcmjwynuw4u4xyngy9675x8dwgj87z9me4h8mdwmc2a0q8mvhjk in generous support of open source software development gets me going. 
> tfw you post localhost endpoint in public forum
just preordered my Vision Pro
thank you for your service
bitcoin needs an allegorical novel
what is the point of bicycles if automobiles exist?
do you have a minimim example of this? I have seen xcashu if thatโs still state of the art
encrypted notes could make sense. seems like a tradeoff introducing complication to discovery & fallback for censorship resistance from a relay DoS
just websockets & http, nostr seemed like an extra dependency + ser/de overhead, but if there were a good reason to use it I could be convinced
Announcing REElay ๐ก: BIP 78-compatible Gullible (pre-serverless) Payjoin PoC https://github.com/payjoin/rust-payjoin/pull/78 This proof of concept demonstrates the ability to receive a payjoin using a relay instead of hosting a public https or onion endpoint. I intend this to be an easy way to receive payjoin in testing environments and potentially as a BIP 78 payjoin v1 compatible fallback for a v2 Serverless Payjoin spec. 
upload to google drive and link to nostr. if the link goes down you can post a new one in reply to the original note. nostr is a transport protocol not a storage one
