CNMV warningThe issuer Sentinum Ltd. is the subject of a warning issued by the Spanish authority CNMV, dated 19 January 2026, under Regulation (EU) 2023/1114 (MiCA).Read more →
A real-time account
Project status
News · Bitcoin Hyper Testnet
Testnet release schedule
The team announced a phased release over six weeks. The announced schedule and verified availability are shown separately.
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
Availability announced by the teamOfficial source · 30 October 2026
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. Testnet Faucet → · Read the article →
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. Testnet Bridge → · Read the article →
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. Testnet Faucet: Availability announced by the team · 30 October 2026.
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.
✓ In the DevNet environment
SVM execution layer
SVM programs run natively on DevNet. SPL tokens, escrow and multi-signature transactions have been tested.
✓ In the DevNet environment
The DevNet block explorer
A public block explorer is available for DevNet.
✓ Live
Public Testnet
The public testnet RPC and explorer are available. Testnet Faucet: Availability announced by the team · 30 October 2026. 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. Open the explorer →
◉ Under way
Sequencer (centralised)
Live on DevNet. At the mainnet launch it is expected to remain centralised and operated by the team.
◎ 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
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.
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
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 2026The 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 2026Team announcement
Official post: the final data availability solution is still under study. Several directions are being considered.
Late 2025DevNet
SVM programs run natively. The block explorer is live. First tests of DeFi, SPL tokens, escrow and multi-signature with selected developers.
Q2–Q4 2025Presale and staking
Distribution of the HYPER$ token. Staking active. A selective DevNet opened to chosen partners and developers.
Q2 2025Foundation phase
Initial architecture, whitepaper v1, formation of the core team.
Smart contract review
GoPlusLabs · May 2026
✓ Verified
✓
Verified source codeThe source code is published and verified on BscScan
✓
No proxyThe smart contract cannot be upgraded through a proxy pattern
✓
No mint functionNo new tokens can be created after deployment
No hidden ownerNo hidden function for transferring ownership
✓
No self-destructThe smart contract cannot be destroyed unilaterally
✓
No blacklistNo mechanism for blocking particular addresses
✓
No whitelistNo selective restriction on transfers
✓
0% tax on buys, sells and transfersNo service fee is charged on transactions
✓
The tax rate cannot be changedFees cannot be raised after deployment
✓
The anti-whale limit cannot be changedThe team cannot alter the cap on holdings
⚠ Points to note
⚠
External call riskThe smart contract makes external calls. GoPlusLabs flags a risk of re-entrancy or unexpected behaviour if the contracts it depends on are updated.
⚠
Possible honeypotThe automated GoPlusLabs check flagged a possible honeypot during simulation. It was not possible to verify a sale independently.
⚠
An anti-whale limit is presentAn 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. 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