docs: v6.7.0 catch-up

[seidroid]

Documentation catch-up for v6.7.0.

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

source PR	pages touched	summary
sei-protocol/sei-chain#3566	node/advanced-config-monitoring.mdx	Adds new opt-in config fields to enable estimated read/write metrics for FlatKV state-commit, state-store, and receipt-store Pebble DBs, plus exposes FlatKV config fields in the server config template.
sei-protocol/sei-chain#3525	evm/reference.mdx	Autobahn (GigaRouter) now supports fullnode mode driven by the node's mode config field, adds a new max_inbound_fullnode_peers config field, moves the autobahn-config-file key to top-level in config.toml, and changes the evmrpc field in autobahn.json to be required on every validator.
sei-protocol/sei-chain#3631	evm/reference.mdx	A new config field evm.max_estimate_gas_calls limits the number of calls allowed in an eth_estimateGasAfterCalls request, defaulting to 100.
sei-protocol/sei-chain#3581	node/giga-storage-migration.mdx	Adds a new 'auto' value for the sc-write-mode node config field, enabling runtime write-mode migration transitions without restarts, with important operator warnings about never using it on flatkv_only nodes.
sei-protocol/sei-chain#3621	evm/reference.mdx	Adds a new EVM RPC config field evm.max_subscriptions_logs to cap concurrent logs subscriptions (default 1000), beyond which new logs subscriptions are rejected.
sei-protocol/sei-chain#3620	node/giga-storage-migration.mdx, node/node-operators.mdx	A new 'littidx' backend option is now accepted for the receipt-store configuration, adding a LittDB-based receipt store with a pebble tag index for eth_getLogs filtering.
sei-protocol/sei-chain#3646	evm/reference.mdx	The eth_createAccessList JSON-RPC endpoint now enforces a request rate limiter and can reject requests with a 'server busy' error when the limit is exceeded.
sei-protocol/sei-chain#3602	node/technical-reference.mdx, node/troubleshooting.mdx	Adds a new node config field hash-vault-disabled-unsafe that lets operators disable the HashVault app-hash equivocation guard, and introduces HashVault recovery guidance for startup panics involving hash mismatches.
sei-protocol/sei-chain#3652	node/advanced-config-monitoring.mdx	Adds a new receipt-store config field/flag receipt-store.log-filter-parallelism (default 16) that bounds how many blocks a single eth_getLogs query scans concurrently in the littidx backend.
sei-protocol/sei-chain#3653	evm/reference.mdx, evm/tracing/index.mdx	The debug_traceStateAccess JSON-RPC method now honors the configured TraceTimeout and caps retained per-module state-access payload at 4 MiB (adding a 'truncated' field to the response), changing behavior to prevent OOM and unbounded traces.
sei-protocol/sei-chain#3648	node/advanced-config-monitoring.mdx	Adds two new EVM RPC config fields (max_request_body_bytes and max_concurrent_request_bytes) plus a new Prometheus metric to bound JSON-RPC request body sizes and concurrent request memory via pre-decode admission control.
sei-protocol/sei-chain#3647	node/advanced-config-monitoring.mdx	Adds a per-block hash logger feature to the state-commit store with five new app.toml config fields (sc-hash-logger-*), enabled by default, for recording named block hashes for debugging/forensics.
sei-protocol/sei-chain#3645	node/advanced-config-monitoring.mdx	LittDB's garbage collection was rewritten to run asynchronously with a durable gc-watermark file, adding six new config fields, changing the default GC period, and removing the CacheAwareGet API.
sei-protocol/sei-chain#3671	node/technical-reference.mdx	Introduces an experimental SEI_CONFIG_MANAGER environment variable that selects the config manager for seid; unset/'legacy' uses the existing path, 'v2' is a not-yet-implemented stub that errors, and invalid values fail hard.
sei-protocol/sei-chain#3641	node/technical-reference.mdx	Adds new gRPC server config fields in app.toml (max-recv-msg-size, max-open-connections, keepalive/connection-age settings) with bounded defaults applied even when absent from older config files.
sei-protocol/sei-chain#3665	node/technical-reference.mdx, node/troubleshooting.mdx	The seidb dump-flatkv command gains new flags (--lthash, --lthash-only, --read-limit-mb) for computing/verifying lattice hashes and throttling scan throughput, and --output-dir is no longer required when using --lthash-only.
sei-protocol/sei-chain#3692	node/advanced-config-monitoring.mdx	OTEL/Prometheus metrics now include a chain_id constant label on every emitted metric series, which affects dashboards and alerting queries for node operators.
sei-protocol/sei-chain#3691	node/technical-reference.mdx	Adds a new 'historical_replay' build tag that produces a consensus-unsafe binary variant using a lenient tx decoder (no body-bloat rejection) for replaying historical blocks.
sei-protocol/sei-chain#3677	evm/tracing/index.mdx	Adds a new EVM RPC config field evm.max_trace_struct_log_bytes that caps retained struct-logger output per traced transaction on default debug_trace* endpoints, defaulting to 32 MiB (0 = unlimited).
sei-protocol/sei-chain#3676	node/giga-storage-migration.mdx, node/technical-reference.mdx	Adds a new hashlog command group to the seidb tool with get-block and compare subcommands for inspecting and diffing hash log archives produced by the hashlogger.
sei-protocol/sei-chain#3704	node/giga-storage-migration.mdx	The state-commit sc-write-mode config now accepts the legacy "cosmos_only" value from v6.4/v6.5 app.toml files, mapping it to the current "memiavl_only" routing for backward-compatible upgrades.
sei-protocol/sei-chain#3683	node/advanced-config-monitoring.mdx	LittDB adds new config fields (FlushChannelSize, ShardControlChannelSize, AutoFlushByteThreshold, KeymapManagerMaxBatchBytes, MetricsServeEndpoint) and tightens the maximum value size to 2^32-1 bytes (~4 GiB), rejecting larger values that previously could span the boundary.
sei-protocol/sei-chain#3725	node/node-operators.mdx, node/technical-reference.mdx	The seid node app now reads pruning options from flags and applies them to baseapp, enabling pruning configuration (e.g., --pruning) to actually take effect.
sei-protocol/sei-chain#3722	evm/reference.mdx	Adds two new EVM RPC config fields (max_state_override_accounts, max_state_override_slots) that cap the size of state overrides in eth_call, eth_estimateGas, eth_estimateGasAfterCalls, and debug_traceCall, with correct go-ethereum SetStorage overlay semantics.
sei-protocol/sei-chain#3682	node/advanced-config-monitoring.mdx	Prometheus telemetry is now automatically tagged with a chain_id global label and new metrics subsystems were added; internal metrics APIs were refactored to use global registries (not user-facing).
sei-protocol/sei-chain#3711	node/technical-reference.mdx, node/troubleshooting.mdx	The seidb evm-logical-digest command gains a new 'composite' backend, a new --memiavl-open-mode flag (snapshot/replay), and new --flatkv-dir/--memiavl-dir flags for comparing EVM logical state across backends on a migrating node.
sei-protocol/sei-chain#3718	evm/reference.mdx, evm/tracing/index.mdx, evm/tracing/javascript-tracers.mdx, evm/tracing/troubleshooting.mdx	New app.toml config fields gate which debug tracers callers may use on debug_trace* endpoints, restricting to a native allowlist and disabling request-supplied JavaScript tracers by default.
sei-protocol/sei-chain#3769	node/advanced-config-monitoring.mdx	LittDB adds a per-table Compression config option (S2 algorithm) that compresses values on disk, introduces a v4 segment metadata format, lowers the max value size to 2^32-2 bytes, and restricts secondary keys to full-value aliases on compressed tables.
sei-protocol/sei-chain#3708	node/technical-reference.mdx	Adds a new node config field max-search-scan-budget (default 100,000) that bounds the total KV index entries all in-flight tx_search/block_search requests may visit, returning an error when the process-wide budget is exceeded.
sei-protocol/sei-chain#3707	node/technical-reference.mdx	The autobahn consensus data layer migrates from the old WAL-based persistence to a LittDB-backed BlockDB, adding new config file fields and new CLI flags to the gen-autobahn-config command for tuning BlockDB retention and GC.
sei-protocol/sei-chain#3767	docs.json, evm/precompiles/auth.mdx, evm/precompiles/authz.mdx, evm/precompiles/cosmwasm-precompiles/addr.mdx, evm/precompiles/cosmwasm-precompiles/bank.mdx, evm/precompiles/evidence.mdx +7 more	Adds eight new query precompiles (auth, authz, evidence, feegrant, mint, params, slashing, upgrade) and expands bank, distribution, and gov precompiles with many new read-only query methods, plus a new AssociatePubKey transaction on the addr precompile.
sei-protocol/sei-chain#3811	evm/differences-with-ethereum.mdx	The EVM module now tracks recent block hashes in a KV store ring (last 256 blocks) plus a process-local cache, making the BLOCKHASH opcode return correct historical block hashes for the previous 256 blocks.
sei-protocol/sei-chain#3759	evm/evm-parity/evm-compatibility.mdx, evm/reference.mdx	Adds a new max_log_bytes EVM config field and changes max_log_no_block behavior so eth_getLogs now errors (instead of silently truncating) when a bounded or open-ended query exceeds the matched-log count or estimated heap-byte budget.
sei-protocol/sei-chain#3737	evm/evm-parity/gas-and-fees.mdx	Dynamic-gas precompiles now charge gas for ABI-decoding calldata before decoding it, so calls that supply too little gas are rejected and gas costs for existing precompile calls have increased slightly.
sei-protocol/sei-chain#3819	node/advanced-config-monitoring.mdx, node/node-operators.mdx, node/node-types.mdx	Seed nodes now expose a Prometheus metrics endpoint (and fail startup on bind failure), the metrics server gains read/write/idle timeouts, and the max-open-connections config field's behavior is clarified.
sei-protocol/sei-chain#3813	evm/evm-parity/gas-and-fees.mdx, evm/precompiles/json.mdx, evm/precompiles/p256-precompile.mdx	The json, p256, and pointerview precompiles switched to a dynamic gas model, changing how gas is metered and charged for these on-chain precompile calls (notably p256 now uses a fixed 3450 gas verification cost per RIP-7212).
sei-protocol/sei-chain#3791	evm/transactions.mdx	Cosmos transaction ante handlers now validate provided public keys (including recursive validation of nested multisig keys with depth and signature-count limits) before deriving addresses or persisting them, rejecting malformed pubkeys and deeply nested multisigs.
sei-protocol/sei-chain#3738	evm/precompiles/distribution.mdx	Distribution reward queries (DelegationRewards / DelegationTotalRewards) are now read-only and no longer mutate validator-period state as of v6.7.0, making them idempotent.
sei-protocol/sei-chain#3678	node/technical-reference.mdx	The SEI_CONFIG_MANAGER=v2 environment variable now activates a sei-config-backed manager that performs advisory config validation (logging warnings for invalid fields) while booting identically to legacy; previously v2 was an unimplemented stub that errored.
sei-protocol/sei-chain#3825	evm/precompiles/example-usage.mdx, evm/precompiles/slashing.mdx	The slashing precompile adds a new unjail() transaction method allowing a validator operator to unjail their validator via the EVM precompile at the slashing precompile address.
sei-protocol/sei-chain#3818	evm/evm-parity/websocket.mdx, node/advanced-config-monitoring.mdx	EVM WebSocket plane (:8546) now shares HTTP admission-control config (max_request_body_bytes, max_concurrent_request_bytes) and adds a new ws_admission_timeout config field, with the WS frame size default dropping from 10 MiB to 5 MiB requiring operator action.

