admin_nodeInfo
Not available through Triport.
admin_*is a node-management namespace and is not exposed by the service.
| Method / Endpoint | admin_nodeInfo (JSON-RPC, POST /rpc/eth) |
| Status | Not supported — always returns -32601 |
| Network | Ethereum |
Not supported
admin_nodeInfo belongs to the node administration namespace (admin_*),
which controls and inspects the internals of an individual Ethereum node (its
identity, enode, peers, data directory). Triport is a multi-host routing
service, not a single managed node, so these methods have no well-defined
meaning across the pool and are not exposed.
Any request to an admin_*, personal_*, or engine_* method is rejected at
the edge — it never reaches an upstream node — with a standard JSON-RPC error:
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32601,
"message": "admin namespace disabled"
}
}The HTTP status is 200; the rejection is carried in the JSON-RPC error
envelope. Classification is case-insensitive (Admin_nodeInfo is rejected
exactly like admin_nodeInfo). This matches the behaviour of every public
Ethereum RPC provider — the admin namespace is disabled on production-facing
endpoints.
What to use instead
- To learn which methods are routed and how the endpoint dispatches requests, see rpc-eth-transport.md.
- For chain and client metadata that is served, use standard read methods such
as
eth_chainId,net_version,eth_syncing, andweb3_clientVersion. - For mempool inspection, use the
txpool_*methods (txpool_status, txpool_content, txpool_inspect).
See the shared errors page for the full error envelope.