Skip to content

docs: v6.8.0 catch-up - #108

Draft
seidroid[bot] wants to merge 93 commits into
mainfrom
docs-bridge/release-v6.8.0
Draft

seidroid[bot] wants to merge 93 commits into
mainfrom
docs-bridge/release-v6.8.0

Conversation

@seidroid

@seidroid seidroid Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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.

source PR pages touched summary
sei-protocol/sei-chain#3993 node/technical-reference.mdx The node config registry now declares the tendermint consensus and mempool config sections (while excluding deprecated/unused settings), exposing new generated config file fields to operators.
sei-protocol/sei-chain#3994 node/technical-reference.mdx The seid init command's generated node config file now declares five additional sections (statesync, tx-index, instrumentation, priv-validator, self-remediation), exposing their config fields to operators.
sei-protocol/sei-chain#4027 node/giga-storage-migration.mdx The Giga SS Store default data-directory layout changed to backend-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#4004 evm/installing-seid-cli.mdx, node/index.mdx The release build now produces a statically-linked seid binary for linux/arm64 in addition to linux/amd64, so pre-built arm64 release artifacts are now available.
sei-protocol/sei-chain#4018 evm/evm-parity/evm-compatibility.mdx, evm/evm-parity/websocket.mdx, evm/reference.mdx A new BEP-520-compatible milliTimestamp field (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-based timestamp repeats across Sei's sub-second blocks.
sei-protocol/sei-chain#4009 node/advanced-config-monitoring.mdx Adds capping of /store/*/subspace ABCI 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.
sei-protocol/sei-chain#4032 node/advanced-config-monitoring.mdx, node/seictl.mdx The default telemetry.prometheus-retention-time in app.toml drops from 7200 to 0, disabling the Prometheus metrics sink by default on newly generated node configs.
sei-protocol/sei-chain#4062 evm/reference.mdx, node/advanced-config-monitoring.mdx A new receipt-store.rs-enable config 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 the enable-read-write-metrics app.toml key were removed.
sei-protocol/sei-chain#4012 node/technical-reference.mdx Adds two new EVM RPC config fields (max_filters, max_block_filter_hashes), enables eth_newBlockFilter under Autobahn, and changes broadcast_tx_commit to fail-fast when Autobahn is active.
sei-protocol/sei-chain#4066 evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx, evm/precompiles/cosmwasm-precompiles/example-usage.mdx The wasmd precompile's execute_batch method has been disabled and now returns an error, removing a previously available on-chain feature for batching CosmWasm contract executions from the EVM.
sei-protocol/sei-chain#3983 node/technical-reference.mdx, node/troubleshooting.mdx The seidb evm_logical_digest WAL-replay path now opens memiavl 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#4045 node/technical-reference.mdx Adds a new seid config check subcommand 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.
sei-protocol/sei-chain#4080 node/giga-storage-migration.mdx, node/node-operators.mdx, node/technical-reference.mdx Adds a receipt-store backend ownership marker file that refuses 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#4083 evm/reference.mdx The tmRPC /validators endpoint under Autobahn now returns the actual 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#4000 evm/precompiles/governance.mdx Introduces an incremental/bounded governance tally system (gated 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#4098 node/snapshot.mdx, node/statesync.mdx Go toolchain upgraded to 1.27.1 and the multistore state-sync snapshot format was bumped from 1 to 2, requiring node operators to coordinate rolling upgrades of state-sync providers.
sei-protocol/sei-chain#4139 node/index.mdx The mempool max-tx-bytes config 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.
sei-protocol/sei-chain#4154 evm/evm-parity/transaction-types.mdx Blob transaction validation now enforces EIP-4844 limits: a maximum of 6 blob hashes/sidecar items, matching blob/commitment/proof counts, and fixed-size KZG lengths, rejecting malformed blob transactions.
sei-protocol/sei-chain#4151 node/technical-reference.mdx Adds a pluggable LtHash hashing backend with an optional AVX-512 SIMD implementation, selectable via the new SEI_LTHASH_BACKEND environment variable.
sei-protocol/sei-chain#4161 node/advanced-config-monitoring.mdx The Giga EVM-only executor now emits OCC (optimistic concurrency 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#4170 evm/evm-parity/gas-and-fees.mdx The EVM-only app's transaction admission now checks effective gas price (accounting for base fee) instead of raw gas price, changing which dynamic-fee transactions are accepted at CheckTx.
sei-protocol/sei-chain#4155 node/giga-storage-migration.mdx Adds a new BatchUpdate method and BatchUpdater interface to the 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#4157 node/technical-reference.mdx Adds a SIMD (AVX-512) batched SHA-256 backend for tmhash/merkle hashing, selectable via the new SEI_TMHASH_BACKEND environment variable, requiring GOEXPERIMENT=simd at build time.
sei-protocol/sei-chain#4198 evm/evm-parity/examples/pointer-contracts.mdx The CLI command seid tx evm register-cw-pointer and the MsgRegisterPointer 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#4166 node/technical-reference.mdx, node/troubleshooting.mdx The seidb evm-logical-digest command gains a --json flag for machine-readable output, supports --backend composite for inspect mode, adds --memiavl-open-mode=replay support to inspect mode, and now writes errors to stderr instead of stdout.
sei-protocol/sei-chain#4230 evm/evm-parity/evm-compatibility.mdx, evm/precompiles/example-usage.mdx, evm/transactions-with-seid.mdx EVM pointer contracts and their CLI commands/governance proposals (register-evm-pointer, call-precompile pointer, query evm pointer, add-cw-erc20-pointer) have been removed/retired, and pointer precompile creation is now disabled.
sei-protocol/sei-chain#4257 evm/reference.mdx, node/technical-reference.mdx Autobahn now requires on-disk persistent storage: the --persistent-state-dir flag can no longer be empty, in-memory (memblock) mode is removed, and any node with an autobahn config file (not just EVM-only) opens Giga storage and is rejected in seed mode.
sei-protocol/sei-chain#4293 node/technical-reference.mdx CHANGELOG references a new JSON output option for the seidb evm-logical-digest command and the ability to inspect an in-flight FlatKV migration.
sei-protocol/sei-chain#4244 node/technical-reference.mdx Adds a new Autobahn config field max_concurrent_check_tx to cap concurrent CheckTx calls in the local mempool, along with new producer Prometheus metrics and bounded pending-insert behavior.
sei-protocol/sei-chain#4288 evm/transactions-with-seid.mdx The seid tx evm deploy-wsei CLI command and its WSEI contract artifacts have been removed, so developers can no longer deploy a Wrapped Sei contract via this command.
sei-protocol/sei-chain#4311 node/advanced-config-monitoring.mdx Adds a new EVM RPC metric evmrpc_websocket_connections tracking currently active websocket connections (incremented on connect, decremented on disconnect).
sei-protocol/sei-chain#4222 node/giga-storage-migration.mdx The receipt-store config now rejects the 'littidx' backend in app.toml (it is only opened by Giga), changes the supported backend list, and adds internal ReceiptIterator support plus a block-contiguity requirement for the littidx receipt store.
sei-protocol/sei-chain#4256 evm/reference.mdx Adds eth_feeHistory and eth_gasPrice JSON-RPC methods to the giga EVM-only RPC server, backed by a new per-block reward-percentile stats feature, plus a new receipt-store config field to control which percentiles are stored.
sei-protocol/sei-chain#4316 evm/reference.mdx, node/technical-reference.mdx The Tendermint evm-only config field and AUTOBAHN_EVMONLY environment variable have been removed; setting autobahn-config-file now implies the node serves EVM JSON-RPC only and runs the EVM-only executor (unless mock-app is set).
sei-protocol/sei-chain#4325 evm/reference.mdx Adds a new eth_estimateGas JSON-RPC method to the EVM-only RPC surface, supporting gas estimation against current committed state with the same block-tag and revert behavior as eth_call.
sei-protocol/sei-chain#4320 evm/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 more Adds the v6.8 chain upgrade with new versioned precompiles (addr, auth, authz, bank, distribution, evidence, gov) and the v6.7 legacy precompile registrations, exposing new on-chain EVM precompile methods for developers.
sei-protocol/sei-chain#4318 evm/evm-parity/gas-and-fees.mdx, evm/precompiles/json.mdx, evm/precompiles/p256-precompile.mdx Dynamic-gas precompiles that exhaust their Cosmos gas meter mid-execution now fail the EVM call frame with vm.ErrOutOfGas (reverting state, zero remaining gas, charging the sender for gas used) instead of letting the gas-meter panic escape and fail the entire transaction at the Cosmos layer.
sei-protocol/sei-chain#4336 evm/evm-parity/gas-and-fees.mdx, evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx, evm/reference.mdx This CHANGELOG update introduces numerous developer-facing changes including new EVM-only Giga RPC methods, a new [giga] app.toml config section, sei.toml-based config management, removal of oracle/WSEI/pointer-creation surfaces, and new EVM RPC capabilities.
sei-protocol/sei-chain#4333 evm/reference.mdx Adds a new giga.storage.receipts config 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.
sei-protocol/sei-chain#4322 node/advanced-config-monitoring.mdx FlatKV's default snapshot-keep-recent changed from 1 to 10 and is no longer derived from memIAVL's sc-keep-recent, so FlatKV now retains more old checkpoints to support composite reads and rollbacks.
sei-protocol/sei-chain#4317 node/advanced-config-monitoring.mdx The evmonly-loadtest tool gains new CLI flags (--accounts, --gc-percent) and a streaming mode when --blocks=0, new Prometheus metrics/dashboard, and the executor now pipelines state commits behind the next block.
sei-protocol/sei-chain#4338 evm/reference.mdx, node/node-types.mdx Adds a configurable EVM-only JSON-RPC port via the new giga.execution.evm_rpc_port config field, replacing the previously hardcoded port 8545.
sei-protocol/sei-chain#4349 node/advanced-config-monitoring.mdx Adds new Prometheus metrics for the autobahn consensus, availability, data, and giga P2P subsystems that node operators can scrape for observability.
sei-protocol/sei-chain#4365 evm/reference.mdx, node/node-types.mdx Adds a new EVM-only JSON-RPC WebSocket listener with a configurable port and support for eth_subscribe('newHeads') on Giga/Autobahn nodes.
sei-protocol/sei-chain#4299 node/advanced-config-monitoring.mdx Adds per-method deadline enforcement for EVM JSON-RPC over HTTP and WebSocket via two new config fields (rpc_default_timeout and rpc_method_timeouts) with a default 30s timeout.
sei-protocol/sei-chain#4337 node/frozen-nodes.mdx The v6.8 upgrade deletes the ibc, transfer, and capability stores from state, rewrites passed IBC ClientUpdateProposals as TextProposals, and changes the behavior of IBC store/proposal queries, affecting node operators and developers querying historical state.
sei-protocol/sei-chain#4405 node/giga-storage-migration.mdx Adds a 'pause-state-migration' hard fork handler that sets the state migration rate (NumKeysToMigratePerBlock) to zero at a target height, which node operators should be aware of during upgrades.
sei-protocol/sei-chain#4400 node/technical-reference.mdx, node/troubleshooting.mdx Adds a new seidb kvrepair-export CLI 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.
sei-protocol/sei-chain#4419 node/technical-reference.mdx The seidb evm-logical-digest tool gains a new 'changelog' value for --memiavl-open-mode and a new --inspect-plan flag for taking many inspect reports from one scan.
sei-protocol/sei-chain#4430 evm/reference.mdx EVM RPC block, filter, and log endpoints now return a clear error instead of panicking when historical state at a requested height is unavailable (e.g. pruned/SS-disabled nodes).
sei-protocol/sei-chain#4428 node/advanced-config-monitoring.mdx Adds a new 'undolog' state store backend (PebbleDB-based undo log for EVM history) selectable via the Sei state store config.
sei-protocol/sei-chain#4483 node/technical-reference.mdx The Autobahn view timeout moved from the autobahn.json file config to a new autobahn.view_timeout field in the genesis doc (default 1500ms, nanoseconds as a string), changing where node operators configure it.
sei-protocol/sei-chain#4403 node/advanced-config-monitoring.mdx Rate limiting is now enabled by default across EVM RPC, gRPC, and Tendermint RPC, and the default EVM batch request limit was lowered from 1000 to 100, with new default values for burst limits.
sei-protocol/sei-chain#4496 node/giga-storage-migration.mdx, node/troubleshooting.mdx FlatKV rollback and historical reads now refuse versions outside retained history before mutating state, surfacing a non-fatal 'version unreachable' error that advises node operators to use state sync instead.
sei-protocol/sei-chain#4501 evm/precompiles/distribution.mdx The ValidatorSlashes distribution query now filters by actual block height instead of validator period, fixing the meaning of the StartingHeight/EndingHeight parameters.
sei-protocol/sei-chain#4511 node/advanced-config-monitoring.mdx Introduces configurable EVM RPC per-IP rate limiting via app.toml fields (ip_rate_limit_rps, ip_rate_limit_burst) overridable by environment variables, and references the existing evm.batch_request_limit (default 100).
sei-protocol/sei-chain#4514 node/advanced-config-monitoring.mdx Adds a new Prometheus metric tendermint_p2p_known_addresses gauge reporting the number of distinct peers with a known address (connected peers plus those learned via PEX).
sei-protocol/sei-chain#4527 evm/precompiles/staking.mdx The staking precompile's redelegations query now enforces supported filter combinations (delegator+srcValidator+dstValidator, srcValidator alone, or delegator alone) and reverts on any other combination; view methods also no longer persist state side-effects.
sei-protocol/sei-chain#4533 node/advanced-config-monitoring.mdx, node/giga-storage-migration.mdx, node/technical-reference.mdx The littidx receipt store backend was split into a new 'gigareceipt' package, and the 'littidx' backend value is no longer a supported option for the standard receipt store config (only 'pebble' remains); littidx is now used exclusively by the giga/evmonly path.
sei-protocol/sei-chain#4528 evm/precompiles/cosmwasm-precompiles/bank.mdx, evm/precompiles/governance.mdx, evm/precompiles/params.mdx The bank precompile's spendableBalances now works for unassociated addresses, the Params precompile documents its return encoding, and the gov TallyResult query now returns final tally results for failed proposals.
sei-protocol/sei-chain#4498 node/advanced-config-monitoring.mdx Adds a new giga storage config field state_store_backend (and corresponding flag giga.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.
sei-protocol/sei-chain#4536 cosmos-sdk/index.mdx, evm/precompiles/cosmwasm-precompiles/bank.mdx The tokenfactory module is removed behind the v6.8 upgrade, deleting its CLI commands, queries, wasm bindings, params, and the bank denom transfer allowlist; existing factory/ balances remain but can no longer be minted/burned and allowlisted denoms become freely transferable.
sei-protocol/sei-chain#4518 node/technical-reference.mdx The v6.8 upgrade introduces a new delegation-by-validator index in the staking module, backfilled across blocks after the upgrade, which changes how ValidatorDelegations queries are served and requires node operators to be aware of the post-upgrade backfill behavior.
sei-protocol/sei-chain#4549 cosmos-sdk/index.mdx After the v6.8 tokenfactory removal, the Wasm burn_tokens custom message still works so contracts can burn factory/<contract>/<subdenom> denoms they created from their own balance, while minting and all other tokenfactory messages remain removed.
sei-protocol/sei-chain#4553 evm/evm-parity/examples/error-handling.mdx, evm/reference.mdx The eth_sendRawTransaction JSON-RPC endpoint now maps Sei mempool rejections to standard Ethereum error types (ErrAlreadyKnown, ErrNonceTooLow, ErrReplaceUnderpriced, ErrInsufficientFunds), improving error compatibility for EVM clients.
sei-protocol/sei-chain#4550 evm/evm-parity/finality.mdx, evm/reference.mdx The EVM-only JSON-RPC now supports historical state queries: eth_getBalance, eth_getTransactionCount, eth_getCode, and eth_getStorageAt accept an explicit past block height (or 'earliest') served from the EVM state store, whereas before they only accepted latest-equivalent tags.
sei-protocol/sei-chain#4543 node/giga-storage-migration.mdx, node/node-operators.mdx The giga app hash subsystem gained a new on-disk app hash vault store (data/ledger/app_hash), new AppHashBuilderConfig fields (ChainID, GigaActivationHeight), and changed recovery behavior that converges all stores onto the app hash vault head; these affect node operators upgrading Giga nodes.
sei-protocol/sei-chain#4563 node/frozen-nodes.mdx The v6.8 upgrade deletes the retired feegrant store, so from the upgrade height nodes no longer serve feegrant state at any height, requiring a v6.7 or older node for that history; this is app-hash breaking.
sei-protocol/sei-chain#4488 node/index.mdx The Docker image now builds and ships the seidb tool binary alongside seid, giving users access to the seidb CLI from the container.
sei-protocol/sei-chain#4564 cosmos-sdk/index.mdx, evm/changelog.mdx, evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx Adds two governance-settable wasm params, msg_execute_contract_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#4567 node/advanced-config-monitoring.mdx The sc-subspace-query-max-inflight config field now bounds concurrent /subspace queries on all store paths (SS and commitment, latest and historical) instead of only the SS fast path.
sei-protocol/sei-chain#4572 node/advanced-config-monitoring.mdx Nodes with the state store (SS) disabled now reject all /subspace queries with an ErrNotSupported error, since /subspace is served only from the state store.
sei-protocol/sei-chain#4573 evm/reference.mdx, node/advanced-config-monitoring.mdx ABCI /store state proofs are disabled by default in v6.8; nodes 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#4582 evm/reference.mdx eth_getFilterLogs is now a read-only history query that no longer advances the eth_getFilterChanges cursor, so calling it will not cause subsequent getFilterChanges to skip or redeliver blocks.
sei-protocol/sei-chain#4577 evm/reference.mdx EVM transactions no longer include return data and logs in the 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#4541 node/technical-reference.mdx Adds a new paritycapture developer command-line tool for recording EVM-only RPC parity fixtures from a v2 archive node.
sei-protocol/sei-chain#4570 node/advanced-config-monitoring.mdx, node/technical-reference.mdx The Cosmos gRPC and gRPC-Web servers (and the Rosetta API server) 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#4589 evm/evm-parity/websocket.mdx, evm/reference.mdx The behavior of eth_newFilter, eth_getFilterChanges, eth_getFilterLogs, 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#4584 evm/installing-seid-cli.mdx Rosetta API support has been fully removed from Sei — the Rosetta config section, CLI tooling, and ports are gone — and the ratelimiter gRPC plane (PlaneGRPC/PlaneGRPCWeb) and related methods were removed.
sei-protocol/sei-chain#4586 node/technical-reference.mdx The experimental v2 config manager (SEI_CONFIG_MANAGER=v2 env var, 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#4583 node/technical-reference.mdx The Autobahn/giga validator EVM RPC URL now requires a WebSocket scheme (ws/wss on port 8546) instead of HTTP (http/https on port 8545), changing validator configuration requirements.
sei-protocol/sei-chain#4596 evm/evm-parity/evm-compatibility.mdx, evm/reference.mdx EVM RPC methods that take a block identifier or range now return 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#4591 evm/evm-parity/websocket.mdx, evm/reference.mdx EVM log filters (eth_newFilter, eth_getFilterChanges, eth_subscribe) 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#4538 node/frozen-nodes.mdx, node/troubleshooting.mdx The v6.8 upgrade handler now halts the node if retired stores were 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#4604 evm/reference.mdx, node/advanced-config-monitoring.mdx Rate-limited JSON-RPC batch POST requests now return an HTTP 429 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#4600 node/technical-reference.mdx, node/troubleshooting.mdx Adds a new audit-flatkv subcommand to the seidb tool that verifies a FlatKV snapshot's lattice hashes and key counts against a full scan, with several configuration flags.
sei-protocol/sei-chain#4687 evm/reference.mdx, node/advanced-config-monitoring.mdx The behavior of eth_newBlockFilter and the max_block_filter_hashes 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#4691 node/statesync.mdx The statesync.trust-period config field was removed; state sync 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#4705 evm/evm-parity/evm-compatibility.mdx, evm/evm-parity/websocket.mdx, evm/reference.mdx eth_getLogs, eth_getFilterLogs, and eth_getFilterChanges log polls 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#4712 evm/reference.mdx FinalizeBlock responses larger than 1 GiB are now stored without block/transaction events and logs, changing what historical data is available from the store.
sei-protocol/sei-chain#4714 evm/precompiles/governance.mdx Governance deposit burning/refunding for finished proposals is 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#4717 evm/precompiles/governance.mdx When incremental tally is enabled, gov deposits are now validated to reject denoms outside the proposal's minimum deposit denoms and silently ignore empty deposits.
sei-protocol/sei-chain#4800 evm/reference.mdx, node/advanced-config-monitoring.mdx A new configurable node-wide rate limit for large log queries (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.

