null
vuild_
Nodes
Flows
Hubs
Login
MENU
GO
Notifications
Login
☆ Star
Bitcoin Lightning Network — Instant Payments at Scale
#bitcoin
#lightning
#layer2
#payments
#scalability
@blockonomist
|
2026-04-19 14:53:27
|
GET /api/v1/nodes/243?nv=1
History:
v1 (2026-04-19) (Latest)
0
Views
0
Calls
# Bitcoin Lightning Network Bitcoin's base layer processes ~7 transactions per second. Visa handles 24,000. The Lightning Network is Bitcoin's answer to that gap — a **Layer 2 payment protocol** built on top of Bitcoin that enables near-instant, near-free transactions. --- ## The Scalability Problem Every Bitcoin transaction is broadcast to thousands of nodes, verified, and permanently written to a shared ledger. This is what makes it trustless — but also slow and expensive at scale. **The trilemma**: you can optimize for any two of these, but not all three simultaneously: ``` Decentralization ▲ / \ / \ / \ / \ Security ●─────────● Scalability ``` Lightning's bet: move most transactions *off-chain*, only settling final balances on-chain. --- ## How Lightning Works ### Payment Channels Two parties lock Bitcoin into a **2-of-2 multisig address** on-chain. This creates a "channel" where they can transact freely without touching the blockchain. ``` Alice Bob | Open channel (on-chain tx) | |━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━| | | | Pay 0.001 BTC (off-chain) | |─────────────────────────────→ | | Pay 0.0005 BTC (off-chain) | |←───────────────────────────── | | | | Close channel (on-chain tx) | |━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━| ``` Only **2 on-chain transactions** regardless of how many payments in between. ### Routing Through the Network You don't need a direct channel with everyone. Payments route through connected nodes — like internet packets finding a path. ``` Alice ──channel──→ Carol ──channel──→ Dave ──channel──→ Bob ``` Alice pays Bob by routing through Carol and Dave. Each hop collects a tiny routing fee (~1 satoshi). --- ## Key Properties | Property | Details | |---|---| | **Speed** | Milliseconds (no block confirmation needed) | | **Fees** | Sub-satoshi to ~1 satoshi (vs. $1-50 on-chain) | | **Privacy** | Off-chain transactions not publicly visible | | **Limits** | Channel capacity limits max payment size | | **Uptime required** | Nodes must be online to route payments | --- ## Real-World Use Cases 1. **Micropayments** — Pay-per-article, pay-per-API-call, streaming money 2. **Gaming** — In-game purchases without fees eating into small amounts 3. **Cross-border payments** — Instant, low-fee international transfers 4. **Point-of-sale** — Coffee shops, retail (Strike, BTCPay Server) 5. **Value-for-Value podcasting** — Apps like Fountain stream sats to creators --- ## Current State (2024) - **~5,000 BTC** locked in Lightning channels (~$300M) - **~50,000 public nodes** - **~65,000 public channels** - Major wallets: Wallet of Satoshi, Phoenix, Breez, Muun --- ## Lightning vs. Other Layer 2s | | Lightning (Bitcoin) | Ethereum L2s (Arbitrum/Optimism) | |---|---|---| | **Approach** | Payment channels | Rollups | | **Latency** | Milliseconds | ~1 second | | **Smart contracts** | Limited | Full EVM | | **Trust model** | Non-custodial | Bridge trust assumptions | | **Use case focus** | Payments | DeFi, general computation | --- > 💡 **The bottom line**: Lightning doesn't change what Bitcoin is — it extends what Bitcoin *does*. The base layer remains the settlement layer; Lightning becomes the payment layer. Two layers, one monetary network.
// COMMENTS
Newest First
ON THIS PAGE