Boltz has disabled its non-custodial swap service until further notice after concluding that it could not safely keep operating while automated attackers probed its infrastructure. The Boltz Bitcoin swaps suspension covers the service that connects Bitcoin’s base layer with the Lightning Network, and the team has not provided an estimated return date.
The company described the shutdown as a precautionary response to a pattern, not a reaction to one newly disclosed theft. It said automated, AI-assisted probing had risen steadily for months and that several exploits had been contained. Over the most recent days, however, the pace increased enough that attackers appeared able to iterate faster than the small team could find and patch weaknesses.
Boltz also said user funds were not put at risk because the service is non-custodial. Its refund infrastructure has not disappeared with the swap interface: the API remains available for cooperative refunds, unilateral refunds can continue without depending on Boltz’s servers, and customer support remains active.
Why Boltz Bitcoin swaps were paused
A swap service that connects onchain bitcoin with Lightning must coordinate several time-sensitive steps. Users rely on cryptographic conditions, payment routing and refund paths to complete an exchange without handing permanent control of funds to an intermediary. Non-custodial design reduces custody exposure, but it does not remove software, routing or infrastructure risk.
That distinction explains why a service can protect funds yet still decide to stop accepting new swaps. A vulnerability may threaten availability, pricing, routing or transaction coordination even when users retain keys and contract-based recovery rights. Continuing to operate during an active security race can enlarge the attack surface and make incident response harder.
The team said its own recent security scans contributed to the decision. It also described being targeted by multiple well-resourced groups while fixes were still being prepared. Under those conditions, disabling new activity creates time to review code and infrastructure without simultaneously defending a live flow of swaps.
AI changes the speed of vulnerability discovery
AI does not make every attack novel, and an automated scan is not proof that a model found a previously unknown flaw. The practical change is speed. Tools can inspect large codebases, generate test cases, vary inputs and retry failed approaches faster than a person working manually.
For defenders, the same techniques can improve code review, fuzzing and monitoring. The difficulty is that attackers need to find one exploitable path, while a service operator must understand and secure the whole system. Small open-source teams may face an especially uneven contest when public code gives many adversaries a shared starting point.
Boltz framed the situation as a wider shift for Bitcoin services built on open-source stacks. That does not mean open source itself is the problem. Public code supports peer review and reproducible security research, but disclosure alone cannot guarantee that maintainers will identify and patch every weakness before an attacker tests it in production.
What users should understand about refunds
The continuing refund paths are central to the incident. A cooperative refund uses the service and user together to unwind a swap. A unilateral refund is designed to let the user recover funds through the protocol’s own conditions without waiting for Boltz infrastructure to return.
Those mechanisms are part of the reason the company could state that funds were not at risk. They also show why non-custodial products should be evaluated by their failure behavior, not only by the normal transaction flow. A resilient design needs a clear answer to what happens when a website, API or operator becomes unavailable.
Users with an incomplete swap should follow the official recovery instructions and avoid unsolicited messages claiming to offer faster support. Security disruptions often attract impersonators who exploit urgency. The service’s own support channels and documented refund tools remain the appropriate reference points.
Why the suspension matters for Bitcoin infrastructure
Lightning and cross-layer swap services help users move between different forms of bitcoin liquidity. When one stops, the Bitcoin network continues, but routing options narrow and integrations that depend on that provider may need to pause or find alternatives.
The event also separates decentralization at the asset layer from operational concentration at the service layer. Bitcoin can remain permissionless while specific applications rely on small teams, hosted interfaces and specialized infrastructure. A non-custodial application can limit the consequences of a failure, but it cannot promise uninterrupted access.
For developers and integrators, the incident raises questions about dependency mapping. They need to know which functions fail when a provider goes offline, whether refund processes have been tested, and how quickly users receive accurate status information. Backup providers may help, but switching services during an incident introduces its own technical and security risks.
A pause is not a completed security review
The suspension should not be interpreted as evidence that every vulnerability has been identified. It is an operating decision that creates room for investigation. Any eventual restart will require more than a statement that the immediate pressure has eased.
Useful evidence would include a clear description of affected components, confirmation that refund systems behaved as intended, independent review where appropriate, and a plan for handling automated probing at a sustainable pace. Some technical details may need to remain private until fixes are widely deployed.
What comes next for Boltz
Boltz has warned users not to expect swaps to resume quickly. The next meaningful update will be whether the team can define conditions for a safe return, not simply whether the front end is reachable again.
The company must decide whether code changes, infrastructure redesign, additional monitoring or outside security support can close the gap it described. It may also need to narrow features or change release practices if the current maintenance burden exceeds the team’s capacity.
The Boltz Bitcoin swaps suspension is therefore a test of non-custodial resilience under a faster security cycle. Funds can remain recoverable while a service pauses, but reliable infrastructure also depends on maintainers having enough time, resources and defensive depth to keep new activity safe.