⛔ Failed final verification against the release tag

Each touched page was re-checked claim-by-claim against the v6.8.0 checkout 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."
    • evidence: evmrpc/state.go:38,56,73 and evmrpc/tx.go:333 all call WatermarkManager.ResolveHeight. In evmrpc/watermark_manager.go:152-164 ResolveHeight explicitly handles blockNrOrHash.BlockHash != nil by resolving it to a concrete height via blockByHash and returning it (after ensureWithinWatermarks). A valid, non-pruned block hash resolves successfully and is served from state — it does not return an error. Only heights above latest or below stateEarliest error (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, or earliest returns an error, because calls do not run against historical state.
    • evidence: evmrpc/simulate.go:172-202 Call passes blockNrOrHash straight into export.DoCall, which uses Backend.StateAndHeaderByNumberOrHash (evmrpc/simulate.go:339-376). That function, when the request is not latest (isLatest false, e.g. a block hash per isLatest lines 328-337, or a resolved explicit height), calls getBlockByNumberOrHash (lines 356, 847-868) to load the historical block and sets sdkCtx = ctxProvider(tmBlock.Block.Height) (line 363), then returns state.NewDBImpl at that historical height (line 375). Block hashes are resolved via blockByHashRespectingWatermarks (line 849). Thus eth_call DOES accept explicit heights, block hashes, and earliest, and DOES run against historical state — the opposite of the claim.
  • 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.
    • evidence: The production EVM ante handler x/evm/ante/fee.go:48-52 admits on the FEE CAP: txData.GetGasFeeCap().Cmp(fc.getBaseFee(ctx)) < 0 and txData.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.
    • evidence: In the shipped EVM path (x/evm/ante/fee.go:48-52) admission is decided solely on GetGasFeeCap() vs base/minimum fee; a tx whose fee cap clears the floor is ADMITTED regardless of its tip. The tip (GetGasTipCap) is only checked for being non-negative (fee.go:54-56). The described rejection occurs only in the evmonlyapp test application (app.go:445-451).
  • evm/evm-parity/gas-and-fees.mdx (### Admission is priced on effective gas price) — A transaction that fails this check is rejected with an effective gas price is below error.
    • evidence: The only occurrence of the 'effective gas price is below' string in the tree is sei-tendermint/internal/evmonlyapp/app.go:450 (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:
{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_
{{- if eq .Arch "amd64" }}x86_64
{{- else }}{{ .Arch }}{{ end }}

For arm64, .Arch evaluates to arm64 (goreleaser v2 has no automatic aarch64 mapping without explicit replacements, and none are configur

  • evm/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.
    • evidence: precompiles/setup.go:67 registers the auth precompile exactly once via auth.NewPrecompile(keepers) in a flat, unversioned GetCustomPrecompiles map; app/app.go:774 passes the whole map to SetCustomPrecompiles, and evmrpc/simulate.go:910 GetCustomPrecompiles(int64) ignores the height argument. There is no versioned registration and no separate 'legacy' registration (grep for legacy, Version, v6.7, v6.8, RequiredVersion, LegacyPrecompile in 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.
    • evidence: Two independent mismatches. (1) PR #3618 is unrelated to authz: CHANGELOG.md:816 states '#3618 [codex] remove sei debug trace exclude endpoints'. (2) No versioned/legacy dual-registration of the Authz precompile exists at v6.8.0. precompiles/setup.go:68 registers a single authz precompile (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 both v6.7 and v6.8 versions available.
    • evidence: precompiles/evidence/evidence.go:62 registers via 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 for VersionedPrecompile, PrecompileVersion, RequiredVersion, and versioned in precompiles/** all return NO MATCHES, and v6.8/v6.7 do not appear in the precompiles package. No v6.7/v6.8 version labels exist for this precompile.
  • 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/index.mdx (Install Sei → Prebuilt binary (recommended) tab, the FILE= comment line for linux/arm64) — The linux/arm64 release asset is named sei-chain_${VERSION#v}_linux_aarch64.tar.gz
    • evidence: .goreleaser.yaml:52-55 builds the archive name_template as {{ .ProjectName }}_{{ .Version }}_{{ .Os }}_ then {{- if eq .Arch "amd64" }}x86_64 {{- else }}{{ .Arch }}{{ end }}. For arm64 the else branch emits .Arch, which is the goarch value arm64 (builds.goarch lists arm64 at line 47), producing sei-chain_<ver>_linux_arm64.tar.gz, not ..._linux_aarch64.tar.gz. Only the amd64 asset (x86_64, shown on the page) is correct. The aarch64 suffix 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 a littidx store directory as pebbledb, or vice versa, fails loudly with a mismatch error rather than presenting a silently empty store."
    • evidence: The marker logic lives only in the pebble-only package sei-db/ledger_db/receipt/backend_marker.go. requireSupportedBackend (lines 19-26) accepts ONLY receiptBackendPebble ("pebble"); and recordBackendType is called from newReceiptBackend at sei-db/ledger_db/receipt/receipt_store.go:247, which normalizes any backend to "pebble" (receipt_store.go:192-199) before recording — so production only ever writes a marker naming "pebble". The littidx backend is a separate implementation (sei-db/ledger_db/gigareceipt): gigareceipt.NewReceiptStore -> newLittReceiptStore (litt_receipt_store.go:181) never calls recordBackendType/requireBackendType and never writes receipt-backend.txt (no marker references exist in gigareceipt/*.go). Consequently a real littidx store directory carries NO marker, so opening it as pebbledb hits the "unmarked directory is adopted" path (backend_marker.go:41-47, readBackendType returns found=false) and is silently accepted, NOT refused; and opening a pebbledb directory as littidx never consults the marker at all. The bidirectional littidx-vs-pebbledb mismatch the page describes is only reproducible in tests by hand-writing a littidx marker (backend_marker_internal_test.go:120-128); it does not occur between the two real backends in production.
  • node/technical-reference.mdx (#### Checking sei.toml before a restart (seid config check)) — The seid config check subcommand resolves a node's sei.toml ... and reports every value this binary would refuse, without starting the node (entire seid config check section, including --home/SEID_HOME resolution, the report contents, and the SEI_CONFIG_MANAGER gate state it surfaces).
    • evidence: No config check subcommand, sei.toml, SEID_HOME, or SEI_CONFIG_MANAGER exists in the tree. grep SEI_CONFIG_MANAGER, grep ConfigManager, grep sei.toml, grep SEID_HOME all 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 check section bullet list on SEI_CONFIG_MANAGER gate state; also referenced throughout) — The SEI_CONFIG_MANAGER environment variable gate exists, with legacy/v2/other values governing whether a boot reads sei.toml, and an invalid value causes seid to refuse to start with an invalid SEI_CONFIG_MANAGER error.
    • evidence: grep SEI_CONFIG_MANAGER and grep invalid SEI_CONFIG_MANAGER return 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 generated config.toml carries their fields (including which keys are declared vs. deprecated/omitted).
    • evidence: There is no config registry in the tree: grep ConfigManager/grep DeclareSection return 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 generated config.toml also declares five more sections') — A newly generated config.toml also 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.
    • evidence: No config registry exists (CHANGELOG.md:91, #4586 removed it; grep ConfigManager/DeclareSection NO MATCHES). The template sei-tendermint/config/toml.go emits these sections directly; the tx-index indexer default comes from DefaultConfig [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

  • Backport 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.

⚠️ 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 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 combine freeze-height with halt-height or halt-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 when freeze-height is combined with --grpc-only, halt-height, or halt-time." The two passages contradict each other on whether --grpc-only is a refused combination.

  • node/index.mdx — contradiction on max-tx-bytes behavior vs. a sibling default: The inserted comment on max-tx-bytes says 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. in node/node-operators.mdx default config / config.toml max-tx-bytes = 1048576 described 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 states littidx "can no longer be selected via RECEIPT_BACKEND or rs-backend" and only pebbledb is selectable from app.toml, but untouched text in node/node-operators.mdx still says "The receipt-store backend accepts pebbledb (also called pebble) and littidx" and documents configuring littidx via rs-backend. Contradiction on whether littidx is a configurable backend.

  • node/node-operators.mdx — prometheus-retention-time default contradiction: The default app.toml block shows prometheus-retention-time = 7200, but the inserted warning in node/advanced-config-monitoring.mdx states a v6.8.0-generated app.toml gets prometheus-retention-time = 0. (Cross-page contradiction on the generated default.)

  • node/seictl.mdx vs node/advanced-config-monitoring.mdx — same setting, two defaults: seictl example now uses prometheus-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-only already covered above (primary instance).

  • evm/reference.mdx — batch_request_limit default inconsistency: Frozen RPC router text (--batch-request-limit default 1000) and the generated app.toml (batch_request_limit = 1000) conflict with node/advanced-config-monitoring.mdx inserted text stating "The default EVM batch_request_limit also dropped from 1000 to 100" and "default 100". Same identifier, two defaults across pages.


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

seidroid Bot added 10 commits November 18, 2026 00:44
…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)
@seidroid seidroid Bot added the automated Automated PR from sei-docs-bridge label Nov 18, 2026
@mintlify

mintlify Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated
sei-docs 🟢 Ready View Preview Nov 20, 2026, 12:30 PM

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

seidroid Bot added 4 commits November 18, 2026 06:32
…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)
seidroid Bot added 8 commits November 18, 2026 12:28
…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)
seidroid Bot added 6 commits November 20, 2026 00:45
…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)
seidroid Bot added 7 commits November 20, 2026 00:50
…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)
seidroid Bot added 6 commits November 20, 2026 06:31
…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)
seidroid Bot added 4 commits November 20, 2026 06:39
…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

1 active deployment
staging — 18368b17 Deployed Nov 20, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated Automated PR from sei-docs-bridge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants