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).More →
Monitoring
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 →
The HYPER used in the portal and the rewards shown serve testing purposes and have no monetary value. Testnet Staking → · Read the article →
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. Testnet Staking · Availability announced by the team · Official source · ↗. We read the announcement and opened the portal’s landing screen. Staking, withdrawals and rewards remain untested.
Weeks are relative to the team’s announcement, not firm dates. This programme is separate from the 2027 roadmap.
SolidProof / Coinsult; no fully public audit was identified for the protocol or the bridge
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.
✓ On devnet
SVM execution layer
According to the project's documentation, SVM programs run natively on the devnet. The project states that SPL tokens, escrow mechanisms and multi-signature configurations have been tested.
✓ On devnet
Devnet explorer
The project maintains a public devnet explorer.
✓ 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)
According to the project, it is operational on the devnet. At mainnet launch it is expected to be centralised and maintained by the team.
◎ In development
Canonical bridge
According to the project's documentation, the canonical bridge is under testing on the devnet. The forced-exit function is not yet implemented, and the initial custody model is federated.
◎ In development
Anchoring to Bitcoin
The documentation describes anchoring via OP_RETURN or Taproot. Adaptive frequency is still under development.
◎ In development
Data availability
The definitive solution is still under study. Among the approaches explored are external data-availability layers, erasure coding and distributed nodes.
○ Planned
Forced inclusion and forced exit
A censorship-resistance mechanism. Still under development and not available on the devnet.
◎ In development
Proving system (ZK/fraud)
The project states that it is developing a hybrid model combining fraud proofs and validity proofs. According to its documentation, this system would not be active at initial launch.
○ Planned
Security audits
Public audits have been identified for the token contract, notably by SolidProof and Coinsult. The SolidProof audit explicitly relates to a single token contract and not to the Layer 2 protocol, the bridge or other contracts. No fully public audit of the protocol or the bridge was identified in this analysis.
○ Planned
Mainnet
The initial plan, as described by the project, comprises a centralised sequencer and a federated bridge. Launch depends in particular on completion of the audits and the canonical bridge.
○ Planned
Sequencer decentralisation
The roadmap envisages a period of 2–4 years after mainnet: rotation, auctions and 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 2026Book
Release of the English edition of Volume I of the book ‘Due Diligence of a Layer 2 – The Bitcoin Hyper Case’ by Michele Stefanelli: an independent technical analysis of the project — 523 pages and 24 chapters; the complete work comprises 36 chapters.
March 2026Team announcement
According to a communication published by the project, the definitive data-availability solution was still under study, and several approaches had been explored.
Late 2025Devnet
According to the project's documentation, SVM programs run natively, with an active explorer and the first tests of DeFi implementations, SPL tokens, escrow and multi-signature with selected developers.
Q2–Q4 2025Presale and staking
The HYPER$ token is offered through a public, phased presale. According to the project, staking is active, and a selective devnet is open to certain partners and developers.
Q2 2025Foundation
Initial architecture, whitepaper v1, and formation of the core team.
Automated contract review
GoPlusLabs · May 2026
✓ Data collected
✓
Source code verifiedSource code published and verified on BscScan
✓
No proxyThe contract cannot be upgraded through a proxy pattern
✓
No mint functionNew tokens cannot be created 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% fee on buy, sell and transferNo fee is charged on transactions
✓
Fees cannot be modifiedFees cannot be raised after deployment
✓
Anti-whale mechanism not modifiableThe team cannot change the holding limit
⚠ Points requiring particular attention
⚠
Risk on external callsThe contract makes external calls. GoPlusLabs flags the risk of re-entrancy or unexpected behaviour if its dependencies are updated.
⚠
Possible honeypotThe automated GoPlusLabs check returned a possible-honeypot indicator during simulation. It was not possible to verify a sale independently.
⚠
Anti-whale mechanism presentAn anti-whale mechanism — a holding limit — is present, although it cannot be modified. This may affect liquidity in the early phase.
Editorial note
The automated GoPlusLabs checks are not a substitute for a formal audit carried out by a specialised independent firm (for example CertiK, Quantstamp or Hacken). The “possible honeypot” indicator requires manual verification: a contract may 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 renouncement of ownership are structurally positive indicators, but they do not guarantee the overall security of the protocol, which also depends on the canonical bridge, staking and governance — none of which were examined in this analysis. Moreover, this automated check must be distinguished from the token-contract audits on Ethereum published by specialised firms.
Data retrieved through the GoPlusLabs Token Security API (BSC chain 56) — May 2026. This review is updated manually; for the most recent data please consult the GoPlusLabs and BscScan services.
Points to monitor
The next key milestones, in order of importance:
1. Publication of full audits of the Layer 2 protocol and the bridge, carried out by recognised independent firms
2. Definition and documentation of the data-availability solution
3. Implementation and testing of forced inclusion and forced exit on the testnet
4. Opening of the public testnet to non-selected developers
5. Publication of the technical specifications for sequencer decentralisation
6. Publication of the GitHub repository for the core code