Live dashboard
Project status
source: official communications from the Bitcoin Hyper team published on bitcoinhyper.com
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
Status of the key 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 key 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 "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.
Official post: the final data-availability solution is still under research. Several directions are being explored.
SVM programs running natively. Explorer live. First DeFi, SPL-token, escrow and multi-signature tests with selected developers.
HYPER$ token distribution. Staking activated. Selective devnet opened to chosen partners and developers.
Initial architecture, whitepaper v1, formation of the core team.
Contract review
GoPlusLabs · May 2026✓ Verified
⚠ Points requiring attention
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
- 6. The core-code GitHub repository made public