Boltz Suspends Bitcoin Swaps Indefinitely as AI Attacks Outpace Patching
Non-custodial Bitcoin swap provider Boltz suspended all services indefinitely on August 3 after months of AI-accelerated attacks overwhelmed its ability to patch vulnerabilities faster than attackers could find them.
Non-custodial Bitcoin swap provider Boltz shut down all services on August 3 after AI-assisted attackers iterated through vulnerabilities faster than its small team could close them.
Key takeaways
- Boltz suspended all Bitcoin mainchain, Lightning, and Liquid swap services indefinitely on August 3, 2026, citing months of AI-assisted attacks that outpaced its patching capacity.
- No user funds were ever at risk. Boltz's HTLC-based non-custodial design protected user assets throughout; the company absorbed operational losses on its own books, and the refund API remains live.
- The shutdown affected downstream wallets and services including ZEUS, Aqua, and Bull Bitcoin, all of which relied on Boltz infrastructure for swap functionality.
Boltz, one of the primary non-custodial Bitcoin swap providers routing atomic swaps between Bitcoin mainchain, the Lightning Network, and Liquid, halted all services on August 3 after what it described as a months-long escalation of AI-powered attacks. The team concluded it could not responsibly re-enable swaps while being actively targeted.
The situation is a clean separation between two things that often get conflated: the cryptographic layer worked exactly as designed, and the operational layer still went dark.
The Escalation That Forced the Shutdown
Boltz disabled its EVM-side swaps (USDT, USDC, TBTC, WBTC, RBTC) on August 1, citing a bug in its EVM integration. Lightning, Liquid, and on-chain Bitcoin swaps stayed live. Two days later, at approximately 3:24 p.m. ET on August 3, Boltz posted that all swap services were "unavailable until further notice" with no elaboration.
That evening, the team posted a full explanation:
"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."
The team did not characterize this as a recoverable operational hiccup. "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," the statement read.
Boltz described "multiple resourceful groups" actively targeting it simultaneously. The losses from exploits were absorbed internally. As the team stated directly: "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."
The downstream effect was immediate. Lightning wallet ZEUS went offline citing Boltz downtime. Bull Bitcoin CEO Francis Pouliot and JAN3 CEO Samson Mow (whose Aqua wallet integrates Boltz) both stated they were working to restore impaired swap functionality.
What the Shutdown Actually Demonstrates
The non-custodial design did its job. Users holding funds through pending swaps were protected by the underlying hashed timelock contracts (HTLCs). The refund API remained online; unilateral refunds work independently of Boltz's infrastructure. The cryptographic guarantees held; this is a story about operational sustainability under machine-speed attack.
A fully bootstrapped team building open-source infrastructure cannot field a 24/7 AI red team. Boltz said plainly it does not believe the offensive-defensive asymmetry will reverse. That sentence deserves to sit on its own: attackers using AI can probe an open-source codebase continuously, find novel exploit paths faster than humans can audit, and iterate on failed attempts in near-real time. A small team cannot match that tempo indefinitely.
Earlier this summer, a Coldcard Mk3 security warning showed how quickly a discovered vulnerability can translate to real losses when attackers move fast. The attack surface for any stateful second-layer service compounds with complexity. The more conditional logic a swap protocol carries, the more paths an automated prober can trace.
The practical distinction matters for anyone routing funds through second-layer infrastructure: non-custodial means your funds are cryptographically protected, not that the service will remain available. Custody on-chain. Use swap infrastructure for what you need. Don't depend on uptime from a bootstrapped team facing machine-speed adversaries without equivalent machine-speed defenses.
Boltz's TVL at the time of the announcement was approximately $180,860 per DeFiLlama, a relatively modest figure that underscores the broader point. Boltz is a small, well-designed, freedom-tech-aligned service being priced out of operability by an asymmetry it did not create and cannot easily close.
The falsifiable version of that thesis: if Boltz re-enables swaps within 60 days using existing staff and open-source tooling alone with no further exploits, the asymmetry argument is too strong. If the community develops shared AI-assisted defensive tooling that makes continuous automated auditing accessible to bootstrapped teams, the gap narrows. Neither has happened yet.
What to Watch
Boltz's next public update will be the clearest signal. A quick return with a narrow patch suggests the team found a discrete vulnerability. An extended silence, or a statement about needing new defensive infrastructure, confirms the asymmetry thesis and sets a harder precedent for every small team running open-source Bitcoin swap infrastructure. Anyone building in this space should be watching whether the response is a fix or a rearchitecture.
Sources
Frequently Asked Questions
Yes. Boltz's non-custodial design means user funds are held in cryptographic contracts (HTLCs) throughout a swap, not in Boltz's custody. If a swap did not complete, the refund API remains live and unilateral refunds work independently of Boltz's main infrastructure. No user funds were lost.
A hashed timelock contract locks funds with two conditions: a cryptographic secret (the hash preimage) or a time expiry. If a swap does not complete within the time window, funds return to the sender automatically without any action from Boltz. The attacker cannot redirect funds because the contract enforces the conditions on-chain regardless of what happens to Boltz's servers.
ZEUS, Aqua (by JAN3), and Bull Bitcoin all relied on Boltz infrastructure for swap functionality and reported impaired or disabled swap capabilities following the shutdown. Any Lightning or Liquid wallet that routes through Boltz's swap infrastructure is affected until service resumes.
