Skip to content

docs: v6.7.0 catch-up - #105

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

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

Conversation

@seidroid

@seidroid seidroid Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Documentation catch-up for v6.7.0.

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

source PR pages touched summary
sei-protocol/sei-chain#3846 evm/precompiles/authz.mdx, evm/precompiles/governance.mdx The Gov precompile adds three new functions—grantVoteAuthorization, voteWithAuthorization, and revokeVoteAuthorization—enabling delegated voting via authz grants from Solidity/EVM.
sei-protocol/sei-chain#3658 node/technical-reference.mdx Adds a new standalone CLI tool evmonly-loadtest for feeding synthetic transfer/ERC20/snapshot-revert blocks to the EVM-only executor, with a large set of tunable flags and Prometheus metrics.
sei-protocol/sei-chain#3867 node/technical-reference.mdx Pagination limits/offsets for node-local LCD/gRPC queries are no longer capped (MaxLimit now equals uint64 max, MaxOffset/scan-limit errors removed), while EVM precompile query paths retain the legacy v6.6 limits for consensus safety.
sei-protocol/sei-chain#3881 node/swagger.mdx The Interchain Accounts (ICA) proto definitions and REST/gRPC query endpoints (including the ICA host and controller params queries) are being removed, meaning the ICA feature and its API endpoints are no longer available.
sei-protocol/sei-chain#3868 node/technical-reference.mdx, node/troubleshooting.mdx The storage garbage collector gains a new LookbackWindow config field and rewrites its pruning model (RollbackWindow + LookbackWindow), and the littblock BlockDB changes its default retention and refuses to open pre-rename on-disk tables — a node-operator migration concern.
sei-protocol/sei-chain#3909 evm/reference.mdx EVM RPC block endpoints (getBlockByHash, getBlockByNumber, GetBlockReceipts) now return a 'receipts have been pruned' error when the requested block's receipt data is no longer available.
sei-protocol/sei-chain#3912 evm/reference.mdx The entire sei2_* JSON-RPC namespace (seven block methods that included bank transfers in block payloads) has been removed from Sei's EVM HTTP RPC, along with its config allowlist entries.
sei-protocol/sei-chain#3893 evm/precompiles/distribution.mdx, evm/precompiles/governance.mdx, evm/precompiles/staking.mdx Adds authorization (authz) grant/execute/revoke methods to the distribution, gov, slashing, and staking EVM precompiles, letting callers delegate withdrawal, voting, proposal submission, unjailing, and staking actions to a grantee.
sei-protocol/sei-chain#3934 node/technical-reference.mdx The unsafe consensus timeout override config fields (unsafe-propose-timeout-override, unsafe-vote-timeout-override, unsafe-commit-timeout-override, unsafe-bypass-commit-timeout-override, etc.) have been removed from config.toml; consensus timeouts are now set via on-chain genesis consensus_params timeout fields instead.
sei-protocol/sei-chain#3940 evm/reference.mdx, evm/tracing/troubleshooting.mdx EVM trace RPC methods (debug_traceTransaction, debug_traceBlockByNumber/ByHash, debug_traceCall, and trace profile) now honor the caller's context deadline/cancellation during historical state reconstruction, returning the deadline/cancel error instead of a synthesized fake trace result.
sei-protocol/sei-chain#3961 docs.json, evm/precompiles/distribution.mdx, evm/precompiles/example-usage.mdx, evm/precompiles/feegrant.mdx, evm/precompiles/governance.mdx A new v6.7 upgrade version adds several new EVM precompiles (auth at 0x...100D, authz at 0x...100E, evidence at 0x...100F, feegrant at 0x...1010) and expands existing precompiles (bank, distribution, gov, addr) with new query and authorization methods that developers can call from smart contracts.
sei-protocol/sei-chain#3956 evm/precompiles/governance.mdx, evm/precompiles/staking.mdx, node/validators.mdx Bank, gov, and staking modules now enforce recipient deliverability checks (CanSendTo/BlockedAddr) so that undelegation, deposit refunds, and unbonding to invalid/blocked recipients are retained rather than sent, changing on-chain behavior for node operators and developers.
sei-protocol/sei-chain#3944 evm/precompiles/oracle.mdx The oracle module is now deprecated (all its messages and queries, plus the CLI/precompile paths, return an 'oracle module is deprecated' error), gasless transactions are removed (oracle votes and MsgAssociate now require fees and count toward block gas), and the native MsgAssociate handler is deprecated.
sei-protocol/sei-chain#3958 evm/precompiles/example-usage.mdx, evm/precompiles/feegrant.mdx The feegrant module is removed from Sei: feegrant execution, module APIs, REST endpoints, and the unreleased feegrant EVM precompile are gone, and transactions with a fee granter different from the payer are now rejected.
sei-protocol/sei-chain#3967 node/troubleshooting.mdx The state store (SS) can now roll back to a target version alongside the commit store during RollbackToVersion, with new behavior around snapshot requirements, changelog retention, and crash recovery, plus a warning when the state store cannot follow the rollback.
sei-protocol/sei-chain#3981 node/frozen-nodes.mdx, node/swagger.mdx IBC transfer (ICS-20) support is removed in v6.7, including CLI commands, REST/gRPC transfer query endpoints, CosmWasm transfer messages, and the IBC EVM precompile's transfer/client/connection/channel keeper injection; pre-v6.7 transfer history must be served by v6.6 freeze nodes.
sei-protocol/sei-chain#4002 node/frozen-nodes.mdx, node/swagger.mdx, node/technical-reference.mdx Sei v6.7 removes all IBC query APIs (gRPC, REST, Protobuf, raw ABCI store, and native CosmWasm queries) along with IBC CLI query commands; retired IBC/transfer/capability store queries now return an ErrIBCDeprecated error and must be served by v6.6 freeze nodes.
sei-protocol/sei-chain#4010 cosmos-sdk/index.mdx, node/technical-reference.mdx IBC messages are now deprecated/retired on Sei — any transaction containing an IBC message (prefixed with /ibc.) is rejected at the ante handler with an ErrIBCDeprecated error.
sei-protocol/sei-chain#3977 node/node-operators.mdx, node/technical-reference.mdx A new internal config registry feature adds mode-aware resolution of Cosmos server config keys, refuses unknown node modes, and reports environment variables that cannot supply certain keys (e.g. telemetry.global-labels), affecting how config defaults resolve per node mode.
sei-protocol/sei-chain#4014 cosmos-sdk/index.mdx, evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx, node/technical-reference.mdx The IBC module has been fully retired/deprecated: IBC wiring, keeper, ante decorator, begin-blocker, metrics, and CosmWasm IBC entry points are removed, and queries to retired IBC stores now return an 'ibc module is deprecated' error.
sei-protocol/sei-chain#3989 node/technical-reference.mdx Adds a new frozen-rpc-router binary/command that routes EVM JSON-RPC requests to live or frozen-height nodes, with new CLI flags and build targets, and introduces a seid start --freeze-height flag.
sei-protocol/sei-chain#4047 evm/installing-seid-cli.mdx, node/index.mdx The release build now produces statically-linked seid binaries for both linux/amd64 and linux/arm64, so Sei users can download a prebuilt arm64 binary in addition to amd64.
sei-protocol/sei-chain#4074 evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx, evm/precompiles/example-usage.mdx The wasmd precompile's execute_batch method has been disabled and now returns an error, removing the ability to batch-execute multiple CosmWasm contract calls via the EVM precompile.
sei-protocol/sei-chain#4113 evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx The v6.7 changelog introduces numerous developer-facing changes including removal of legacy sei_* and sei2_* JSON-RPC APIs, eth_getProof removal, origin-aware ABCI pagination caps with new config fields, EVM RPC admission/rate-limiting config, new precompile authorization features, a freeze mode for historical EVM RPC, and new CLI commands for address association.
sei-protocol/sei-chain#4255 node/technical-reference.mdx The seidb evm-logical-digest tool adds a --json flag for machine-readable output (narration redirected to stderr), extends --inspect-bucket to support the composite backend and the replay open mode, and documents SEI_LOG_OUTPUT=stderr for clean JSON reports.
sei-protocol/sei-chain#4294 node/technical-reference.mdx A seidb CLI command gained JSON output support and new inspection capability, plus internal changelog/migration fixes.
sei-protocol/sei-chain#4334 evm/evm-parity/gas-and-fees.mdx, evm/precompiles/p256-precompile.mdx Dynamic-gas precompiles now convert an executor's out-of-gas (gas-meter) panic into a reverted/failed EVM call frame with vm.ErrOutOfGas and zero remaining gas, instead of propagating the panic and failing the entire transaction at the Cosmos layer.
sei-protocol/sei-chain#4409 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#4410 node/giga-storage-migration.mdx, node/technical-reference.mdx Adds a new seidb kvrepair-export CLI command for generating KV repair files from evm-logical-digest reports, a new embedded kvrepair hard-fork mechanism that applies reviewed key/value fixes at a target height, and new flags/guidance (--key-offset) for the evm-logical-digest inspect workflow.
sei-protocol/sei-chain#4439 node/giga-storage-migration.mdx, node/technical-reference.mdx The seidb evm-logical-digest command gains a new changelog memiavl open mode and a new --inspect-plan flag for taking multiple inspect reports from one scan.

