CHAIN / LNSOURCE-LED COMPARISONS
On-chain vs. Lightning Network
Examine differences in settlement, fees, liquidity and the operating conditions of each payment method.
Lightning moves bitcoin through payment channels without publishing every payment to the blockchain. Participants update signed channel states; routed payments use conditional contracts so intermediaries cannot simply take the funds. Bitcoin’s base layer remains the court of final settlement.
02The differences that matter
An on-chain transaction spends Bitcoin outputs and creates new ones. Confirmation includes it in the public chain of blocks.
Opening a channel creates an on-chain funding transaction whose output can be spent only under the channel’s agreed script. The parties then exchange commitment transactions that divide that fixed balance. Lightning does not create additional bitcoin; it changes who can claim the locked bitcoin under enforceable conditions.
Additional blocks reduce reorganization risk under usual security assumptions. Waiting for a block is not a guaranteed ten minutes, and confirmation is not absolute irreversibility.
A successful recipient can usually treat the fulfilled conditional payment as final within the channel system, while ultimate dispute enforcement remains anchored to Bitcoin and its confirmation process.
You need spendable outputs and funds for the fee. The recipient does not need inbound payment-channel capacity.
A channel can send only from the balance available on its outgoing side and receive only into available inbound capacity. Wallets hide some complexity, but routing, backups, uptime and channel management remain real trade-offs. A route may lack capacity, fees may exceed the payer’s limit, a node may be offline or channel information may be stale. Wallets retry alternative paths, sometimes splitting a payment. Fast everyday success is an emergent network property, not a guarantee that every invoice always completes.
The on-chain fee depends primarily on transaction size and the chosen fee rate, not just the amount sent. Demand for block space affects the necessary rate.
Routing nodes may charge base and proportional fees. Opening, closing and managing liquidity can add costs; Lightning is not always free or cheaper.
Self-custody requires safe keys and backups. A recipient's wallet need not be online to receive at a known address; payment can be verified later.
A self-custodial Lightning wallet gives the user enforceable channel claims but must manage backups, chain monitoring and emergency fees. A custodial wallet can hide all channel operations while making the provider the actual controller of funds. The Lightning label alone does not reveal who holds the keys.
Lightning is not a separate coin and not a promise to settle later in an unrelated system. Its channel claims are constructed so disputes can ultimately be enforced with Bitcoin transactions. Lightning Network is used by both self-custodial and custodial wallets. Check who controls the keys and whether you can close the channel or withdraw funds without the provider’s permission.
This comparison describes ordinary self-custodial Lightning Network channels; apps may add services and other custody models. Unilateral closure may require waiting for timelocks, confirmations and additional transaction fees.