A real-time account
Project status
Current phase
Testnet
Public RPC · Progressive rollout
Mainnet launch
3 December 2026
Announced · completion to be verified
Network audit report announced
26 November 2026
Announced · completion to be verified
RPC Testnet
Available
Network observation through RPC
The state of the main components
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.
Timeline of significant updates
Testnet Staking
Availability announced by the team · Official source · ↗
The HYPER used in the portal and the rewards shown serve testing purposes and have no monetary value.
Testnet Bridge
Availability announced by the team · Official source · ↗
The network distinction matters: the Bitcoin Hyper side is a testnet, while the Ethereum and Solana sides use their respective Mainnets. The announcement concerns experimental HYPER$ tokens on these networks. It does not demonstrate an operational canonical BTC bridge or Bitcoin Hyper mainnet.
The team states that these tokens are for testing only, have no monetary value and are not the official HYPER$ tokens. Receiving them is not a presale allocation, a purchase or a claim of the official token. No independent functional test of the Faucet has been performed. Availability announced by the team
Read the article → Testnet Faucet →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.
Read the update → Testnet Wallet →The explorer is accessible following the public RPC. What users can consult, how the tools differ and which releases remain planned.
Read the article →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 →
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.
Official post: the final data availability solution is still under study. Several directions are being considered.
SVM programs run natively. The block explorer is live. First tests of DeFi, SPL tokens, escrow and multi-signature with selected developers.
Distribution of the HYPER$ token. Staking active. A selective DevNet opened to chosen partners and developers.
Initial architecture, whitepaper v1, formation of the core team.
Smart contract review
GoPlusLabs · May 2026✓ Verified
⚠ Points to note
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. Publication of the first security audits carried out by recognised third parties
- 2. Settling and documenting the data availability solution
- 3. Implementing and testing forced inclusion and forced exit on testnet
- 4. Launching a public testnet, open to all developers without selection
- 5. Publishing the technical specifications for decentralising the sequencer
- 6. Making the GitHub repository for the core code public