A real-time account

Project status

Accessed: today — sources: documentation published by the project and the external checks cited on this page. Official website: bitcoinhyper.com

Current phase

DevNet

Selective access

Mainnet expected

Q3–Q4 2026

Dependent on the audits

Public audit

Not yet

Announced for before the TGE

SVM on DevNet

Live

Rust/Anchor tested

The state of the main components

✓ In the DevNet environment

SVM execution layer

SVM programs run natively on DevNet. SPL tokens, escrow and multi-signature transactions have been tested.

◉ Under way

Sequencer (centralised)

Live on DevNet. At the mainnet launch it is expected to remain centralised and operated by the team.

✓ In the DevNet environment

The DevNet block explorer

A public block explorer is available for DevNet.

◎ In development

Canonical bridge

Under test on DevNet. Forced exit not yet implemented. A federated custody model.

◎ In development

Anchoring to Bitcoin

The architecture is defined (OP_RETURN/Taproot). Adjustable frequency is in development.

◎ In development

data availability

The final solution is still under study. Directions being considered: external DA layers, erasure coding, distributed nodes.

○ Planned

Forced inclusion/exit

An anti-censorship mechanism. Still in development and not available on DevNet.

◎ In development

Proof system (ZK/fraud)

A hybrid fraud/validity-proof model is in development. It will not be active at launch.

○ Planned

Security audit

The project has announced that these will be completed before the TGE. As at 28.04.2026 no public audit of the protocol or the bridge had been published.

○ Planned

Public testnet

A launch for developers and the wider community. Ahead of mainnet.

○ Planned

Mainnet

A centralised sequencer and a federated bridge. Dependent on completion of the audits and the bridge.

○ Planned

Decentralisation of the sequencer

Two to four years from mainnet, according to the roadmap. Rotation, auctions, leader election.

Timeline of significant updates

July 2026 The Book

Publication of Michele Stefanelli's book “Due Diligence of a Layer 2 – The Bitcoin Hyper Case, Volume I” — the first independent technical analysis of the project (523 pages, 24 chapters; the complete work: 36 chapters). In preparation.

March 2026 Team announcement

Official post: the final data availability solution is still under study. Several directions are being considered.

Late 2025 DevNet

SVM programs run natively. The block explorer is live. First tests of DeFi, SPL tokens, escrow and multi-signature with selected developers.

Q2–Q4 2025 Presale and staking

Distribution of the $HYPER token. Staking active. A selective DevNet opened to chosen partners and developers.

Q2 2025 Foundation phase

Initial architecture, whitepaper v1, formation of the core team.

Smart contract review

GoPlusLabs · May 2026

✓ Verified

✓
Verified source code The source code is published and verified on BscScan
✓
No proxy The smart contract cannot be upgraded through a proxy pattern
✓
No mint function No new tokens can be created after deployment
✓
Ownership renounced Owner address: 0x000…0000 (dead address)
✓
No hidden owner No hidden function for transferring ownership
✓
No self-destruct The smart contract cannot be destroyed unilaterally
✓
No blacklist No mechanism for blocking particular addresses
✓
No whitelist No selective restriction on transfers
✓
0% tax on buys, sells and transfers No service fee is charged on transactions
✓
The tax rate cannot be changed Fees cannot be raised after deployment
✓
The anti-whale limit cannot be changed The team cannot alter the cap on holdings

⚠ Points to note

⚠
External call risk The smart contract makes external calls. GoPlusLabs flags a risk of re-entrancy or unexpected behaviour if the contracts it depends on are updated.
⚠
Possible honeypot The automated GoPlusLabs check flagged a possible honeypot during simulation. It was not possible to verify a sale independently.
⚠
An anti-whale limit is present An anti-whale mechanism (a cap on holdings) is present, although it cannot be changed. It may affect liquidity in the early stages.

Editorial note

Automated GoPlusLabs checks are no substitute for a formal audit by a specialist third party (CertiK, Quantstamp, Hacken and the like). The “possible honeypot” flag calls for a manual check on testnet: conditional logic tied to liquidity or to a lock can make a contract return a positive result in simulation. The absence of a mint function and the renouncement of ownership are structurally positive indicators, but they do not guarantee the overall security of the protocol, which also depends on the bridge, staking and governance contracts, none of which is covered by this card.

The figures are taken from the GoPlusLabs Token Security API (BSC chain 56) — May 2026. This card is updated manually; for the latest figures see the GoPlusLabs and BscScan page.

Signals to watch

The next decisive milestones, in order of importance:

  1. 1. Publication of the first security audits carried out by recognised third parties
  2. 2. Settling and documenting the data availability solution
  3. 3. Implementing and testing forced inclusion and forced exit on testnet
  4. 4. Launching a public testnet, open to all developers without selection
  5. 5. Publishing the technical specifications for decentralising the sequencer
  6. 6. Making the GitHub repository for the core code public