Node Operations on Sei

Deploy and maintain Sei Network infrastructure with comprehensive guides for validators, RPC nodes, and archive nodes, including hardware requirements, installation steps, and operational best practices.

Power the Sei Network Infrastructure

Comprehensive guides for running, maintaining, and optimizing Sei network nodes. Whether you’re setting up a validator, an RPC node, or a relayer, you’ll find detailed instructions and best practices to ensure optimal performance and security.

RPC/API Nodes

Validator Nodes

Statesync Nodes

Archive Nodes

Network Versions

Live binary versions, genesis, and seed peers — see the technical reference.

Hardware Requirements

Component	Required
CPU	16 cores (Intel Xeon/Core i7/i9 or AMD Epyc/Ryzen)
RAM	256 GB DDR5 or better
Storage	2 TB NVMe SSD (high IOPS required)
Network	2 Gbps with low latency

Installation & Setup Steps

1. Environment Setup

   System Preparation

   1. Update and Upgrade System

   sudo apt update && sudo apt upgrade -y
   

   2. Install Essential Packages

   sudo apt install make gcc git jq chrony curl lz4 wget tar build-essential -y
   

   3. Synchronize System Time

   sudo timedatectl set-timezone UTC
   sudo systemctl enable --now chronyd
   timedatectl
   

   Install Go

   You need Go only if you build seid 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. Check the go.mod at the release tag you check out (e.g. v6.6.1) for its exact requirement.

   Installation Steps

   # Check for existing Go installations — more than one entry means another copy
   # may still win on your PATH after this install
   which -a go
   go version
   
   # Bumping Go? Change these two lines only
   GO_TARBALL=go1.25.6.linux-amd64.tar.gz
   GO_SHA256=f022b6aad78e362bcba9b0b94d09ad58c5a70c6ba3b7582905fababf5fe0181a
   
   curl -fLO https://go.dev/dl/${GO_TARBALL}
   
   # Verify integrity before trusting the archive (go.dev/dl publishes a SHA256 per file
   # at ${GO_TARBALL}.sha256), then replace any previous installation — extracting over
   # one leaves stale files behind
   echo "${GO_SHA256}  ${GO_TARBALL}" | sha256sum -c - \
     && sudo rm -rf /usr/local/go \
     && sudo tar -C /usr/local -xzf ${GO_TARBALL}
   
   # Add Go to your environment variables
   echo 'export PATH=$PATH:/usr/local/go/bin' >> $HOME/.bashrc
   source $HOME/.bashrc
   
   # Verify installation
   go version
   

   sudo rm -rf /usr/local/go is the replacement step Go’s install docs prescribe, but it only clears 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 rather than starting over.

