Boltz has suspended its Bitcoin swap service until further notice after reporting a sustained increase in automated and AI-assisted attacks against its infrastructure. The decision followed months of repeated security pressure rather than one isolated breach. Boltz says attackers began iterating faster than its small team could identify and patch weaknesses, leading it to conclude that restoring swaps immediately would be irresponsible.
The non-custodial provider supports atomic swaps across Bitcoin, the Lightning Network and Liquid, among other Bitcoin-linked networks. Boltz said previous exploits caused losses to the company but did not place customer funds at risk. That no-user-loss assessment remains a company statement rather than an independently verified forensic conclusion, since Boltz has not released a detailed technical incident report covering the attacks.
Update: Boltz will stay disabled until further notice.
Our API remains available to process refunds cooperatively. In any case, unilateral refunds will work, as they do not depend on our infrastructure.
Our support team stays reachable.
To be clear: this is not a response to a… https://t.co/kv8zWt4bym
— Boltz – Non-Custodial Bitcoin Bridge (@Boltzhq) August 3, 2026
Refund Paths Remain Available While New Swaps Stay Offline
Boltz has kept its API online to process cooperative refunds for unfinished swaps, while unilateral refunds remain functional without depending on company infrastructure. Its documentation emphasizes that integrations must leave end users in control of the information and keys required to recover failed swaps. The shutdown therefore interrupts new swap activity without eliminating the recovery path for funds already committed to existing transactions.
The distinction matters because operational downtime and custody loss represent different risks. Boltz’s swap architecture uses cryptographic conditions that allow users to reclaim funds after failed transactions, while Taproot-based cooperative refunds can accelerate that recovery when both parties participate. Non-custodial architecture can limit financial exposure without making the supporting infrastructure immune to attack or service disruption.
DeFiLlama currently shows approximately $262,000 in total value locked for Boltz and labels the protocol as deprecated, with its tracked balance split between Rootstock and Arbitrum. That TVL figure does not measure Boltz’s complete historical swap activity across Bitcoin, Lightning and Liquid, so it should not be interpreted as the total economic value affected by the shutdown.
Boltz Frames Attack Wave as a Security Model Problem
The team described the acceleration as a wider challenge for Bitcoin services operating on open-source software, arguing that increasingly automated attackers can identify weaknesses and adapt faster than smaller development teams can respond. That characterization is Boltz’s assessment of the threat environment, not independently verified attribution to specific AI systems, individuals or threat groups.
Boltz has not announced a restart date and warned users not to expect swaps to return quickly while it reviews its security posture and deploys fixes. Customer support remains available, but the company has not identified the attackers or disclosed the vulnerabilities involved. The immediate priority is containment and remediation, while the larger test will be whether Boltz can strengthen its defenses sufficiently to restore swaps without reopening the same attack surface.
For Bitcoin infrastructure providers, the episode illustrates how self-custody and service availability must be evaluated separately. Open-source financial infrastructure can preserve user control while still depending on teams capable of defending production systems against rapidly evolving threats. Boltz’s shutdown shows that non-custodial design can protect against one category of failure while leaving cybersecurity, availability and operational capacity as distinct risks.