Four Bitcoin Scaling Paths Compared: Lightning, Stacks, RGB++, and BitVM
摘要
Lightning, Stacks, RGB++, and BitVM all promise to expand Bitcoin, but they solve different problems. Payments, BTCFi, programmable assets, and trust-minimized bridges may not share one winner.
By BTCFi Editorial Desk
Last updated: May 9, 2026
Bitcoin scaling debates often pretend there must be one winner. That is the wrong frame.
Lightning, Stacks, RGB++, and BitVM are not four versions of the same product. They are four answers to different questions. Can Bitcoin move cheaply at the point of sale? Can BTC enter smart contracts? Can Bitcoin-native assets gain programmability without turning Bitcoin into Ethereum? Can rollups and bridges inherit more of Bitcoin's security without changing Bitcoin itself?
Those questions overlap, but they do not collapse into one race.
Lightning Is the Payments Layer
The Lightning Network is still the cleanest answer for small, frequent Bitcoin payments.
The original Lightning paper described a network of payment channels where transactions can happen offchain and settle to Bitcoin only when needed. The official Lightning site frames the benefit in plain language: instant payments, low cost, and settlement without putting every individual payment on the base chain.
That makes Lightning strongest for coffee, remittances, creator payments, game payments, and exchange transfers. Its weakness is equally clear. Lightning does not make Bitcoin a general smart-contract platform. It also has operational headaches around inbound liquidity, channel management, routing reliability, and custodial shortcuts.
Lightning wins when the job is payment. It does not win every job.
Stacks Is the BTCFi Application Layer
Stacks is trying to make BTC useful inside smart contracts.
The 2026 Stacks roadmap focuses on BTC capital activation, sBTC, higher capacity, Bitcoin-native lending, payments, AI agents, and deeper DeFi liquidity. Its core asset is sBTC, a 1:1 Bitcoin-backed token on Stacks designed to bring BTC into lending, trading, and other smart-contract applications.
That is a very different proposition from Lightning. Stacks is not trying to make every retail payment faster. It is trying to give Bitcoin holders access to programmable financial markets while anchoring the system to Bitcoin finality.
The trade-off is trust and complexity. sBTC depends on signers, peg mechanics, smart contracts, and ecosystem liquidity. Institutions will care less about slogans and more about withdrawals, audits, custody workflows, and stress behavior.
Stacks wins if BTCFi becomes a serious institutional category. It loses if users decide the bridge and liquidity risks are not worth the extra yield or programmability.
RGB++ Is the UTXO-Native Asset Route
RGB++ is a more technical bet: keep close to Bitcoin's UTXO model while using CKB's programmability to manage asset state and logic.
The RGB++ documentation describes an isomorphic binding between Bitcoin UTXOs and CKB cells. In practice, a Bitcoin UTXO acts as a single-use seal, while CKB provides a programmable layer for state and verification. The goal is to let Bitcoin-native assets gain richer behavior without forcing all computation onto Bitcoin L1.
This is elegant for developers who care about UTXO-native design, asset issuance, and programmability. It is also harder to explain to mainstream users. Lightning has a simple pitch: fast Bitcoin payments. Stacks has a simple pitch: BTC in DeFi. RGB++ has a more nuanced pitch: Bitcoin-aligned assets with programmable state through CKB.
That nuance may be a strength for builders and a hurdle for adoption.
BitVM Is the Bridge and Rollup Bet
BitVM is less an app ecosystem than a verification paradigm.
Robin Linus's original BitVM paper proposed a way to verify complex computation on Bitcoin without changing Bitcoin consensus rules. BitVM2 then improved the model by allowing permissionless runtime challenges, making it more relevant for bridges and second-layer verification.
The promise is enormous: if Bitcoin can verify fraud proofs or validity-related claims in a practical way, then future Bitcoin rollups and bridges may rely on weaker trust assumptions than today's multisig-style designs.
The catch is that BitVM is still infrastructure research moving toward implementation. It is not the thing a normal user opens to pay a bill. It is the thing that might secure the next generation of Bitcoin layers.
BitVM wins if it becomes the trust-minimized bridge layer for Bitcoin rollups. It is not competing with Lightning for coffee.
So Who Wins?
The most likely answer is not one winner. It is specialization.
Lightning can own fast payments. Stacks can push BTCFi and smart-contract use cases. RGB++ can grow around programmable Bitcoin-native assets and UTXO-based design. BitVM can become the security primitive for more credible Bitcoin rollups and bridges.
The real loser may be the old idea that Bitcoin scaling has to look like one monolithic chain doing everything.
Bitcoin's base layer will probably remain conservative. The expansion will happen around it, with different layers accepting different trade-offs. That is messier than a single victorious protocol, but it is also more honest.
If there is a final standard, it will be user behavior. Payments will flow to the layer that feels invisible. Institutions will use the layer they can audit. Developers will build where tools, liquidity, and security line up. The market will not crown one winner by narrative. It will sort these systems by usefulness.