⛔ 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/installing-seid-cli.mdx (Prebuilt binary tab, bash sample: # FILE=sei-chain_${VERSION#v}_linux_aarch64.tar.gz # linux/arm64; and the block referring to the aarch64 asset) — The linux/arm64 prebuilt binary asset is named sei-chain_${VERSION#v}_linux_aarch64.tar.gz
    • evidence: .goreleaser.yaml:52-55 archive name_template outputs x86_64 only for amd64 and falls back to {{ .Arch }} for all other arches, which for arm64 renders the literal arm64. There is no replacements mapping in the archives config (no match for 'replacements' in .goreleaser.yaml). The actual arm64 asset is therefore sei-chain_<version>_linux_arm64.tar.gz, not ..._linux_aarch64.tar.gz. (The amd64 x86_64 filename at line 54 is correct.)
  • evm/tracing/troubleshooting.mdx (Section 'Node configuration for better performance' TOML block) — TOML sample under [evm] uses trace-timeout = "300s" to configure the trace timeout.
    • evidence: The shipped config key is trace_timeout (underscore), rendered as trace_timeout = "{{ .EVM.TraceTimeout }}" in evmrpc/config/config.go:904 and declared mapstructure:"trace_timeout" at evmrpc/config/config.go:186. No hyphenated trace-timeout key exists (grep 'trace-timeout' -> NO MATCHES). An operator copying trace-timeout would not set the timeout.
  • evm/tracing/troubleshooting.mdx (Section 'Node configuration for better performance' TOML block) — TOML sample under [evm] uses trace-memory-limit = "1GB".
    • evidence: No such config key exists at the tag: grep 'trace-memory-limit' and 'trace_memory_limit' both return NO MATCHES. The evmrpc template (evmrpc/config/config.go) has no memory-limit trace key; the nearest real key is max_trace_struct_log_bytes (config.go:196/912), which is not a byte-size string like '1GB'.
  • evm/tracing/troubleshooting.mdx (Section 'Node configuration for better performance' TOML block) — TOML sample under [evm] uses trace-cache-size = 1000 to enable trace caching.
    • evidence: No such config key exists at the tag: grep 'trace-cache-size', 'trace_cache_size', and 'trace_cache' all return NO MATCHES. No trace cache size key is rendered by the evmrpc template (evmrpc/config/config.go).
  • node/frozen-nodes.mdx (How freeze mode works — new v6.7 paragraph) — Raw ABCI store queries against the retired IBC-related stores now return an ErrIBCDeprecated error.
    • evidence: No identifier ErrIBCDeprecated exists in the tree (grep for ErrIBCDeprecated|IBCDeprecated returns no matches). The raw ABCI store query deprecation error is app/retiredibc.ErrDeprecated = sdkerrors.New("ibc", 103, "ibc module is deprecated") at app/retiredibc/query.go:18, returned via QueryResponse() at app/retiredibc/query.go:30 (dispatched from app/app.go:474 and sei-wasmd/app/app.go:237). The only similarly-named error is ErrIBCPrecompileRetired at precompiles/ibc/ibc.go:21, which is the EVM precompile revert, not the ABCI store query error.
  • node/giga-storage-migration.mdx (Section 'Pausing the migration network-wide') — A pause-state-migration hard fork handler can halt the migration rate across the network at a configured target height ... it takes effect at the target height without a node restart ... Node operators should be aware of this hard fork during upgrades, since it changes the effective migration rate at the target height.
    • evidence: app/upgrades/migrationpause/upgrade.go defines the handler (const upgradeName = "pause-state-migration", ExecuteHandler sets NumKeysToMigratePerBlock=0), but it is NEVER registered in the production binary. app/app.go:1004-1010 registers only v0upgrade.NewHardForkUpgradeHandler and kvrepair.Register on app.HardForkManager. grep for 'migrationpause' returns only app/upgrades/migrationpause/upgrade.go (the definition) and app/abci_test.go:91 (a test). No live registration means no node at v6.7.0 runs this handler, so the claim that it takes effect network-wide at a target height is wrong at this tag.
  • node/index.mdx (Install Sei > Prebuilt binary (recommended) tab, callout (changed region)) — The prebuilt arm64 release asset is named with linux_aarch64 ("pick the asset matching your architecture (linux_x86_64 for amd64, linux_aarch64 for arm64)").
    • evidence: .goreleaser.yaml:52-55 archive name_template renders {{ .ProjectName }}_{{ .Version }}_{{ .Os }}_ then x86_64 for amd64 else {{ .Arch }}; for the arm64 build (goarch arm64, .goreleaser.yaml:45-47) .Arch is arm64, so the asset is sei-chain_<version>_linux_arm64.tar.gz, not linux_aarch64. There is no replacements map and no aarch64 anywhere in .goreleaser.yaml (grep: NO MATCHES), and no renaming in .github/workflows (grep x86_64 in workflows: NO MATCHES). aarch64 appears only as an internal Dockerfile ARCH_SUFFIX (Dockerfile:14) and libwasmvm archive names, not as the GitHub release asset name.
  • node/technical-reference.mdx — verification could not complete: verifier exceeded 30 tool turns
  • node/troubleshooting.mdx (## BlockDB refuses to open on a pre-rename table) — On startup the block DB now refuses to open if a pre-rename ledger table directory is still present under any of its root paths, and the node fails to start with an error block db: found a pre-rename "ledger" table at [...]; the table is now named "blocks", so those blocks and QCs would be neither served nor reclaimed. Delete or move the directory aside to start from an empty store.
    • evidence: sei-db/ledger_db/block/littblock/litt_block_db.go NewBlockDB (lines 39-72) opens/builds the table unconditionally; there is no check for an existing ledger directory and no refusal path. The documented error string does not exist anywhere in the tree (grep for 'block db: found', 'pre-rename', 'neither served nor reclaimed', 'table is now named', 'Delete or move the directory' all return no matches). The only 'ledger'-related messages in this file are internal error wraps like 'failed to build ledger table' (line 64). tableName = "blocks" (line 18) but no migration/detection guard accompanies the rename.
  • node/troubleshooting.mdx (## BlockDB refuses to open on a pre-rename table / ### Recovery) — The refusal happens before anything is written, so the directory is left exactly as found — nothing new is created beside the legacy table; after deleting/moving the legacy ledger directory the block DB opens fresh under the blocks name.
    • evidence: No refusal logic exists (see above). NewBlockDB in sei-db/ledger_db/block/littblock/litt_block_db.go:39-72 always builds the 'blocks' table via db.BuildTable regardless of any legacy directory; there is no code path implementing the described 'refuse before writing' behavior.

Reviewer notes

  • Backport release/v6.7: seidb: add changelog mode and --inspect-plan to speed up EVM digest sei-chain#4439 — The technical-reference evm-logical-digest flag list already documents the changelog open mode accurately, so only the inspect-mode prose and the new --inspect-plan flag need attention there. The troubleshooting page already documents changelog mode correctly. The kvrepair-export command source comment in the PR was updated to prefer changelog; the giga-storage-migration repair-generation example should mirror that recommendation. No new pages are needed and no migration step is required.

⚠️ 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 four issue categories:

  • Distribution precompile — contradictory expiration validation: grantWithdrawAuthorization says "The expiration must be after the current block time, otherwise the call reverts," while the governance precompile and staking precompile describe their grants consistently. Within distribution itself there is no direct contradiction — no issue here.

  • example-usage.mdx vs cosmwasm.mdx on execute_batch: The example-usage table now says execute_batch() "is disabled and reverts with wasmd execute_batch is disabled." The cosmwasm.mdx page's own How does the CosmWasm precompile work? section and Functions lists still describe execute_batch() as an available/working function ("exposes functions such as execute(), execute_batch(), and query()" and "Run batch operations that execute multiple contract calls efficiently in a single transaction") while the top Danger banner says it is disabled and reverts. This is a direct contradiction on the same page (cosmwasm.mdx): batch execution described as both disabled/reverting and as a working capability.

  • Oracle precompile — min_valid_per_window vs retired oracle: The technical-reference network parameters now list an Oracle min_valid_per_window: 0% parameter as a current chain parameter, while oracle.mdx states the entire oracle module is deprecated and all oracle module queries fail. Potential tension, but the parameter note explains it is retained/changed due to the retired feeder, so not a clean contradiction. No issue reported.

  • Feegrant precompile — removed vs configurable/callable: feegrant.mdx says the precompile "has been removed... is not available at any address... no longer callable." But the technical-reference "Retired IBC messages" note lists feegrant among modules whose EVM precompile query paths "keep the legacy v6.6 pagination behavior" — implying the feegrant precompile query path still exists and runs. This is a setting/feature described as both removed (feegrant.mdx) and still operative (technical-reference).

  • Identifier spelling — enable-read-write-metrics vs ss-enable-read-write-metrics: In app.toml the state-store key is ss-enable-read-write-metrics and the receipt-store key is enable-read-write-metrics; these are distinct keys, not inconsistent spellings. No issue.

Reporting the confirmed findings:

  • Direct contradiction within cosmwasm.mdx: the Danger banner and the execute_batch() reference/Query functions state that batch execution is disabled and reverts (wasmd execute_batch is disabled), while the same page's "How does the CosmWasm precompile work?" and "What you'll learn" sections still describe execute_batch() as a working/available function for efficient batch operations.
  • Setting described as both removed and configurable/callable: feegrant.mdx says the feegrant EVM precompile "has been removed," "is not available at any address," and is "no longer callable," but technical-reference.mdx lists feegrant among modules whose EVM precompile query paths "keep the legacy v6.6 pagination behavior" (implying it still runs during execution).

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

seidroid Bot added 7 commits November 13, 2026 00:44
…ion, voteWithAuthorization, and revokeVoteAuthorization—enabling delegated voting via authz grants from Solidity/EVM. (sei-protocol/sei-chain#3846)
…ynthetic transfer/ERC20/snapshot-revert blocks to the EVM-only executor, with a large set of tunable flags and Prometheus metrics. (sei-protocol/sei-chain#3658)
…o longer capped (MaxLimit now equals uint64 max, MaxOffset/scan-limit errors removed), while EVM precompile query paths retain the legacy v6.6 limits for consensus safety. (sei-protocol/sei-chain#3867)
…uery endpoints (including the ICA host and controller params queries) are being removed, meaning the ICA feature and its API endpoints are no longer available. (sei-protocol/sei-chain#3881)
… field and rewrites its pruning model (RollbackWindow + LookbackWindow), and the littblock BlockDB changes its default retention and refuses to open pre-rename on-disk tables — a node-operator migration concern. (sei-protocol/sei-chain#3868)
…lockReceipts) now return a 'receipts have been pruned' error when the requested block's receipt data is no longer available. (sei-protocol/sei-chain#3909)
…included bank transfers in block payloads) has been removed from Sei's EVM HTTP RPC, along with its config allowlist entries. (sei-protocol/sei-chain#3912)
@seidroid seidroid Bot added the automated Automated PR from sei-docs-bridge label Nov 13, 2026
seidroid Bot added 3 commits November 13, 2026 06:34
…distribution, gov, slashing, and staking EVM precompiles, letting callers delegate withdrawal, voting, proposal submission, unjailing, and staking actions to a grantee. (sei-protocol/sei-chain#3893)
…pose-timeout-override, unsafe-vote-timeout-override, unsafe-commit-timeout-override, unsafe-bypass-commit-timeout-override, etc.) have been removed from config.toml; consensus timeouts are now set via on-chain genesis consensus_params timeout fields instead. (sei-protocol/sei-chain#3934)
…ByNumber/ByHash, debug_traceCall, and trace profile) now honor the caller's context deadline/cancellation during historical state reconstruction, returning the deadline/cancel error instead of a synthesized fake trace result. (sei-protocol/sei-chain#3940)
@mintlify

mintlify Bot commented Nov 13, 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 14, 2026, 12:43 AM

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

seidroid Bot added 5 commits November 13, 2026 06:45
…th at 0x...100D, authz at 0x...100E, evidence at 0x...100F, feegrant at 0x...1010) and expands existing precompiles (bank, distribution, gov, addr) with new query and authorization methods that developers can call from smart contracts. (sei-protocol/sei-chain#3961)
…lity checks (CanSendTo/BlockedAddr) so that undelegation, deposit refunds, and unbonding to invalid/blocked recipients are retained rather than sent, changing on-chain behavior for node operators and developers. (sei-protocol/sei-chain#3956)
…es, plus the CLI/precompile paths, return an 'oracle module is deprecated' error), gasless transactions are removed (oracle votes and MsgAssociate now require fees and count toward block gas), and the native MsgAssociate handler is deprecated. (sei-protocol/sei-chain#3944)
…dule APIs, REST endpoints, and the unreleased feegrant EVM precompile are gone, and transactions with a fee granter different from the payer are now rejected. (sei-protocol/sei-chain#3958)
…gside the commit store during RollbackToVersion, with new behavior around snapshot requirements, changelog retention, and crash recovery, plus a warning when the state store cannot follow the rollback. (sei-protocol/sei-chain#3967)
seidroid Bot added 4 commits November 13, 2026 12:36
… commands, REST/gRPC transfer query endpoints, CosmWasm transfer messages, and the IBC EVM precompile's transfer/client/connection/channel keeper injection; pre-v6.7 transfer history must be served by v6.6 freeze nodes. (sei-protocol/sei-chain#3981)
…ABCI store, and native CosmWasm queries) along with IBC CLI query commands; retired IBC/transfer/capability store queries now return an ErrIBCDeprecated error and must be served by v6.6 freeze nodes. (sei-protocol/sei-chain#4002)
…n containing an IBC message (prefixed with /ibc.) is rejected at the ante handler with an ErrIBCDeprecated error. (sei-protocol/sei-chain#4010)
…on of Cosmos server config keys, refuses unknown node modes, and reports environment variables that cannot supply certain keys (e.g. telemetry.global-labels), affecting how config defaults resolve per node mode. (sei-protocol/sei-chain#3977)
seidroid Bot added 6 commits November 13, 2026 18:23
…eeper, ante decorator, begin-blocker, metrics, and CosmWasm IBC entry points are removed, and queries to retired IBC stores now return an 'ibc module is deprecated' error. (sei-protocol/sei-chain#4014)
…N-RPC requests to live or frozen-height nodes, with new CLI flags and build targets, and introduces a seid start --freeze-height flag. (sei-protocol/sei-chain#3989)
…for both linux/amd64 and linux/arm64, so Sei users can download a prebuilt arm64 binary in addition to amd64. (sei-protocol/sei-chain#4047)
…nd now returns an error, removing the ability to batch-execute multiple CosmWasm contract calls via the EVM precompile. (sei-protocol/sei-chain#4074)
… including removal of legacy sei_* and sei2_* JSON-RPC APIs, eth_getProof removal, origin-aware ABCI pagination caps with new config fields, EVM RPC admission/rate-limiting config, new precompile authorization features, a freeze mode for historical EVM RPC, and new CLI commands for address association. (sei-protocol/sei-chain#4113)
…e-readable output (narration redirected to stderr), extends --inspect-bucket to support the composite backend and the replay open mode, and documents SEI_LOG_OUTPUT=stderr for clean JSON reports. (sei-protocol/sei-chain#4255)
seidroid Bot added 2 commits November 13, 2026 18:33
…as-meter) panic into a reverted/failed EVM call frame with vm.ErrOutOfGas and zero remaining gas, instead of propagating the panic and failing the entire transaction at the Cosmos layer. (sei-protocol/sei-chain#4334)
seidroid Bot added 2 commits November 13, 2026 18:35
…state migration rate (NumKeysToMigratePerBlock) to zero at a target height, which node operators should be aware of during upgrades. (sei-protocol/sei-chain#4409)
…V repair files from evm-logical-digest reports, a new embedded kvrepair hard-fork mechanism that applies reviewed key/value fixes at a target height, and new flags/guidance (`--key-offset`) for the evm-logical-digest inspect workflow. (sei-protocol/sei-chain#4410)
…miavl open mode and a new `--inspect-plan` flag for taking multiple inspect reports from one scan. (sei-protocol/sei-chain#4439)

This branch was successfully deployed

1 active deployment
staging — 31c25150 Deployed Nov 14, 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