Getting Started
Last updated
⌘Ctrlk
Pod provides an Ethereum-like interface, so developers can use existing toolchains and wallets out of the box - ethers.js, viem, web3.py, alloy, cast, or any EVM-compatible library. No new SDKs or custom clients required.
import { ethers } from "ethers";
const provider = new ethers.JsonRpcProvider("https://rpc.podtestnet.dev");
const balance = await provider.getBalance("0xYourAddress");Name
pod
RPC
https://rpc.podtestnet.dev
Chain ID
129301
Explorer
https://explorer.pod.network
Currency Symbol
USD
EVM Version
Prague (Ethereum block 22,431,084, Released May 7th, 2025)
Mainnet is not live yet. Network details will be published here once mainnet launches.
Transaction hashes as identifiers. Pod often uses the transaction hash — the value returned by eth_sendRawTransaction when the transaction was submitted — as the identifier for the entity that transaction created. For example, a bridge withdrawal's claim proof is fetched by the withdrawal tx hash, and account recovery references its target transaction by tx hash.
Exception — orderbook orders. A resting order is identified by a computed order_id = keccak256(abi.encode(signer, nonce, sequence)), not its submitOrder tx hash. The orderbook precompile's cancel(orderbookId, canceledOrder, …), update(orderbookId, updatedOrder, …), and getOrders(orderbookId, orderIds) all take this order_id; ob_getOrders returns it as order_id (and the originating tx hash separately as tx_hash). See the Orderbook precompile for details.
Pod supports standard Ethereum RPC methods under the eth_ namespace, with a few differences due to Pod's blockless architecture. Pod also introduces additional namespaces for protocol-specific and orderbook functionality:
JSON-RPC - Standard eth_ methods, Pod-specific pod_ extensions, and orderbook data via ob_ endpoints.
Precompiles - Enshrined applications and internal protocol operations exposed as precompile contracts, callable via eth_call and eth_sendRawTransaction.
Last updated