Networks and connectivity

Real Testnet

Use Real Testnet to check your integration before you rely on it in production.

Network settingsTestnet

Network name

Real TestnetCopyCopiedSelected

Chain ID

117711CopyCopiedSelected

Gas token

ASSET18 decimalsCopyCopiedSelected

RPC

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

Explorer

https://testnet.explorer.real.financeCopyCopiedSelected

Faucet

https://testnet.faucet.real.financeCopyCopiedSelected

Add Real Testnet to walletGet test ASSET

Connect a wallet or application

To add the network to MetaMask, Rabby, or Core, use the Add Real Testnet to wallet button above, or follow Add Real Testnet to your wallet. To connect an application, use the chain ID, the full RPC URL, and the native token from the card. Check the selected chain before you sign. Use the explorer to inspect the transactions you submit.

The RPC path contains an Avalanche blockchain ID. The two IDs do different jobs:

• The Avalanche blockchain ID in the path tells the node which blockchain to serve.
• The numeric EVM chain ID identifies the network when you sign transactions.

They are different values. You cannot use one in place of the other.

Gas and transaction fees

Real Testnet uses native ASSET to pay for transaction execution. Asset tokens and payment stablecoins cannot pay for gas. Request test ASSET from the faucet. Keep enough in the submitting wallet for every transaction in your workflow.

Gas cost depends on the operation and on current network fee conditions. Estimate the actual transaction against Real Testnet before you submit it. A permissioned transfer can run identity and compliance checks, so it can use a different amount of gas than a simple native-token transfer. A transaction that reverts can still consume gas.

Network fees are separate from asset purchase amounts and application service fees. A multi-step workflow can need separate approval and execution transactions. Fetch current fee data. Do not treat a configured network parameter as a permanent price.

Faucet limits

The public faucet has these limits:

• 1 ASSET per successful request
• a rolling 24-hour window
• one request per address
• three per IP
• a required CAPTCHA

The faucet pays from a prefunded balance, and that balance can run out. A faucet page that loads does not guarantee that your request will succeed. Faucet tokens are test tokens for gas and testing only.

What RPC access provides

The public gateway exposes the Ethereum-compatible JSON-RPC calls that you use to read chain state and submit signed transactions. The gateway blocks administrative APIs and applies request limits. A public endpoint does not expose every method that a private node offers.

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

Access is separate from authority

Public RPC access lets your application read state and submit signed transactions. It does not give you any other permission:

• To administer a contract, you need the relevant role.
• To receive a permissioned token, the recipient must pass that token's identity and compliance checks.

Testnet tokens are for testing. Do not treat testnet addresses, balances, or deployment state as production configuration. Any other environment needs its own configuration.

Testnet services

Developer endpoints

These links are service entry points. Each service sets its own authentication, supported operations, and response formats. A published link does not mean that every operation allows anonymous access.

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

This is the live-update connection for the application API. It is not an Ethereum JSON-RPC WebSocket endpoint. Do not set it as a wallet RPC, and do not send Ethereum subscription methods to it.