Networks

Networks

Sentrix runs two networks. Mainnet (chain 7119) for production; Testnet (chain 7120) for development.

Mainnet (chain 7119)

Chain ID	7119 (0x1bcf)
RPC	https://rpc.sentrixchain.com
Explorer	scan.sentrixchain.com
Block time	1 second
Consensus	DPoS + BFT (Voyager LIVE since 2026-04-25), 4 validators
EVM	Active — Solidity contracts, MetaMask compatible
Native coin	SRX
Status	LIVE

Testnet (chain 7120)

Chain ID	7120 (0x1bd0)
RPC	https://testnet-rpc.sentrixchain.com
Explorer	scan.sentrixchain.com (toggle "Testnet" in UI)
Faucet	faucet.sentrixchain.com — testnet drip 10M tSRX per claim
Block time	1 second
Consensus	DPoS + BFT, 4 validators
EVM	Active — same surface as mainnet
Native coin	tSRX (testnet — no real value)

How chain_id works

The binary reads SENTRIX_CHAIN_ID env at startup. Peers with a different chain_id are rejected on libp2p handshake — mainnet and testnet can never talk to each other. Transactions include chain_id in the signing payload, so a mainnet tx is invalid on testnet and vice-versa.

Connect via curl (REST)

# Chain info (height, supply, validators)
curl -s https://rpc.sentrixchain.com/chain/info | jq

# Account balance
curl -s https://rpc.sentrixchain.com/accounts/0xYOUR_ADDR/balance

# Validator set
curl -s https://rpc.sentrixchain.com/validators

Connect via JSON-RPC (eth_*)

# eth_chainId
curl -X POST https://rpc.sentrixchain.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

# eth_blockNumber
curl -X POST https://rpc.sentrixchain.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

# eth_call (read contract)
curl -X POST https://rpc.sentrixchain.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_call","params":[{"to":"0x...","data":"0x..."},"latest"],"id":1}'

WebSocket subscriptions

Endpoint: wss://rpc.sentrixchain.com/ws. Supports 9 channels via eth_subscribe:

• EVM-compat: newHeads, logs, newPendingTransactions, syncing
• Sentrix-native: sentrix_finalized, sentrix_validatorSet, sentrix_tokenOps, sentrix_stakingOps, sentrix_jail

Full reference: WebSocket Subscriptions.

Connect via ethers / viem / wagmi

See Developer Quickstart for full JS examples.

Architecture

Public RPC traffic resolves via Cloudflare → edge proxy → load-balanced across mainnet validators (round-robin via internal mesh). Testnet RPC has a single validator backend.

Full operational detail: docs.sentrixchain.com/operations.