RPC/API nodes
Validator nodes
State sync nodes
Archive nodes
Network versions
For live binary versions, genesis, and seed peers, see the technical reference.Hardware requirements
Installation & setup steps
1
Environment setup
System preparation
1. Update and upgrade system
2. Install essential packages
3. Synchronize system time
Install Go
You need Go only if you buildseid from source. The prebuilt binary and Docker
install paths in the next step do not require it.Current seid releases require Go 1.25.6 or later. For the exact requirement, check the
go.mod at the release tag that you check out (for example,
v6.6.1).Installation steps
sudo rm -rf /usr/local/go is the replacement step that Go’s install
docs prescribe. It clears only a tarball install. A
package-manager Go (/usr/lib/go-*, Homebrew) survives it and can still shadow
/usr/local/go/bin/go. If the final go version reports the old release,
which -a go lists every copy on your PATH. If the extraction itself fails, the
verified tarball is still in your working directory. Re-run the sudo tar command
instead of starting over.2
Install Sei
Install the seid binary
For the current recommended version, see the Network Versions table above.- Prebuilt binary (recommended)
- Build from source
- Docker
Each release attaches a statically linked
seid build for linux/amd64 with no
runtime dependencies. You do not need to install a Go toolchain or shared libraries.Prebuilt binaries are attached from
v6.6.1 onward. For earlier versions,
build from source or use Docker. Prebuilt binaries are linux/amd64 only and do not
include hardware Ledger support. On other architectures, or if you sign with a Ledger
device, build from source or use Docker.If you are switching from a previous
make install build, remove the old copy
(rm -f "$(go env GOPATH)/bin/seid"). Alternatively, make sure that your service unit
points at /usr/local/bin/seid. The which -a seid command lists every copy on your PATH.Initialize chain files
The default init mode is full, in which RPC and P2P bind to all interfaces. For validator or seed nodes, use
--mode validator or --mode seed. In these modes, RPC and P2P bind to localhost only. For the full validator init example, see the Validator Operations Guide.- Sei Mainnet (pacific-1):
- Sei Testnet (atlantic-2):
Configure app settings
If you run an archive node, use this command to set
ss-keep-recent = 0 in your state-store settings:Advanced configuration
Advanced configuration
Archive node setup
An archive node keeps the complete historical record of the chain. To run one, you must disable state sync and start from a pre-existing database (a snapshot).1. Disable state sync: In$HOME/.sei/config/config.toml, modify the [statesync] section:Mempool configuration
For optimal transaction handling and resource management, update the mempool settings in yourconfig.toml file.If you have performance or resource issues on your hardware, adjust these parameters.
pending-ttl-duration and pending-ttl-num-blocks are deprecated and have no effect. They are ignored, whatever value you set.3
Run node
Setting up a systemd service
If you see an error such as
panic: recovered: runtime error: integer divide by zero, it means that you cannot start nodes directly from the genesis file. Instead, sync to the block tip with state sync or a snapshot.Monitoring & troubleshooting
Check your node’s status with these commands:Sync issues
- Verify that you have enough disk space
- Make sure that the network connection is stable
- Confirm that the system time is synchronized
- Consider using state sync for the initial setup
Performance problems
- Monitor system resources (CPU, RAM, I/O)
- Evaluate disk performance and network bandwidth
- Adjust mempool and peer settings if needed
Node resources
Node setup
Node operations guide
Complete guide to setting up and running a Sei node, with hardware requirements and configuration steps.
Validator operations guide
Specialized instructions for validators, including staking, commission settings, and security best practices.
Default configurations
Full reference for the
app.toml, config.toml, and client.toml files from the latest seid release.Advanced operations
Configuration & monitoring
Optimize your node’s performance with advanced settings and monitoring tools.
Giga SS store migration
Move EVM historical state into dedicated state-store databases on supported RPC nodes.
Technical reference
Detailed technical specifications, API endpoints, and commands for node operators.