⛔ Failed final verification against the release tag

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

• evm/precompiles/example-usage.mdx (Available precompiles table, new 'Feegrant' row) — Feegrant is an available precompile at 0x0000000000000000000000000000000000001010 for querying fee allowances
  • evidence: The Feegrant precompile is NOT registered at the tag. precompiles/setup.go:54-75 (GetCustomPrecompiles) lists auth (100D), authz (100E), evidence (100F), p256 (1011), mint (1012), params (1013), slashing (1014), upgrade (1015) but has no feegrant entry; there is no FeegrantAddress constant or precompiles/feegrant package. precompiles/setup_test.go:14-19 (TestFeegrantPrecompileIsNotRegistered) explicitly asserts that the address 0x...1010 is NOT present in the registered precompiles map. The address 1010 appears only in that negative test, not as a live registration.
• evm/precompiles/feegrant.mdx (Address section / entire page) — The Feegrant precompile exists and is located at the fixed address 0x0000000000000000000000000000000000001010
  • evidence: precompiles/setup.go:50-76 (GetCustomPrecompiles) registers 21 precompiles (bank, wasmd, json, addr, staking, gov, distribution, oracle, ibc, pointer, pointerview, p256, solo, auth, authz, evidence, mint, params, slashing, upgrade) — none at 0x...1010 and no feegrant entry. precompiles/setup_test.go:14-19 is a dedicated test TestFeegrantPrecompileIsNotRegistered asserting that common.HexToAddress("0x0000000000000000000000000000000000001010") is NOT present in GetCustomPrecompiles. No feegrant precompile package exists (grep for 'feegrant' in precompiles/**/*.go returns NO MATCHES).
