Bitcoin Transaction Capacity, Confirmation Times, and Lightning
Summary
The guide explains how Bitcoin’s block size, roughly ten-minute block interval, and transaction demand constrain base-layer throughput. It describes the mempool as a queue where miners tend to prioritize transactions with higher fees, so congestion can delay lower-fee transactions. It distinguishes an initial confirmation from the additional confirmations many services require for greater settlement confidence.
The article presents the Lightning Network as a layer-two approach using payment channels, with channel openings and closings recorded on-chain while intermediate payments occur off-chain. It also describes Replace-by-Fee as a way to resubmit an eligible transaction with a higher fee, and mentions transaction accelerators. The throughput, timing, and six-confirmation figures are approximate descriptions, not guarantees: confirmation time varies with block production and congestion, and the comparison with centralized payment networks is not like-for-like. The guide gives no empirical evaluation of Lightning reliability, security tradeoffs, or fee conditions.
Key ideas
- Bitcoin’s block capacity and block interval limit base-layer transaction throughput.
- Higher-fee transactions may receive priority when the mempool is congested.
- A first confirmation and multiple confirmations provide different levels of settlement assurance.
- Lightning channels move intermediate payments off-chain and record channel settlement on-chain.
- Replace-by-Fee can raise a transaction’s fee to improve its chances of confirmation.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.