Testnet network and RPC
AvailableAccess point for querying the test network.
Bitcoin Hyper: what is the network doing? We read the service responses and separate confirmations from transfers.
News · Bitcoin Hyper Testnet
The team announced a phased release over six weeks. The announced schedule and verified availability are shown separately.
Access point for querying the test network.
Explorer: view network activity and state.
Availability announced by the team on 23 October 2026. Installation and functions have not been independently tested. Testnet Wallet → · Read the article →
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.
HYPER is native to the testnet, with no separate contract. The team states that preparation tokens on Ethereum and Solana have no value and are not the future official token.
Editorial captions explain the tools’ purpose, not currently usable features. The faucet is planned; its process and amounts are not yet documented.
Sample period not yet available.
Totals declared by the service for up to ten intervals, usually about one minute each. These are distinct from the blocks analysed for transfers.
Partial sample: unread blocks are excluded from transfer counts.
First reading pending
New reading every 30 seconds while this page is visible, without overlapping requests. The service produces statistics about every 60 seconds; manual readings are at least 15 seconds apart and service limits may require longer pauses.
A short work cycle that the network considers confirmed.
Totals declared by the service for up to ten intervals, usually about one minute each. These are distinct from the blocks analysed for transfers.
Successful sends of a positive amount between different addresses.
A node is a program participating in the network.
Votes are messages through which nodes confirm blocks. A vote may also pay a fee.
A fee is the cost of an operation. A balance change may also result from account creation: it does not by itself prove a transfer.
Sample period not yet available.
| Block / slot | Block time¹ | Operations in the sample | Network votes | Native sends² | Other tokens² | Failed operations | With fee |
|---|---|---|---|---|---|---|---|
| No sample read. Data are not simulated. | |||||||
¹ Time reported by the RPC, displayed in Europe/Rome. ² Number of recognised transfer instructions; one operation may contain multiple sends, including internal ones. Failed operations and self-transfers are excluded.
At least two successful readings are needed to compare slots.
We display up to 20 actual readings. The chart restarts when you reopen the page; slot progress does not imply transfers. The tab’s sample and chart restart; older blocks leave the moving window.
Reported software: —
Project announcement and schedule ↗Data read from the project endpoint; no independent verification against other nodes.
A slot is a turn of the network. This number shows the latest turn the service considers confirmed, not a count of operations or transfers. An advancing slot alone does not tell us how many people use the network or how many tokens move.
If the slot advances from 1,000 to 1,005, five turns have passed. That does not mean five operations occurred.
The service declares this total for the effective window. It includes consensus votes and non-vote operations, not just transfers. The window moves: new intervals enter and old ones leave, so the total can rise or fall. It is not a lifetime counter.
A window has 120 operations: 110 votes and 10 non-votes. An interval with 20 leaves and one with 15 enters: the new total is 115.
We count successful transfers recognised in the blocks actually analysed, with a positive amount and different source and destination addresses. Native currency and other tokens are separate.
This is a partial sample, not the whole network. Zero means no transfer recognised in the blocks read. One operation can contain several transfer instructions, and custom programs may not be recognised. The sample stays in this tab, resets on reload and drops blocks outside the window; its count can fall.
In 20 blocks we recognise two transfers in one operation: the transfer counter shows 2, but there is one operation. We do not estimate transfers in unread blocks.
These are distinct identities reported by the service for programs participating in the network. They are not counts of people, users, independent owners or physical computers. One organisation may control several identities; the number alone does not prove decentralisation.
Three reported identities could all be managed by one organisation. They do not prove three independent owners.
This is the period covered by the intervals actually returned. We request ten, normally about a minute each; fewer intervals mean a shorter window and gaps are reported.
The window moves and block times are service estimates. Reading age and interval age are separate. The page reads every 30 seconds while visible; statistics are produced about every 60 seconds. Only the sampled blocks are analysed for transfers.
If the service lists 1,000 blocks and we read 20, coverage is 2%. Window totals and recognised transfers in those 20 blocks have different coverage.
These are messages or operations through which nodes take part in confirming the network. This figure is the service-declared vote count for the window, separate from non-votes. One node can produce many votes. Votes are not counts of people or token transfers; even a vote may pay a fee.
Two node identities can produce 100 votes in a period. This does not mean 100 people or 100 transfers.
These operations are distinguished from consensus votes by the service. They can include transfers, account creation or program interactions. Non-vote does not automatically mean successful transfer: details and outcomes must be analysed. Recognised transfers have a separate counter limited to the blocks read.
Ten non-vote operations may include account creation and other tests. We cannot call them ten transfers merely because they are not votes.
The central number counts operations only in analysed blocks. The circle splits them into successful votes, other successful operations and failed operations, not the whole window total.
The sample adds distinct blocks, drops those outside the window and resets on reload; it is held in this tab, not a cumulative history. The title’s question mark is a guiding question, not an error or missing value. Other operations, fees and balance changes alone do not prove transfers.
A sample can contain 40 operations: 38 votes, one other success and one failure. The centre shows 40 even if the window total is much higher. It can fall when old blocks leave.