Available for testnetOfficial source · 23 October 2026
Availability announced by the team on 23 October 2026. Installation and functions have not been independently tested. Testnet Wallet → · Read the article →
Week 4
Faucet
In developmentRelease planned in the team’s programme
Faucet: obtain trial tokens for testing.
Week 5
Bridge
In developmentRelease planned in the team’s programme
Bridge: test connections with Ethereum, Solana and Bitcoin.
Week 6
Staking dashboard
In developmentRelease planned in the team’s programme
Dashboard for staking tests.
Green: public RPC and explorer interface accessible. Yellow: subsequent releases planned by the team. Access is not a complete functional or security audit. Historical RPC observations: 10 October 2026; explorer source: 15 October 2026. Editorial revision and page-opening check: . Wallet: available for testnet according to the team’s announcement of 23 October 2026; the shared editorial check reached the ZIP link, without installing or functionally testing the extension.
Weeks are relative to the team’s announcement, not firm dates. This programme is separate from the 2027 roadmap.
New: the testnet RPC is available and the ecosystem is opening progressively. The other cards retain the earlier devnet picture; they do not confirm that the same tools are already available on the new testnet.
✓ Live
SVM execution layer
SVM programs running natively on devnet. SPL tokens, escrow and multi-signature have been tested.
✓ Live
Devnet explorer
A public explorer is available for the devnet.
✓ Live
Public Testnet
The public testnet RPC and explorer are available. The team opened wallet testing in its announcement of 23 October 2026; the Faucet is planned for the following week. Bridge and staking remain subsequent announced releases. Open the explorer →
◉ Under way
Sequencer (centralised)
Operational on devnet. At mainnet launch it is expected to be centralised and run by the team.
◎ 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
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
Testnet · Wallet
The team opens testing of Bitcoin Hyper Wallet, distributed as an unpacked extension. The Faucet is planned for the week after the announcement. No independent installation or functional test has been performed. Use only a test wallet without real-wallet seeds or real funds.
The team made the public testnet RPC available to the community. The explorer followed with the release of 15 October 2026. Team’s source: 8 October 2026. Shared RPC observations recorded on 10 October 2026 are historical network observations, distinct from this portal’s current editorial revision. Read the article →
July 2026Book
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 2026Team announcement
Official post: the final data-availability solution is still under research. Several directions are being explored.
Late 2025Devnet
SVM programs running natively. Explorer live. First DeFi, SPL-token, escrow and multi-signature tests with selected developers.
Q2–Q4 2025Presale & staking
HYPER$ token distribution. Staking activated. Selective devnet opened to chosen partners and developers.
Q2 2025Foundation
Initial architecture, whitepaper v1, formation of the core team.
Contract review
GoPlusLabs · May 2026
✓ Verified
✓
Verified sourceSource code published and verified on BscScan
✓
No proxyContract not upgradeable through a proxy pattern
✓
No mint functionNew tokens cannot be minted after deployment
No hidden ownerNo concealed ownership-transfer function
✓
No self-destructThe contract cannot be destroyed unilaterally
✓
No blacklistNo mechanism to block specific addresses
✓
No whitelistNo selective restriction on transfers
✓
0% tax on buy/sell/transferNo fee applied to transactions
✓
Tax not modifiableFees cannot be raised after deployment
✓
Anti-whale not modifiableThe holding limit cannot be changed by the team
⚠ Points requiring attention
⚠
External call riskThe contract makes external calls. GoPlusLabs flags the risk of re-entrancy or unexpected behaviour should dependent contracts be updated.
⚠
Possible honeypotThe automated GoPlusLabs checker returned a possible-honeypot flag during simulation. It was not possible to independently verify a sale.
⚠
Anti-whale presentAn 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. Publication of the first security audits by recognised third-party firms
2. Definition and documentation of the data-availability solution
3. Implementation and testing of forced inclusion/exit on testnet
4. Opening of the public testnet to non-selected developers
5. Publication of technical specifications for sequencer decentralisation