Build against verified public endpoints.

This documentation describes the public developer surfaces currently exposed for Chain ID 22028. Endpoint availability is observable and testable; internal network-promotion gates remain governed by the project’s separate readiness process.

EVM compatibleChain ID 22028ZVQ · 18 decimalsHTTPS JSON-RPC

Canonical connection

NetworkZEVARYQ Mainnet

Chain ID22028 · 0x560c

Native assetZVQ · 18 decimals

RPChttps://rpc.kriptoaman.com

Explorerhttps://explorer.kriptoaman.com

Machine config/developer/network.json

Public developer model

Use the public RPC for ordinary EVM reads and signed transaction broadcast from a wallet or backend. Use Explorer REST APIs for indexed blocks, transactions, addresses, tokens and verified-contract data.

Security boundary: public developer documentation does not expose validator administration, private RPC origins, signing keys, keystores, seed phrases, treasury credentials, or privileged namespaces.

Runnable starter: open the browser-safe ZVQ Live dApp Starter for same-origin Explorer verification and user-approved wallet onboarding. The canonical source remains available in the GitHub starter folder.

Explorer REST API

BlocksGET /api/v2/blocks TransactionsGET /api/v2/transactions Network statsGET /api/v2/stats ERC-20 tokensGET /api/v2/tokens?type=ERC-20 Verified contractsGET /api/v2/smart-contracts Verification configGET verification/config

Recommended development flow

Read network.json and validate Chain ID.
Probe eth_chainId and eth_blockNumber.
Build read-only calls first.
Connect a user wallet for signed transactions; never collect private keys.
Confirm the transaction in Explorer.
Verify deployed contracts using the supported verification configuration.

Core JSON-RPC methods

eth_chainId, eth_blockNumber, eth_getBalance, eth_getCode, eth_call, eth_estimateGas, eth_gasPrice, eth_getTransactionByHash and wallet-signed transaction submission are standard starting points. Availability remains governed by the public RPC gateway policy.

What this page does not claim

No TPS headline, validator uptime percentage, market price, market cap, total supply, circulating supply, staking yield or exchange availability is asserted here unless independently supported by a public source.

Public RPC and Explorer availability are developer-access facts. They do not, by themselves, replace internal governance/readiness gates recorded elsewhere in the project.