How does Bitcoin handle scalability issues?

Bitcoin's scalability is limited to ~7 TPS on-chain, but solutions like SegWit and the Lightning Network boost capacity, reduce fees, and enable faster transactions.

Aug 07, 2025 at 10:54 am

Understanding Bitcoin’s Scalability Challenge

Bitcoin’s design prioritizes decentralization, security, and immutability, but these principles come with trade-offs, particularly in transaction throughput. The base layer of Bitcoin, known as the Bitcoin blockchain, is limited by its block size and block time. Each block is capped at 1 megabyte (MB) in size and is mined approximately every 10 minutes. This constraint limits the network to processing roughly 7 transactions per second (TPS). In contrast, traditional payment systems like Visa can handle thousands of transactions per second. As demand for Bitcoin transactions increases, this limitation leads to network congestion, higher fees, and longer confirmation times. These issues are central to what is known as the scalability trilemma, where improving scalability often risks compromising decentralization or security.

Segregated Witness (SegWit): A Layer-One Upgrade

One of the most significant improvements to Bitcoin’s scalability came with the activation of Segregated Witness (SegWit) in August 2017. SegWit addressed scalability by modifying the structure of Bitcoin transactions. It does so by separating (or segregating) signature data (witness data) from the main transaction data. This change effectively increases the number of transactions that can fit into a single block without increasing the block size limit. The key mechanism is that witness data is counted at a lower weight under the new block weight system introduced by SegWit, allowing blocks to hold more transaction data while staying within the 4 million weight unit limit (equivalent to about 4 MB in practice). The benefits of SegWit include:

• Increased transaction capacity per block
• Reduced transaction fees due to more efficient block space usage
• Fixing transaction malleability, which was a prerequisite for the Lightning Network
• Enabling more efficient use of block space through better signature encoding

Users and wallets must support SegWit to take advantage of these improvements. Transactions sent from SegWit-enabled addresses (beginning with "bc1" or "3") benefit from lower fees and faster confirmations.

Lightning Network: Off-Chain Scaling Solution

The Lightning Network is a layer-two protocol built on top of Bitcoin that enables fast, low-cost transactions by moving most interactions off the main blockchain. It operates by creating bidirectional payment channels between participants. Once a channel is opened with an on-chain transaction, users can conduct an unlimited number of instant transactions between each other without broadcasting each one to the Bitcoin network. Only the final state of the channel is settled on-chain when it is closed.

To use the Lightning Network, users must:

• Install a Lightning-compatible wallet (e.g., Phoenix, Wallet of Satoshi, or Eclair)
• Fund a payment channel by sending Bitcoin to a multisig address on the blockchain
• Conduct instant peer-to-peer transactions within the network
• Close the channel to settle the final balance on the main chain

The network uses Hash Time-Locked Contracts (HTLCs) to enable payments across multiple hops, allowing users to transact even if they don’t have a direct channel. The Lightning Network dramatically increases scalability by reducing the number of transactions recorded on the blockchain, potentially enabling millions of TPS across the network if widely adopted.

Block Size Debates and Alternative Proposals

The debate over how to scale Bitcoin has led to various proposals over the years. One of the most controversial was Bitcoin Cash (BCH), which forked from Bitcoin in 2017 by increasing the block size to 8 MB (later increased further). Proponents argued that larger blocks would allow more transactions per block, directly increasing throughput. However, larger blocks require more storage and bandwidth, potentially leading to centralization risks as fewer nodes can afford to run full nodes.

Other proposals have included block weight increases, dynamic block sizing, and alternative consensus mechanisms, but these have not been adopted due to concerns about decentralization and security. The Bitcoin community generally favors conservative changes that maintain the network’s core principles. As a result, scaling efforts have focused more on layer-two solutions and efficiency improvements rather than increasing base-layer block sizes.

Future Upgrades and Efficiency Improvements

Bitcoin continues to evolve through soft forks and protocol upgrades that improve efficiency without altering the fundamental block size. One such upgrade is Taproot, activated in November 2021, which enhances privacy, reduces transaction data size, and lowers fees. Taproot combines multiple transaction types into a single signature format using Schnorr signatures and Merkelized Abstract Syntax Trees (MAST). This reduces the amount of data needed for complex transactions, freeing up block space for more transactions.

Another area of development is client-side block filtering (e.g., Neutrino) and compact block relay, which improve node performance and reduce bandwidth usage. These optimizations help maintain decentralization while supporting higher transaction volumes. Research into covenants and eltoo (a simplified channel update mechanism for Lightning) may further enhance scalability in the future, though they require careful implementation to avoid unintended consequences.

Frequently Asked Questions

What is the maximum number of transactions Bitcoin can process per second?

Bitcoin’s base layer can handle approximately 7 transactions per second under normal conditions. With SegWit adoption, this can increase to around 10–15 TPS due to more efficient block space usage. The actual number varies based on transaction size and network conditions.

How do transaction fees relate to scalability?

When the network is congested and block space is limited, users bid higher fees to prioritize their transactions. This fee market is a direct result of scalability constraints. Solutions like SegWit and Lightning reduce fees by increasing capacity or moving transactions off-chain.

Can anyone run a Lightning Network node?

Yes, anyone can run a Lightning node by installing compatible software like LND, c-lightning, or Eclair. Users need a Bitcoin full node (optional but recommended), a static IP or Tor address, and some Bitcoin to fund channels. Running a node supports network decentralization and allows direct channel management.

Why doesn’t Bitcoin increase block size to solve scalability?

Increasing block size could lead to higher hardware requirements for running full nodes, risking centralization. Larger blocks require more bandwidth and storage, potentially excluding users with limited resources. The Bitcoin community prioritizes decentralization and security, favoring layer-two solutions over base-layer bloat.