Repository navigation
docs: v6.7.0 catch-up - #105
Draft
seidroid[bot] wants to merge 30 commits into
Draft
seidroid[bot] wants to merge 30 commits into
seidroid[bot] wants to merge 30 commits into
Conversation
…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)
…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)
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
…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)
… 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)
…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)
…on capability, plus internal changelog/migration fixes. (sei-protocol/sei-chain#4294)
…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)
…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
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.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.
evm/precompiles/authz.mdx,evm/precompiles/governance.mdxnode/technical-reference.mdxevmonly-loadtestfor feeding synthetic transfer/ERC20/snapshot-revert blocks to the EVM-only executor, with a large set of tunable flags and Prometheus metrics.node/technical-reference.mdxnode/swagger.mdxnode/technical-reference.mdx,node/troubleshooting.mdxevm/reference.mdxevm/reference.mdxevm/precompiles/distribution.mdx,evm/precompiles/governance.mdx,evm/precompiles/staking.mdxnode/technical-reference.mdxevm/reference.mdx,evm/tracing/troubleshooting.mdxdocs.json,evm/precompiles/distribution.mdx,evm/precompiles/example-usage.mdx,evm/precompiles/feegrant.mdx,evm/precompiles/governance.mdxevm/precompiles/governance.mdx,evm/precompiles/staking.mdx,node/validators.mdxevm/precompiles/oracle.mdxevm/precompiles/example-usage.mdx,evm/precompiles/feegrant.mdxnode/troubleshooting.mdxnode/frozen-nodes.mdx,node/swagger.mdxnode/frozen-nodes.mdx,node/swagger.mdx,node/technical-reference.mdxcosmos-sdk/index.mdx,node/technical-reference.mdxnode/node-operators.mdx,node/technical-reference.mdxcosmos-sdk/index.mdx,evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx,node/technical-reference.mdxnode/technical-reference.mdxevm/installing-seid-cli.mdx,node/index.mdxevm/precompiles/cosmwasm-precompiles/cosmwasm.mdx,evm/precompiles/example-usage.mdxevm/precompiles/cosmwasm-precompiles/cosmwasm.mdxnode/technical-reference.mdxnode/technical-reference.mdxevm/evm-parity/gas-and-fees.mdx,evm/precompiles/p256-precompile.mdxnode/giga-storage-migration.mdxnode/giga-storage-migration.mdx,node/technical-reference.mdxseidb kvrepair-exportCLI 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.node/giga-storage-migration.mdx,node/technical-reference.mdxchangelogmemiavl open mode and a new--inspect-planflag 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.0checkout 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 namedsei-chain_${VERSION#v}_linux_aarch64.tar.gzx86_64only for amd64 and falls back to{{ .Arch }}for all other arches, which for arm64 renders the literalarm64. There is noreplacementsmapping in the archives config (no match for 'replacements' in .goreleaser.yaml). The actual arm64 asset is thereforesei-chain_<version>_linux_arm64.tar.gz, not..._linux_aarch64.tar.gz. (The amd64x86_64filename at line 54 is correct.)evm/tracing/troubleshooting.mdx(Section 'Node configuration for better performance' TOML block) — TOML sample under[evm]usestrace-timeout = "300s"to configure the trace timeout.trace_timeout(underscore), rendered astrace_timeout = "{{ .EVM.TraceTimeout }}"in evmrpc/config/config.go:904 and declaredmapstructure:"trace_timeout"at evmrpc/config/config.go:186. No hyphenatedtrace-timeoutkey exists (grep 'trace-timeout' -> NO MATCHES). An operator copyingtrace-timeoutwould not set the timeout.evm/tracing/troubleshooting.mdx(Section 'Node configuration for better performance' TOML block) — TOML sample under[evm]usestrace-memory-limit = "1GB".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]usestrace-cache-size = 1000to enable trace caching.node/frozen-nodes.mdx(How freeze mode works — new v6.7 paragraph) — Raw ABCI store queries against the retired IBC-related stores now return anErrIBCDeprecatederror.ErrIBCDeprecatedexists in the tree (grep forErrIBCDeprecated|IBCDeprecatedreturns no matches). The raw ABCI store query deprecation error isapp/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 isErrIBCPrecompileRetiredat 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') — Apause-state-migrationhard 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.node/index.mdx(Install Sei > Prebuilt binary (recommended) tab, callout (changed region)) — The prebuilt arm64 release asset is named withlinux_aarch64("pick the asset matching your architecture (linux_x86_64for amd64,linux_aarch64for arm64)").{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_thenx86_64for amd64 else{{ .Arch }}; for the arm64 build (goarcharm64, .goreleaser.yaml:45-47).Archisarm64, so the asset issei-chain_<version>_linux_arm64.tar.gz, notlinux_aarch64. There is noreplacementsmap and noaarch64anywhere in .goreleaser.yaml (grep: NO MATCHES), and no renaming in .github/workflows (grep x86_64 in workflows: NO MATCHES).aarch64appears 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 turnsnode/troubleshooting.mdx(## BlockDB refuses to open on a pre-rename table) — On startup the block DB now refuses to open if a pre-renameledgertable directory is still present under any of its root paths, and the node fails to start with an errorblock 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.ledgerdirectory 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 legacyledgerdirectory the block DB opens fresh under theblocksname.Reviewer notes
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.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
expirationvalidation:grantWithdrawAuthorizationsays "Theexpirationmust 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.mdxvscosmwasm.mdxonexecute_batch: The example-usage table now saysexecute_batch()"is disabled and reverts withwasmd execute_batch is disabled." The cosmwasm.mdx page's ownHow does the CosmWasm precompile work?section andFunctionslists still describeexecute_batch()as an available/working function ("exposes functions such asexecute(),execute_batch(), andquery()" 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_windowvs retired oracle: The technical-reference network parameters now list an Oraclemin_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
feegrantamong 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-metricsvsss-enable-read-write-metrics: In app.toml the state-store key isss-enable-read-write-metricsand the receipt-store key isenable-read-write-metrics; these are distinct keys, not inconsistent spellings. No issue.Reporting the confirmed findings:
cosmwasm.mdx: the Danger banner and theexecute_batch()reference/Query functionsstate 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 describeexecute_batch()as a working/available function for efficient batch operations.feegrant.mdxsays the feegrant EVM precompile "has been removed," "is not available at any address," and is "no longer callable," buttechnical-reference.mdxlistsfeegrantamong 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.