BTC audit trail: On-chain visibility vs Lightning privacy

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

Implications for auditability and privacy

• Entry/exit visibility:
  On-chain transactions (opening/closing channels or swaps) remain globally visible. They show funds leaving A and arriving at B.
• Lightning opacity:
  The intermediate path across Lightning is not recorded on the blockchain. Observers cannot trace the hops between participants.
• Fresh address advantage:
  Using brand-new, never-before-seen addresses reduces heuristic linkage. Timing, amounts, or external metadata can still create inferences.
• KYC boundaries:
  Touching regulated infrastructure re-links identity. Privacy gains are strongest when avoiding KYC chokepoints post-Lightning.
• Practical takeaway:
  Lightning + fresh cold addresses significantly blurs the trail but does not erase it if coins re-enter KYC environments.

Best practices for offline wallet hygiene

• Use new addresses:
  Generate a fresh receiving address for each on-chain return from Lightning to minimize heuristic clustering.
• Control timing and amounts:
  Avoid distinctive patterns that make correlation easier (e.g., identical amounts at predictable intervals).
• Minimize reuse:
  Don’t reuse addresses; keep channel funding UTXOs distinct from savings UTXOs whenever possible.
• Be cautious with swaps:
  Third-party swap services can introduce metadata. Prefer trust-minimized or non-custodial options where feasible.
• Understand re-identification:
  Depositing back to a KYC exchange re-establishes identity regardless of off-chain routing privacy.