Network Endpoints

Endpoint Availability

Every gear-tech.io / vara.network endpoint on this page was operated by Gear for the TestNet and MainNet campaigns and is no longer served. They stay documented because the chain IDs, explorers and deployed contracts are unchanged, and because the roles map cleanly onto replacements:

Ethereum RPC and Beacon RPC — plain Ethereum endpoints. Substitute any Hoodi or Mainnet provider; everything else keeps working.
Vara.eth RPC (validator network) — Gear's own ethexe validators. There is no drop-in public replacement; run your own node to get pre-confirmations and Vara.eth state queries.

Hoodi Testnet

The Vara.eth testnet deployment on Ethereum Hoodi.

Parameter	Value
Network name	Vara.eth (Hoodi)
Chain ID	`560048`
RPC (HTTPS)	`https://hoodi-reth-rpc.gear-tech.io`
RPC (WebSocket)	`wss://hoodi-reth-rpc.gear-tech.io/ws`
Base L1	Ethereum Hoodi testnet
Block explorer	hoodi.etherscan.io

MetaMask Configuration

Network Name:  Hoodi Testnet
RPC URL:       https://hoodi-reth-rpc.gear-tech.io
Chain ID:      560048
Currency:      ETH
Explorer:      https://hoodi.etherscan.io

ethers.js Connection

import { ethers } from "ethers";

// HTTPS (for queries and transactions)
const provider = new ethers.JsonRpcProvider(
  "https://hoodi-reth-rpc.gear-tech.io"
);

// WebSocket (for subscriptions and real-time events)
const wsProvider = new ethers.WebSocketProvider(
  "wss://hoodi-reth-rpc.gear-tech.io/ws"
);

Beacon RPC (Hoodi)

https://hoodi-lighthouse-rpc.gear-tech.io

Vara.eth RPC (Validator Network)

For pre-confirmations and state queries via the validator P2P network. These campaign validators are retired — use the RPC port of your own node instead:

wss://vara-eth-validator-1.gear-tech.io   (retired)
wss://vara-eth-validator-2.gear-tech.io   (retired)
wss://vara-eth-validator-3.gear-tech.io   (retired)
wss://vara-eth-validator-4.gear-tech.io   (retired)

Whichever endpoint you use, it plugs into the @vara-eth/api providers (WsVaraEthProvider / HttpVaraEthProvider) for injected transactions and pre-confirmation flows — a local node exposes the same interface on ws://127.0.0.1:9944.

Ethereum Mainnet

Parameter	Value
Network name	Vara.eth (Mainnet)
Chain ID	`1`
RPC (HTTPS)	`https://mainnet-reth-rpc.gear-tech.io`
RPC (WebSocket)	`wss://mainnet-reth-rpc.gear-tech.io/ws`
Base L1	Ethereum Mainnet
Block explorer	etherscan.io

ethers.js Connection

import { ethers } from "ethers";

// HTTPS (for queries and transactions)
const provider = new ethers.JsonRpcProvider(
  "https://mainnet-reth-rpc.gear-tech.io"
);

// WebSocket (for subscriptions and real-time events)
const wsProvider = new ethers.WebSocketProvider(
  "wss://mainnet-reth-rpc.gear-tech.io/ws"
);

Beacon RPC (Mainnet)

https://mainnet-lighthouse-rpc.gear-tech.io

Vara.eth RPC (Validator Network)

For pre-confirmations and state queries via the validator P2P network. These campaign validators are retired — use the RPC port of your own node instead:

wss://validator-1-eth.vara.network   (retired)
wss://validator-2-eth.vara.network   (retired)
wss://validator-3-eth.vara.network   (retired)
wss://validator-4-eth.vara.network   (retired)

Network Health

Run these against whichever Ethereum RPC you use — your provider's Hoodi endpoint, or http://127.0.0.1:8545 on a full local stack.

Check RPC Status

curl -X POST <YOUR_HOODI_RPC> \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Check Chain ID

curl -X POST <YOUR_HOODI_RPC> \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'
# Should return "0x88bb0" (560048)

Network Endpoints

On this page