UPDATE ON THE FUTURE OF BOLTZ 📢 Over the past couple of months, AI-assisted attackers have been targeting Boltz with increasing frequency, intensity and sophistication. Several of these attacks succeeded, but because Boltz is non-custodial, user funds were never at risk. The entirety of the risk was ours, and as a result of the losses incurred, on August 3rd we made the difficult decision to suspend the service to prevent further damage. While working on a plan to bring Boltz back over the past days, we had to accept one painful insight: as a bootstrapped five-person startup, we simply don't have the resources to withstand the current level of attacks in the long run. Today, we are happy to announce that a group of veteran Bitcoiners came forward to help, bringing the capital and engineering power the project needs. They have agreed to take over Boltz and continue the service. Work to find and fix the vulnerabilities is already under way, with the goal of bringing swaps back as soon as possible. As we want to give them the freedom to introduce themselves in their own time, we are not attaching any names today. All original founders of Boltz have stepped down from the company, effective immediately. None of us will have any formal or authoritative role with the Boltz project going forward, and any future open-source participation by us is strictly on a voluntary basis. We are grateful for the community's support all these years, for the patience and understanding of our integrators affected by the disruption of our service, and to everyone who reached out offering support over the past week. It was a hell of a ride, and we are proud of our contributions to the Bitcoin ecosystem. Godspeed to the new Boltz team as they navigate these perilous times. We know Boltz is in good hands. - Kilian, Michael & Karl

Payjoin 1.0.0 has been released! What a journey it has been. Congrats to the PDK team. Expect excellent news on the same to follow shortly. We at BULL been working very hard to improve Payjoin, it's privacy and its adoption across the network.

LLMs are used very successfully to find vulnerabilities in Bitcoin software. Can they also help prove the security of a modern cryptographic library for Bitcoin? To explore this question, @remix7531 and I are publishing libshrincs. libshrincs is a handwritten C library implementing WOTS+C, the one-time signature used by SHRINCS. It is a proof of concept and should not be used in production. Its machine-checked proofs connect the C implementation to an unforgeability theorem. The current theorem does not yet give a full post-quantum security bound. The post and review tutorial describe its current limits. Code and proofs: Review tutorial for the security proof (no Rocq or SSProve background required): @remix7531 has written three excellent posts on the library and verification work: Towards libshrincs The grind was the only detector Choosing a verification toolchain

I am working on something internally @AntidoteBTC codenamed Project Safety Net in response to the Coldcard debacle. I'm going to be a little opaque on details, but this will focus on software coordination rather than hardware. I am willing to put capital behind this to assemble the team and reach MVP. Engineers (front+back) plus PM needed, please DM if curious and/or put the word out.

I'm going to need to raise ticket prices to @tabconf to $256. Inspired by the best hashing algorithm for Bitcoin.. but more importantly because I want to do cool things for the last TAB and want to make sure to cover my nut. Book in the next 2 days to get the lower ticket price!