JSON-RPC

HTTP	https://rpc.utn.network
WebSocket	wss://rpc.utn.network
Chain id	20261003 (0x135288b)

The public Besu node enables the eth, net, and web3 namespaces, on HTTP and on WebSocket. Admin, QBFT, debug, and txpool methods are not on this URL.

curl -s https://rpc.utn.network \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"eth_chainId","params":[]}'

result is 0x135288b. net_version returns "20261003". web3_clientVersion returns a besu/v26.9.0/... string. eth_gasPrice returns 0x6ed3cf9800 (476 gwei).

The wallet host also exposes POST https://wallet.utn.network/rpc (GET is HTTP 405). It is the same guard, with a tighter edge limit (below). Browsers on the wallet use that path. Other apps should use https://rpc.utn.network.

Limits

Two layers apply to https://rpc.utn.network.

Limit	Where	Value
HTTP requests	Edge, per IP	600 per minute
WebSocket upgrades	Edge, per IP	20 per minute
POST /rpc on the wallet host	Edge, per IP	240 per minute
Request body	rpc-guard	1 MiB (1048576 bytes)
JSON-RPC batch	rpc-guard	50 calls
eth_sendRawTransaction	rpc-guard, per IP	30 per minute

The 600 per minute HTTP cap is sized for a wallet that polls several methods. The send cap is separate and smaller.

Errors

Condition	HTTP	Body
Body larger than 1 MiB	413	{"error":"too large"}
Batch longer than 50	200	JSON-RPC error -32600, Batch too large (max 50).
More than 30 sends in a minute from one IP	200	-32005, Too many transactions from this connection. Wait a minute and try again.
The node did not answer	200	-32603, RPC unavailable: …

A batch that mixes a rejected send with other calls returns one JSON-RPC array. The rejected positions carry -32005. The rest are the node's answers.

The edge rate limit is a separate HTTP 429 from the JSON-RPC errors above. The guard does not see requests the edge already refused.

Malformed JSON is forwarded to the node. The guard does not replace it with its own error.