Network Status

This page lists the public endpoints for Monolythium networks and describes how to check node health and network status.

Public Endpoints

Service	Testnet	Mainnet
Cosmos RPC	https://rpc.testnet.mononodes.xyz	https://rpc.mainnet.mononodes.xyz
REST API	https://rest.testnet.mononodes.xyz	https://rest.mainnet.mononodes.xyz
gRPC	grpc.testnet.mononodes.xyz:443	grpc.mainnet.mononodes.xyz:443
EVM JSON-RPC	https://evm.testnet.mononodes.xyz	https://evm.mainnet.mononodes.xyz
EVM WebSocket	wss://ws.testnet.mononodes.xyz	wss://ws.mainnet.mononodes.xyz
Block Explorer	testnet.monoscan.xyz	monoscan.xyz

Local Node Defaults

If you are running a local node, the default ports are: Cosmos RPC 26657, REST API 1317, gRPC 9090, EVM JSON-RPC 8545, EVM WebSocket 8546.

Checking Node Status

Local Node

Query your local node's sync status:

curl localhost:26657/status | jq '.result.sync_info'

Key fields in the response:

Field	Meaning
latest_block_height	Current block height
latest_block_time	Timestamp of the latest block
catching_up	true if the node is still syncing, false if fully caught up

Public RPC

Check the public testnet RPC:

curl https://rpc.testnet.mononodes.xyz/status | jq '.result.sync_info'

EVM Chain ID Verification

Confirm the EVM chain ID from any JSON-RPC endpoint:

curl -X POST https://evm.testnet.mononodes.xyz \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Expected responses:

Network	Expected result	Decimal
Testnet	0x1b1c	6940
Mainnet	0x1b1d	6941

Latest Block via EVM

curl -X POST https://evm.testnet.mononodes.xyz \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

Peer Discovery

To connect your node to the network, you need seed nodes and persistent peers.

Seed Nodes

Official seed nodes are published in the monolythium/networks repository:

Network	Seed DNS
Testnet	seed1.testnet.mononodes.xyz seed2.testnet.mononodes.xyz seed3.testnet.mononodes.xyz
Mainnet	seed1.mainnet.mononodes.xyz seed2.mainnet.mononodes.xyz seed3.mainnet.mononodes.xyz

Configure seeds in your config.toml:

[p2p]
seeds = "seed1.testnet.mononodes.xyz:26656,seed2.testnet.mononodes.xyz:26656,seed3.testnet.mononodes.xyz:26656"

Persistent Peers

Community-maintained peer lists are available in the mono-core-peers repository. Add peers to your config.toml:

[p2p]
persistent_peers = "<node_id>@<ip>:26656,<node_id>@<ip>:26656"

For detailed peer configuration, see Seeds & Peers.

Health Monitoring

Monoscan Block Explorer

The quickest way to check network health is via the block explorer:

• Testnet: testnet.monoscan.xyz
• Mainnet: monoscan.xyz

The explorer shows live block production, validator status, and transaction throughput.

Monarch CLI

If you have Monarch CLI installed, use the built-in status commands:

# Check node status and sync state
monarch status

# Run a comprehensive health check
monarch doctor

monarch doctor verifies connectivity, sync status, peer count, disk space, and configuration integrity.

Prometheus Metrics

For operators running monitoring infrastructure, monod exposes Prometheus metrics on port 26660 by default. See Monitoring for Grafana dashboard setup.

Further Reading

• Networks -- Full network parameter reference
• Seeds & Peers -- Peer configuration and management
• Monitoring -- Prometheus and Grafana setup for operators
• Chain IDs -- Chain identifier reference