Testnet network and RPC
AvailableAccess point for querying the test network.
BITCOIN HYPER / TESTNET
Testnet Observatory
Bitcoin Hyper: what is the network doing? We read the service responses and separate confirmations from transfers.
Observation onlyNo wallet · no funds sent
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.
Explorer
In developmentRelease planned in the team’s programmeExplorer: view network activity and state.
Wallet
In developmentRelease planned in the team’s programmeWallet: view native HYPER balances on the testnet.
Faucet
In developmentRelease planned in the team’s programmeFaucet: obtain trial tokens for testing.
Bridge
In developmentRelease planned in the team’s programmeBridge: test connections with Ethereum, Solana and Bitcoin.
Staking dashboard
In developmentRelease planned in the team’s programmeDashboard for staking tests.
Green: RPC verified reachable. Yellow: planned release, not yet verified available. “In development” describes the announced programme, not a technical check of development.
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.
We query the network endpoint. Numbers appear after a complete reading.
Latest finalised slot
—
A short work cycle that the network considers confirmed.
The first reading establishes the starting point.
Operations in the sample
—
Operations recorded in — recent available blocks.
A block is a group of recorded operations.
Recognized transfers
—
Successful sends of a positive amount between different addresses.
Native coin — · other tokens —
Reported node identities
—
A node is a program participating in the network.
This does not mean independent owners or physical computers.
How to read operations
Confirmations or transfers?
—Operations in the sample
Network votes—
Other successful operations—
Failed operations—
Votes are messages through which nodes confirm blocks. A vote may also pay a fee.
We wait for data before describing the sample.
—Operations with a fee
—Successful operations with balance changes beyond the 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 details
Latest blocks read
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.
During this session
Are slots advancing?
At least two successful readings are needed to compare slots.
We display up to 12 actual readings. The chart restarts when you reopen the page; slot progress does not imply transfers.
Reported software: —
Project announcement and schedule ↗Data read from the project endpoint; no independent verification against other nodes.