Cover linux/arm64 in the prebuilt seid install and upgrade steps

evm/installing-seid-cli.mdx

@@ -22,12 +22,17 @@
 
 <Tabs>
  <Tab title="Prebuilt binary (recommended)">
- Each release attaches a statically linked `seid` build for `linux/amd64` with no
- runtime dependencies:
+ Each release attaches statically linked `seid` builds for `linux/amd64` and
+`linux/arm64` with no runtime dependencies:
 
  ```bash
  VERSION=<version-tag> # e.g. v6.6.1 — see the version table above
- FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz # asset filenames omit the leading v
+ 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
@@ -39,9 +44,10 @@
  ```
 
  <Info>
- Prebuilt binaries are attached from `v6.6.1` onward — for earlier versions, build
- from source. They are `linux/amd64` only and omit hardware Ledger support. On
- other architectures, or if you sign with a Ledger device, build from source.
+ 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. They omit hardware Ledger support, so if you sign with a Ledger device,
+ build from source.
  </Info>
 
  <Note>
@@ -81,7 +87,7 @@
 
 For more information see [here](https://pkg.go.dev/cmd/go#hdr-GOPATH_environment_variable).
 
 ## 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:
 
@@ -129,7 +135,7 @@
 Use "seid [command] --help" for more information about a command.
 ```
 
 ## Adding a Wallet
 
 You can create a new wallet using the seid keys command:
 
@@ -180,16 +186,16 @@
  mnemonic: ""
 ```
 
 ## EVM Wallet Compatibility
 
 ### 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
 
 To create a new wallet that's compatible with EVM wallets like MetaMask:
 
@@ -216,7 +222,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
 
 To import an existing wallet from MetaMask or other EVM wallets:
 
@@ -242,7 +248,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
 
 To see your local wallets, you can run:
 
@@ -281,7 +287,7 @@
 
 to see details about a specific wallet.
 
 ## Deleting Wallets
 
 To delete a wallet/key, you can use the following command:
 

node/index.mdx

@@ -19,13 +19,13 @@
  <Card horizontal title="Archive Nodes" icon="database" />
 </CardGroup>
 
 ## Network Versions
 
 <VersionTable />
 
 _Live binary versions, genesis, and seed peers — see the [technical reference](/node/technical-reference)._
 
 ## Hardware Requirements
 
 | Component | Required |
 | --------- | ------------------------------------------------------ |
@@ -34,7 +34,7 @@
 | Storage | 2 TB NVMe SSD (high IOPS required) |
 | Network | 2 Gbps with low latency |
 
 ## Installation & Setup Steps
 
 <Steps>
 
@@ -47,13 +47,13 @@
 sudo apt update && sudo apt upgrade -y
 ```
 
 ###### 2. Install Essential Packages
 
 ```bash
 sudo apt install make gcc git jq chrony curl lz4 wget tar build-essential -y
 ```
 
 ###### 3. Synchronize System Time
 
 ```bash
 sudo timedatectl set-timezone UTC
@@ -61,7 +61,7 @@
 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.
@@ -71,7 +71,7 @@
 (e.g. [`v6.6.1`](https://github.com/sei-protocol/sei-chain/blob/v6.6.1/go.mod)) for its
 exact requirement.
 
 ###### Installation Steps
 
 ```bash
 # Check for existing Go installations — more than one entry means another copy
@@ -118,12 +118,18 @@
 
 <Tabs>
  <Tab title="Prebuilt binary (recommended)">
- Each release attaches a statically linked `seid` build for `linux/amd64` with no
- runtime dependencies: no Go toolchain and no shared libraries to install.
+ 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.
 
  ```bash
  VERSION=<version-tag> # e.g. v6.6.1 — see the Network Versions table above
- FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz # asset filenames omit the leading v
+ 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
@@ -138,10 +144,10 @@
  ```
 
  <Info>
- Prebuilt binaries are attached from `v6.6.1` onward. For earlier versions,
-build from source or use Docker. They are `linux/amd64` only and omit hardware
-Ledger support. On other architectures, or if you sign with a Ledger device,
- build from source or use Docker.
+ 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.
  </Info>
 
  <Note>
@@ -196,7 +202,7 @@
  </Tab>
 </Tabs>
 
 ##### 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>
 
@@ -224,7 +230,7 @@
 sed -i 's/persistent-peers = .*/persistent-peers = "'$PEERS'"/' ~/.sei/config/config.toml
 ```
 
 ##### Configure App Settings
 
 ```bash
 # Set minimum gas price (recommended; helps prevent spam transactions)
@@ -254,7 +260,7 @@
 
 <Accordion title="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".
 
@@ -268,7 +274,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
 
 For optimal transaction handling and resource management, it is recommended to update the mempool settings in your `config.toml` file.
 
@@ -356,7 +362,7 @@
 sudo systemctl start seid
 ```
 
 ##### Monitoring & Troubleshooting
 
 Check your node's status with these commands:
 
@@ -392,9 +398,9 @@
 
 [View Complete Node Setup Guide](/node/node-operators)
 
 ## Node Resources
 
 ### Node Setup
 
 <CardGroup cols={3}>
  <Card horizontal title="Node Operations Guide" icon="server" href="/node/node-operators">
@@ -408,7 +414,7 @@
  </Card>
 </CardGroup>
 
 ### Advanced Operations
 
 <CardGroup cols={3}>
  <Card horizontal title="Configuration & Monitoring" icon="gauge-simple-high" href="/node/advanced-config-monitoring">

node/node-operators.mdx

@@ -9,9 +9,9 @@
 including configuration management, maintenance procedures, and best practices
 for stable and performant operations.
 
 ## Configuration Management
 
 ### Directory Structure
 
 The Sei node configuration is stored in `$HOME/.sei/config/`:
 
@@ -40,9 +40,9 @@
 [Default Configurations](#default-configurations) at the bottom of this
 section.
 
 ### Essential Configuration Parameters
 
 #### Network Settings (config.toml)
 
 ```toml
 [p2p]
@@ -68,7 +68,7 @@
 timeout-broadcast-tx-commit = "10s"
 ```
 
 #### Application Settings (app.toml)
 
 ```toml
 # Minimum gas prices to prevent spam transactions
@@ -108,7 +108,7 @@
 rs-backend = "pebbledb"
 ```
 
 ### Default Configurations
 
 The full unmodified `app.toml`, `config.toml`, and `client.toml` produced by
 `seid init` against the latest tagged `seid` release. Use these as the
@@ -1362,7 +1362,7 @@
  </Tab>
 </Tabs>
 
 ## Database Management
 
 ### Architecture
 
@@ -1386,7 +1386,7 @@
 deprecated and slated for removal — new deployments and existing nodes
 should run on SeiDB.
 
 ### SeiDB Configuration
 
 The full set of knobs is in the auto-generated
 [Default Configurations](#default-configurations) above. The block below
@@ -1460,7 +1460,7 @@
 snapshot creation. Too-large (less frequent) intervals mean pruning takes
 longer overall, which can cause missed blocks and excessive resync time.
 
 #### PebbleDB version encoding
 
 Fresh PebbleDB state stores use descending-version MVCC encoding. Sei includes
 the version in each key and sorts newer versions first. This lets
@@ -1513,7 +1513,7 @@
 but it does not remove the cost of long-history iteration. Benchmark the
 replacement under your trace workload before you cut over.
 
 ### Giga Storage and Giga Executor
 
 These are two **separate** opt-in features that ship in newer `seid`
 releases. Both default to off; only enable them deliberately and after
@@ -1557,7 +1557,7 @@
 occ_enabled = false
 ```
 
 ### Database Maintenance
 
 The database is typically stable and can be left alone, although some attention
 may be required:
@@ -1584,9 +1584,9 @@
 
 <Warning>The wipe command above deletes the entire local database (everything except `priv_validator_state.json`) and the `wasm` folder. It does not compact data in place — after running it, the node must be re-synced from a [snapshot](/node/snapshot) or via [state sync](/node/statesync) before it can serve traffic again.</Warning>
 
 ## Service Management
 
 ### Systemd Commands
 
 ```bash
 # Check service status
@@ -1605,7 +1605,7 @@
 journalctl -fu seid -o cat
 ```
 
 ### Log Management
 
 Prevent logs from consuming excessive disk space by enabling rotation:
 
@@ -1626,7 +1626,7 @@
 EOF
 ```
 
 ## Update Procedures
 
 <Info>
  Upgrade with the same method you originally installed with: `make install`
@@ -1636,7 +1636,7 @@
  `which -a seid` lists every copy.
 </Info>
 
 ### Minor Updates
 
 For minor updates that are non-consensus-breaking:
 
@@ -1648,7 +1648,12 @@
 
  # Download and verify the new release binary
  VERSION=<new-version> # the new release tag, e.g. v6.6.1
- FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz # asset filenames omit the leading v
+ 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
@@ -1678,7 +1683,7 @@
  </Tab>
 </Tabs>
 
 ### Major Updates
 
 For major upgrades that introduce state-breaking changes:
 
@@ -1693,7 +1698,12 @@
  ```bash
  # After node halts
  VERSION=<new-version> # the new release tag, e.g. v6.6.1
- FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz
+ 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
 
  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
@@ -1722,7 +1732,7 @@
  halt-height so the swap takes seconds at upgrade time.
 </Tip>
 
 ## Performance Optimization
 
 Performance optimizations can yield different results depending on your system's
 hardware, workload, and network conditions. Before implementing any changes,
@@ -1730,7 +1740,7 @@
 your specific configuration and requirements. Always back up important data
 before making modifications.
 
 ### Memory Management (sysctl tuning)
 
 Optimizing memory management settings can help improve performance and
 stability, particularly for high-load nodes. These settings control swap usage
@@ -1744,7 +1754,7 @@
 vm.dirty_writeback_centisecs = 100 # Frequency (in hundredths of a second) at which the system writes "dirty" pages to disk
 ```
 
 ### Network Stack Optimization
 
 Tuning the network stack can enhance packet processing efficiency and
 throughput, particularly for nodes handling a large number of peers and high
@@ -1758,7 +1768,7 @@
 net.core.wmem_max = 16777216 # send buffer size for network sockets
 ```
 
 ### Storage Optimization
 
 Optimizing storage settings can significantly reduce write latency and improve
 database performance, especially for nodes using NVMe SSDs.
@@ -1768,9 +1778,9 @@
 blockdev --setra 4096 /dev/nvme0n1 # readahead value to optimize sequential reads
 ```
 
 ## Backup and Recovery
 
 ### Regular Backups
 
 Automate backups to avoid data loss:
 
@@ -1789,7 +1799,7 @@
 systemctl start seid
 ```
 
 ### Recovery Procedure
 
 Restoring from backup in case of corruption or accidental deletion:
 
@@ -1807,7 +1817,7 @@
 systemctl start seid
 ```
 
 ## Security Considerations
 
 - Use firewalls and rate-limiting to prevent attacks
 - Keep your system and node software updated