• 1. Wallet of Satoshi (WoS)
  • Sending sats:
  • Withdrawing to L1:
• 2. Phoenix Wallet
  • Sending sats:
  • Withdrawing to L1:
• 3. Your Own Lightning Node
  • Sending sats:
  • Withdrawing to L1:
• Core Tech Behind It: HTLCs, Multisig — and No Sidechain
• Summary Table
• Bonus: Withdrawing from LN to On-Chain

And what does it mean to withdraw back to Bitcoin Layer 1?

Disclaimer: This post was written with help from ChatGPT-4o. If you spot any mistakes or have suggestions — feel free to reply or zap in feedback!

Let’s break it down — using three popular setups:

§1. Wallet of Satoshi (WoS)

Custodial — you don’t touch Lightning directly

§Sending sats:

• You open WoS, paste a Lightning invoice, hit send.
• WoS handles the payment entirely within their system.
  • If recipient uses WoS: internal balance update.
  • If external: routed via their node.
• You never open channels, construct routes, or sign anything.

§Withdrawing to L1:

• You paste a Bitcoin address.
• WoS sends a regular on-chain transaction from their custodial wallet.
• You pay a fee. It’s like a bank withdrawal.

You don’t interact with Lightning directly. Think of it as a trusted 3rd party Lightning “bank”.

§2. Phoenix Wallet

Non-custodial — you own keys, Phoenix handles channels

§Sending sats:

• You scan a Lightning invoice and hit send.
• Phoenix uses its backend node (ACINQ) to route the payment.
• If needed, it opens a real 2-of-2 multisig channel on-chain automatically.
• You own your keys (12-word seed), Phoenix abstracts the technical parts.

§Withdrawing to L1:

• You enter your Bitcoin address.
• Phoenix closes your Lightning channel (cooperatively, if possible).
• Your sats are sent as a real Bitcoin transaction to your address.

You’re using Lightning “for real,” with real Bitcoin channels — but Phoenix smooths out the UX.

§3. Your Own Lightning Node

Self-hosted — you control everything

§Sending sats:

• You manage your channels manually (or via automation).
• Your node:
  • Reads the invoice
  • Builds a route using HTLCs
  • Sends the payment using conditional logic (preimages, time locks).
• If routing fails: retry or adjust liquidity.

§Withdrawing to L1:

• You select and close a channel.
• A channel closing transaction is broadcast:
  • Cooperative = fast and cheap
  • Force-close = slower, more expensive, and time-locked
• Funds land in your on-chain wallet.

You have full sovereignty — but also full responsibility (liquidity, fees, backups, monitoring).

§Core Tech Behind It: HTLCs, Multisig — and No Sidechain

• Lightning channels = 2-of-2 multisig Bitcoin addresses
• Payments = routed via HTLCs (Hashed Time-Locked Contracts)
• HTLCs are off-chain, but enforceable on-chain if needed
• Important:
  • The Lightning Network is not a sidechain.
  • It doesn’t use its own token, consensus, or separate blockchain.
  • Every Lightning channel is secured by real Bitcoin on L1.

Lightning = fast, private, off-chain Bitcoin — secured by Bitcoin itself.

§Summary Table

§Bonus: Withdrawing from LN to On-Chain

• WoS: sends sats from their wallet — like PayPal.
• Phoenix: closes a real channel and sends your UTXO on-chain.
• Own node: closes your multisig contract and broadcasts your pre-signed tx.

Bitcoin + Lightning = Sovereign money + Instant payments.
Choose the setup that fits your needs — and remember, you can always level up later.

P.S. What happens in Lightning… usually stays in Lightning.