Boltz suspended its Bitcoin swap services on Aug. 3 after reporting sustained automated attacks and contained exploits. The company says customer funds were not exposed, but the shutdown still knocked out swap functionality for wallets and services that rely on its backend.
- Swaps halted indefinitely on Aug. 3
- Boltz says no customer funds were exposed
- Aqua, Bull Bitcoin, and ZEUS were affected
- The team blamed sustained automated probing, possibly AI-assisted
This is the part of crypto that gets less worship and more bruises: noncustodial design can protect user funds and still leave the plumbing exposed to abuse. Your coins may be safe. The service around them can still get battered into the dirt.
Boltz runs noncustodial Bitcoin bridge infrastructure connecting Bitcoin mainnet, the Lightning Network, Liquid, and other supported networks. In plain English, it helps users move value across different Bitcoin-related systems without depositing funds with a custodial exchange. That model is one reason people use it in the first place. It removes a giant honeypot from the middle of the setup.
According to Boltz, the attack pressure had been building for months and then picked up sharply in recent days. The company described the suspected attackers as “multiple resourceful groups” and said it could not “responsibly restore swaps” while the system remained under active attack.
That language should be treated carefully. Boltz says the activity looked automated and AI-assisted, but no independent technical proof has been published in the materials available here. So yes, the company clearly thinks the attackers were using faster, machine-driven tooling. No, that is not the same thing as a verified forensic conclusion. Cybersecurity gets enough smoke without people setting off extra flares.
Boltz also said it identified and contained multiple exploits, though it did not publish technical details about what was hit, how it was hit, or what conditions would be required for a restart. The company has not given a reopening date. It also has not provided a remediation timetable or a detailed vulnerability list.
The company said no customer funds were exposed and that it absorbed the losses from the contained exploits because it is a fully bootstrapped business. That is the good news. The bad news is that noncustodial does not mean invulnerable. It means an attacker has a much harder time stealing user funds directly, but they can still knock the system sideways, force a shutdown, and leave downstream apps scrambling.
This matters because Boltz is not just one app sitting politely in a corner. Other wallets and services depend on it as shared infrastructure. When that backend goes dark, the fallout spreads fast.
Bull Bitcoin said the shutdown temporarily disabled Lightning payments and conversions between Liquid Bitcoin and onchain Bitcoin. It also said standard Bitcoin transfers, Liquid transfers, wallet restoration, and storage functions continued operating normally. Aqua notified users that its swap functions were affected. ZEUS disabled its own deployment of the open source Boltz stack. Neither wallet reported customer asset losses.
Boltz had first warned on Aug. 1 about a bug in its Ethereum Virtual Machine integration and initially disabled swaps involving USDT, USDC, WBTC, TBTC, and RBTC. At that stage, Bitcoin, Lightning, and Liquid swaps remained operational. Two days later, the company stopped all swap services.
For readers wondering why a Bitcoin-focused service would even have EVM exposure: because some swap infrastructure touches Ethereum-compatible assets and integrations too. That is the messy reality of crypto plumbing. Even “Bitcoin-native” tools often end up connected to a whole pile of other systems because users want interoperability, not ideological purity in a vacuum.
The deeper lesson here is not that noncustodial tools are broken. It is that they are still operational systems, and operational systems can fail under pressure. Noncustodial design protects custody, not uptime. It reduces the chance of a catastrophic fund loss, but it does not guarantee continuity when the backend is under sustained attack.
There is also a more uncomfortable truth: shared infrastructure can create a single point of failure across multiple brands. A wallet can look independent on the surface while quietly leaning on the same swap backend as everyone else. When that backend breaks, the “different” products suddenly have the same problem.
Open-source Bitcoin infrastructure cuts both ways. Transparency helps review, integration, and reuse, and that is a real strength. But public code also gives attackers more to inspect and test at scale. When automated tooling can probe relentlessly, small teams can get overwhelmed before they can fully understand the attack surface. That is not an argument against open source. It is an argument for treating security and redundancy as real engineering work instead of brochure copy.
For users, the practical takeaway is straightforward: know what your wallet depends on. If a swap provider is the hidden backbone for payments or cross-network transfers, an outage there can break functionality even when your own funds remain untouched. That distinction matters, especially for people who assume “noncustodial” means “nothing can go wrong.”
What happened to Boltz? Boltz suspended its swap services on Aug. 3 after reporting sustained automated attacks and contained exploits. It said the pressure had become too intense to safely keep swaps running.
Were customer funds stolen? No. Boltz said no customer funds were exposed, and that it absorbed the losses from the contained exploits itself.
Was AI definitely involved? Boltz says the attacks appeared automated and AI-assisted, but that claim has not been independently verified in the material available here. It should be treated as Boltz’s assessment, not settled fact.
Why did this affect wallets like Aqua and Bull Bitcoin? Those services rely on Boltz for swap functionality. When the shared backend stopped, their swap-related features were disrupted even though other wallet functions kept working.
Does noncustodial mean immune from hacks? No. Noncustodial systems are designed so the operator does not hold customer funds, which lowers the risk of theft. But the service can still be attacked, degraded, or forced offline.
Will swaps come back soon? Boltz has not given a reopening date. Without a published remediation plan or restart conditions, users and integrators are left waiting for proof that the system is safe to run again.
Boltz’s shutdown is a useful reality check for crypto. Noncustodial infrastructure can protect user funds while still failing under sustained pressure, and shared backend risk can spread faster than the marketing deck ever admits. That is not a reason to abandon the model. It is a reason to build it like the internet may actually fight back.
Further reading
A few related angles worth keeping an eye on:
- Boltz halts swaps as AI attacks outpace its team
- Boltz halts Bitcoin swaps indefinitely due to overwhelming pressure
- AI-assisted attacks force Bitcoin bridge Boltz to halt
- Mexican Government breach via Claude-assisted attack
- Square brings Bitcoin payments to 1 million U.S. merchants
- Lightning Network: Bitcoin’s scalability solution and its challenges
