Networks and RPC
Kortana Testnet and Mainnet, and the RPC surface each actually implements.
Networks
Both networks are live. Studio validates the chain ID at connection time and blocks the connection on a mismatch.
| Kortana Testnet | Kortana Mainnet | |
|---|---|---|
| RPC | https://poseidon-rpc.testnet.kortana.xyz/ | https://zeus-rpc.mainnet.kortana.xyz |
| Chain ID | 72511 | 9002 |
| Currency | DNR | DNR |
| Explorer | explorer.testnet.kortana.xyz | explorer.mainnet.kortana.xyz |
What the endpoints implement
Both expose the standard Ethereum JSON-RPC surface: eth_call, eth_estimateGas, eth_sendRawTransaction, eth_getTransactionReceipt, eth_getLogs, eth_getBalance, eth_getCode, eth_getStorageAt and the rest. EIP-1559 fields are present, so Studio builds type-2 transactions.
Kortana adds a small ktn_* namespace. Three methods were verified live: ktn_nodeInfo (EIP-3085 network metadata, genesis hash, height, validator identity), ktn_getValidators, and ktn_getStakingInfo.
Capability detection
Studio does not assume any of this. At connection time it probes each method and records whether the endpoint implements it, then gates every dependent feature off the result. You can see the full table in the Network panel.
The rule: a JSON-RPC -32601 means the method is absent. Anything else — including a -32602 rejecting the probe arguments — proves the node routed the call, so the method exists.
Mainnet safety
Mainnet is visually distinct throughout the product and uses an alarm colour reserved for nothing else. Switching to it requires a confirmation, and deploying to it requires a second, typed acknowledgement. An accidental network switch never silently redirects a deployment.