personal_listAccounts

Not available through Triport. personal_* is a node account-management namespace and is not exposed by the service.

Not supported

personal_listAccounts belongs to the node account-management namespace (personal_*), which enumerates and unlocks keystore accounts held by an individual Ethereum node. Triport does not custody customer keys and is a multi-host routing service, not a single managed node, so this namespace is 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": "personal namespace disabled"
  }
}

The HTTP status is 200; the rejection is carried in the JSON-RPC error envelope. Classification is case-insensitive. This matches the behaviour of every public Ethereum RPC provider — the personal namespace is disabled on production-facing endpoints (and is deprecated in go-ethereum itself).

What to use instead

• Manage keys client-side and submit signed transactions with eth_sendRawTransaction.
• To learn which methods are routed, see rpc-eth-transport.md.

See the shared errors page for the full error envelope.