Network & RPC Endpoints
This is the primary environment for builders to experiment, deploy trial contracts, and integrate Relix into their applications.
Network details
Name: Relix Testnet
Chain ID:
4127Native currency:
RLXRPC URL:
https://rpc-testnet.relixchain.comBlock explorer:
https://testnet.relixchain.com
You can apply these values in:
EVM wallets (MetaMask, Rabby, OKX Wallet, etc.)
Development frameworks (Hardhat, Foundry, Truffle)
Backend services that talk to the chain via JSON-RPC
As more environments (e.g. mainnet, staging networks, or dedicated archives) go live, they can be added to this list with the same structure.
JSON-RPC usage
The Relix RPC behaves like a typical EVM endpoint:
Uses HTTPS over standard JSON-RPC
Accepts common methods such as
eth_call,eth_sendRawTransaction,eth_getLogs,eth_getBlockByNumber, and so onReturns chain-specific values (block numbers, gas prices, balances) for chain ID 4127
For most clients, you only need to swap the RPC URL and chain ID:
In a wallet, this means adding Relix Testnet as a custom network.
In backend code, this usually means changing a single
RPC_URLenvironment variable.
If your application performs heavy operations (for example, broad log scans or historical indexing), it is good practice to:
Cache frequently used data where appropriate
Limit very large
eth_getLogsrangesMonitor how the RPC behaves under your workload and adjust polling intervals accordingly
Example configuration (for developers)
Below is a minimal example of how a typical client would be configured to talk to Relix Testnet. The exact syntax will differ by library and language, but the parameters are always the same:
Any framework that supports custom EVM networks can be pointed at Relix by supplying this information.
Verifying connectivity
After configuring your wallet or client:
Make sure the active network reports Relix Testnet with chain ID 4127.
Query a simple RPC method such as
eth_blockNumberor view your address onhttps://testnet.relixchain.com.Confirm that the response includes recent blocks and a non-error status.
Once these checks pass, your setup is ready for deploying contracts, interacting with dApps, and integrating Relix into your product stack.
Last updated