• evm/precompiles/feegrant.mdx (Interface section) — Solidity interface IFeegrant with constants FEEGRANT_PRECOMPILE_ADDRESS / FEEGRANT_CONTRACT exists
  • evidence: grep for 'IFeegrant' and 'FEEGRANT_PRECOMPILE_ADDRESS' across the checkout both return NO MATCHES; no such Solidity interface or ABI ships at the tag.
• evm/precompiles/feegrant.mdx (Methods section) — Methods allowance(address,address), allowances(address,bytes), and allowancesByGranter(address,bytes) are exposed by the precompile
  • evidence: grep for 'allowancesByGranter' returns NO MATCHES; there is no feegrant precompile executor or ABI defining these methods anywhere in the tree.
• evm/precompiles/feegrant.mdx (Interface / Methods / Notes sections) — Grant and AllowancesResponse structs, JSON-encoded allowance field, pagination via pageKey/nextKey, revert-on-value behaviour
  • evidence: All describe the non-existent feegrant precompile; no corresponding code exists (no feegrant package in precompiles/, no address constant, setup_test.go:14-19 confirms the address is unregistered).
• evm/precompiles/slashing.mdx (Final block at the bottom of the page) — All methods on the Slashing precompile are read-only view queries. Sending value to any of them reverts.
  • evidence: precompiles/slashing/slashing.go:389-396 IsTransaction returns true for UnjailMethod, GrantUnjailMethod, UnjailWithAuthzMethod, RevokeUnjailMethod — these are state-mutating transactions, not views. precompiles/slashing/abi.json shows unjail (line 201) with stateMutability nonpayable (line 209), and other nonpayable entries at lines 23, 82, 228. The page's own unjail section even states it 'is a state-mutating transaction'. Thus the claim that ALL methods are read-only view queries is false.
