Networks and connectivity

REAL Testnet

Use the testnet to validate integrations before relying on them in a production environment. The RPC below responded with EVM chain ID 117711 on 16 September 2026.

RPC URL

https://testnet.rpc.real.finance/ext/bc/F9iT4dEEByJ4hCn76XtgEqu3UwEEL1PA25ZCkWSn6TMR1div9/rpc

Connect a wallet or application

Follow Add Real Testnet to your wallet for MetaMask, Rabby, or Core. Applications use the chain ID, full RPC URL, and native token above. Confirm the selected chain before signing. Obtain test ASSET from the faucet when a wallet needs gas, and use the explorer to inspect submitted transactions.

The RPC path includes an Avalanche blockchain ID. That identifier selects the blockchain served by the node; the numeric EVM chain ID identifies the network when signing transactions. They are different values and cannot be substituted for one another.

Gas and transaction fees

Faucet limits

The public faucet configuration on 17 September 2026 reported 1 ASSET per successful request, a rolling 24-hour window, one request per address, and three per IP. A CAPTCHA is required. The dispenser is prefunded and can run out; an available web page is not a guarantee of a successful request. These are test tokens for gas and testing.

Real Testnet uses native ASSET to pay for transaction execution. Asset tokens and payment stablecoins do not provide the native balance required for gas. Request test ASSET from the faucet and keep enough in the submitting wallet for every transaction in the workflow.

Gas cost depends on the operation and current network fee conditions. Estimate the actual transaction against Real Testnet before submitting it. A permissioned transfer can execute identity and compliance checks, so its gas use can differ from a simple native-token transfer. A reverted transaction can still consume gas.

Network fees are separate from asset purchase amounts and application service fees. A multi-step workflow may also require separate approval and execution transactions. Fetch current fee data rather than treating a configured network parameter as a permanent price.

What RPC access provides

The public gateway exposes Ethereum-compatible JSON-RPC calls used to read chain state and submit signed transactions. The gateway configuration restricts administrative APIs and applies request limits. Do not assume a public endpoint exposes every method available on a private node.

The chain RPC gateway does not expose its corresponding Ethereum WebSocket path. Use HTTP for chain RPC calls. The separate live API WebSocket is listed under developer endpoints below.

Access is separate from authority

Public RPC access lets an application read state and submit signed transactions. Contract administration requires the relevant role, and receiving a permissioned token requires its identity and compliance checks. These are separate from connecting to the network.

Testnet tokens support testing. Testnet addresses, balances, and deployment state must not be treated as production configuration. A separate verified configuration is required for another environment.

Testnet services

Developer endpoints

These are service entry points. Authentication, supported operations, and response formats depend on the service; publishing a link does not imply anonymous access to every operation.

Live API WebSocket: wss://testnet.api.real.finance/v1/ws

This is the application API's live-update connection, not an Ethereum JSON-RPC WebSocket endpoint. Do not configure it as a wallet RPC or assume it accepts Ethereum subscription methods.