AQUA Launches Indra to Replace Boltz Swaps

When Boltz pulled the plug on its swap services on August 3, the shutdown didn't just affect Boltz's own users — it knocked out a piece of infrastructure that several other Bitcoin wallets had quietly been leaning on for months. Boltz cited a rising wave of automated, AI-assisted probing that its small team could no longer patch fast enough to stay ahead of, and rather than keep operating exposed, it suspended Bitcoin, Lightning, and Liquid swap functionality indefinitely. Wallets including ZEUS, Bull Bitcoin, and AQUA all found a working piece of their product suddenly gone.

Six weeks later, AQUA — the wallet built by JAN3, the Bitcoin-focused company led by Samson Mow — has an answer. According to JAN3's own blog, AQUA has built and opened testing on Indra, an in-house Lightning-to-Liquid swap system designed as a direct, plug-in replacement for the gap Boltz left behind.

Built to be a drop-in replacement

The technical choice behind Indra is a pragmatic one: rather than designing a new interface from scratch, JAN3 built Indra to replicate Boltz's own API signature. That means any wallet or service that already integrated with Boltz's swap API can, in principle, point the same integration at Indra with minimal rework — a deliberate design decision aimed at the exact problem Boltz's shutdown created, where wallets suddenly needed a replacement that wouldn't force a rebuild of swap functionality from zero.

Indra has opened in public testing with a narrower feature set than a full Boltz replacement would eventually need. For now, it supports paying Lightning invoices funded from L-BTC, the Liquid Network's Bitcoin-pegged asset — the outbound half of the swap. The reverse direction, receiving Lightning payments that land as L-BTC, is planned but not yet live, meaning AQUA users can spend into Lightning through Indra today but can't yet receive that way through the new system.

Why the Lightning-Liquid bridge matters

Submarine swaps between Lightning and Liquid exist because the two networks solve different problems. Lightning offers fast, cheap, instant Bitcoin payments but requires channel liquidity and online availability; Liquid offers confidential, federated-sidechain settlement with different tradeoffs around speed and custody assumptions. Wallets like AQUA that want to offer both without forcing users to manage two separate balances rely on swap infrastructure to move value between the two transparently in the background — which is exactly the plumbing Boltz had been providing, and exactly what breaks silently for end users when that plumbing disappears.

That reliance on a single third-party provider is also the deeper lesson of the whole episode. Lightning-adjacent infrastructure bugs and outages tend to cascade across products that share the same underlying dependency, and Boltz's shutdown is a case study in how quickly a widely-used piece of shared plumbing can go from invisible to indispensable to gone. Building Indra in-house trades that third-party dependency for the burden of maintaining swap infrastructure directly — a tradeoff JAN3 has apparently decided is worth making rather than wait for Boltz, or an alternative, to return.

A pattern across Bitcoin's second-layer stack

AQUA is not the only project treating recent infrastructure stress as a forcing function for rebuilding on more resilient footing. The Liquid Network itself has spent parts of this year working through its own operational disruptions, including episodes where block production resumed while transaction processing stayed paused and a security incident that led one service to refund fees tied to a $320 million exploit. Set against that backdrop, JAN3 building its own swap layer rather than depending on someone else's looks less like a one-off reaction to a single bad month and more like a broader shift toward vertical control across Bitcoin's Layer 2 ecosystem, where projects increasingly view shared third-party infrastructure as a single point of failure worth engineering around.