• evm/reference.mdx — verification could not complete: verifier exceeded 30 tool turns
• node/advanced-config-monitoring.mdx — verification could not complete: verifier exceeded 30 tool turns
• node/giga-storage-migration.mdx (### Operator-facing knobs — the sc-keys-to-migrate-per-block paragraph and its toml sample ([state-commit] / sc-write-mode = "migrate_evm" / sc-keys-to-migrate-per-block = 1024)) — sc-keys-to-migrate-per-block is an app.toml [state-commit] config key that controls the per-block migration drain rate, with a default of 1024 and a constraint that the value must be > 0; shown in a TOML sample as sc-keys-to-migrate-per-block = 1024.
  • evidence: No such config key exists at the tag: grep for sc-keys-to-migrate-per-block, keys-to-migrate, and migrate-per-block all return no matches, and the [state-commit] template in sei-db/config/toml.go (lines 9–95) renders only sc-write-mode and sc-write-mode-enable-auto, not this key. The drain rate is a governance parameter, not an app.toml knob: app/abci.go:64-93 reads migration.NumKeysToMigratePerBlock from chain state (applyMigrationBatchSize), and app/migration/params.go:34-37 sets DefaultNumKeysToMigratePerBlock uint64 = 0 (not 1024), with the comment that this gov param 'is the sole source of the per-block rate' and 'there is no node-local fallback'. An operator copying the sample sets a key that is never read.
• node/technical-reference.mdx — verification could not complete: not verified — run time budget exhausted mid-check
• node/troubleshooting.mdx — verification could not complete: not verified — run time budget exhausted mid-check

Reviewer notes

• feat(precompiles): expose module Query rpcs as precompile methods sei-chain#3767 — Precompile addresses in the diff are mixed-case/short-form; confirm the canonical lowercase addresses when creating pages (auth 0x…100D, authz 0x…100E, evidence 0x…100F, feegrant 0x…1010, mint 0x…1012, params 0x…1013, slashing 0x…1014, upgrade 0x…1015). Note the P256 precompile already occupies 0x…1011, and the new mint/params/slashing/upgrade precompiles start at 0x…1012. These precompiles are versioned at v6.6, so they may not be available on older chain versions — reviewers should confirm the live availability before publishing. All new precompile methods are read-only views that run on a branched/discarded context; the gov tallyResult and auth nextAccountNumber queries have documented side-effect-avoidance behavior worth noting. The governance.mdx page's claim that the ABI is 'write-only' is now factually incorrect and is the highest-priority correction. I did not list a dedicated addr page under evm/precompiles/ (the addr precompile is documented under evm/precompiles/cosmwasm-precompiles/addr.mdx per the supplied page list).
• perf(evm): cache BLOCKHASH via 32-byte hash ring (CON-372) sei-chain#3811 — This is an internal keeper/state change (new 0x20 KV-store prefix, BeginBlock block-hash ring, and process-local cache). The user-visible effect is that the BLOCKHASH opcode now reliably returns hashes for the previous 256 blocks, which aligns Sei closer to Ethereum Yellow Paper behavior. The existing opcode-differences table note ('Usable for recent blocks only') is now more accurate but could be clarified to state the 256-block window. No new page is needed; the KV-store prefix and caching are implementation details not surfaced in docs. Consider whether the EVM compatibility matrix (evm/evm-parity/evm-compatibility.mdx) warrants an opcode row, but it currently has no opcode section, so leaving it out is reasonable.
• feat(evmrpc): bound eth_getLogs peak memory with matched-log count and byte budgets sei-chain#3759 — The new behavior is a potentially breaking change for clients that relied on silent truncation of eth_getLogs results; callers must now handle 'too many logs'/'too many log bytes' errors by narrowing the block range or filter criteria. The benchmark script in node/advanced-config-monitoring.mdx checks for logsCount === 10000 as a limit sentinel — reviewers may want to confirm whether that example should be updated to detect the new error response, but it is illustrative rather than authoritative. No migration step is required; defaults preserve prior count behavior (10000) and add a 64 MiB byte cap.
• precompile: price dynamic-gas calldata decoding by supplied gas sei-chain#3737 — This is an internal gas-metering/DoS-hardening change affecting all dynamic-gas precompiles (bank, wasmd, oracle, ibc, json, distribution, pointer, addr, etc.). The precompile reference pages state gas costs only generically and already direct users to estimate gas, so no per-precompile ABI or value change is strictly required. The gas-and-fees page is the best central place to note the behavior change; the per-precompile pages do not document hard-coded gas numbers that would now be wrong. No migration step is required for users, but anyone forwarding minimal gas to precompiles may see previously-succeeding calls revert. The changed gas-cost test values in the diff are internal to sei-chain and not surfaced in docs.
• feat(seed): serve Prometheus metrics in seed mode sei-chain#3819 — The config.toml sample in node-operators.mdx was truncated before the [instrumentation] section, so the exact wording to correct isn't visible, but the max-open-connections / prometheus-listen-addr behavior change clearly belongs there. The read/write/idle timeout detail (10s/30s/60s) and the gauge-seeding-at-construction change are internal/behavioral and may only warrant a brief mention rather than their own section. No migration step is required. Judgment call: node-types.mdx port 26660 note says the Prometheus port is 'not open' in default config — verify whether instrumentation is enabled by default before rewriting that line.
• precompile: convert json/pointerview/p256 to dynamic-gas precompiles sei-chain#3813 — The pointerview precompile moved from flat RequiredGas (2000) to dynamic state-access-based metering, but no dedicated pointerview precompile doc page exists in the supplied list — pointer lookups are covered in evm/evm-parity/examples/pointer-contracts.mdx, which does not document gas costs, so no targeted edit is needed there. The gas-and-fees page is the best place to capture the pointerview change via its dynamic-precompile list. The p256 page is the most significant gap because it documents a now-incorrect concrete gas figure (48,000) in multiple places.
• Harden account key validation sei-chain#3791 — This change affects Cosmos SDK transaction ante handling, which is deprecated per SIP-3 (see cosmos-sdk/index.mdx). There is no active docs page documenting the Cosmos ante-handler/pubkey validation behavior, so the gap is minor and arguably doesn't warrant new documentation given the deprecation. The TxSigLimit parameter is surfaced in evm/precompiles/auth.mdx (AuthParams.txSigLimit) but that page documents a read-only query, not validation behavior, so no edit is needed there. The SigVerificationDecorator deprecation is an internal code-level note with no corresponding public docs page. Reviewer judgment: this may be a WONTFIX given deprecated Cosmos functionality; the suggested add_section to evm/transactions.mdx is the most relevant touchpoint if documentation is desired.
• fix(distribution): make delegation-reward queries read-only sei-chain#3738 — The change is primarily a behavioral/correctness fix in sei-cosmos; it is most visible to users through the Distribution precompile's rewards() view query, which is documented in evm/precompiles/distribution.mdx. The gRPC/legacy querier endpoints (DelegationRewards/DelegationTotalRewards) are not covered by a dedicated sei-docs page, so no other page needs updating. The old mutating behavior is preserved only for re-tracing pre-v6.7 blocks via debug_trace*, which could optionally be mentioned in evm/tracing/index.mdx, but this is an edge-case replay detail and likely not worth adding there. No migration step is required.
• feat(configmanager): SeiConfigManager v2 body — validate-passthrough (PLT-775 PR2) sei-chain#3678 — Only node/technical-reference.mdx documents SEI_CONFIG_MANAGER and it is now factually wrong for v2. The updated behavior worth noting: v2 validates the on-disk config advisorily (warns at warn level, e.g. missing chain.min_gas_prices), never rewrites files or refuses boot, and a fresh node is only validated from the second boot onward (first boot has no config on disk). Invalid-value handling and exact-match semantics are unchanged. No migration step is required.
• feat(precompiles): expose module Msg rpcs as precompile methods sei-chain#3825 — The core doc update is to evm/precompiles/slashing.mdx. The unjail() method takes no arguments and unjails the validator whose operator address is the caller's associated Sei address; it is non-payable and reverts on delegatecall/staticcall, on an unassociated caller, and on a caller that is not a validator operator. The example-usage.mdx table edit is minor/optional. Note that @sei-js/precompiles may not yet export the updated ABI (docs reference v6.6.1 ABIs), so any TS examples using the new method should be flagged accordingly by the editor.
• evmrpc: extend admission control to the WebSocket plane sei-chain#3818 — Migration flag: operators relying on the old 10 MiB WS frame cap must set [evm].max_request_body_bytes = 10485760 in app.toml before upgrading, which also raises the HTTP body limit to 10 MiB. The removed exported constant DefaultWebsocketMaxMessageSize is an internal Go API detail, not documented in sei-docs, so no doc change is needed for it. The evm/reference.mdx eth_subscribe entry mentions WebSocket transport but does not document frame-size limits, so the websocket.mdx page is the better home for the WS limits; reference.mdx could optionally cross-link but does not require a change.

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

• In evm/evm-parity/evm-compatibility.mdx, the inserted eth_getLogs note links to /node/node-operators/rpc-configuration; evm/evm-parity/gas-and-fees.mdx links to a non-existent rpc-configuration page too — but more concretely, the eth_getLogs note references max_log_bytes/max_log_no_block which matches evm/reference.mdx, so no contradiction there. (Not a reportable category.)
• P256 gas cost contradiction in evm/precompiles/p256-precompile.mdx: the updated "Gas costs" section says the verification cost is a fixed P256VerifyGas = 3450 gas, but the untouched "Performance considerations" section still states "Gas efficiency: 48,000 gas per verification". These describe the same cost two different ways on the same page.
• Identifier inconsistency for the matched-log limit: evm/reference.mdx (untouched "Filter and subscription limits") and evm/evm-parity/evm-compatibility.mdx both use max_log_no_block (default 10000), consistent. But the gas-and-fees SSTORE value stays 72,000 across pages — consistent. (No issue.)
• eth_getLogs byte-limit identifier: the inserted compatibility-matrix note and evm/reference.mdx both name max_log_bytes — consistent. (No issue.)
• Misplaced insertion in evm/precompiles/distribution.mdx: the inserted "Read-only as of v6.7.0" <Info> block sits between the ### rewards heading (and its sentence "Returns the reward information for a delegator across all validators.") and the method's Solidity signature code block, interrupting the heading's own content.

---

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
sei-docs	🟢 Ready	View Preview	Oct 15, 2026, 12:22 PM

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

[cursor]

PR Summary

Low Risk
Documentation-only changes with no runtime impact; incorrect RPC or migration guidance could mislead integrators and operators during v6.7 upgrades.

Overview
Documentation catch-up for Sei v6.7.0, aligning EVM parity guides, RPC reference, precompile pages, and node-operator docs with current chain behavior.

EVM / JSON-RPC: Documents that eth_getProof is unsupported since v6.7.0 (removes the standalone state-proofs page and redirects to the compatibility matrix). eth_getLogs now errors when limits are exceeded (max_log_no_block, max_log_bytes) with no partial results. Pending-state and WebSocket behavior is tightened: no newPendingTransactions / pending filters; pending nonce can include mempool txs; frame/body limits and admission metrics on WS/HTTP (default 5 MiB frame, with an upgrade note for former 10 MiB clients). BLOCKHASH is documented as returning the last 256 blocks. Autobahn validator vs fullnode routing for broadcast and pending nonce is expanded. Legacy sei_* docs drop synthetic receipt lookup; debug_trace* gains tracer allowlist and struct-logger cap notes.

Precompiles: Adds nav and new pages for Auth, Authz, Evidence, Mint, Params, Slashing, and Upgrade (v6.7.0). Updates Governance (query methods), Bank (extra queries), Distribution (read-only rewards()), P256/JSON gas, and example-usage / sei-chain v6.7.1 ABI pointers.

Node ops: FlatKV EVM migration is described as governance-driven with default auto write mode (replacing operator-only sc-keys-to-migrate narrative). Covers littidx receipt backend, seed Prometheus, chain_id on metrics, HashVault, per-block hash logger, seidb (dump-flatkv, hashlog, evm-logical-digest composite), and related app.toml / troubleshooting updates.

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

[seidroid]

This large automated v6.7.0 docs catch-up has several issues that block merging. It adds a Feegrant precompile page and nav entry for a precompile that isn't registered at the tag, and it documents a nonexistent sc-keys-to-migrate-per-block app.toml key. It also has an unmatched </Note> that can break MDX compilation, a pruning TOML sample under the wrong table, and misplaced evm-logical-digest flags. The PR's own "Failed final verification" section lists several of these and says they must be resolved before merging, and verification never finished for four pages.

Findings: 10 blocking | 9 non-blocking | 11 posted inline

Blockers

• The PR body's "Failed final verification against the release tag" section is unresolved. The Feegrant precompile, the slashing "all view" note and sc-keys-to-migrate-per-block contradict the v6.7.0 tag, so this PR must not merge until those items are fixed.
• Claim-by-claim verification never completed for evm/reference.mdx, node/advanced-config-monitoring.mdx, node/technical-reference.mdx and node/troubleshooting.mdx (verifier turn/time budget ran out). Someone needs to check these pages against the release by hand before merge.
• docs.json adds evm/precompiles/feegrant to the navigation. Feegrant isn't registered at v6.7.0 (TestFeegrantPrecompileIsNotRegistered), so remove the nav entry along with the page.
• 7 blocking issue(s) flagged inline on specific lines.

Non-blocking

• The Cursor review pass produced no output (cursor-review.md is empty). REVIEW_GUIDELINES.md is also empty, so this review applied the AGENTS.md conventions instead.
• Generated prose leaks internal source-PR references such as (#3618), (#3818) and (#) into reader-facing copy: evm/reference.mdx:1173, node/advanced-config-monitoring.mdx:586, node/node-operators.mdx:818, evm/precompiles/distribution.mdx:265. Several of these also cite the wrong PR (#3618 is used for the pruning change, which came from #3725). Strip them.
• The new precompile pages (auth, authz, evidence, mint, params, slashing, upgrade) are versioned at v6.6/v6.7. Add an availability or version note, and check that @sei-js/precompiles exports the matching ABIs before any TS examples reference them.
• The eth_getLogs change from truncating to erroring may break clients. The benchmark in node/advanced-config-monitoring.mdx that checks logsCount === 10000 should probably check for the new error instead.
• The WebSocket frame-size default drops from 10 MiB to 5 MiB, which requires operator action. Make sure websocket.mdx presents this as an upgrade <Warning>, not plain prose.
• 4 suggestion(s)/nit(s) flagged inline on specific lines.

Inline comments (could not post inline; listed here)

• node/node-operators.mdx:831 (RIGHT) -- [blocker] This </Note> has no matching opener because the previous <Note> already closes at line 812. Unbalanced JSX will fail MDX compilation. Either remove this tag or wrap the new "Cosmos SDK state pruning" section in its own <Note>. Also drop the (#3618) reference at line 818; it's an internal PR link and points at the wrong PR (the pruning change is #3725).
• evm/precompiles/feegrant.mdx:13 (RIGHT) -- [blocker] No Feegrant precompile ships at v6.7.0. precompiles/setup.go has no feegrant entry, and setup_test.go explicitly asserts that 0x…1010 is NOT registered. IFeegrant, allowance, allowances and allowancesByGranter don't exist either. Delete this page, remove it from docs.json nav, and don't publish it until the precompile actually ships (AGENTS.md: no speculation about unreleased features).
• evm/precompiles/example-usage.mdx:28 (RIGHT) -- [blocker] Remove the Feegrant row. Nothing is registered at 0x…1010 in v6.7.0.
• node/giga-storage-migration.mdx:322 (RIGHT) -- [blocker] sc-keys-to-migrate-per-block isn't an app.toml key at the tag. The [state-commit] template renders only sc-write-mode and sc-write-mode-enable-auto. The drain rate comes from the governance param NumKeysToMigratePerBlock, which defaults to 0 and has no node-local fallback. Operators who copy the sample at line 332 would set a key that is never read. Rewrite this section to describe the governance param, or remove it.
• evm/precompiles/slashing.mdx:177 (RIGHT) -- [blocker] This contradicts the unjail() section on the same page. unjail (plus grantUnjail, unjailWithAuthz and revokeUnjail per slashing.go IsTransaction) is nonpayable and changes state. The ISlashing interface (lines 26-60) also leaves out unjail(), so anyone calling through that interface can't invoke it. Add it to the interface, and update this note and the intro on line 6, which says "read-only queries".
• node/technical-reference.mdx:505 (RIGHT) -- [blocker] These pruning keys come after [state-store], so TOML parses them as state-store.pruning, etc., not top-level settings. Move pruning, pruning-keep-recent and pruning-interval above the first table header, for example next to minimum-gas-prices.
• node/technical-reference.mdx:289 (RIGHT) -- [blocker] This block lists the evm-logical-digest flags (--backend, --db-dir, --flatkv-dir, --memiavl-open-mode, …), but it sits in the new hashlog compare section. It also repeats the "The command accepts these flags:" lead-in from line 279, so readers will take these as hashlog flags. Move lines 289-305 back under the evm-logical-digest section (around line 180-200).
• evm/precompiles/p256-precompile.mdx:167 (RIGHT) -- [suggestion] This line now says 3,450 gas, but "Performance considerations" (line 441) still says 48,000 gas per verification. Update line 441 to match.
• evm/evm-parity/evm-compatibility.mdx:55 (RIGHT) -- [suggestion] /node/node-operators/rpc-configuration has no page and no redirect in docs.json, so this link is broken. Point it at an existing page or anchor, such as the filter/subscription limits section in evm/reference.mdx. Run mint broken-links to confirm.
• evm/precompiles/distribution.mdx:265 (RIGHT) -- [suggestion] Two problems here. The (#) placeholder leaked into copy. The <Info> also sits between the ### rewards heading/description and the method signature, which interrupts the method docs. Remove (#) and move the callout below the signature block.
• evm/differences-with-ethereum.mdx:104 (RIGHT) -- [nit] "Before this change" is changelog wording that won't make sense to readers later; say "Before v6.7.0" instead. The BeginBlock/ring/cache/staking-fallback details are implementation internals; consider trimming to the user-visible behavior (a 256-block window, zero outside it). Also remove the stray JSX comment at line 106.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.

There are 3 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit a41747d. Configure here.}

[seidroid]

This automated v6.7.0 catch-up adds a lot of useful material, but it can't merge as is. It documents a Feegrant precompile that the PR's own release-tag check says doesn't exist, it adds an MDX tag with no matching opening tag, and several insertions break page structure (tables, flag lists) or contradict text elsewhere on the same page.

Findings: 9 blocking | 21 non-blocking | 19 posted inline

Blockers

• The PR description's own 'Failed final verification against the release tag' section lists contradictions that are still unresolved: the Feegrant precompile (0x...1010) is not registered at v6.7.0 (TestFeegrantPrecompileIsNotRegistered), and the Slashing page's 'all methods are view' note is false. The description says these must be resolved before merging.
• Verification never finished for evm/reference.mdx, node/advanced-config-monitoring.mdx, node/technical-reference.mdx, and node/troubleshooting.mdx (it ran out of turns or time). A human needs to check the new config keys, defaults, and error strings against v6.7.0 before publishing.
• evm/precompiles/governance.mdx: the intro (around line 9, outside the diff) still says the ABI is write-only and sends readers elsewhere for queries. That now contradicts the new 'Query functions' section. The source-PR notes call this the highest-priority correction.
• 6 blocking issue(s) flagged inline on specific lines.

Non-blocking

• evm/precompiles/p256-precompile.mdx: the 'Performance considerations' section (outside the diff, around line 441) still says 48,000 gas per verification. The updated 'Gas costs' section now says 3,450.
• node/giga-storage-migration.mdx: the existing sc-keys-to-migrate-per-block app.toml knob (unchanged context) was flagged by the release-tag check as nonexistent. The per-block rate is a governance param that defaults to 0. Consider fixing it in this catch-up.
• The hashlog and HashVault content is duplicated almost word for word across node/giga-storage-migration.mdx, node/technical-reference.mdx, and node/troubleshooting.mdx. Keep one canonical section and link to it from the others to avoid drift.
• evm/transactions.mdx gains a Cosmos ante-handler pubkey section. Cosmos-SDK content is deprecated (SIP-3) and new content should target EVM, so consider dropping it or adding a deprecation note.
• Several insertions leave stray runs of blank lines (two to four) before and after the added sections. Tidy them up.
• Run mint broken-links and node scripts/check-redirects.mjs. At least one new link (/node/node-operators/rpc-configuration) appears to have no destination.
• REVIEW_GUIDELINES.md was empty, so no repo-specific guidelines were applied beyond AGENTS.md.
• The Cursor second-opinion review (cursor-review.md) was empty, so that pass produced no output. Codex's findings are included above.
• 13 suggestion(s)/nit(s) flagged inline on specific lines.

Inline comments (could not post inline; listed here)

• evm/precompiles/feegrant.mdx:13 (RIGHT) -- [blocker] Per the PR's own release-tag verification, nothing is registered at 0x...1010 in v6.7.0. GetCustomPrecompiles has no feegrant entry, and setup_test.go asserts the address is NOT registered. There is also no IFeegrant ABI and no allowancesByGranter method. Remove this page, or hold it until the precompile actually ships.
• docs.json:205 (RIGHT) -- [blocker] Remove the evm/precompiles/feegrant nav entry along with the page. That precompile isn't registered at v6.7.0.
• evm/precompiles/example-usage.mdx:28 (RIGHT) -- [blocker] The Feegrant row lists a precompile that isn't registered at v6.7.0. Remove it.
• node/node-operators.mdx:1002 (RIGHT) -- [blocker] This closing </Note> has no opening tag. The preceding Note already closes at line 983, so this breaks MDX compilation for the page. Remove it.
• evm/precompiles/slashing.mdx:177 (RIGHT) -- [blocker] This is false. unjail() (documented above) is a nonpayable, state-mutating transaction. Per the release-tag check, grantUnjail, unjailWithAuthz, and revokeUnjail are transactions too. Reword the note, and update the intro on line 6, which also calls the page read-only.
• evm/precompiles/slashing.mdx:26 (RIGHT) -- [suggestion] The ISlashing interface leaves out unjail(), so callers can't use the documented method through this interface. Add function unjail() external returns (bool success);. Also consider documenting the other transaction methods that ship in the ABI (grantUnjail, unjailWithAuthz, revokeUnjail).
• node/technical-reference.mdx:291 (RIGHT) -- [blocker] The dump-flatkv and hashlog sections were inserted between the evm-logical-digest intro and its flag list. The original 'The command accepts these flags:' at line 229 now introduces the dump-flatkv flags. This duplicated heading, under 'Inspecting hash log archives', now presents the evm-logical-digest flags (--backend composite, --memiavl-open-mode, and so on) as if they were hashlog flags. Move the evm-logical-digest flag list back under its own section, and put the new sections after it.
• evm/tracing/index.mdx:60 (RIGHT) -- [suggestion] This <Note> (and the blank line before it) splits the methods table. The debug_traceTransactionProfile row after it will render as plain pipe-delimited text. Move the note below the table.
• node/advanced-config-monitoring.mdx:763 (RIGHT) -- [suggestion] These litt_compression_* rows come after a blank line, so they're cut off from the LittDB metrics table and have no header row. They'll render as plain text. Remove the blank line on line 762 so they join the table above.
• evm/evm-parity/evm-compatibility.mdx:55 (RIGHT) -- [suggestion] /node/node-operators/rpc-configuration has no page and no redirect in docs.json, so this link is broken. Link to the log-filter limits in /evm/reference or to an existing node-config page instead.
• evm/evm-parity/evm-compatibility.mdx:55 (RIGHT) -- [nit] This cell holds four sentences. Consider trimming it to a short summary that links to the limits section in evm/reference.mdx, which already explains the details.
• evm/precompiles/p256-precompile.mdx:166 (RIGHT) -- [suggestion] This now says 3,450 gas, but 'Performance considerations' further down the page still says '48,000 gas per verification'. Update that section too. Also check that 'Up to 60x more efficient' still holds at the new price.
• node/node-operators.mdx:989 (RIGHT) -- [nit] Stray (#3618) PR reference in reader-facing copy. It's also the wrong number: the pruning change is sei-chain#3725. Remove it.
• evm/reference.mdx:1173 (RIGHT) -- [nit] Stray (#3618) PR reference. The tracer-gating change is #3718. Remove it from reader-facing copy.
• node/advanced-config-monitoring.mdx:586 (RIGHT) -- [nit] Remove the internal (#3818) PR reference from the metric description.
• evm/precompiles/distribution.mdx:265 (RIGHT) -- [nit] Leftover (#) placeholder in the callout title. Also, this Info block sits between the rewards description and its Solidity signature. Move it below the signature block.
• evm/tracing/troubleshooting.mdx:147 (RIGHT) -- [suggestion] This tracer-allowlist subsection is inserted directly under '### 4. Network and connection issues'. That separates the heading from its existing connection refused content and files the tracer error under networking. Move it to its own numbered section.
• node/technical-reference.mdx:215 (RIGHT) -- [nit] These examples use -d /.sei/data/... (a path at the filesystem root). Other examples use $HOME/.sei/data/...; use that here too.
• evm/transactions.mdx:295 (RIGHT) -- [nit] This section covers Cosmos transaction ante handling, which is deprecated under SIP-3. Per AGENTS.md, new content should target EVM. Consider dropping it or adding an explicit deprecation note.

[seidroid]

This large v6.7.0 catch-up looks well structured, and it fixes the items that failed verification at the release tag. The Feegrant page/row is gone, the false read-only note on the slashing page is gone, sc-keys-to-migrate-per-block is removed, the P256 48,000-gas figure is replaced, the distribution <Info> now sits after the signature, and the state-proofs redirect anchor exists. Before merge, a human should confirm several behavior claims that no source PR backs, plus four pages that the bot could not finish checking.

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

Blockers

• None at the file/PR level.

Non-blocking

• The bot could not finish checking four pages against the v6.7.0 tag: evm/reference.mdx, node/advanced-config-monitoring.mdx, node/technical-reference.mdx and node/troubleshooting.mdx. It ran out of tool turns or time budget. These pages make up most of the operator-facing changes, so a maintainer should spot-check them against the tag before merging.
• Several significant changes have no source PR in the description table: (1) eth_getProof becomes 'Not supported' and evm/evm-parity/state-proofs.mdx is deleted; (2) sei_getTransactionReceipt is removed from the legacy sei_* allowlist; (3) the SC migration becomes governance-driven, with the default auto mode, the NumKeysToMigratePerBlock gov param and sc-write-mode-enable-auto; (4) enable-pebble-metrics is no longer applied. Link each one to the sei-chain PR it comes from, or confirm it at the tag. Deleting a whole page on an unverified claim is risky.
• The PR description still has a '⛔ Failed final verification … must be resolved before merging' section. The diff appears to resolve those items, so update the description to keep reviewers from assuming the PR is blocked.
• The state-proofs page removal is handled correctly: it is dropped from the nav, a redirect points to /evm/evm-parity/evm-compatibility#proof-verification (that heading exists), and learn/sei-giga-developers.mdx is relinked. Run node scripts/check-redirects.mjs and mint broken-links to confirm.
• Codex reported no material issues and said the redirect validation check passed. The Cursor review file (cursor-review.md) was empty, so that pass produced no output.
• REVIEW_GUIDELINES.md was empty. I applied the AGENTS.md conventions instead.
• 3 suggestion(s)/nit(s) flagged inline on specific lines.

Inline comments (could not post inline; listed here)

• node/giga-storage-migration.mdx:250 (RIGHT) -- [suggestion] This is a v6.7.0 catch-up, but this sentence describes v6.7.1 behavior: refusing to start on a pinned mode that disagrees with the on-disk state. If v6.7.1 hasn't shipped, this is a claim about an unreleased version, which AGENTS.md doesn't allow. If it has shipped, confirm the behavior against that tag. Otherwise, drop the sentence or reword it for v6.7.0.
• node/node-operators.mdx:1694 (RIGHT) -- [nit] The comment just above says the node runs in auto by default and ignores sc-write-mode. The sample still sets sc-write-mode = "memiavl_only" with no sc-write-mode-enable-auto line, so readers may think it does something. Consider commenting this line out, or showing it with sc-write-mode-enable-auto = false next to it.
• evm/precompiles/auth.mdx:17 (RIGHT) -- [nit] The address literals use inconsistent hex casing across the new pages: 100D here, and lowercase 100e/100f in Authz/Evidence. Solidity rejects mixed-case address literals that fail the EIP-55 checksum. Confirm each *_PRECOMPILE_ADDRESS literal compiles as written, ideally by copying the checksummed form from sei-chain's interface files.

[seidroid]

This is a large, well-structured v6.7.0 catch-up, and the failures listed in the PR description look fixed in the final diff: the Feegrant page is gone, the slashing note and the sc-keys-to-migrate-per-block sample are corrected, the P256 page now says 3,450 gas, and the distribution <Info> has moved. Nothing blocks the merge, but a few claims need source confirmation and four heavily edited pages never finished the bot's claim-by-claim verification.

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

Blockers

• None at the file/PR level.

Non-blocking

• The 'Failed final verification' section in the PR description is stale. Its items appear fixed in the diff: no Feegrant page, docs.json entry, or table row remains; the slashing 'all view' note is gone; the sc-keys-to-migrate-per-block sample is replaced; and the P256 48,000-gas text is updated. Update the description so a reviewer doesn't block on resolved items.
• Four pages never finished the bot's tag verification: evm/reference.mdx, node/advanced-config-monitoring.mdx, node/technical-reference.mdx, and node/troubleshooting.mdx. These hold most of the new config keys, defaults, and error strings (for example max_log_bytes, ws_admission_timeout, the sc-hash-logger-* keys, the [grpc] defaults, max-search-scan-budget, and the dump-flatkv flags). A human should spot-check them against the v6.7.0 tag before merging.
• Several user-facing behavior changes don't map to any source PR in the description's table. These include: eth_getProof now always returns -32000, which deletes the state-proofs page; removal of sei_getTransactionReceipt; eth_newPendingTransactionFilter and newPendingTransactions now always fail; and new eth_getTransactionCount("pending") mempool semantics. Confirm which sei-chain PRs and release these come from (for example #3927), because they reverse what the docs said before.
• The new precompile pages say 'available since v6.7.0', but the bot's own note on #3767 says these precompiles are 'versioned at v6.6'. Confirm the correct version and whether they are live on Sei Mainnet before publishing.
• Several links and claims point to v6.7.1 in a v6.7.0 catch-up: the ABI links in distribution, governance, staking, and p256, the precompiles tree link, and the 'Since v6.7.1, a node also refuses to start…' sentence in giga-storage-migration. Confirm the v6.7.1 tag exists and that mixing versions is intended.
• example-usage.mdx says v6.7 added methods to Staking. However, staking.mdx only gets an updated ABI link and doesn't document any new query methods, unlike Bank, Governance, and Distribution.
• llms.txt and llms-full.txt still link to the deleted /evm/evm-parity/state-proofs. The redirect covers this, and the weekly regenerate workflow should refresh the files, but consider triggering it manually after merge.
• Second opinions: Codex reported 'No material issues found'. The Cursor review file was empty, so that pass produced no output. REVIEW_GUIDELINES.md was also empty, so this review used no repo-specific guidelines beyond AGENTS.md.
• 2 suggestion(s)/nit(s) flagged inline on specific lines.

Comments that couldn't be anchored to the diff

• evm/evm-parity/evm-compatibility.mdx:208 -- [suggestion] This turns eth_getProof from 'Supported with differences' into 'Not supported', and the PR deletes the state-proofs page. None of the source PRs in the description cover this change. Please link the sei-chain change that made eth_getProof return -32000 at v6.7.0, so reviewers can confirm the exact error message and release.

Inline comments (could not post inline; listed here)

• evm/precompiles/authz.mdx:17 (RIGHT) -- [suggestion] The address literal casing is inconsistent across the new pages. auth.mdx uses ...100D, while authz.mdx (...100e) and evidence.mdx (...100f) use lowercase. The page headers use uppercase. Solidity rejects 40-hex-digit literals that fail the EIP-55 checksum, so a non-checksummed literal makes the copy-paste interface fail to compile. Check each constant against its EIP-55 checksum, or copy the literal from the sei-chain .sol interface. Use the canonical casing everywhere.
• node/node-operators.mdx:1702 (RIGHT) -- [nit] The comment says the node runs in auto and ignores this value, yet the sample still sets sc-write-mode = "memiavl_only". Readers may think they are pinning memiavl_only, which the giga-storage-migration page warns makes the node diverge once governance starts the migration. Consider showing the value that seid init now generates, or adding an explicit note that this line has no effect unless sc-write-mode-enable-auto = false.