Developers / EVM tooling

Build open.
Verify everything.

Network connectivity and familiar developer tools form the currently documented entry point. The wider service ecosystem is an implementation roadmap.

01 / Network configuration

Deploy with familiar tooling.

Use documented parameters, independently review RPC trust and always test before main-network deployment.

CHAIN NAMEVolrex
CHAIN ID1378 (0x562)
RPC ENDPOINThttps://rpc.volrex.network/
NATIVE ASSETVLRX
EXPLORERexplorer.volrex.networkOpen ↗

This requests wallet network configuration only. No transaction or signature is requested.

JavaScript / viem
import { createPublicClient, http, defineChain } from 'viem';

const volrex = defineChain({
  id: 1378,
  name: 'Volrex',
  nativeCurrency: { name: 'Volrex', symbol: 'VLRX', decimals: 18 },
  rpcUrls: { default: { http: ['https://rpc.volrex.network/'] } },
  blockExplorers: { default: { name: 'Volrex Explorer', url: 'https://explorer.volrex.network/' } }
});

const client = createPublicClient({ chain: volrex, transport: http() });
console.log(await client.getBlockNumber());

Test the actual RPC, explorer, contracts, consensus characteristics and toolchain compatibility before relying on production behaviour. Never store private keys in frontend files.

The next chapter

Ship carefully. Measure independently.

Begin with network connectivity, a tested contract and a reproducible release process.