diff --git a/node/index.mdx b/node/index.mdx
index 323bd87..f4c25b6 100644
--- a/node/index.mdx
+++ b/node/index.mdx
@@ -222,12 +222,19 @@ Peers can be found here -
 
 ```bash
 # Initialize node (default mode is full: RPC/P2P bind to all interfaces)
+# --chain-id is required, e.g. pacific-1 or atlantic-2
 # 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.
+# For known public networks (pacific-1, atlantic-2), seid init also pre-populates
+# bootstrap-peers in config.toml with the built-in Sei Labs seed nodes, so peer
+# discovery works with no manual configuration. Devnets (arctic-1) and
+# unknown/private chains get none, and any bootstrap-peers value you already set
+# is never overwritten.
+
+# Optionally configure additional persistent peers in config.toml.
 PEERS="<comma-separated-peer-list>"
 
 #Set persistent peers in config.toml
diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx
index f8c9c2d..6cc7fe0 100644
--- a/node/technical-reference.mdx
+++ b/node/technical-reference.mdx
@@ -264,6 +264,13 @@ The config.toml file controls the core consensus engine and networking:
 [p2p]
 laddr = "tcp://0.0.0.0:26656"
 external-address = ""
+# bootstrap-peers holds seed/peer addresses (NodeID@host:port, comma-separated)
+# dialled to populate the address book via PEX. As of v6.6.2 (#), `seid init`
+# auto-populates this field with the built-in Sei Labs seed nodes for
+# well-known public networks (pacific-1, atlantic-2). Devnets (arctic-1) and
+# unknown/private chains get none, and an existing bootstrap-peers value is
+# never overwritten. The example below reflects a fresh init on an
+# unrecognised chain.
 bootstrap-peers = ""
 persistent-peers = ""
 upnp = false
@@ -272,6 +279,13 @@ max-outbound-connections = 20
 max-packet-msg-payload-size = 10240
 handshake-timeout = "20s"
 dial-timeout = "3s"
+# How often the node accepts a new inbound connection. The default is "10ms"
+# (a sustained accept rate of ~100 connections/s), raised so the accept loop
+# drains the kernel listen backlog fast enough; an interval too large lets
+# arriving peers wait past handshake-timeout, silently stopping the node from
+# acquiring inbound peers. A value of 0 disables the limiter. Negative values
+# are rejected during config validation.
+accept-interval = "10ms"
 
 # RPC Configuration
 [rpc]
diff --git a/node/validators.mdx b/node/validators.mdx
index 28ffa9b..8482e0f 100644
--- a/node/validators.mdx
+++ b/node/validators.mdx
@@ -27,6 +27,12 @@ seid init <moniker> --chain-id <chain-id> --mode validator
 
 The default init mode is **full**, which binds RPC and P2P to all interfaces (`0.0.0.0`). For validator (and seed) nodes, use `--mode validator` or `--mode seed` so that RPC and P2P listen on localhost only. Genesis is written automatically for known networks; no separate download is required.
 
+<Note>
+`--chain-id` is required — pass a value such as `pacific-1` or `atlantic-2`.
+
+For recognized public networks (`pacific-1`, `atlantic-2`), `seid init` automatically writes the Sei Labs seed nodes into the `bootstrap-peers` field of `config.toml`, so a freshly initialized node bootstraps peer discovery with no additional configuration. Devnets (`arctic-1`) and unknown or private chains receive no seeds, and any pre-existing `bootstrap-peers` value is never overwritten.
+</Note>
+
 ### Key Management
 
 The security of your validator begins with proper key management. Your validator requires several distinct keys: