<oembed><type>rich</type><version>1.0</version><title>Boltz wrote</title><author_name>Boltz (npub1ps…q8970)</author_name><author_url>https://yabu.me/npub1psm37hke2pmxzdzraqe3cjmqs28dv77da74pdx8mtn5a0vegtlas9q8970</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>Update: Boltz will stay disabled until further notice.&#xA;&#xA;Our API remains available to process refunds cooperatively. In any case, unilateral refunds will work, as they do not depend on our infrastructure.&#xA;&#xA;Our support team stays reachable.&#xA;&#xA;To be clear: this is not a response to a single incident. Over the past months we have seen a steady rise in automated, AI-assisted probing of our infrastructure, and we have dealt with several exploits. Each was contained, but the pattern is clear: attackers now iterate faster than a team our size can find and patch. In the past few days alone we saw a drastic acceleration, and we do not believe this asymmetry will reverse. After reviewing the results of our own recent security scans, we cannot responsibly re-enable Boltz swaps, especially as we are being actively targeted by what appear to be multiple resourceful groups while we race to deploy fixes.&#xA;&#xA;What we are seeing is a major paradigm shift for Bitcoin services operating on an open source stack, and it needs careful analysis. Do not expect swap services to resume shortly.&#xA;&#xA;To be explicit: no user funds were ever at risk. Boltz is non-custodial by design. And as a fully bootstrapped company, the losses were ours alone.&#xA;&#xA;We don&#39;t know yet how things will continue from here, but we&#39;ll keep you posted as soon as we have had the time to catch our breath and make a decision 🙏&#xA;&#xA;&#xA;nostr:nevent1qvzqqqqqqypzqrphra0dj5rkvy6y86pnr39kpq5w6eaumma2z6v0kh8f67ejshlmqqs0pwe2ankgd5a6e4uaelhtwyhgu5sfpn8ayccx934t8uls54xjhfsyxm3s3 </html></oembed>