1. The Layer 2 Scaling Thesis
[ANALYSIS] Every distributed consensus network faces the Blockchain Trilemma: decentralization, security, and scalability cannot all be optimized simultaneously on a single base layer. Bitcoin chooses uncompromising decentralization and thermodynamic security on L1, capping throughput at ≈ 7 transactions per second.
Just as global financial clearing (Fedwire) is not used for buying everyday items, Bitcoin L1 serves as final institutional settlement. The Lightning Network shifts micro-transactions off-chain, retaining Bitcoin L1 as the supreme dispute resolution arbiter.
2. Payment Channel State Machines
[FACT] A payment channel begins with an on-chain Funding Transaction that locks Bitcoin into a 2-of-2 multisig address between Alice and Bob:
- Commitment Transactions: As Alice pays Bob, they negotiate a new balance state off-chain (e.g. Alice: 0.6 BTC, Bob: 0.4 BTC → Alice: 0.5 BTC, Bob: 0.5 BTC). Both sign an updated commitment transaction spending the funding output.
- Asymmetric Revocation Keys: To prevent either party from broadcasting an outdated, favorable balance, each commitment transaction includes a penalty clause. If Alice broadcasts an old state, Bob can use a pre-shared revocation secret to seize 100% of the channel capacity.
- Channel Closure: Channels can be closed cooperatively (a single on-chain transaction returning exact current balances) or unilaterally through a force-close dispute period.
3. Hash Time-Locked Contracts (HTLCs) & Sphinx Onion Routing
[FACT] Users do not need a direct channel with everyone they pay. Payments route across multiple hops atomically using Hash Time-Locked Contracts (HTLCs):
1. If Recipient reveals Preimage R such that SHA256(R) = H → Payment releases instantly.
2. If Timelock T expires before R is revealed → Funds refund automatically to sender.
Because all intermediary nodes link payments to the identical hash H, either every hop succeeds or every hop fails atomically. Intermediaries route encrypted packets using the Sphinx onion protocol, meaning each node only knows the previous hop and the next hop, preserving sender and recipient privacy.
4. Channel Liquidity & Lightning Service Providers (LSPs)
[ANALYSIS] A channel's total capacity is constant. The direction of capital determines payment viability:
- Outbound Liquidity: Funds on the local side of the channel, allowing the node to send payments.
- Inbound Liquidity: Funds on the remote side, required for a node to receive payments.
New nodes frequently suffer from "inbound liquidity starvation" because they cannot receive money until someone opens a channel to them. Lightning Service Providers (LSPs) solve this via dual-funded channels, just-in-time (JIT) channels, and Submarine Swaps (swapping off-chain sats for on-chain sats to rebalance channel allocations).
5. Routing Node Economics & Capital Efficiency
[FACT] Routing node operators earn fee revenue by forwarding payments across their channels. Fee schedules consist of two components:
Where PPM (Parts Per Million) represents satoshis charged per 1,000,000 satoshis forwarded. High-volume institutional routing nodes rebalance channels dynamically using circular self-payments or automated liquidity managers, generating 2% to 6% annualized yield on deployed BTC capital.