docs: v6.6.2 catch-up

[seidroid]

Documentation catch-up for v6.6.2.

2 source PR(s) produced changes across 2 commit(s). Each source PR is a separate commit, so this reviews commit-by-commit.

source PR	pages touched	summary
sei-protocol/sei-chain#3939	node/technical-reference.mdx	Adds a new p2p config field accept-interval that paces inbound connection acceptance and changes the default accept rate from 1/s to 100/s to prevent nodes silently failing to acquire inbound peers.
sei-protocol/sei-chain#3954	node/index.mdx, node/technical-reference.mdx, node/validators.mdx	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.

Reviewer notes

• Backport release/v6.6: fix(p2p): make the inbound accept rate configurable and raise its default sei-chain#3939 — The auto-generated config.toml block in node-operators.mdx is marked AUTO-GENERATED and may be regenerated from the release template, so the edit there may only need to happen once the tagged release includes the new field; flag for a human to confirm whether it is hand-maintained or regenerated. dial-interval is intentionally kept out of the generated template (expert-only) but its default rate behavior also changed context — no doc currently mentions dial-interval, so no update is strictly required for it. The behavioral change (accept rate 1/s -> 100/s and negative-value rejection) is validation/pacing internals not currently surfaced in any doc, so documenting it in the technical-reference [p2p] section is the best fit.
• Backport release/v6.6: feat(seeds): ship Sei Labs seeds as the default bootstrap-peers sei-chain#3954 — The --chain-id required behavior was already enforced at runtime (init panics if unset) before this PR; the change is only to the help text and default seeds. No migration step is required — pre-existing bootstrap-peers values are preserved, and arctic-1/private chains are unaffected. The node/index.mdx RandomPeers snippets and persistent-peers guidance still work but are now somewhat redundant with the auto-populated bootstrap-peers; a human may want to reconcile the two. The Sei Labs seed node addresses themselves (app/seeds package) are internal and likely don't need to be listed verbatim in docs, though the technical-reference already references seed peers via the version table.

⚠️ Possible contradictions or misplaced sections

Flagged by a review of every touched page's final text. Each source PR was analysed in isolation, so these were invisible to the per-PR checks. Verify before merging — the checker cannot tell which side of a contradiction is correct.

Checking the pages for the four issue types.

• accept-interval default contradiction (technical-reference.mdx): the inserted comment says the default is "10ms" "raised so the accept loop drains the kernel listen backlog fast enough" — but a raise implies a different old default, and the same comment simultaneously states "The default is '10ms'" while the phrasing "raised" describes it as changed. This is internally muddled but the concrete value 10ms matches the setting line, so not a hard contradiction — excluding.

• Go version contradiction (index.mdx): Text says "Current seid releases require Go 1.25.6 or later" and points to the go.mod at tag v6.6.1, while GO_TARBALL=go1.25.6. Consistent — no issue.

• min_signed_per_window naming (technical-reference.mdx): slashing param labeled min_signed_per_window; oracle note references min_valid_per_window explicitly distinguishing them. Consistent.

NONE

---

Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
sei-docs	🟢 Ready	View Preview	Aug 20, 2026, 12:10 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.