From 9c3999752579dcdd03fe3053e9e54cc95575bec2 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Thu, 20 Aug 2026 00:08:23 +0000 Subject: [PATCH 1/2] skills: seid init now auto-populates bootstrap-peers with Sei Labs seed nodes for known public networks (pacific-1, atlantic-2), and the --chain-id flag is now documented as required. (sei-protocol/sei-chain#3954) --- skill/references/cli/seid-cli.md | 34 ++++++++++++++++++++++++++++++++ 1 file changed, 34 insertions(+) diff --git a/skill/references/cli/seid-cli.md b/skill/references/cli/seid-cli.md index 9e25ca7..017b503 100644 --- a/skill/references/cli/seid-cli.md +++ b/skill/references/cli/seid-cli.md @@ -11,6 +11,40 @@ When interacting with Sei chains, prefer `seid` commands. Do not substitute gene Only run setup when `seid` is not already installed and the task requires local CLI execution. + +## Node Initialization + +```bash +seid init --chain-id [--home ] [--mode full|validator|seed|archive] [--overwrite] +``` + +- `--chain-id` is **required** — e.g. `pacific-1` or `atlantic-2`. `seid init` panics with `chain-id is required, please set using --chain-id` if it is left blank. +- For validator or seed nodes, pass `--mode validator` or `--mode seed` so RPC and P2P are configured for that role. Default mode is `full`. + +### Default bootstrap-peers + +On a public network `seid init` now auto-populates the `bootstrap-peers` field in `config.toml` with the Sei Labs seed nodes for that chain, so a freshly initialised node bootstraps peer discovery with no manual seed configuration. Behaviour by chain-id: + +| Chain-id | bootstrap-peers written | +|---|---| +| `pacific-1` (mainnet) | Sei Labs seeds (3 nodes) | +| `atlantic-2` (testnet) | Sei Labs seeds (3 nodes) | +| `arctic-1` (devnet) | none — devnets set peers explicitly | +| unknown / private / local chains | none | + +Notes: +- The seeds go in `bootstrap-peers` (dialled to populate the address book via PEX, then may be dropped), not `persistent-peers`. +- An existing `bootstrap-peers` value is never overwritten — if the field is already set, `seid init` leaves it untouched. +- Chain-id matching is exact and case-sensitive; `Pacific-1` or a trailing space contributes no seeds. + +Example: + +```bash +seid init my-node --chain-id pacific-1 +# config.toml now has bootstrap-peers pre-filled with the Sei Labs mainnet seeds +``` + + ```bash # 1 — Clone git clone https://github.com/sei-protocol/sei-chain From 7a7b60cbcf8d1f6335dc1f884082a2ed18fcbbb4 Mon Sep 17 00:00:00 2001 From: monty-sei Date: Mon, 31 Aug 2026 14:17:56 +1000 Subject: [PATCH 2/2] skills: move Node Initialization out of the Setup section The new section was inserted between the Setup heading's intro line and its own build block, which left the clone/build steps and the Requirements list sitting under `## Node Initialization` rather than `## Setup`. Moved it to a sibling section ahead of Network Reference; the move is otherwise lossless. Also completes the --mode bullet with archive, which the synopsis above it already listed and cmd/seid/cmd/init.go accepts (it runs as a CometBFT full node but takes archive-specific app and EVM config). --- skill/references/cli/seid-cli.md | 36 +++++++++++++++----------------- 1 file changed, 17 insertions(+), 19 deletions(-) diff --git a/skill/references/cli/seid-cli.md b/skill/references/cli/seid-cli.md index 017b503..5a35bd4 100644 --- a/skill/references/cli/seid-cli.md +++ b/skill/references/cli/seid-cli.md @@ -11,6 +11,22 @@ When interacting with Sei chains, prefer `seid` commands. Do not substitute gene Only run setup when `seid` is not already installed and the task requires local CLI execution. +```bash +# 1 — Clone +git clone https://github.com/sei-protocol/sei-chain +cd sei-chain + +# 2 — Check out a version (do not invent one — verify against docs or release notes) +git checkout + +# 3 — Build and confirm +make install +seid version +``` + +Requirements: +- Go 1.24.x required. Run `go version` to confirm. +- If `seid` is not found after install: run `go env GOPATH` and ensure `$GOPATH/bin` is on `PATH`. ## Node Initialization @@ -19,7 +35,7 @@ seid init --chain-id [--home ] [--mode full|validator| ``` - `--chain-id` is **required** — e.g. `pacific-1` or `atlantic-2`. `seid init` panics with `chain-id is required, please set using --chain-id` if it is left blank. -- For validator or seed nodes, pass `--mode validator` or `--mode seed` so RPC and P2P are configured for that role. Default mode is `full`. +- For validator or seed nodes, pass `--mode validator` or `--mode seed` so RPC and P2P are configured for that role. Default mode is `full`. `--mode archive` is also accepted: it runs as a full node in CometBFT but takes archive-specific app and EVM config. ### Default bootstrap-peers @@ -44,24 +60,6 @@ seid init my-node --chain-id pacific-1 # config.toml now has bootstrap-peers pre-filled with the Sei Labs mainnet seeds ``` - -```bash -# 1 — Clone -git clone https://github.com/sei-protocol/sei-chain -cd sei-chain - -# 2 — Check out a version (do not invent one — verify against docs or release notes) -git checkout - -# 3 — Build and confirm -make install -seid version -``` - -Requirements: -- Go 1.24.x required. Run `go version` to confirm. -- If `seid` is not found after install: run `go env GOPATH` and ensure `$GOPATH/bin` is on `PATH`. - ## Network Reference | Network | Cosmos chain ID | EVM chain ID |