Frequently asked questions (FAQ)

According to the published documentation, Bitcoin Hyper presents itself as a Layer 2 rollup on Bitcoin that is intended to use the Solana Virtual Machine (SVM) as its execution environment. The underlying concept is that transactions and smart contracts are executed off-chain, with state commitments published to Bitcoin.

Bitcoin forms the base layer, whose processing capacity is limited and whose programmability is deliberately constrained. Bitcoin Hyper presents itself as a complementary layer that is intended to use the SVM to execute smart contracts, but which introduces additional trust assumptions, particularly around the sequencer and the bridge. How much security can be inherited from Bitcoin depends on the specific implementation of anchoring, data availability, the bridge and the verification mechanisms.

The SVM requires each transaction to declare the accounts it uses, which allows mutually non-conflicting transactions to be executed in parallel. The EVM, by contrast, uses a sequential execution model at the protocol level. According to the project, this difference would increase throughput. Actual compatibility with the programs and tooling of the Solana ecosystem needs to be verified against the technical documentation and independent testing.

As at 28 April 2026, Bitcoin Hyper is in a devnet phase with selective access. According to the project, SVM programs run natively, the Explorer is live, and SPL tokens, basic DeFi applications and multi-signature configurations have been tested. The Canonical Bridge is in testing on devnet. Mainnet and public security audits are not yet available.

The original whitepaper placed the mainnet between the fourth quarter of 2025 and the first quarter of 2026. As at 28 April 2026, the mainnet was not yet operational. The window the project has since indicated is Q3–Q4 2026 — an indicative figure that depends on the completion of the security audits, the bridge, the forced-exit mechanism and the data-availability solution.

As at 28 April 2026, no public audit report on the protocol or the bridge could be confirmed. The whitepaper anticipates its publication before the TGE. This remains a critical milestone that has yet to be verified.

According to the architecture described, the sequencer would compute a state commitment — typically a Merkle root — and periodically publish it to Bitcoin via OP_RETURN or Taproot. This would make it possible to verify that the commitment has indeed been recorded, but does not, in itself, allow the correctness of the state, data availability or the security of the bridge to be verified. The documentation envisages an adaptive frequency: more frequent anchoring could shorten the time to finality, albeit at the cost of higher fees on Bitcoin.

This is one of the most significant risks of the current design. Were a forced-exit mechanism to be introduced, users would be able to withdraw their funds directly on Bitcoin without the involvement of the sequencer. While this feature remains under development, a sequencer failure or censorship could temporarily block transactions and funds within the rollup.

This depends on which data-availability solution is ultimately chosen. If the data is publicly accessible and accompanied by appropriate verification mechanisms, the implementation could correspond to a rollup model. If the data remains solely under the control of the sequencer or of a restricted group, the implementation would be closer to a validium-type model. As at 28 April 2026, the definitive approach was still under examination.

According to the tokenomics published by the project, the expected total supply is 21 billion $HYPER. The stated distribution is: 25% Treasury, 30% Development, 20% Marketing, 15% Rewards and 10% Listings. The terms published for the presale indicate a seven-day vesting period.

According to the project’s documentation, $HYPER is intended to be used for payments, for participation in staking and, at a later stage, for governance mechanisms. The roadmap also mentions possible buyback-and-burn mechanisms linked to sequencer revenues. These functions remain to be verified once the mainnet has launched.

The risk associated with $HYPER is very high: the project is in a pre-mainnet phase, no security audit has been published for the protocol or the bridge, the initial implementation requires a centralised sequencer, and the custody tied to the bridge is said to be federated. A total loss of the capital invested is possible. This site is educational in nature and does not offer personal investment advice. For an individual assessment, please consult an authorised adviser.

The author sets out his views on the project in the book. Up-to-date information on his positions is published in the disclosure of interests on this site.

Three profiles of reader: (1) the curious reader who wants to understand without becoming an engineer; (2) the investor or adviser assessing the project with a due-diligence approach; (3) the developer or researcher who wants to explore the architectural choices in depth. Volume I: 523 pages, 24 chapters. The complete work spans two volumes: 36 chapters.

The book is available on Amazon. First edition, July 2026. It can be purchased on amazon.com — search for ‘Due Diligence of a Layer 2 – The Bitcoin Hyper Case’.