linkChains

Chain configurations for Seismic networks

The seismic-alloy SDK supports multiple Seismic networks. Each chain has a specific chain ID, RPC endpoint, and recommended network type. This section documents the available chains and how to connect to them.

Overview

Unlike the Python SDK, seismic-alloy does not use pre-configured chain objects. Instead, you pass the RPC URL directly to the provider constructor and select the appropriate network type (SeismicReth or SeismicFoundry). The chain ID is fetched automatically from the node.

use seismic_prelude::foundry::*;
use alloy_signer_local::PrivateKeySigner;

let signer: PrivateKeySigner = "0xYOUR_PRIVATE_KEY".parse()?;
let wallet = SeismicWallet::from(signer);

// Testnet
let url = "https://gcp-1.seismictest.net/rpc".parse()?;
let provider = sreth_signed_provider(wallet, url).await?;

// Local (Sanvil)
let url = "http://127.0.0.1:8545".parse()?;
let provider = sfoundry_signed_provider(wallet, url).await?;

Supported Chains

Chain
Chain ID
RPC URL
Network Type
Description

5124

https://gcp-1.seismictest.net/rpc

SeismicReth

Public testnet for development and testing

31337

http://127.0.0.1:8545

SeismicFoundry

Local development node

Choosing a Chain

Chain ID Handling

The Alloy provider automatically fetches the chain ID from the connected node via the ChainIdFiller. You do not need to specify it manually in most cases. The chain ID is used for:

  • EIP-155 replay protection in transaction signing

  • EIP-712 typed data signing

  • Transaction validation

Pages

Page
Description

Public testnet configuration and usage

Local development with Sanvil

See Also

Last updated