Node Operations

Power the Sei Network Infrastructure

This section provides 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.

Node Types:

RPC/API Nodes

Validator Nodes

Statesync Nodes

Archive Nodes

Network Versions

Network	Version	Chain ID	Genesis File
Mainnet	Fetching...	pacific-1	Genesis
Testnet	Fetching...	atlantic-2	Genesis

Hardware Requirements

⚠️

For best performance, run seid directly on bare metal hardware (no virtualization or containers). Running seid under Docker or Kubernetes for example can significantly degrade performance and cause your node to consistenly fall behind the chain tip.

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

Installation & Setup Steps

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

Suggested Version: Go 1.22.x (Do NOT use Go 1.23.x)

Installation Steps


# Check for existing Go installation
go version
 
# Download and install Go 1.22.x
wget https://go.dev/dl/go1.22.12.linux-amd64.tar.gz
sudo tar -C /usr/local -xzf go1.22.12.linux-amd64.tar.gz
 
# Add Go to your environment variables
echo 'export PATH=$PATH:/usr/local/go/bin' >> $HOME/.bashrc
source $HOME/.bashrc
 
# Verify installation
go version

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

Suggested Version: Go 1.22.x (Do NOT use Go 1.23.x)

Installation Steps


# Check for existing Go installation
go version
 
# Download and install Go 1.22.x
wget https://go.dev/dl/go1.22.12.linux-amd64.tar.gz
sudo tar -C /usr/local -xzf go1.22.12.linux-amd64.tar.gz
 
# Add Go to your environment variables
echo 'export PATH=$PATH:/usr/local/go/bin' >> $HOME/.bashrc
source $HOME/.bashrc
 
# Verify installation
go version

Install Sei Binary


# 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

See Network Versions table above for current recommended version.

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

Use go env GOPATH to find your GOPATH

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


export GOPATH=[your GOPATH from step 1]
export PATH=$PATH:$GOPATH/bin

For more information see here .

Initialize Chain Files

Peers can be found here -

mainnet (pacific-1):


PEERS="3be6b24cf86a5938cce7d48f44fb6598465a9924@p2p.state-sync-0.pacific-1.seinetwork.io:26656,b21279d7092fde2e41770832a1cacc7d0051e9dc@p2p.state-sync-1.pacific-1.seinetwork.io:26656,616c05e9ba24acc89c0de630b5e3adbedaebb478@p2p.state-sync-2.pacific-1.seinetwork.io:26656"

testnet (atlantic-2):


PEERS="b2664ccaa84a04b67683093fefb802b172ead6d1@sei-a2-rpc.p2p.brocha.in:30612,babc3f3f7804933265ec9c40ad94f4da8e9e0017@testnet-seed.rhinostake.com:11956"


# Initialize node
seid init <your-moniker> --chain-id <chain-id>
 
# Get genesis file
wget -O $HOME/.sei/config/genesis.json <genesis-file-url>
 
# 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

In case of running an Archive Node, make sure to set you state-store settings bash copy sed -i 's/^ss-keep-recent = [0-9]*/ss-keep-recent = 0/' ~/.sei/config/app.toml

Configure App Settings


# Set minimum gas price (recommended)
sed -i -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"0usei\"/" $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
 
# Adjust pruning settings for better performance (optional)
sed -i -e "s/^pruning *=.*/pruning = \"custom\"/" $HOME/.sei/config/app.toml
sed -i -e "s/^pruning-keep-recent *=.*/pruning-keep-recent = \"100\"/" $HOME/.sei/config/app.toml
sed -i -e "s/^pruning-interval *=.*/pruning-interval = \"50\"/" $HOME/.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.

3. Restore from Snapshot

Archive nodes must restore from a trusted, full historical snapshot. There may be several providers.

Archive Snapshot Resources:

Additional guidance can be found here.

Snapshot Restoration Steps:

Stop the node service:


sudo systemctl stop seid

Restart the node service after downloading and extracting the snapshot (not shown):


sudo systemctl start seid

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

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 | jq .SyncInfo
 
# 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.

Advanced Operations

Configuration & Monitoring

Optimize your node’s performance with advanced settings and monitoring tools.

Technical Reference

Detailed technical specifications, API endpoints, and commands for node operators.