Live dashboard

Project status

Updated on — source: official communications from the Bitcoin Hyper team published on bitcoinhyper.com

Current phase

Devnet

Selective access

Estimated mainnet

Q3–Q4 2026

Subject to audit

Public audits

Not yet

Stated as pre-TGE

SVM on devnet

Operational

Rust/Anchor tested

Status of the key components

✓ Live

SVM execution layer

SVM programs running natively on devnet. SPL tokens, escrow and multi-signature have been tested.

◉ Under way

Sequencer (centralised)

Operational on devnet. At mainnet launch it is expected to be centralised and run by the team.

✓ Live

Devnet explorer

A public explorer is available for the devnet.

◎ In development

Canonical bridge

Under testing on devnet. Forced exit is not yet implemented. Federated custody model.

◎ In development

Anchoring to Bitcoin

Architecture defined (OP_RETURN/Taproot). Adaptive frequency under development.

◎ In development

Data availability

The final solution is still under research. Approaches explored: external DA layers, erasure coding, distributed nodes.

○ Planned

Forced inclusion/exit

Anti-censorship mechanism. Still under development and not available on devnet.

◎ In development

Proving system (ZK/fraud)

A hybrid fraud/validity-proof model is under development. Not active at launch.

○ Planned

Security audits

Stated by the project as due before the TGE. No public audit had been published as of 28/04/2026.

○ Planned

Public testnet

Opening to developers and the wider community. Pre-mainnet.

○ Planned

Mainnet

Centralised sequencer, federated bridge. Contingent on completion of the audits and the bridge.

○ Planned

Sequencer decentralisation

Roadmap of 2–4 years from mainnet. Rotation, auctions, leader election.

Timeline of key updates

July 2026 Book

Publication of "Due Diligence of a Layer 2 – The Bitcoin Hyper Case, Vol. I" by Michele Stefanelli — the first independent technical analysis of the project (523 pages, 24 chapters; complete work: 36 chapters). Forthcoming.

March 2026 Team announcement

Official post: the final data-availability solution is still under research. Several directions are being explored.

Late 2025 Devnet

SVM programs running natively. Explorer live. First DeFi, SPL-token, escrow and multi-signature tests with selected developers.

Q2–Q4 2025 Presale & staking

$HYPER token distribution. Staking activated. Selective devnet opened to chosen partners and developers.

Q2 2025 Foundation

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

Contract review

GoPlusLabs · May 2026

✓ Verified

✓
Verified source Source code published and verified on BscScan
✓
No proxy Contract not upgradeable through a proxy pattern
✓
No mint function New tokens cannot be minted after deployment
✓
Ownership renounced Owner address: 0x000…0000 (dead address)
✓
No hidden owner No concealed ownership-transfer function
✓
No self-destruct The contract cannot be destroyed unilaterally
✓
No blacklist No mechanism to block specific addresses
✓
No whitelist No selective restriction on transfers
✓
0% tax on buy/sell/transfer No fee applied to transactions
✓
Tax not modifiable Fees cannot be raised after deployment
✓
Anti-whale not modifiable The holding limit cannot be changed by the team

⚠ Points requiring attention

⚠
External call risk The contract makes external calls. GoPlusLabs flags the risk of re-entrancy or unexpected behaviour should dependent contracts be updated.
⚠
Possible honeypot The automated GoPlusLabs checker returned a possible-honeypot flag during simulation. It was not possible to independently verify a sale.
⚠
Anti-whale present An anti-whale mechanism (holding limit) is present, although it is not modifiable. It may affect liquidity in the early phase.

Editorial note

The automated GoPlusLabs checks are not a substitute for a formal audit by a specialised third-party firm (e.g. CertiK, Quantstamp, Hacken). The "possible honeypot" flag requires manual verification on testnet: a contract can return a positive result in simulation because of conditional logic tied to liquidity or to a lock. The absence of a mint function and the renounced 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 that are not examined in this card.

Data retrieved from the GoPlusLabs Token Security API (BSC chain 56) — May 2026. This card is updated manually; for the most recent data please consult GoPlusLabs and BscScan.

Signals to watch

The next critical milestones (in order of importance):

  1. 1. Publication of the first security audits by recognised third-party firms
  2. 2. Definition and documentation of the data-availability solution
  3. 3. Implementation and testing of forced inclusion/exit on testnet
  4. 4. Opening of the public testnet to non-selected developers
  5. 5. Publication of technical specifications for sequencer decentralisation
  6. 6. The core-code GitHub repository made public