BTC audit trail: On-chain visibility vs Lightning privacy

Moving funds from a fresh offline (cold) BTC wallet into Lightning, across Lightning, and back out to a brand-new cold wallet: this page shows what’s visible on-chain, what’s private off-chain, and how KYC audit trails are affected.

On-chain: visible on the blockchain Off-chain: private in Lightning channels KYC: identity at regulated entry/exit

Scenario overview: Fresh cold to Lightning, Lightning hops, fresh cold

  • Step 1 — Open/Swap In (On-chain):
    From Cold Wallet A (new address) you open a Lightning channel or use a swap service. This creates an on-chain transaction visible to everyone.
  • Step 2 — Lightning Payment (Off-chain):
    Funds move across Lightning via routed hops. These payments are off-chain; the global blockchain does not record them.
  • Step 3 — Close/Swap Out (On-chain):
    You exit Lightning to Cold Wallet B (brand-new address). A new on-chain transaction appears, but the intermediate Lightning path remains hidden.
Privacy gain: Lightning obscures the middle steps. Observers see coins leave A and later arrive at B, but not the off-chain route.
Continuity blur, not erasure: Entry and exit are still on-chain. If coins touch KYC infrastructure at either end, identity can be linked there.
Re-identification risk: Returning to a KYC exchange later reconnects funds to your identity, even if the Lightning path was private.
Cold Wallet A New on-chain address Lightning Off-chain payment Lightning Off-chain payment Cold Wallet B Brand-new address On-chain: channel open / swap-in (visible) Off-chain: Lightning hops (private) On-chain: channel close / swap-out (visible) KYC linkage at entry/exit Identity attaches where funds touch regulated services Re-link if returning to KYC Fresh address helps privacy; KYC still re-identifies
Solid cyan arrows mark on-chain visibility; dashed orange arrows mark off-chain Lightning privacy.

Implications for auditability and privacy

Best practices for offline wallet hygiene