Where Zroarus stands today, what is being worked on, and what still has to happen before Mainnet. Every item is a documented milestone with its evidence.
Mainnet is not live
Zroarus is in Testnet testing. Milestones describe focus areas and status, not launch dates. A target date appears only when the team has approved one, and it is a target, not a guarantee.Counted only from published milestones. This is not a percentage of the way to Mainnet: the full set of launch criteria has not been published yet.
18 / 18 complete
Core protocol and chain configuration.
Zroarus Testnet runs Hyperledger Besu with QBFT consensus (instant finality), chain ID 305583, 2-second blocks, a 50M block gas limit and the Cancun EVM.
How we know: eth_chainId returns 305583 and the genesis hash matches the published Testnet genesis. Verified 2026-09-26.
CREATE2 deployer, Multicall3 and Permit2 at their canonical addresses, plus Wrapped tZROAR (WtZROAR) and the tZUSD test stablecoin.
How we know: All five contracts recorded in the Testnet deployment manifest have deployed code. Verified 2026-09-26.
Chain ID, genesis and public endpoints for a Zroarus Testnet. No Testnet configuration has been published yet; this status reflects published information only.
How we know: The explorer network registry reserves a Testnet entry with no chain ID or endpoints.
Validators, infrastructure, reliability and monitoring.
One QBFT validator produces Testnet blocks. With a single validator there is no fault tolerance: if it stops, blocks stop.
How we know: Every checked block is signed by the Testnet validator. Verified 2026-09-26.
Automated checks of the chain, RPC, WebSocket, explorer, indexer and faucet, published with uptime history and incident records.
How we know: The explorer status API reports all six components with a last-checked time. Verified 2026-09-26.
Automatic recovery and operator alerting for the Testnet validator node, so an outage does not halt the chain unnoticed.
How we know: Listed as an open item in the Testnet integration reference.
A published policy for when the Testnet may be reset, how much notice teams get, and where the new genesis hash is announced.
How we know: Listed as an open item in the Testnet integration reference.
Security reviews, key custody and network validation.
All Testnet chain keys (validator, treasury, faucet, deployer, test wallets) are held in a managed secret store. No keys in code, configuration files or client bundles.
How we know: Documented in the Testnet integration reference, security section.
Opcode and precompile checks for the Cancun EVM: PUSH0, TSTORE/TLOAD, MCOPY, BLOBBASEFEE, CHAINID and the KZG precompile work. Prague and Osaka features are not active.
How we know: Contract-creation eth_call tests recorded in the Testnet integration reference.
RPC, explorer, faucet, verification and documentation.
JSON-RPC over HTTPS and WebSocket (with subscriptions) is open to everyone, with CORS enabled. ETH, NET, WEB3 and TXPOOL namespaces are available.
How we know: HTTPS RPC answers eth_chainId; the status monitor confirms WebSocket subscriptions. Verified 2026-09-26.
Blocks, transactions, addresses, tokens, contracts, pools and validators, with a public API.
How we know: Explorer and API respond; indexer reports 0 blocks behind. Verified 2026-09-26.
Dispenses tZROAR and tZUSD test assets with a 24-hour cooldown per asset. Claims are bound to a wallet signature that authorises no transfer.
How we know: Faucet status API reports both assets available with live (not simulated) payouts. Verified 2026-09-26.
Upload Solidity sources to the explorer to verify deployed bytecode.
How we know: The explorer verification API and compiler list respond, but no contract has been verified through it yet. Checked 2026-09-26.
Documented request, batch and eth_getLogs block-range limits so indexers and apps can page correctly.
How we know: The maximum eth_getLogs range and nginx rate limits are listed as unverified in the Testnet integration reference.
Wallet support and the path for new users.
EIP-3085 parameters so any compatible EVM wallet can add Zroarus Testnet in one step.
How we know: wallet_addEthereumChain parameters published on this site and by the explorer network API.
Applications, integrations and partner deployments.
ZolaSwap factory, router, fee controller, liquidity locker, TWAP oracle and related contracts are deployed on Testnet, with pools indexed by the explorer.
How we know: Factory and router have deployed code; pools are indexed by the explorer. Verified 2026-09-26.
The MemeHedge bonding-curve launch factory is deployed on Testnet and token launches are indexed by the explorer.
How we know: The launch factory has deployed code and launches appear in the explorer. Verified 2026-09-26.
NFT collection, lazy-mint and marketplace contracts for Testnet testing.
How we know: Listed under "still to deploy" in the Testnet integration reference; no NFT collections are indexed.
Foundation, governance and launch operations.
Awaiting team input