[seidroid]

Status — human verification: checked against the sei-chain v6.6.3 tag. The failed-verification item below (freeze-height under a [base] section) is fixed in 91b572d: it is a top-level app.toml key. The other fixes are listed in this comment; 5070310 addresses the seidroid review.

Skill catch-up for v6.6.3.

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

source PR	files touched	summary
sei-protocol/sei-chain#3978	skill/references/cli/seid-cli.md, skill/references/ecosystem/node-operations.md	Adds a new '--freeze-height' CLI flag and 'freeze-height' app.toml config field that stops a node before executing a target block while continuing to serve RPC, with validation constraints against halt-height/halt-time, grpc-only, state sync, seed mode, and Autobahn.
sei-protocol/sei-chain#4024	skill/references/cli/frozen-rpc-router.md, skill/references/cli/seid-cli.md	Adds a new frozen-rpc-router binary that proxies EVM JSON-RPC requests to live and freeze-height-frozen nodes based on block number, plus a new --freeze-height flag on seid start.
sei-protocol/sei-chain#4034	skill/references/cli/frozen-rpc-router.md	The frozen-rpc-router command adds a new --max-block-reference-depth CLI flag (default 16) to bound nested block reference parsing depth.
sei-protocol/sei-chain#4048	skill/references/cli/frozen-rpc-router.md	The frozen-rpc-router adds two new CLI flags, --batch-request-limit and --write-timeout, to configure JSON-RPC batch size limits and HTTP response write timeouts.

⛔ Failed final verification against the release tag

Each touched page was re-checked claim-by-claim against the v6.6.3 checkout after all commits were assembled. The items below contradict what actually ships at the tag and must be resolved before merging.

• skill/references/cli/seid-cli.md (Node Start (seid start) → --freeze-height, bullet: "Also settable via the freeze-height field in the [base] section of app.toml") — The freeze height is also settable via the freeze-height field in the [base] section of app.toml.
  • evidence: sei-cosmos/server/config/toml.go:44-47 renders freeze-height = {{ .BaseConfig.FreezeHeight }} inside the ManualConfigTemplate under the "Base Configuration" comment banner (toml.go:17-19), which is at the TOP LEVEL of app.toml with no [base] TOML section header. The first section header in the template is [state-sync] (toml.go:77); grep for [base] in toml.go returns no matches. There is no [base] section in app.toml, so the key does not live under a [base] section.

Reviewer notes

