Comparable architectures
Competitor analysis
Bitcoin Hyper compared with the principal Bitcoin scaling designs. Source: chapters 25–29 and Appendix C of Michele Stefanelli’s book.
Note: This is not a contest. Lightning, Stacks, RSK and Bitcoin Hyper address partly different use cases and rely on different trust assumptions. The purpose of this table is to clarify how each individual system is positioned — not to declare a “winner”.
| Dimension | Bitcoin Hyper | Lightning | Stacks | Rootstock (RSK) |
|---|---|---|---|---|
| Type | Rollup (SVM) | Payment channels | Blockchain + PoX | Sidechain (EVM) |
| Primary use case | DeFi, smart contracts, applications | Fast micropayments | Smart contracts, DeFi | EVM smart contracts |
| Programmability | Intended for general-purpose use (SVM/Rust) | Not general-purpose; focused mainly on payments | Clarity | General-purpose (EVM/Solidity) |
| Security model | Anchored to Bitcoin per the announced plan, with additional trust assumptions | Bitcoin via payment channels | Stacks and Bitcoin via PoX | Merge-mining and a sidechain-specific model |
| Finality | Envisaged as periodic, via anchoring to Bitcoin | Instant within the channel | Depends on Stacks | Sidechain-specific |
| Decentralisation | Envisaged as limited at launch → roadmap | High, with decentralised nodes | Medium | Medium |
| Maturity | Devnet; pre-mainnet phase, per the project’s documented status | In production since 2018 | In production | In production since 2018 |
| Developer ecosystem | Compatibility with the Solana ecosystem, as stated by the project; full verification is still required | Specialised for payments (LND, CLN) | Clarity-specific ecosystem | EVM ecosystem |
| Liquidity required | No | Yes, pre-locked liquidity | No | No |
| Native token | $HYPER — stated supply of 21 billion | BTC, no native token | STX | RBTC, pegged to BTC |
| Published security audits | Two public audits of the token contract have been identified (Coinsult and SolidProof); as at 10 August 2026, no complete public audit of the Layer 2 architecture or bridge had been identified | Yes (LND, CLN) | Yes | Yes |
💡 Features stated by the project, and the limits of verification
- • An SVM-based execution environment, designed for smart contracts and applications
- • Compatibility with Solana ecosystem tooling, as stated by the project, subject to full verification
- • SVM/Sealevel parallelisation, presented as an effort to increase processing throughput; in the current state of the documentation, no specific performance measurement has been published
- • Planned use of Bitcoin to record state commitments (State Commitments), with associated additional risks relating to the bridge, the sequencer, data availability and the proving system
⚠ Limitations and specific risks
- • A young project with no comparable operational track record in production, in the current state of the documentation
- • Two public audits of the token contract have been identified (Coinsult and SolidProof); as at 10 August 2026, no complete public audit of the Layer 2 protocols or bridge had been identified
- • Sequencer, presented as centralised at launch
- • Data availability, described as an element not yet finalised
- • Bridge custody, described as federated or centralised at launch