Lightning, the Liquid sidechain and Tor each hide a different part of your Bitcoin activity. Lightning keeps payments off the blockchain, Liquid hides amounts, and Tor hides your IP address. None of them hides everything, and moving coins between them goes through services that see both sides. This guide explains what each layer hides, how people combine them for privacy, and which parts of that route work in November 2026. For a deeper look at Lightning itself, see our guide on Lightning Network architecture.
Lightning payments travel through payment channels and do not appear on the blockchain one by one. The network’s onion routing means each node on a route sees only the node before it and the node after it, never the full path. That protection has limits. Your wallet’s channel partner can usually tell which payments come from you: most phone wallets have a single channel, to a company called a Lightning service provider (LSP), and with some wallets, such as Phoenix, that company also sees where your payments go. A custodial wallet, where a company holds the keys, sees all your payments. Our chain analysis lesson sums up what Lightning hides and what it doesn’t.
On the blockchain, a channel shows up twice: once when it is opened and once when it is closed. A cooperative close shows only each side’s final balance, not the payments in between, so the activity inside a channel stays off the public record. A force close can also show payments that were still pending at that moment.
The Liquid sidechain adds a different kind of privacy. Liquid uses confidential transactions, which hide amounts from outside observers, though anyone can still see which addresses send to which. Its coin, Liquid bitcoin (L-BTC), is a claim on bitcoin held by a federation of companies. Only federation members can peg out, that is, redeem L-BTC for bitcoin directly; everyone else converts through a member platform or a swap service. On 6 September 2026 a software bug let about 4,000 unbacked L-BTC be redeemed for real bitcoin from the federation’s reserve, which fell from about 4,205 BTC to 197 BTC; the people behind the exploit returned 3,400 BTC the next day. The federation said in early November 2026 that the reserve again backs every L-BTC one to one, while its own peg-outs stay restricted.
People combine these layers into a route: bitcoin moves onto Lightning, through a swap into Liquid, and back to the main chain at a fresh address. For example, bitcoin bought on an exchange that verified your identity can take this route on its way to cold storage. The coin that arrives has no on-chain link to your exchange withdrawal, but every service along the way saw part of the path: your LSP, the swap into Liquid and the swap back. Keep coins that went through it apart from exchange coins, as our coin control guide explains, and keep your records for tax: privacy is not a way around legal obligations.
Proper implementation requires careful attention to operational security details. Using Tor when interacting with swap services hides your IP address from them, though an observer who can watch both your connection and the service can still match the timing. Timing analysis can be frustrated by introducing irregular delays between stages. Amounts can be varied to avoid obvious matches. These operational considerations decide how much privacy the route gives you.
Keep on Liquid only what you are moving, and only for as long as you need to. L-BTC is backed by bitcoin that the federation holds, and the September 2026 incident showed that the backing itself can fail.
These techniques will keep changing as Lightning and Liquid services come and go, and chain analysis will keep improving too. Review your setup periodically: in 2026 alone, Boltz, a widely used swap service between these layers, went offline, and Liquid’s reserve was drained and then restored.
In conclusion, Lightning, Liquid and Tor each cover part of the picture. Combined with careful operational habits, they give you stronger privacy than plain on-chain transactions, as long as you account for every service that sees both sides.
Step-by-Step Guide
This guide covers moving bitcoin from an identified source to your long-term cold storage through Lightning and Liquid, while keeping the records you need for tax.
Before you start (checked 7 November 2026): two of the services this route depends on have had a hard year. Boltz, a widely used non-custodial swap service between Bitcoin, Lightning and Liquid, switched off all its swaps on 3 August 2026 and had announced no restart date. Liquid’s federation peg-outs have been restricted since the 6 September 2026 incident. Check that every service you plan to use is running before you send it anything, and start with a small amount.
Step 1: Set up your privacy infrastructure. Install Tor on your computer or use Tails for maximum isolation. Choose a Lightning wallet that can connect over Tor: Phoenix (it needs a separate Tor app such as Orbot), Electrum with Tor enabled, or a self-hosted LND/CLN node running over Tor. Install a Liquid-capable wallet such as the Blockstream app (formerly Blockstream Green) or SideSwap. Route every step of this workflow through Tor so the services never see your IP address; our network privacy lesson shows how.
Step 2: Fund your Lightning wallet from a KYC source. Send bitcoin from your exchange or KYC wallet to your Lightning wallet, by opening a channel or with the on-chain-to-Lightning swap your wallet offers. The on-chain transaction from your KYC wallet is visible and linked to your identity; that is expected. The privacy improvement starts once funds are inside Lightning, and only toward outside observers: your channel partner still knows where the funds came from.
Step 3: Use Lightning normally. Pay invoices and make purchases as usual. These payments are invisible to on-chain observers, and nodes along a route only see their neighbors. Your wallet’s channel partner, though, sees the amount and time of each payment, and with Phoenix the provider (ACINQ) also knows where it goes. Lightning does not mix your balance: to your provider it is still the balance you funded.
Step 4: Swap your Lightning balance to Liquid. Create a fresh Liquid receive address in your Liquid wallet, then use a swap service that pays Lightning into Liquid: you pay its Lightning invoice and it sends L-BTC to your address. Boltz, the service this guide used to name for this step, has had its swaps switched off since 3 August 2026, so check what your Liquid wallet offers and that it is running. The swap service sees the Lightning payment it receives and the Liquid address it pays. Over a multi-hop route it does not see who sent the payment, but your LSP sees the amount and time of your payment, and with Phoenix the provider also sees that it went to the swap service.
Step 5: Optionally move L-BTC between your own Liquid addresses. Liquid hides amounts by default, so outside observers cannot read what you hold. Moving L-BTC between addresses you control adds little, though: Liquid’s transaction graph is public, so anyone can still follow which address paid which. A Liquid transaction typically pays 20 to 150 sats in fees (recent blocks on liquid.network, 7 November 2026).
Step 6: Swap L-BTC back to bitcoin at a fresh on-chain address. Only Liquid Federation members can peg out, so you can’t redeem L-BTC yourself; you swap it for bitcoin through a member platform or a swap service. Generate a new receive address in your cold storage wallet, one that has never been used, and give it to the provider. As of November 2026, SideSwap’s L-BTC-to-bitcoin service has been open since 20 October 2026, at one to one minus its 0.1% fee. It pays from its own bitcoin wallet, which it refills by hand, so a payout can wait in a queue. The bitcoin that reaches your cold storage comes from the provider’s wallet, with no on-chain connection to your original KYC withdrawal. The provider, however, sees both the L-BTC you sent and the address it paid.
Step 7: Introduce timing variations between stages. Chain analysis firms use timing correlation to link transactions that occur in rapid succession. Do not run all the stages back to back. Introduce irregular delays: wait hours or days between the Lightning-to-Liquid swap and the swap back to the main chain. Vary the amounts slightly (swap 4,850,000 sats instead of a round 5,000,000) to avoid pattern matching on common round numbers.
Step 8: Maintain tax compliance records separately. Track the cost basis and acquisition date of the original KYC bitcoin. Moving bitcoin between your own wallets is usually not a sale, but some tax authorities may treat a swap into L-BTC and back as one, so check the rules where you live. Keep a private ledger that records the original purchase date, purchase price and amount, each swap with its date and fee, and the final cold storage UTXO. With these records you can report correctly without showing the intermediate steps to anyone who does not need them.
Common Mistakes to Avoid
1. Using the same IP address across all pipeline stages without Tor. If you access your exchange, Lightning wallet, swap services and Liquid wallet from the same residential IP address, network-level surveillance can correlate all activities to you regardless of the on-chain privacy gained. Every interaction along the route must route through Tor, and ideally through different Tor circuits for different stages. In Tor Browser, use “New Identity” between stages: “New Tor circuit for this site” changes only that site’s circuit and does not unlink your activity. For wallet apps, restart Tor (or Orbot) between stages.
2. Moving exact round amounts along the route. Swapping exactly 0.01 BTC from Lightning to Liquid, then swapping exactly 0.01 BTC (minus fees) back to the main chain, creates a pattern that timing and amount analysis can match. Vary amounts by batching multiple smaller swaps and adding or subtracting irregular amounts before the final swap back.
3. Reusing addresses or wallets between runs. Each run should use fresh Lightning invoices, fresh Liquid addresses, and a fresh cold storage receive address. If you receive several swaps back to the same on-chain address, you link all those runs together and undo the privacy separation. Use a new derivation index for each cold storage deposit.
4. Attempting to use the route for tax evasion. This route is designed to break chain analysis surveillance, not to hide taxable events. You still owe taxes on any gains when you dispose of Bitcoin, regardless of whether chain analysis can trace the funds. A private record of every step lets you report correctly. Evading tax obligations is illegal and carries criminal penalties in most jurisdictions — the goal is financial privacy, not concealment of income.
5. Trusting a swap service with large amounts before testing with small amounts. Swap services fail, have bugs and go offline: Boltz switched off its swaps in August 2026, and SideSwap’s L-BTC-to-bitcoin service was closed from the 6 September incident until 20 October 2026. Always test the full Lightning-to-Liquid-to-on-chain route with a small amount (50,000-100,000 sats) before running significant funds through it. Verify that the final UTXO appears in your cold storage wallet and that the amounts match expected values after fees.
Frequently Asked Questions
Is using Lightning and Liquid for privacy legal?
Yes. Using Lightning Network and Liquid is legal in virtually all jurisdictions. These are standard Bitcoin technologies for faster payments and improved privacy. Financial privacy is a right in most democracies, and using technical tools to exercise that right is lawful. The legality of your activity depends on the underlying transaction (buying legal goods, paying taxes on gains, etc.), not on the payment technology used. Consult local regulations if you are uncertain about specific jurisdictional rules regarding cryptocurrency privacy tools.
How much does the full Lightning-to-Liquid-to-on-chain route cost in fees?
A route through three services pays three sets of fees: Lightning routing fees for the payment into the swap, the swap service’s fee for Lightning to Liquid, Liquid transaction fees (typically 20 to 150 sats each, 7 November 2026), and the fee to swap L-BTC back to bitcoin (0.1% at SideSwap in November 2026), plus the on-chain fee that depends on mempool congestion. Fees change with each service and with the network, so check every one before you start. For comparison, as of November 2026 a CoinJoin in Wasabi costs mining fees only, while entering Ashigaru’s Whirlpool pools costs 5% of the pool size plus mining fees.
Can chain analysis firms trace through Lightning Network channels?
Chain analysis firms cannot see individual Lightning payments on the blockchain. They can see channel openings and closings, and they can make probabilistic inferences about channel balances. Within a channel, who paid whom, for how much and when is known only to the two channel partners, and with onion routing each node on a route knows only its neighbors. The weak point is your own channel partner: a phone wallet’s LSP can usually tell which payments come from you, Phoenix’s provider also sees where they go, and a custodial wallet sees everything. Lightning is a real privacy improvement over on-chain payments against outside observers, less so against your provider.
What is the difference between this approach and CoinJoin for privacy?
CoinJoin works on the base layer: several people build one transaction with equal outputs, so no one can tell which output is yours, as long as the other participants aren’t one party pretending to be many and the coordinator, if there is one, is honest. It leaves visible evidence that a CoinJoin occurred, which some exchanges flag. The Lightning-Liquid route moves your coins through services instead: on the main chain, your final coin simply comes from a swap provider’s wallet, with no visible privacy step. But your Lightning provider, the swap into Liquid and the swap back each see part of the path, and together they see all of it. CoinJoin also protects you from the services involved, provided the coordinator is honest and you spend carefully afterwards; the route protects you from outside observers only, and depends on several services being up.
Do I need to run my own Lightning node for this to work?
Not necessarily. A mobile Lightning wallet such as Phoenix can pay the swap service’s Lightning invoice for the step into Liquid. We used to list Breez here as well; as of November 2026 its original app has left the app stores. We also used to name Wallet of Satoshi alongside Phoenix. Its website now calls it self-custodial, with a 12-word recovery phrase, but the company’s disclosure (25 August 2026) describes two modes: self-custody on Spark, a layer 2 from Lightspark, and a custodial mode in some regions, which the app assigns by default where it is offered. Check which one you have; we have not verified what Spark’s operators can see. A phone wallet’s provider still sees your payments (Phoenix’s provider, ACINQ, also knows where they go), and if you use a custodial wallet, the provider sees all your Lightning transactions and can correlate them with your identity. For maximum privacy, run your own Lightning node (LND or CLN) over Tor, which takes the wallet provider out of your payments. Self-hosted nodes also give you full control over channel management and fee settings, improving the reliability of larger swaps.
Related Resources
- Bitcoin Privacy: Why It Matters and How Chain Analysis Works — Comprehensive overview of all major Bitcoin privacy techniques including CoinJoin, PayJoin, and Lightning.
- Bitcoin CoinJoin Methods Compared — Alternative on-chain privacy techniques that complement the Lightning-Liquid approach. Note: US authorities seized Samourai’s Whirlpool coordinator in April 2024, and the original JoinMarket software has been archived and is unsafe to use; its maker/taker market, with no central coordinator, lives on through JoinMarket NG, an independent reimplementation. PayJoin (BIP78) still works in other software, such as Sparrow for sending and BTCPay Server for receiving. Our CoinJoin lesson lists what still works as of November 2026.
- Silent Payments Bitcoin: Complete Guide — Emerging privacy technology for receiving Bitcoin without address reuse.
- KYC vs Non-KYC Bitcoin: Privacy Paradox — Wallet management strategies for maintaining separation between identity-linked and private Bitcoin holdings.
- Lightning Loop Tutorial: Submarine Swaps — Technical deep dive into how submarine swaps work, the same idea behind the swap services in this route.