• Backport release/v6.6: Add freeze mode for historical EVM RPC sei-chain#3978 — The primary home for this change is node-operations.md, which already documents app.toml BaseConfig fields (halt-height is a natural sibling) and node startup/systemd usage. The seid-cli.md addition is a secondary/optional judgment call — that file focuses on wallet/query/tx subcommands and does not currently document 'seid start' flags at all, so a reviewer may prefer to keep the flag documentation solely in node-operations.md. No existing skill mentions halt-height, so this is net-new content in both cases.
• Backport release/v6.6: Add frozen RPC router and Docker integration cluster (#3989) sei-chain#4024 — The --freeze-height flag is already well-documented in both cli/seid-cli.md and ecosystem/node-operations.md, and the existing exclusive-boundary description ('settles at freeze-height - 1') matches the PR — so the freeze-height flag itself is largely covered and may only need a cross-reference to the new router. The genuinely new, undocumented artifact is the frozen-rpc-router binary and its CLI flags, which no skill file mentions; a new reference file is the primary gap. Proposed path cli/frozen-rpc-router.md fits the existing cli/ category; alternatively it could live under ecosystem/ since it's an operational proxy tool — judgment call left to the reviewer.
• Backport release/v6.6: Bound block reference parsing depth sei-chain#4034 — The change is a single new CLI flag on frozen-rpc-router, fully covered by the existing frozen-rpc-router.md skill. The flag bounds nested block-reference depth (e.g. EIP-1898 {"blockNumber": ...} objects); the router now returns an empty/unknown reference (routing to live) when depth exceeds the limit. A brief note on this routing behavior for over-deep references could also be added to the Routing behaviour section, but the primary gap is the missing flag entry. The seid-cli.md frozen-rpc-router mentions are only cross-references and need no change.
• Backport release/v6.6: Bound frozen RPC router batch allocations sei-chain#4048 — The frozen-rpc-router skill file is the only place documenting this command. The Flags table needs the two new rows, and the 'Other error codes' section should note that batches exceeding --batch-request-limit are rejected with code -32600 and message 'batch too large'. No other skill files reference these flags.

⚠️ 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.

Analyzing the pages for the specified issues.

• Contradiction on --freeze-height app.toml section (seid-cli.md): The new text says freeze-height is settable via the [base] section of app.toml, while node-operations.md (and the router page) treat it consistently—but within seid-cli.md itself it's stated as [base], whereas node-operations.md says BaseConfig section "alongside halt-height / halt-time". These are two different section names ([base] vs BaseConfig) for the same field across the update, but not on the same page — noting only same-page issues: no direct same-page contradiction here.
• sei_traceBlockByNumberExcludeTraceFail removal vs sei2_*ExcludeTraceFail remaining (node-operations.md): The "Removed (as of Sei v6.6.0)" bullet says the two sei_* block-trace endpoints are removed and can no longer be enabled, but then states the sei2_*ExcludeTraceFail block variants "all remain." Meanwhile the sei2_* namespace section lists "the *ExcludeTraceFail variants" as gated/enable-able methods. This is consistent (sei_ removed, sei2_ remain), so not a contradiction.

NONE

---

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

[github-actions]

We truly appreciate your contribution and the time you’ve invested in this PR.
Before we can merge it, we’d love your help addressing the remaining feedback or sharing your perspective.
If we don’t hear back within 2 day(s), this PR will close automatically — but don’t worry, you can reopen it anytime when you’re ready to continue.

[alexander-sei]

Checked this against the sei-chain v6.6.3 tag and pushed the fixes in 91b572d.

Verified as written: all seven frozen-rpc-router flags and their defaults, its error codes and Sei-RPC-Route values, make build-frozen-rpc-router, and the seid start freeze checks (halt-height/halt-time, grpc-only, state-sync fallback, Autobahn, the height checks). The router code is unchanged through v6.7.3.

Fixed:

• The [base] claim the bot flagged: freeze-height is a top-level app.toml key next to halt-height/halt-time; there is no [base] section (sei-cosmos/server/config/toml.go). node-operations.md's "BaseConfig section" wording is fixed the same way.
• Freeze mode is full-node only. Validator mode is rejected too, not just seed mode (sei-tendermint/node/public.go).
• A frozen node is read-only from startup: broadcasts, including eth_sendRawTransaction, fail with RPC writes are disabled in freeze mode. Both pages now say so.
• frozen-rpc-router.md: rejoined the flags table (blank lines had split off the last three rows), cited sei-chain#4024 instead of "#frozen-rpc-router", and documented the batch too large error and the block-reference depth fallback.
• Linked cli/frozen-rpc-router.md from SKILL.md and SKILL-ECOSYSTEM.md. Without that, flattened installs drop the page (REVIEW.md §2).

Merges cleanly with main, and with #19 in either order.

[cursor]

PR Summary

Low Risk
Documentation-only skill updates with no runtime or application code changes.

Overview
Documents v6.6.3 operator features for freeze-height nodes and historical EVM RPC.

Adds a new cli/frozen-rpc-router.md reference (usage, flags, block-based routing, Sei-RPC-Route header, error codes) and wires it into SKILL.md and SKILL-ECOSYSTEM.md.

Extends seid-cli.md and node-operations.md with --freeze-height / top-level app.toml freeze-height: exclusive boundary semantics, read-only RPC behavior, and startup validation constraints, with cross-links between node ops, CLI, and the router.

^{Reviewed by Cursor Bugbot for commit 550c967. Bugbot is set up for automated code reviews on this repo. Configure here.}

[seidroid]

This docs-only catch-up for v6.6.3 adds --freeze-height to the seid CLI and node-operations references, plus a new frozen-rpc-router page. The "[base] section" error that the PR description flags as a failed verification is already fixed in the diff: every page now calls freeze-height a top-level app.toml key. Only one small doc inconsistency is left.

Findings: 0 blocking | 2 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• [suggestion] The PR description still has a '⛔ Failed final verification' section saying freeze-height is documented under a [base] section. The current diff already says it is a top-level key on all pages. Update or remove that section so reviewers aren't told to fix a problem that no longer exists.
• 1 suggestion(s)/nit(s) flagged inline on specific lines.

Inline comments (could not post inline; listed here)

• skill/references/cli/frozen-rpc-router.md:61 (RIGHT) -- [suggestion] This sentence contradicts the list below it. It says the header is set on "responses served by a single backend", but the mixed value is for a batch split across several backends. Reword it to something like "Responses carry a Sei-RPC-Route header describing which backend(s) served the request". Also check against the router source that mixed is really emitted, so the doc doesn't mislead people integrating against the header.

[alexander-sei]

@seidroid review

[seidroid]

This docs-only v6.6.3 catch-up is consistent across pages: freeze-height is called a top-level app.toml key everywhere, and the new frozen-rpc-router.md is linked from both SKILL.md and SKILL-ECOSYSTEM.md, so flattened installs will include it. The earlier Sei-RPC-Route header wording issue is fixed: the page now says the header describes "which backend(s)" served the response, which agrees with the mixed value.

Findings: 0 blocking | 0 non-blocking | 0 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• None at the file/PR level.

[alexander-sei]

Verified against the sei-chain v6.6.3 tag (details in the comment above). seidroid's suggestions are addressed and its re-review on 550c967 found nothing; Bugbot is clean.