Getting Started

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");

Network Configuration

Testnet

Property	Value
Name	pod
RPC	https://rpc.podtestnet.dev
Chain ID	1293
Explorer	https://explorer.v1.pod.network
Currency Symbol	USD
EVM Version	Prague (Ethereum block 22,431,084, Released May 7th, 2025)

Mainnet

Next Steps

Transaction hashes as identifiers. Pod uses the transaction hash — the value returned by eth_sendRawTransaction when the transaction was submitted — as the canonical identifier for the entity that transaction created. Anywhere a later call needs to reference that entity, pass its creating tx hash. For example, the orderbook precompile's cancel(orderbookId, canceledOrder, …) and update(orderbookId, updatedOrder, …) both take the submitOrder tx hash as the order id, and ob_getOrders exposes the same value as tx_hash.

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.