What Caused the 72-Hour Lightning Network Outage of Three Major Bitcoin Wallets?

AQUA Wallet Goes Dark as a Dependent

Because Boltz powered the swap backend for several major wallets, its shutdown immediately disabled Lightning and Liquid swap functionality for AQUA Wallet, Bull Bitcoin, and ZEUS within hours . AQUA's outage was a direct consequence of losing access to Boltz's swap rails—it was a dependent service interruption, not a separate hack . AQUA confirmed that all other features, including regular Bitcoin and Liquid transactions, remained operational .

ZEUS Wallet's Independent Security Incident

Separately, on August 5, 2026, ZEUS Wallet—which had already lost Boltz swap access—suffered its own cybersecurity incident. ZEUS discovered an attack on its infrastructure and proactively took its entire system offline as a precaution . This made ZEUS the third prominent Lightning provider outage within approximately 72 hours .

Crucially, ZEUS confirmed that its investigation found no evidence that the attack resulted from a flaw in the Lightning Network protocol or Lightning node software itself . The breach was contained to ZEUS's internal infrastructure .

Were Customer Funds Lost?

A central question for any outage is whether users lost money. The answer across all three providers is no. Here is the evidence:

• Boltz: No user funds were lost. Boltz is non-custodial and never holds user coins directly. The system uses Hash Time-Locked Contracts (HTLCs) to ensure swaps complete safely or revert. Boltz absorbed any operational losses itself .
• AQUA Wallet: AQUA publicly stated that all user funds remained safe and fully in user control .
• ZEUS Wallet: ZEUS confirmed in its official security update and via founder Evan Kaloudis that no customer funds were lost or placed at risk . ZEUS noted that because it is a self-custodial wallet, users always controlled their private keys and Bitcoin throughout the incident .

Was the Lightning Network Protocol or Capacity Affected?

• No protocol-level vulnerability was found. ZEUS explicitly stated its investigation found no exploitable flaw in the Lightning Network protocol or node software . Boltz's issue was with its own application-layer swap infrastructure, not the underlying LN protocol .
• Network capacity was not materially affected. The Lightning Network as a whole remained operational. The outages removed significant swap liquidity because Boltz was a dominant atomic-swap bridge, but they did not reduce the network's total channel capacity or routing capability .
• Ecosystem concentration risk was starkly exposed. The events highlighted a heavy dependency of multiple prominent wallets on a single backend provider (Boltz), which industry commentators immediately identified as a systemic risk .

Evidence Connecting the Incidents

The connection between Boltz and AQUA is direct and clear: AQUA relied on Boltz's swap API and went dark as a direct consequence of Boltz shutting down . The connection to ZEUS is temporal and indirect—ZEUS lost Boltz swap functionality on August 3, but its own infrastructure hack on August 5 was a separate, distinct incident . No evidence suggests that the same attacker group was responsible for both the Boltz AI-driven attacks and the ZEUS cyberattack. The cluster of outages within 72 hours heightened attention on Lightning infrastructure security, but the proximate causes differ .

Recovery Paths and Status

Boltz:

• Swaps remain disabled indefinitely with no restart timeline. Boltz stated it "cannot responsibly re-enable swaps" after internal security scans . The API remains available only to process cooperative refunds; unilateral refunds (on-chain) work independently of Boltz's infrastructure . Recovery depends on whether Boltz can fundamentally re-architect its system to withstand AI-driven automated exploit cycles—a challenge it publicly acknowledged may exceed its team's capacity .

AQUA Wallet:

• AQUA's team stated on August 3 that restoring Liquid/Lightning swap services was their top priority, that they were evaluating multiple paths, and that they had offered to help Boltz address its infrastructure issues . Since AQUA's outage is purely dependency-based, recovery means either Boltz restoring its API or AQUA integrating a different swap backend provider. AQUA noted that basic Bitcoin and Liquid transactions remained functional throughout .

ZEUS Wallet:

• ZEUS contained the attack within hours and proactively took infrastructure offline for a full security audit . ZEUS Pay Lightning Addresses came back online on August 6, 2026, and ZEUS confirmed that its White, block source, and graph data services remained operational throughout the incident . Currency exchange rate services experienced brief disruptions but were restored . Full restoration of all services is pending completion of the comprehensive security audit .

Broader Implications

• AI-assisted attacks on Bitcoin infrastructure are an emerging and growing threat. Boltz's case is notable because attackers used AI to automate vulnerability discovery faster than a human team could react—a scale and speed of attack that may become more common across the cryptocurrency industry .
• Single-provider dependency risk in the Lightning ecosystem was starkly illustrated. Multiple wallets losing core functionality because of one backend failure has spurred discussion about the need for redundancy and decentralized swap providers .
• User funds remained safe across all three incidents because of non-custodial architecture and HTLC-based swap design . This is a critical reassurance for users of self-custodial Bitcoin wallets.