RPC Methods

Seismic nodes expose a JSON-RPC API that is almost entirely compatible with standard Ethereum RPC. You can use the same tools (curl, cast, ethers.js, viem) with the same methods you already know.

This section documents the methods most relevant to Seismic developers — including Seismic-specific methods and standard Ethereum methods that behave differently on Seismic.

Seismic-Specific Methods

Method	Description
seismic_getTeePublicKey	Returns the TEE's encryption public key, used for ECDH key exchange when building Seismic transactions

Modified Ethereum Methods

These standard Ethereum methods work on Seismic but have important behavioral differences:

Method	Seismic Behavior
eth_call	Zeroes the from field on unsigned calls to prevent caller-dependent behavior leaks. Supports signed reads via Seismic tx type 0x4A
eth_sendRawTransaction	Accepts Seismic transaction type 0x4A with encrypted calldata and SeismicElements metadata
eth_getStorageAt	Fails with an error if the requested storage slot holds shielded (private) data

Standard Ethereum Methods

These methods work identically to their Ethereum counterparts:

Method	Description
net_version	Returns the current network ID

All other standard Ethereum RPC methods (eth_blockNumber, eth_getBalance, eth_chainId, etc.) work identically to Ethereum and are fully supported.

RPC Endpoints

Network	URL
Testnet	https://gcp-0.seismictest.net/rpc
Devnet	https://node-2.seismicdev.net/rpc

Quick Test

curl -X POST https://gcp-0.seismictest.net/rpc \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Seismic supports almost every RPC endpoint available in Reth. Only tracing endpoints are modified (shielded data is removed from traces). See Differences from Ethereum for details.