Network Configuration

Environment Variables

Configure network and endpoints via environment variables:

Variable
Description
Default
Options

ZETRIX_NETWORK

Network to connect to

mainnet

mainnet, testnet

ZETRIX_RPC_URL

Custom HTTP RPC endpoint

Auto

Any valid HTTPS URL

ZETRIX_WS_URL

Custom WebSocket endpoint

Auto

Any valid WS/WSS URL

Example Configuration:

{
  "env": {
    "ZETRIX_NETWORK": "mainnet",
    "ZETRIX_RPC_URL": "https://custom-node.zetrix.com",
    "ZETRIX_WS_URL": "ws://custom-ws.zetrix.com"
  }
}

Network Endpoints

Mainnet:

  • HTTP RPC: https://node.zetrix.com

  • WebSocket: ws://node-ws.zetrix.com

  • Chain ID: 0 (mainnet)

  • Purpose: Production applications with real value

Testnet:

  • HTTP RPC: https://test-node.zetrix.com

  • WebSocket: ws://test-node-ws.zetrix.com

  • Chain ID: 0 (testnet)

  • Purpose: Development, testing, experimentation

Switching Networks

Method 1: Update Configuration File

Edit your Claude Desktop config:

Then restart Claude Desktop.

Method 2: Run Both Networks Simultaneously

Configure two separate MCP servers:

Now you can specify which network:

  • "Check mainnet balance of..."

  • "Get testnet latest block..."

Method 3: Custom RPC Endpoints

Use custom or private nodes:

Use Cases for Custom Endpoints:

  • Private node infrastructure

  • Load-balanced RPC endpoints

  • Regional nodes for lower latency

  • Testing with local nodes

  • Custom network configurations

When to Use Testnet vs Mainnet

Use Testnet for:

  • ✅ Development and testing

  • ✅ Learning blockchain operations

  • ✅ Experimenting with transactions

  • ✅ Smart contract deployment testing

  • ✅ No real value at risk

  • ✅ Free test tokens available

Use Mainnet for:

  • ✅ Production applications

  • ✅ Real value transactions

  • ✅ Live smart contract deployment

  • ✅ Enterprise operations

  • ⚠️ Verified and tested code only

  • ⚠️ Irreversible transactions


Last updated