Repository navigation
docs: v6.8.0 catch-up - #108
Draft
seidroid[bot] wants to merge 93 commits into
Draft
seidroid[bot] wants to merge 93 commits into
seidroid[bot] wants to merge 93 commits into
Conversation
…and mempool config sections (while excluding deprecated/unused settings), exposing new generated config file fields to operators. (sei-protocol/sei-chain#3993)
… five additional sections (statesync, tx-index, instrumentation, priv-validator, self-remediation), exposing their config fields to operators. (sei-protocol/sei-chain#3994)
…end-qualified paths (data/state_store/{cosmos,evm}/{backend}), a new `evm-ss-separate-dbs` config field is documented, and a data-directory snapshot restore path for enabling Giga SS Store is added. (sei-protocol/sei-chain#4027)
…for linux/arm64 in addition to linux/amd64, so pre-built arm64 release artifacts are now available. (sei-protocol/sei-chain#4004)
…nds as a hex quantity) is added to EVM RPC block headers returned by eth_getBlockByNumber/Hash and eth_subscribe newHeads, since the standard seconds-based `timestamp` repeats across Sei's sub-second blocks. (sei-protocol/sei-chain#4018)
…te-commit]` config fields (sc-subspace-max-pairs, sc-subspace-max-bytes, sc-subspace-query-max-inflight), empty-prefix rejection, and concurrency limits — requiring migration action for indexers issuing wide prefix scans. (sei-protocol/sei-chain#4009)
…rops from 7200 to 0, disabling the Prometheus metrics sink by default on newly generated node configs. (sei-protocol/sei-chain#4032)
…s disable the receipt store (defaults to true); when off the EVM RPC listeners refuse to start and receipt-dependent eth_* methods now return ErrNotConfigured, plus the legacy receipt migration and the `enable-read-write-metrics` app.toml key were removed. (sei-protocol/sei-chain#4062)
…er_hashes), enables eth_newBlockFilter under Autobahn, and changes broadcast_tx_commit to fail-fast when Autobahn is active. (sei-protocol/sei-chain#4012)
…nd now returns an error, removing a previously available on-chain feature for batching CosmWasm contract executions from the EVM. (sei-protocol/sei-chain#4066)
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
…without repairing a torn changelog tail, so on a live node it refuses mid-write records and asks for a rerun instead of truncating committed data. (sei-protocol/sei-chain#3983)
…'s sei.toml against the current binary without starting the node, exiting non-zero if any value would be refused at boot. (sei-protocol/sei-chain#4045)
… opening a store directory with a mismatched backend, and introduces offline littdb iterator/prune/range utilities for the littidx receipt store; also changes the package path for the rollback utility. (sei-protocol/sei-chain#4080)
…ctual committee that certified a given global block height (resolving omitted height to the app tip and handling pruned/exceeded heights), replacing the previous behavior that always returned the fixed genesis committee. (sei-protocol/sei-chain#4083)
…d behind the v6.8 upgrade) that changes proposal tallying behavior, adds new genesis fields and vote-delegation snapshots, charges additional gas for new vote tally records, and requires a store migration (Migrate3to4). (sei-protocol/sei-chain#4000)
…napshot format was bumped from 1 to 2, requiring node operators to coordinate rolling upgrades of state-sync providers. (sei-protocol/sei-chain#4098)
…ed; transaction admission and gossip are enforced by a fixed protocol gossip limit (1MiB), and oversized messages are discarded rather than closing the P2P connection. (sei-protocol/sei-chain#4139)
…imum of 6 blob hashes/sidecar items, matching blob/commitment/proof counts, and fixed-size KZG lengths, rejecting malformed blob transactions. (sei-protocol/sei-chain#4154)
…2 SIMD implementation, selectable via the new SEI_LTHASH_BACKEND environment variable. (sei-protocol/sei-chain#4151)
…y control) Prometheus/OpenTelemetry metrics and adds a MaxIncarnation field to OCCStats, giving node operators new observability signals for parallel execution behavior. (sei-protocol/sei-chain#4161)
…as price (accounting for base fee) instead of raw gas price, changing which dynamic-fee transactions are accepted at CheckTx. (sei-protocol/sei-chain#4170)
… sei-db view manager, introducing asynchronous staged folds, and changes FlatKV behavior so corrupted account rows now surface on read (panic) instead of on block apply. (sei-protocol/sei-chain#4155)
… hashing, selectable via the new SEI_TMHASH_BACKEND environment variable, requiring GOEXPERIMENT=simd at build time. (sei-protocol/sei-chain#4157)
…egisterPointer` handler for creating CosmWasm wrappers (CW20/CW721/CW1155) around ERC20/721/1155 tokens have been removed/deprecated; the handler now returns an error and the wrapper wasm is no longer shipped. (sei-protocol/sei-chain#4198)
…disabled and contract_execution_disabled, letting governance halt CosmWasm contract execution in stages; the wasm module moves to consensus version 2 and is app-hash breaking at the v6.8 upgrade. (sei-protocol/sei-chain#4564)
…urrent /subspace queries on all store paths (SS and commitment, latest and historical) instead of only the SS fast path. (sei-protocol/sei-chain#4567)
…ce queries with an ErrNotSupported error, since /subspace is served only from the state store. (sei-protocol/sei-chain#4572)
… reject proof queries with ErrNotSupported (code 37) unless operators set the new config field state-commit.sc-enable-state-proof = true, affecting light clients and any ABCI client sending prove=true. (sei-protocol/sei-chain#4573)
…er advances the eth_getFilterChanges cursor, so calling it will not cause subsequent getFilterChanges to skip or redeliver blocks. (sei-protocol/sei-chain#4582)
…Cosmos result data, so `tx_response.data` and `/block_results` omit them for new transactions (EVM RPC still serves logs via receipts), which also changes `LastResultsHash` from the v6.8 upgrade height. (sei-protocol/sei-chain#4577)
…rding EVM-only RPC parity fixtures from a v2 archive node. (sei-protocol/sei-chain#4541)
…r) have been removed from seid; the [grpc] and [grpc-web] config sections, their ports (9090/9091), and related CLI flags are gone, meaning developers can no longer query the node over gRPC. (sei-protocol/sei-chain#4570)
…terLogs, and eth_subscribe('logs') log filters changed to poll from a fixed cursor, with new handling of fromBlock/toBlock tags, oversized blocks, and a new error notification format for logs subscriptions. (sei-protocol/sei-chain#4589)
…ta config section, CLI tooling, and ports are gone — and the ratelimiter gRPC plane (PlaneGRPC/PlaneGRPCWeb) and related methods were removed. (sei-protocol/sei-chain#4584)
…ar, sei.toml support, and the `seid config check` subcommand) is being removed/reverted, eliminating a developer-facing environment variable, config file, and CLI command. (sei-protocol/sei-chain#4586)
…t scheme (ws/wss on port 8546) instead of HTTP (http/https on port 8545), changing validator configuration requirements. (sei-protocol/sei-chain#4583)
…n JSON-RPC error -32000 (receipts pruned) for heights below the node's receipt floor instead of empty/null results, affecting eth_feeHistory, debug_traceBlock*, log filters, and transaction-by-block-index lookups. (sei-protocol/sei-chain#4596)
…ribe) now reject a numeric fromBlock above 0 that is below the earliest available (non-pruned) block, and report pruned blocks when pruning passes a filter's cursor. (sei-protocol/sei-chain#4591)
…ere not deleted because data/upgrade-info.json did not name the upgrade at startup, requiring operators to write upgrade-info.json and restart. (sei-protocol/sei-chain#4538)
…9 response as an array of per-request error objects (one per non-notification request) instead of a single error object, aligning rejection response shape with request shape. (sei-protocol/sei-chain#4604)
…ifies a FlatKV snapshot's lattice hashes and key counts against a full scan, with several configuration flags. (sei-protocol/sei-chain#4600)
…hes config field changed: on non-Autobahn nodes the block filter now polls the CometBFT block store from a cursor, and the config field now governs per-poll block coverage in addition to unpolled-hash retention. (sei-protocol/sei-chain#4687)
… now uses a per-chain trust period built into the binary (112h on pacific-1, atlantic-2, arctic-1; 168h default elsewhere), and seid now warns if the obsolete setting is present. (sei-protocol/sei-chain#4691)
…lls now share a unified admission system with a new JSON-RPC error code -32005 (limit exceeded, retry later) for rate-limit and load-based refusals, and refusal error messages no longer expose internal server counts. (sei-protocol/sei-chain#4705)
…t block/transaction events and logs, changing what historical data is available from the store. (sei-protocol/sei-chain#4712)
…now spread across blocks via a new budgeted settlement mechanism (up to 1000 deposit records per block), changing when deposits are actually burned or refunded after a proposal ends. (sei-protocol/sei-chain#4714)
…ed to reject denoms outside the proposal's minimum deposit denoms and silently ignore empty deposits. (sei-protocol/sei-chain#4717)
…`large_log_query_rps`, default 30) replaces the previous hardcoded limit of 30, letting operators tune or disable rate limiting for eth_getLogs, eth_getFilterLogs, and filter polls over 100 blocks. (sei-protocol/sei-chain#4800)
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documentation catch-up for v6.8.0.
93 source PR(s) produced changes across 93 commit(s). Each source PR is a separate commit, so this reviews commit-by-commit.
node/technical-reference.mdxnode/technical-reference.mdxnode/giga-storage-migration.mdxevm-ss-separate-dbsconfig field is documented, and a data-directory snapshot restore path for enabling Giga SS Store is added.evm/installing-seid-cli.mdx,node/index.mdxevm/evm-parity/evm-compatibility.mdx,evm/evm-parity/websocket.mdx,evm/reference.mdxmilliTimestampfield (Unix milliseconds as a hex quantity) is added to EVM RPC block headers returned by eth_getBlockByNumber/Hash and eth_subscribe newHeads, since the standard seconds-basedtimestamprepeats across Sei's sub-second blocks.node/advanced-config-monitoring.mdx/store/*/subspaceABCI queries with new[state-commit]config fields (sc-subspace-max-pairs, sc-subspace-max-bytes, sc-subspace-query-max-inflight), empty-prefix rejection, and concurrency limits — requiring migration action for indexers issuing wide prefix scans.node/advanced-config-monitoring.mdx,node/seictl.mdxtelemetry.prometheus-retention-timein app.toml drops from 7200 to 0, disabling the Prometheus metrics sink by default on newly generated node configs.evm/reference.mdx,node/advanced-config-monitoring.mdxreceipt-store.rs-enableconfig field lets node operators disable the receipt store (defaults to true); when off the EVM RPC listeners refuse to start and receipt-dependent eth_* methods now return ErrNotConfigured, plus the legacy receipt migration and theenable-read-write-metricsapp.toml key were removed.node/technical-reference.mdxevm/precompiles/cosmwasm-precompiles/cosmwasm.mdx,evm/precompiles/cosmwasm-precompiles/example-usage.mdxnode/technical-reference.mdx,node/troubleshooting.mdxnode/technical-reference.mdxseid config checksubcommand that validates a node's sei.toml against the current binary without starting the node, exiting non-zero if any value would be refused at boot.node/giga-storage-migration.mdx,node/node-operators.mdx,node/technical-reference.mdxevm/reference.mdxevm/precompiles/governance.mdxnode/snapshot.mdx,node/statesync.mdxnode/index.mdxmax-tx-bytesconfig field is now effectively unused; transaction admission and gossip are enforced by a fixed protocol gossip limit (1MiB), and oversized messages are discarded rather than closing the P2P connection.evm/evm-parity/transaction-types.mdxnode/technical-reference.mdxnode/advanced-config-monitoring.mdxevm/evm-parity/gas-and-fees.mdxnode/giga-storage-migration.mdxnode/technical-reference.mdxevm/evm-parity/examples/pointer-contracts.mdxseid tx evm register-cw-pointerand theMsgRegisterPointerhandler for creating CosmWasm wrappers (CW20/CW721/CW1155) around ERC20/721/1155 tokens have been removed/deprecated; the handler now returns an error and the wrapper wasm is no longer shipped.node/technical-reference.mdx,node/troubleshooting.mdxevm-logical-digestcommand gains a--jsonflag for machine-readable output, supports--backend compositefor inspect mode, adds--memiavl-open-mode=replaysupport to inspect mode, and now writes errors to stderr instead of stdout.evm/evm-parity/evm-compatibility.mdx,evm/precompiles/example-usage.mdx,evm/transactions-with-seid.mdxevm/reference.mdx,node/technical-reference.mdxnode/technical-reference.mdxnode/technical-reference.mdxmax_concurrent_check_txto cap concurrent CheckTx calls in the local mempool, along with new producer Prometheus metrics and bounded pending-insert behavior.evm/transactions-with-seid.mdxseid tx evm deploy-wseiCLI command and its WSEI contract artifacts have been removed, so developers can no longer deploy a Wrapped Sei contract via this command.node/advanced-config-monitoring.mdxevmrpc_websocket_connectionstracking currently active websocket connections (incremented on connect, decremented on disconnect).node/giga-storage-migration.mdxevm/reference.mdxevm/reference.mdx,node/technical-reference.mdxevm-onlyconfig field andAUTOBAHN_EVMONLYenvironment variable have been removed; settingautobahn-config-filenow implies the node serves EVM JSON-RPC only and runs the EVM-only executor (unlessmock-appis set).evm/reference.mdxevm/changelog.mdx,evm/precompiles/auth.mdx,evm/precompiles/authz.mdx,evm/precompiles/cosmwasm-precompiles/bank.mdx,evm/precompiles/distribution.mdx,evm/precompiles/evidence.mdx+1 moreevm/evm-parity/gas-and-fees.mdx,evm/precompiles/json.mdx,evm/precompiles/p256-precompile.mdxevm/evm-parity/gas-and-fees.mdx,evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx,evm/reference.mdxevm/reference.mdxgiga.storage.receiptsconfig field that controls whether the receipt store opens and the EVM RPC starts, with a startup refusal if receipts are disabled while a receipt store with history is on disk.node/advanced-config-monitoring.mdxnode/advanced-config-monitoring.mdxevm/reference.mdx,node/node-types.mdxnode/advanced-config-monitoring.mdxevm/reference.mdx,node/node-types.mdxnode/advanced-config-monitoring.mdxnode/frozen-nodes.mdxnode/giga-storage-migration.mdxnode/technical-reference.mdx,node/troubleshooting.mdxseidb kvrepair-exportCLI command and a kvrepair hard-fork mechanism that applies reviewed key/value repairs to module stores at a target height; also updates evm-logical-digest guidance to use --key-offset.node/technical-reference.mdxevm/reference.mdxnode/advanced-config-monitoring.mdxnode/technical-reference.mdxautobahn.view_timeoutfield in the genesis doc (default 1500ms, nanoseconds as a string), changing where node operators configure it.node/advanced-config-monitoring.mdxnode/giga-storage-migration.mdx,node/troubleshooting.mdxevm/precompiles/distribution.mdxnode/advanced-config-monitoring.mdxnode/advanced-config-monitoring.mdxtendermint_p2p_known_addressesgauge reporting the number of distinct peers with a known address (connected peers plus those learned via PEX).evm/precompiles/staking.mdxnode/advanced-config-monitoring.mdx,node/giga-storage-migration.mdx,node/technical-reference.mdxevm/precompiles/cosmwasm-precompiles/bank.mdx,evm/precompiles/governance.mdx,evm/precompiles/params.mdxnode/advanced-config-monitoring.mdxstate_store_backend(and corresponding flaggiga.storage.state_store_backend) that selects how the EVM state store keeps history: 'pebbledb' (every version) or 'undolog' (prior values over current state), with historical state views now served from either backend.cosmos-sdk/index.mdx,evm/precompiles/cosmwasm-precompiles/bank.mdxnode/technical-reference.mdxcosmos-sdk/index.mdxburn_tokenscustom message still works so contracts can burnfactory/<contract>/<subdenom>denoms they created from their own balance, while minting and all other tokenfactory messages remain removed.evm/evm-parity/examples/error-handling.mdx,evm/reference.mdxevm/evm-parity/finality.mdx,evm/reference.mdxnode/giga-storage-migration.mdx,node/node-operators.mdxnode/frozen-nodes.mdxnode/index.mdxcosmos-sdk/index.mdx,evm/changelog.mdx,evm/precompiles/cosmwasm-precompiles/cosmwasm.mdxnode/advanced-config-monitoring.mdxnode/advanced-config-monitoring.mdxevm/reference.mdx,node/advanced-config-monitoring.mdxevm/reference.mdxevm/reference.mdxtx_response.dataand/block_resultsomit them for new transactions (EVM RPC still serves logs via receipts), which also changesLastResultsHashfrom the v6.8 upgrade height.node/technical-reference.mdxparitycapturedeveloper command-line tool for recording EVM-only RPC parity fixtures from a v2 archive node.node/advanced-config-monitoring.mdx,node/technical-reference.mdxevm/evm-parity/websocket.mdx,evm/reference.mdxevm/installing-seid-cli.mdxnode/technical-reference.mdxseid config checksubcommand) is being removed/reverted, eliminating a developer-facing environment variable, config file, and CLI command.node/technical-reference.mdxevm/evm-parity/evm-compatibility.mdx,evm/reference.mdxevm/evm-parity/websocket.mdx,evm/reference.mdxnode/frozen-nodes.mdx,node/troubleshooting.mdxevm/reference.mdx,node/advanced-config-monitoring.mdxnode/technical-reference.mdx,node/troubleshooting.mdxaudit-flatkvsubcommand to the seidb tool that verifies a FlatKV snapshot's lattice hashes and key counts against a full scan, with several configuration flags.evm/reference.mdx,node/advanced-config-monitoring.mdxnode/statesync.mdxevm/evm-parity/evm-compatibility.mdx,evm/evm-parity/websocket.mdx,evm/reference.mdxevm/reference.mdxevm/precompiles/governance.mdxevm/precompiles/governance.mdxevm/reference.mdx,node/advanced-config-monitoring.mdxlarge_log_query_rps, default 30) replaces the previous hardcoded limit of 30, letting operators tune or disable rate limiting for eth_getLogs, eth_getFilterLogs, and filter polls over 100 blocks.⛔ Failed final verification against the release tag
Each touched page was re-checked claim-by-claim against the
v6.8.0checkout after all commits were assembled. The items below contradict what actually ships at the tag and must be resolved before merging.evm/evm-parity/finality.mdx(Block tags section, added paragraph: "A block hash, or a height above the current head, returns an error.") — For state-reading methods (eth_getBalance, eth_getTransactionCount, eth_getCode, eth_getStorageAt), "A block hash ... returns an error."latestor belowstateEarliesterror (ensureWithinWatermarks, lines 217-224).evm/evm-parity/finality.mdx(Block tags section, added paragraph, final sentence about eth_call) — eth_call accepts only the latest-equivalent tags; an explicit height, a block hash, orearliestreturns an error, because calls do not run against historical state.evm/evm-parity/gas-and-fees.mdx(### Admission is priced on effective gas price) — Transaction admission at CheckTx compares a transaction's effective gas price against the minimum gas price, not its fee cap.txData.GetGasFeeCap().Cmp(fc.getBaseFee(ctx)) < 0andtxData.GetGasFeeCap().Cmp(fc.getMinimumFee(ctx)) < 0, both returning sdkerrors.ErrInsufficientFee. EffectiveGasPrice (line 128,txData.EffectiveGasPrice(utils.Big0)) is used only for priority/metrics, never for rejection. The effective-gas-price admission check exists only in the experimental EVM-only test app (sei-tendermint/internal/evmonlyapp/app.go:449), which giga/evmonly/README.md:1-5 states is 'intentionally separate from the current Cosmos-backed giga wiring in app/app.go' and whose custom precompiles are still placeholders.evm/evm-parity/gas-and-fees.mdx(### Admission is priced on effective gas price) — A dynamic-fee (type 2) transaction with a high maxFeePerGas but a low or zero maxPriorityFeePerGas is rejected at admission, even though its fee cap would clear the floor.evm/evm-parity/gas-and-fees.mdx(### Admission is priced on effective gas price) — A transaction that fails this check is rejected with aneffective gas price is belowerror.ethereum transaction effective gas price is below %s), inside the experimental EVM-only test app's parseTx. The production ante-handler rejection path returns sdkerrors.ErrInsufficientFee (x/evm/ante/fee.go:49,52), which does not carry this string.evm/installing-seid-cli.mdx— verification could not complete: unparseable verifier response: Confirmed. The archive name template is:For arm64,
.Archevaluates toarm64(goreleaser v2 has no automatic aarch64 mapping without explicit replacements, and none are configurevm/precompiles/auth.mdx(Intro paragraph under the Address line) — The versioned Auth precompile is available as of the v6.8 chain upgrade, with a v6.7 legacy registration retained for historical calls.auth.NewPrecompile(keepers)in a flat, unversionedGetCustomPrecompilesmap;app/app.go:774passes the whole map toSetCustomPrecompiles, andevmrpc/simulate.go:910 GetCustomPrecompiles(int64)ignores the height argument. There is no versioned registration and no separate 'legacy' registration (grep forlegacy,Version,v6.7,v6.8,RequiredVersion,LegacyPrecompilein precompiles/** returns no matches). The claimed dual/versioned-with-legacy-retained registration does not exist in the tree.evm/precompiles/authz.mdx(Intro paragraph under the Address line) — The Authz precompile is available since the v6.8 chain upgrade (#3618), which registers the versioned Authz precompile alongside the v6.7 legacy implementation.ecommon.HexToAddress(authz.AuthzAddress): check(authz.NewPrecompile(keepers))) with no v6.7-legacy counterpart, and precompiles/authz/authz.go has no versioning mechanism (no RequiredVersion/legacy/versioned symbols — grep returns no matches). Moreover CHANGELOG.md:117 (#4551) at this tag explicitly 'Remove[s] legacy precompiles and height-versioned precompile routing', so a 'versioned ... alongside the v6.7 legacy implementation' arrangement does not ship at v6.8.0.evm/precompiles/evidence.mdx(Intro paragraph under the address line (changed sentence)) — The Evidence precompile is registered as a versioned precompile with bothv6.7andv6.8versions available.pcommon.NewDynamicGasPrecompile(newAbi, p, common.HexToAddress(EvidenceAddress), "evidence")— a single unversioned registration. precompiles/setup.go:69 registers it once in GetCustomPrecompiles with no version.DynamicGasPrecompile(precompiles/common/precompiles.go:166-175) carries no version field. There is no versioned-precompile mechanism in the tree: grep forVersionedPrecompile,PrecompileVersion,RequiredVersion, andversionedin precompiles/** all return NO MATCHES, andv6.8/v6.7do not appear in the precompiles package. Nov6.7/v6.8version labels exist for this precompile.evm/reference.mdx— verification could not complete: verifier exceeded 30 tool turnsnode/advanced-config-monitoring.mdx— verification could not complete: verifier exceeded 30 tool turnsnode/index.mdx(Install Sei → Prebuilt binary (recommended) tab, theFILE=comment line for linux/arm64) — The linux/arm64 release asset is namedsei-chain_${VERSION#v}_linux_aarch64.tar.gz{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_then{{- if eq .Arch "amd64" }}x86_64 {{- else }}{{ .Arch }}{{ end }}. For arm64 the else branch emits.Arch, which is the goarch valuearm64(builds.goarch listsarm64at line 47), producingsei-chain_<ver>_linux_arm64.tar.gz, not..._linux_aarch64.tar.gz. Only the amd64 asset (x86_64, shown on the page) is correct. Theaarch64suffix in Dockerfile:12 is for a separate Docker build step, not the release archive.node/node-operators.mdx(Second added block under "Essential configuration parameters" (the receipt-backend.txt marker note)) — The receipt store's receipt-backend.txt marker refuses to open a directory that belongs to a different backend — "for example, opening alittidxstore directory aspebbledb, or vice versa, fails loudly with a mismatch error rather than presenting a silently empty store."node/technical-reference.mdx(#### Checking sei.toml before a restart (seid config check)) — Theseid config checksubcommand resolves a node'ssei.toml... and reports every value this binary would refuse, without starting the node (entireseid config checksection, including--home/SEID_HOMEresolution, the report contents, and theSEI_CONFIG_MANAGERgate state it surfaces).config checksubcommand,sei.toml,SEID_HOME, orSEI_CONFIG_MANAGERexists in the tree.grep SEI_CONFIG_MANAGER,grep ConfigManager,grep sei.toml,grep SEID_HOMEall return NO MATCHES in source (only CHANGELOG.md). CHANGELOG.md:91 (#4586, recent/v6.8.0): 'Remove ConfigManager and the in-tree config registry'. The feature was removed at this release tag.node/technical-reference.mdx(config checksection bullet list onSEI_CONFIG_MANAGERgate state; also referenced throughout) — TheSEI_CONFIG_MANAGERenvironment variable gate exists, withlegacy/v2/other values governing whether a boot readssei.toml, and an invalid value causesseidto refuse to start with aninvalid SEI_CONFIG_MANAGERerror.grep SEI_CONFIG_MANAGERandgrep invalid SEI_CONFIG_MANAGERreturn NO MATCHES in source. The ConfigManager was removed (CHANGELOG.md:91, #4586). No such env var or error string ships at the tag.node/technical-reference.mdx( beginning 'The node config registry now declares the[consensus]and[mempool]sections') — The node config registry now declares the[consensus]and[mempool]sections, so a newly generatedconfig.tomlcarries their fields (including which keys are declared vs. deprecated/omitted).grep ConfigManager/grep DeclareSectionreturn NO MATCHES; CHANGELOG.md:91 (#4586) 'Remove ConfigManager and the in-tree config registry'. config.toml is generated by the plain tendermint template (sei-tendermint/config/toml.go), not a registry. The claim attributes behavior to a removed component.node/technical-reference.mdx( beginning 'A newly generatedconfig.tomlalso declares five more sections') — A newly generatedconfig.tomlalso declares five more sections via the config registry:[statesync],[tx-index],[instrumentation],[priv-validator], and[self-remediation], with the[tx-index]indexer default varying by mode as a registry-declared behavior.[kv]with validators overridden to[null]at sei-tendermint/config/config.go:117, not a registry. Attributing it to the removed 'config registry' is a failed claim.Reviewer notes
release/v6.8: Make the large eth_getLogs rate limit configurable sei-chain#4800 — The hardcoded GlobalRPSLimit of 30 was never documented as a value, so the main gaps are documenting the new configurable field and the admission-order change. The behavior change (load check before limiter) is operator-visible mainly via the evm/reference.mdx admission wording. No migration step is required since the default (30) preserves prior behavior; negative values are rejected at startup.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 final text and diff for the reportable issues:
node/technical-reference.mdx— setting both removed and configurable (freeze mode--grpc-only): The Freeze mode warning now says you "cannot combinefreeze-heightwithhalt-heightorhalt-time" (dropping--grpc-only), but the newly untouched text in the Freeze mode body still says: "Do not start the node with--grpc-only. The node refuses to start whenfreeze-heightis combined with--grpc-only,halt-height, orhalt-time." The two passages contradict each other on whether--grpc-onlyis a refused combination.node/index.mdx— contradiction onmax-tx-bytesbehavior vs. a sibling default: The inserted comment onmax-tx-bytessays it "no longer controls transaction admission or gossip … Setting a different value only logs a startup warning and otherwise has no effect," yet the untouched mempool guidance elsewhere (e.g. innode/node-operators.mdxdefault config /config.tomlmax-tx-bytes = 1048576described as "Maximum size of a single transaction") still presents it as an active size limit. (Same identifier described two ways across the touched config pages.)node/giga-storage-migration.mdx— receipt backend described as both removed/unselectable and selectable: New text stateslittidx"can no longer be selected viaRECEIPT_BACKENDorrs-backend" and onlypebbledbis selectable fromapp.toml, but untouched text innode/node-operators.mdxstill says "The receipt-store backend acceptspebbledb(also calledpebble) andlittidx" and documents configuringlittidxviars-backend. Contradiction on whetherlittidxis a configurable backend.node/node-operators.mdx—prometheus-retention-timedefault contradiction: The defaultapp.tomlblock showsprometheus-retention-time = 7200, but the inserted warning innode/advanced-config-monitoring.mdxstates a v6.8.0-generatedapp.tomlgetsprometheus-retention-time = 0. (Cross-page contradiction on the generated default.)node/seictl.mdxvsnode/advanced-config-monitoring.mdx— same setting, two defaults: seictl example now usesprometheus-retention-time = 7200(changed from 60), consistent with node-operators but contradicting the "0 by default in v6.8.0" claim.node/technical-reference.mdx—freeze-height+--grpc-onlyalready covered above (primary instance).evm/reference.mdx—batch_request_limitdefault inconsistency: Frozen RPC router text (--batch-request-limitdefault1000) and the generatedapp.toml(batch_request_limit = 1000) conflict withnode/advanced-config-monitoring.mdxinserted text stating "The default EVMbatch_request_limitalso dropped from1000to100" and "default100". Same identifier, two defaults across pages.Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.