> For the complete documentation index, see [llms.txt](https://docs.seismic.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seismic.systems/clients/typescript/react/chains/create-seismic-devnet.md).

# Create Seismic Devnet

Factory function that creates a RainbowKit-compatible chain configuration for any Seismic node. Use this when the pre-configured chains (`seismicTestnet`, `sanvil`, `localSeismicDevnet`) do not match your node's host.

## Import

```typescript
import { createSeismicDevnet } from "seismic-react/rainbowkit";
```

## Parameters

| Parameter     | Type     | Required | Description                                              |
| ------------- | -------- | -------- | -------------------------------------------------------- |
| `nodeHost`    | `string` | Yes      | Hostname for the node (e.g. `testnet-1.seismictest.net`) |
| `explorerUrl` | `string` | No       | Block explorer URL                                       |

## Return Type

`RainbowKitChain` -- a chain object compatible with RainbowKit's `getDefaultConfig` and wagmi's `createConfig`.

The returned chain has:

* **Chain ID**: `5124`
* **Name**: `Seismic`
* **Native Currency**: ETH (18 decimals)
* **RPC (HTTPS)**: `https://<nodeHost>/rpc`
* **RPC (WSS)**: `wss://<nodeHost>/ws`
* **Seismic transaction formatters**

## Usage

### Basic

```typescript
import { createSeismicDevnet } from "seismic-react/rainbowkit";

const myDevnet = createSeismicDevnet({
  nodeHost: "my-node.example.com",
});
// RPC: https://my-node.example.com/rpc
// WSS: wss://my-node.example.com/ws
```

### With RainbowKit

```typescript
import { getDefaultConfig } from "@rainbow-me/rainbowkit";
import { createSeismicDevnet } from "seismic-react/rainbowkit";

const myChain = createSeismicDevnet({
  nodeHost: "my-node.example.com",
});

const config = getDefaultConfig({
  appName: "My App",
  projectId: "YOUR_PROJECT_ID",
  chains: [myChain],
});
```

### With wagmi Config

```typescript
import { http, createConfig } from "wagmi";
import { createSeismicDevnet } from "seismic-react/rainbowkit";

const myChain = createSeismicDevnet({
  nodeHost: "my-node.example.com",
});

const config = createConfig({
  chains: [myChain],
  transports: {
    [myChain.id]: http(),
  },
});
```

### With Explorer URL

```typescript
const myChain = createSeismicDevnet({
  nodeHost: "my-node.example.com",
  explorerUrl: "https://explorer.example.com",
});
```

## Notes

* The `nodeHost` parameter should be the bare hostname without a protocol prefix or path. HTTPS and WSS URLs are constructed automatically.
* The Seismic icon is included automatically for display in RainbowKit's chain selector.
* The underlying implementation delegates to `createSeismicDevnet` from `seismic-viem` and wraps the result with RainbowKit metadata.

## See Also

* [Chains Overview](/clients/typescript/react/chains.md) - All supported chains
* [Seismic Testnet](/clients/typescript/react/chains/seismic-testnet.md) - Public testnet configuration
* [Sanvil](/clients/typescript/react/chains/sanvil.md) - Local development chains
* [Wallet Guides](/clients/typescript/react/wallet-guides.md) - RainbowKit setup guides


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.seismic.systems/clients/typescript/react/chains/create-seismic-devnet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.