2. Install Sei

   Install the seid binary

   See the Network Versions table above for the current recommended version.

   Prebuilt binary (recommended)

   Each release attaches statically linked seid builds for linux/amd64 and linux/arm64 with no runtime dependencies: no Go toolchain and no shared libraries to install.

   VERSION=<version-tag>  # e.g. v6.6.1 — see the Network Versions table above
   case "$(uname -m)" in
     x86_64)        ARCH=x86_64 ;;
     aarch64|arm64) ARCH=arm64  ;;
     *) echo "unsupported architecture: $(uname -m)" >&2; exit 1 ;;
   esac
   FILE=sei-chain_${VERSION#v}_linux_${ARCH}.tar.gz  # asset filenames omit the leading v
   
   curl -fLO https://github.com/sei-protocol/sei-chain/releases/download/${VERSION}/${FILE}
   curl -fLO https://github.com/sei-protocol/sei-chain/releases/download/${VERSION}/checksums.txt
   
   # Verify integrity before trusting the binary; extract and install only if it passes
   sha256sum -c checksums.txt --ignore-missing \
     && tar -xzf ${FILE} seid \
     && sudo install -m 0755 seid /usr/local/bin/seid
   
   # Verify installation
   seid version
   

   Prebuilt binaries are attached from v6.6.1 onward, and linux/arm64 from <arm64-release-tag>. For earlier versions, or other architectures, build from source or use Docker. They omit hardware Ledger support, so if you sign with a Ledger device, build from source or use Docker.

   Switching from a previous make install build? Remove the old copy (rm -f "$(go env GOPATH)/bin/seid") or make sure your service unit points at /usr/local/bin/seid — which -a seid lists every copy on your PATH.

   Build from source

   Requires Go and a C toolchain (see the Environment Setup step above).

   # Clone repository and install
   git clone https://github.com/sei-protocol/sei-chain.git
   cd sei-chain
   git checkout <version-tag>  # Replace with specific version
   make install
   
   # Verify installation
   seid version
   

   If you encounter an error like command not found: seid, you may need to set your GOPATH environment variable.

   Add the following to your ~/.bashrc or ~/.zshrc:

   export GOPATH=$(go env GOPATH)
   export PATH=$PATH:$GOPATH/bin
   

   Then reload your shell with source ~/.bashrc or source ~/.zshrc.

   For more information see here.

   Docker

   Official Docker images are available at GitHub Container Registry.

   # Pull the latest version
   docker pull ghcr.io/sei-protocol/sei:latest
   
   # Or pull a specific version (recommended)
   docker pull ghcr.io/sei-protocol/sei:v6.3.1
   

   Available architectures: linux/amd64 and linux/arm64.

   Initialize Chain Files

   Default init mode is full (RPC/P2P bind to all interfaces). For validator or seed nodes, use --mode validator or --mode seed so RPC and P2P bind to localhost only. See the Validator Operations Guide for the full validator init example.

   Peers can be found here -

   • mainnet (pacific-1):

   • testnet (atlantic-2):

   # Initialize node (default mode is full: RPC/P2P bind to all interfaces)
   # For validator nodes, use: seid init <your-moniker> --chain-id <chain-id> --mode validator
   seid init <your-moniker> --chain-id <chain-id>
   
   # Genesis is written automatically for known networks (mainnet and testnets); no download needed.
   
   # Configure peers in config.toml.
   PEERS="<comma-separated-peer-list>"
   
   #Set persistent peers in config.toml
   sed -i 's/persistent-peers = .*/persistent-peers = "'$PEERS'"/' ~/.sei/config/config.toml
   

   Configure App Settings

   # Set minimum gas price (recommended; helps prevent spam transactions)
   # Mainnet enforces a chain-wide minimum of 0.02usei, so set at least that value
   # Use "0usei" only for local development or private networks
   sed -i -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"0.02usei\"/" $HOME/.sei/config/app.toml
   
   # Tune mempool settings
   sed -i \
     -e 's/^keep-invalid-txs-in-cache = .*/keep-invalid-txs-in-cache = true/' \
     -e 's/^ttl-duration = .*/ttl-duration = "5s"/' \
     -e 's/^ttl-num-blocks = .*/ttl-num-blocks = 5/' \
     $HOME/.sei/config/config.toml
   
   # Set Concurrent Workers to 500 and enable occ
   sed -i -e "s/^#concurrency-workers *=.*/concurrency-workers = 500/" $HOME/.sei/config/app.toml
   sed -i -e "s/^occ-enabled *=.*/occ-enabled = true/" $HOME/.sei/config/app.toml
   

   In case of running an Archive Node, make sure to set your state-store settings to ss-keep-recent = 0 with

   sed -i 's/^ss-keep-recent = [0-9]*/ss-keep-recent = 0/' ~/.sei/config/app.toml
   

   Advanced Configuration

   Archive Node Setup

   An archive node maintains the complete historical record of the chain. This requires disabling state sync and starting with a pre-existing database using a “snapshot”.

   1. Disable State Sync — In $HOME/.sei/config/config.toml , modify the [statesync] section:

   # State sync configuration
   [statesync]
   enable = false
   

   2. Configure Archive Node Peers — To sync from the height your snapshot was created at, you need peers retaining a large amount of historical blocks. The node will require specific peers during initial sync, which can be changed at a later time.

   Mempool Configuration

   For optimal transaction handling and resource management, it is recommended to update the mempool settings in your config.toml file.

   Adjust these parameters if you encounter performance or resource issues on your specific hardware.

   # Mempool configuration settings
   [mempool]
   
   # Broadcast transactions to other nodes
   broadcast = true
   
   # Maximum number of transactions in the mempool
   size = 5000
   
   # Limit the total size of all txs in the mempool.
   max-txs-bytes = 10737418240
   
   # Size of the cache (used to filter duplicate transactions)
   cache-size = 10000
   
   # Do not remove invalid transactions from the cache
   keep-invalid-txs-in-cache = true
   
   # Maximum size of a single transaction
   max-tx-bytes = 2048576
   
   # Maximum size of a batch of transactions to send to a peer
   max-batch-bytes = 0
   
   # Maximum length of time a transaction can remain in the mempool
   ttl-duration = "3s"
   
   # Maximum number of blocks a transaction can remain in the mempool
   ttl-num-blocks = 5
   
   tx-notify-threshold = 0
   
   check-tx-error-blacklist-enabled = true
   
   check-tx-error-threshold = 50
   
   pending-size = 5000
   
   max-pending-txs-bytes = 1073741824
   
   pending-ttl-duration = "3s"
   
   pending-ttl-num-blocks = 5
   
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 you can’t start nodes straight from the genesis file. Instead, sync to the block tip via state sync or using a snapshot.

   For production deployments, configure a systemd service to ensure your node restarts automatically:

   # Create the systemd service file
   sudo tee /etc/systemd/system/seid.service > /dev/null << EOF
   [Unit]
   Description=Sei Node
   After=network-online.target
   
   [Service]
   User=$USER
   ExecStart=$(which seid) start
   Restart=always
   RestartSec=3
   LimitNOFILE=65535
   
   [Install]
   WantedBy=multi-user.target
   EOF
   
   # Reload systemd, enable and start the service
   sudo systemctl daemon-reload
   sudo systemctl enable seid
   sudo systemctl start seid
   

   Monitoring & Troubleshooting

   Check your node’s status with these commands:

   # Check sync status
   seid status
   
   # Monitor logs in real-time
   journalctl -u seid -f -o cat
   
   # Check validator status (if running a validator)
   seid query staking validator $(seid keys show <your_key> --bech val -a)
   

   Common Issues & Solutions

   Sync Issues

   • Verify sufficient disk space
   • Ensure stable network connectivity
   • Confirm system time is synchronized
   • Consider using state sync for initial setup

   Performance Problems

   • Monitor system resources (CPU, RAM, I/O)
   • Evaluate disk performance and network bandwidth
   • Adjust mempool and peer settings if needed

View Complete Node Setup Guide

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 app.toml, config.toml, and client.toml shipped by 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.