Skip to content

docs: align Go requirements with source modules #58

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alexander-sei merged 3 commits into from
Aug 12, 2026
+41 −9
Merged

docs: align Go requirements with source modules #58

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d5b61d7
docs: align Go requirements with source modules
alexander-sei Aug 10, 2026
89bc692
docs: address review feedback on Go requirements
alexander-sei Aug 10, 2026
09ea59f
docs: correct GOTOOLCHAIN behavior and harden Go install block
alexander-sei Aug 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion evm/installing-seid-cli.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@

## Prerequisites

- Go 1.23+ (build from source only): Installation instructions are available [here](https://go.dev/doc/install). The prebuilt binary has no prerequisites.
- [Go 1.25.6 or later](https://go.dev/doc/install) is required only when building from source. Check the `go.mod` at the release tag you check out below (e.g. [`v6.6.1`](https://github.com/sei-protocol/sei-chain/blob/v6.6.1/go.mod)) for its exact requirement. Prebuilt binaries have no prerequisites.

@seidroid seidroid Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] node/seictl.mdx explains that under the default GOTOOLCHAIN=auto an older local Go still builds because the toolchain is downloaded on demand — but this line and node/index.mdx:69 state 1.25.6 as a hard floor with no such caveat. That makes the requirement stricter than reality and inconsistent across the three touched pages. A short parenthetical ("with the default GOTOOLCHAIN=auto, an older Go will fetch the required toolchain automatically") would align them.


## Installation

Expand Down Expand Up @@ -81,7 +81,7 @@

For more information see [here](https://pkg.go.dev/cmd/go#hdr-GOPATH_environment_variable).

## Command Overview

Check warning on line 84 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L84 

Use sentence case for headings: 'Command Overview'.

Seid supports all the commands you need to interact with the chain. To see a list of available commands and explanations of what they do, run seid:

Expand Down Expand Up @@ -129,7 +129,7 @@
Use "seid [command] --help" for more information about a command.
```

## Adding a Wallet

Check warning on line 132 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L132 

Use sentence case for headings: 'Adding a Wallet'.

You can create a new wallet using the seid keys command:

Expand Down Expand Up @@ -180,16 +180,16 @@
mnemonic: ""
```

## EVM Wallet Compatibility

Check warning on line 183 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L183 

Use sentence case for headings: 'EVM Wallet Compatibility'.

### Understanding Coin Types

Check warning on line 185 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L185 

Use sentence case for headings: 'Understanding Coin Types'.

Sei supports two coin types:

- Coin type 118 (default): Standard Cosmos address format
- Coin type 60: Ethereum-compatible address format for EVM wallets

### Creating an EVM-Compatible Wallet

Check warning on line 192 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L192 

Use sentence case for headings: 'Creating an EVM-Compatible Wallet'.

To create a new wallet that's compatible with EVM wallets like MetaMask:

Expand All @@ -216,7 +216,7 @@

<Info>`evm_address` is shown as empty here because it's only displayed after the key first broadcasts a transaction or is associated on-chain. The `0x` address is deterministically derived from the secp256k1 public key.</Info>

### Importing an Existing EVM Wallet

Check warning on line 219 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L219 

Use sentence case for headings: 'Importing an Existing EVM Wallet'.

To import an existing wallet from MetaMask or other EVM wallets:

Expand All @@ -242,7 +242,7 @@

<Info>Use coin type 60 when you want to use the same address across EVM-compatible chains or import from MetaMask. Use the default coin type 118 for standard Cosmos operations.</Info>

## Managing Wallets

Check warning on line 245 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L245 

Use sentence case for headings: 'Managing Wallets'.

To see your local wallets, you can run:

Expand Down Expand Up @@ -281,7 +281,7 @@

to see details about a specific wallet.

## Deleting Wallets

Check warning on line 284 in evm/installing-seid-cli.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

evm/installing-seid-cli.mdx#L284 

Use sentence case for headings: 'Deleting Wallets'.

To delete a wallet/key, you can use the following command:

Expand Down
38 changes: 31 additions & 7 deletions node/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,13 +19,13 @@
<Card horizontal title="Archive Nodes" icon="database" />
</CardGroup>

## Network Versions

Check warning on line 22 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L22 

Use sentence case for headings: 'Network Versions'.

<VersionTable />

_Live binary versions, genesis, and seed peers — see the [technical reference](/node/technical-reference)._

## Hardware Requirements

Check warning on line 28 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L28 

Use sentence case for headings: 'Hardware Requirements'.

| Component | Required |
| --------- | ------------------------------------------------------ |
Expand All @@ -34,7 +34,7 @@
| Storage | 2 TB NVMe SSD (high IOPS required) |
| Network | 2 Gbps with low latency |

## Installation & Setup Steps

Check warning on line 37 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L37 

Use sentence case for headings: 'Installation & Setup Steps'.

<Steps>

Expand All @@ -47,13 +47,13 @@
sudo apt update && sudo apt upgrade -y
```

###### 2. Install Essential Packages

Check warning on line 50 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L50 

Use sentence case for headings: '2. Install Essential Packages'.

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

###### 3. Synchronize System Time

Check warning on line 56 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L56 

Use sentence case for headings: '3. Synchronize System Time'.

```bash
sudo timedatectl set-timezone UTC
Expand All @@ -61,22 +61,36 @@
timedatectl
```

##### Install Go

Check warning on line 64 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L64 

Use sentence case for headings: 'Install Go'.

Only needed if you build `seid` from source — the prebuilt binary and Docker
install paths in the next step don't require 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.

Suggested Version: Go 1.24.x (required for seid v6.3+)
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`](https://github.com/sei-protocol/sei-chain/blob/v6.6.1/go.mod)) for its
exact requirement.

###### Installation Steps

Check warning on line 74 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L74 

Use sentence case for headings: 'Installation Steps'.

```bash
# Check for existing Go installation
# 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

# Download and install Go 1.24.x
wget https://go.dev/dl/go1.24.5.linux-amd64.tar.gz
sudo tar -C /usr/local -xzf go1.24.5.linux-amd64.tar.gz
# Bumping Go? Change these two lines only
GO_TARBALL=go1.25.6.linux-amd64.tar.gz
GO_SHA256=f022b6aad78e362bcba9b0b94d09ad58c5a70c6ba3b7582905fababf5fe0181a

@seidroid seidroid Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] Hardcoding the digest makes this snippet silently rot: every Go bump needs a manual checksum lookup, and if the constant is ever wrong the && chain aborts at sha256sum -c with a bare FAILED and no hint that the docs — not the download — are at fault. The comment two lines down already notes that go.dev publishes a per-file .sha256; fetching it makes the block self-maintaining and reduces the bump to one line:

curl -fLO https://go.dev/dl/${GO_TARBALL}
curl -fL https://go.dev/dl/${GO_TARBALL}.sha256 -o ${GO_TARBALL}.sha256
echo "$(cat ${GO_TARBALL}.sha256)  ${GO_TARBALL}" | sha256sum -c -

If you prefer to keep the pinned constant (it does defend against a compromised download endpoint serving a matching checksum), please double-check the value against go.dev before merge — I wasn't able to reach the network to verify it.


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 \

@seidroid seidroid Bot Aug 10, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] sudo rm -rf /usr/local/go is the procedure Go's own install docs prescribe, and gating it behind the checksum via && is the right ordering — no complaint about the intent. Two small things for a copy-paste block:

  • It deletes a working toolchain before the replacement is extracted, so a failed tar (out of disk, interrupted) leaves the reader with no Go at all.
  • It's a no-op for anyone who installed Go via a package manager (/usr/lib/go-*, Homebrew), and that older go can still win on PATH afterwards — mirroring the existing which -a seid tip with a which -a go hint would close that loop, since line 94's go version is what surfaces the problem.

&& sudo tar -C /usr/local -xzf ${GO_TARBALL}

# Add Go to your environment variables
echo 'export PATH=$PATH:/usr/local/go/bin' >> $HOME/.bashrc
Expand All @@ -85,6 +99,16 @@
# Verify installation
go version
```

<Note>
`sudo rm -rf /usr/local/go` is the replacement step [Go's install
docs](https://go.dev/doc/install) 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,

@seidroid seidroid Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[suggestion] This Note correctly diagnoses the shadowing case but stops short of the fix, and the cause is right above it: line 96 appends with export PATH=$PATH:/usr/local/go/bin, so a package-manager Go in /usr/bin keeps winning even after a clean install. Readers who hit the symptom you describe are left with which -a go output and no remedy. Suggest either prepending in the snippet (export PATH=/usr/local/go/bin:$PATH) or adding one sentence here telling readers to put /usr/local/go/bin ahead of $PATH, or to remove the packaged Go.

`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.
</Note>
</Step>

<Step title="Install Sei">
Expand Down Expand Up @@ -174,7 +198,7 @@
</Tab>
</Tabs>

##### Initialize Chain Files

Check warning on line 201 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L201 

Use sentence case for headings: 'Initialize Chain Files'.

<Info>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](/node/validators) for the full validator init example.</Info>

Expand Down Expand Up @@ -202,7 +226,7 @@
sed -i 's/persistent-peers = .*/persistent-peers = "'$PEERS'"/' ~/.sei/config/config.toml
```

##### Configure App Settings

Check warning on line 229 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L229 

Use sentence case for headings: 'Configure App Settings'.

```bash
# Set minimum gas price (recommended; helps prevent spam transactions)
Expand Down Expand Up @@ -232,7 +256,7 @@

<Accordion title="Advanced Configuration">

#### Archive Node Setup

Check warning on line 259 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L259 

Use sentence case for headings: '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".

Expand All @@ -246,7 +270,7 @@

**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

Check warning on line 273 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L273 

Use sentence case for headings: 'Mempool Configuration'.

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

Expand Down Expand Up @@ -334,7 +358,7 @@
sudo systemctl start seid
```

##### Monitoring & Troubleshooting

Check warning on line 361 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L361 

Use sentence case for headings: 'Monitoring & Troubleshooting'.

Check your node's status with these commands:

Expand Down Expand Up @@ -370,9 +394,9 @@

[View Complete Node Setup Guide](/node/node-operators)

## Node Resources

Check warning on line 397 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L397 

Use sentence case for headings: 'Node Resources'.

### Node Setup

Check warning on line 399 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L399 

Use sentence case for headings: 'Node Setup'.

<CardGroup cols={3}>
<Card horizontal title="Node Operations Guide" icon="server" href="/node/node-operators">
Expand All @@ -386,7 +410,7 @@
</Card>
</CardGroup>

### Advanced Operations

Check warning on line 413 in node/index.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/index.mdx#L413 

Use sentence case for headings: 'Advanced Operations'.

<CardGroup cols={3}>
<Card horizontal title="Configuration & Monitoring" icon="gauge-simple-high" href="/node/advanced-config-monitoring">
Expand Down
10 changes: 9 additions & 1 deletion node/seictl.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@

## Installation

### Pre-built Binaries (Recommended)

Check warning on line 23 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L23 

Use sentence case for headings: 'Pre-built Binaries (Recommended)'.

Pre-built binaries are available for Linux, macOS, and Windows. Download the latest release from
the [releases page](https://github.com/sei-protocol/seictl/releases).
Expand Down Expand Up @@ -87,7 +87,7 @@
seictl --version
```

#### Verify Download (Optional)

Check warning on line 90 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L90 

Use sentence case for headings: 'Verify Download (Optional)'.

All releases include a `checksums.txt` file for verification, e.g.:

Expand All @@ -99,13 +99,21 @@
sha256sum -c checksums.txt 2>&1 | grep seictl_Linux_x86_64.tar.gz
```

### Build from Source

Check warning on line 102 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L102 

Use sentence case for headings: 'Build from Source'.

If you prefer to build from source or need a specific configuration:

#### Prerequisites

- Go 1.24.5 or higher
- [Go 1.26.0 or later](https://go.dev/doc/install). The commands below build `main`, whose requirement is set in [`go.mod`](https://github.com/sei-protocol/seictl/blob/main/go.mod).

@seidroid seidroid Bot Aug 11, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nit] Linking blob/main/go.mod pins prose ("Go 1.26.0 or later") to a branch tip, so the stated number and the linked file will drift apart on the next bump — the same failure mode this PR is fixing for 1.23/1.24. The seid docs handle this better by linking a tag (v6.6.1). If seictl publishes release tags, consider linking the latest tag's go.mod instead; otherwise it may be worth phrasing the requirement as "see go.mod on main" without repeating the version inline.


<Note>
This is newer than the Go version needed to build `seid` (1.25.6), so the toolchain from
the [node setup guide](/node) is a minor version behind. Under the default
`GOTOOLCHAIN=auto` that still builds: the go command downloads the toolchain `go.mod`
asks for. If you've set `GOTOOLCHAIN=local` or build without network access, install Go
1.26.0 or later, or use a prebuilt binary above.
</Note>

#### Build

Expand All @@ -115,7 +123,7 @@
go build -o seictl
```

### Install via Go

Check warning on line 126 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L126 

Use sentence case for headings: 'Install via Go'.

```bash
go install github.com/sei-protocol/seictl@latest
Expand All @@ -127,13 +135,13 @@
seictl [global options] command [command options] [arguments...]
```

### Global Options

Check warning on line 138 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L138 

Use sentence case for headings: 'Global Options'.

- `--home <path>`: Sei home directory (default: `~/.sei`, can be set via `SEI_HOME` environment variable)

## Commands

### Patch Command

Check warning on line 144 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L144 

Use sentence case for headings: 'Patch Command'.

#### `patch`

Expand Down Expand Up @@ -168,7 +176,7 @@

**Note:** The file extension (`.toml` or `.json`) is used to determine the format automatically.

### Genesis Commands

Check warning on line 179 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L179 

Use sentence case for headings: 'Genesis Commands'.

#### `genesis patch`

Expand Down Expand Up @@ -199,7 +207,7 @@
seictl genesis patch patch.json -i
```

### Config Commands

Check warning on line 210 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L210 

Use sentence case for headings: 'Config Commands'.

#### `config patch`

Expand Down Expand Up @@ -235,7 +243,7 @@
seictl config patch patch.toml -o /path/to/output.toml
```

## Configuration Targets

Check warning on line 246 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L246 

Use sentence case for headings: 'Configuration Targets'.

The `config` command can work with three different configuration files:

Expand Down Expand Up @@ -271,7 +279,7 @@
- State sync and block sync
- Transaction indexing

## Merge Patch Behavior

Check warning on line 282 in node/seictl.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/seictl.mdx#L282 

Use sentence case for headings: 'Merge Patch Behavior'.

The merge patch algorithm works as follows:

Expand Down
Loading