Why are async payments not the lightning priority what could possibly be more important isn’t that what we need for self custodial mobile zaps

Payjoin Dev Kit payjoin-0.23.0 is out. This release focuses on ergonomic polish. It is now even harder for implementors to make mistakes. It features session persistence as a first-class abstraction async operation, support for decentralized BIP 77 directory operation, and a multi-sender Payjoin client. Bonus: testing coverage improved from unmeasured, to 60%, to over 80% Full release notes:

GitHub

Release Release payjoin-0.23.0 · payjoin/rust-payjoin

Summary This release features a first-class persistence abstraction, wire protocol changes for RFC 9540 support, and better compliance with the BIP...

Many thanks to the 10 contributors who helped with this release.

Bitcoin Dev mailing list is back up

how the heck do I embed a note

Google’s official stance: Bitcoin Dev is “unwanted”

Chat I think I need to eat a frisbee on stream

MEV is just miner alpha and if that alpha either gets to miners at the same time as everyone else or never gets leaked then it seems like the problem goes away so just don’t leak it

Does nostr in current form sufficiently replace mailing lists? In audience quality for me, almost. In pure reach maybe not. Gotta try highlighter. But then how do I link to the rascal post from my own host?

Saying the “other stuff” on nostr is more important than censorship resistant social media is like saying blockchain technology is more important than bitcoin

Nostr boils down to a censorship resistant comms layer. Applying it to batched transaction coordination begs the question: Is coordination censorship the bottleneck to adoption?

Payjoin Probing Attacks: Facts, Mitigations, and Why Payjoin Still Wins for Privacy

Payjoin Probing Attacks: Facts, Mitigations, and Why Payjoin Still Wins for Privacy | Payjoin