Sei node
A Sei RPC node of your own. Built around EVM JSON-RPC.
Sei is moving to EVM only, so the part of a node to build on is its EVM JSON-RPC, on ports 8545 and 8546. Rent a dedicated Sei node and get a private endpoint for it, with the Cosmos endpoints that still work today. It needs a very large server. A backup node sits beside yours.
Updated . Prices checked .
- Full
- $289/mo
- Ready
- 24 h
On this pageNode type
02Node type
What a Sei RPC node does.
A Sei RPC node is the default kind of node: it follows the chain and answers requests. It does not sign blocks.
Full node
$289/mo
- Does
- Runs seid, keeps up with every new Sei block and serves your calls
- Serves
- EVM JSON-RPC over HTTP on 8545 and WebSocket on 8546. Also CometBFT RPC on 26657, REST on 1317 and gRPC on 9090, while Sei keeps them
- History
- A node that serves RPC must keep the historical state store on. The Sei docs show 100,000 states as about 28 hours of history
- Archive
- Not offered. The Sei node types page says an archive node needs at least 10 TB
- Validator
- Not offered. This page is for the RPC node only
The one-line test
Do you read Sei with eth_ calls from an EVM app, bot or indexer? A node of your own fits. Do you rely on sei1 addresses or IBC? Plan your move, because the final Cosmos shutdown has no date yet.
03How it works
Inside a Sei node: one program, two kinds of API.
The Sei program runs consensus and the EVM together. You choose which API your app talks to.
seid
The Sei node program. It contains CometBFT consensus and the EVM, so there is nothing to wire together.
Peer port
Port 26656 connects the node to the rest of the network.
EVM side
JSON-RPC over HTTP on 8545 and over WebSocket on 8546.
Cosmos side
Cosmos RPC, REST and gRPC answer at the same private URL, for as long as Sei serves them.
Sei has no separate execution and consensus programs to match. One binary, seid, carries both.
The EVM ports 8545 and 8546 are the ones to rely on. No Sei page says whether Cosmos RPC, REST or gRPC survive the final upgrade.
A fresh node cannot start from the first block. The Sei docs say that fails, so start from a snapshot or state sync.
04Know the field
What Sei really needs to run.
The Sei docs ask for a server far bigger than most chains do, and the sizes show why.
The snapshot was taken at block height 239,951,863. The docs ask for NVMe storage with high IOPS, which means many reads and writes per second.
Sei docs, hardware
Pruned snapshot
Storage change (Eidos)
Sync
Read in October 2026. The storage database setting must be pebbledb. RocksDB support is to be removed, with no date given.
CPU, memory and network figures for Sei nodes, from the official docs: see the node requirements index.
05Sei, specifically
SIP-3: Sei's move to EVM only, step by step.
From the Sei migration guide. The last step has no date, and we will not guess one.
May 2025: SIP-3 accepted
The Sei SIP-3 announcement set the plan: drop CosmWasm and native Cosmos transactions, so only EVM addresses start transactions.
Proposal 115
The Sei SIP-3 migration guide says proposal 115 disabled CosmWasm code uploads and new contract instantiations.
Proposals 116 and 120
Both switched inbound IBC off, so tokens stopped arriving from other Cosmos chains.
Proposal 121, 31 July 2026
Switched outbound IBC off. Tokens can no longer leave over IBC. The final shutdown of Cosmos interfaces has no date.
What stays
Native SEI transfers, staking, the Sei EVM, and execute and query calls on existing CosmWasm contracts keep working, per the guide.
What stops
After the final upgrade, sei1 addresses and Cosmos-native transactions stop, and so does the IBC precompile.
06Who rents one
Why teams rent one.
People who need Sei's EVM side on infrastructure nobody else shares.
EVM bots and market makers
Send and read EVM calls without sharing a public endpoint or its rate limits.
Exchanges and custodians
Check deposits and balances on EVM addresses from a node you control, as Cosmos addresses wind down.
Indexers and explorers
Read blocks and EVM logs from a node that keeps its historical state store on.
EVM apps on Sei
Point your contracts and backends at one private URL. Every node price is listed in one place.
07Price check
Under half the Allnodes price.
Allnodes publishes a dedicated Sei price for its full node, so that bar compares directly. Nobody else we checked publishes one.
Full node
Allnodes: the cheapest dedicated plan on its Sei pricing page.
You save each month
$351 full
against the Allnodes list price above
08What you get
Set the term.
Pick the node type and how long to prepay. The price updates as you choose.
Your Sei node
Term
- A dedicated server sized for Sei
- seid with EVM JSON-RPC and Cosmos endpoints, one endpoint
- A backup node, included
- A private endpoint on nodes.herorpc.com
- Your server logins
- No setup fee, ready within 24 hours
$289
a month, full node
Billed monthly
Pay in BTC, ETH, USDT, USDC, BNB, SOL, TRX, LTC, DOGE or XMR.
10Questions
Sei RPC node questions
Real questions from node operators, answered plainly.
What is a Sei RPC node?
A server running seid that follows the Sei chain and answers requests. It is the default Sei node kind, and it does not sign blocks.
Is Sei still a Cosmos chain?
It is moving to EVM only under SIP-3. CosmWasm uploads are disabled and IBC is switched off both ways. The final shutdown of Cosmos interfaces has no date in the Sei docs.
Will Cosmos RPC still work after SIP-3?
The docs say sei1 addresses and Cosmos-native transactions will stop. They do not say whether CometBFT RPC, REST or gRPC survive, so build on the EVM ports.
Which ports does a Sei node use?
Peers on 26656, CometBFT RPC on 26657, REST on 1317, gRPC on 9090, EVM HTTP on 8545 and EVM WebSocket on 8546.
How much memory does a Sei node need?
The Sei docs ask for 256 GB of DDR5 memory or better, a 16-core CPU, 2 TB of NVMe storage and 2 Gbps. That is why Sei sits at a higher price than most chains.
How big is a Sei node?
A pruned snapshot was 227 GB in October 2026. The docs recommend 2 TB of disk, and say an archive node needs at least 10 TB.
Is there a Sei archive node?
Not offered. Your RPC node keeps a historical state store, and the retention setting decides how far back it reaches.
Why does state sync fail sometimes?
The Sei docs say it can need about 4 to 5 attempts. The same docs say a node cannot sync from the first block at all, so use a snapshot or state sync.
What does it cost?
$289 every month, with nothing to pay up front for setup. Twelve months prepaid cuts 25 percent.
How soon is my Sei node ready?
Usually under a day. When the node has caught up, the dashboard lists your URL and login details.
Your own Sei RPC, EVM first.
$289 monthly. A second node runs next to yours, ready within a day.