skills: v6.6.0 catch-up - #16
Conversation
… always returns a JSON-RPC error (code -32000, 'blobs not supported on this chain') since Sei does not support EIP-4844 blob transactions. (sei-protocol/sei-chain#3080)
…sactionFilter, debug_getRawBlock/Header/Receipts/Transaction, eth_blobBaseFee) are now explicitly registered but return JSON-RPC error -32000 with a clear message instead of -32601 method not found. (sei-protocol/sei-chain#3086)
…gates deprecated sei_* and sei2_* JSON-RPC methods, deprecates those namespaces, and returns JSON-RPC errors plus a deprecation HTTP header for gated calls. (sei-protocol/sei-chain#3109)
…e-commit (SC) is now mandatory; multiple CLI commands and config fields tied to IAVL/pruning have been removed, and the node will panic if SC is not enabled. (sei-protocol/sei-chain#3146)
…r` flag to the `state-size` command for analyzing FlatKV stores. (sei-protocol/sei-chain#3312)
…torage keys, rejects malformed keys, and enforces a maximum of 1024 storage keys per request. (sei-protocol/sei-chain#3556)
…) now supports pagination via standard pagination flags and request/response fields. (sei-protocol/sei-chain#3524)
… and sei_traceBlockByHashExcludeTraceFail have been removed from the EVM RPC server and legacy sei API allowlist. (sei-protocol/sei-chain#3618)
… backend-independent digest of EVM logical state (account/code/storage) so memiavl and flatkv nodes can be compared at the same height. (sei-protocol/sei-chain#3611)
Cross-checked against sei-chain v6.6.0. Fixes the 2 major and 5 minor findings: - --page-key takes the raw key at the CLI (vendored ReadPageRequest never base64-decodes); base64 next_key advice scoped to REST/gRPC only - move the four unsupported/deprecated/removed JSON-RPC sections out of 'What Works Unchanged' into their own section - move the seidb Tool section out of the middle of the curl/JSON-RPC section - note sei_getBlockBy*ExcludeTraceFail also survive the #3618 removal - evm.enabled_legacy_sei_apis is a viper/AppOptions key, not a CLI flag - paginated-by-default caveat on the denoms-from-creator example
| - `sei2_getBlockTransactionCountByHash` | ||
| - `sei2_getBlockTransactionCountByNumber` | ||
|
|
||
| ## What Works Unchanged |
There was a problem hiding this comment.
These four sections all describe what doesn't work, but they rendered directly under "## What Works Unchanged", and that section's own bullets ended up dangling after the last subsection. I've moved them into their own H2 in c767aa1.
| | `--limit` | Max number of denoms per page | | ||
| | `--offset` | Number of denoms to skip | | ||
| | `--page` | Page number (1-based; combines with `--limit`) | | ||
| | `--page-key` | Raw next key for key-based paging — not the base64 `pagination.next_key` (see below) | |
There was a problem hiding this comment.
The CLI never base64-decodes --page-key. The vendored ReadPageRequest uses the raw flag bytes (sei-cosmos/client/utils.go:49-72, upstream's FlagSetWithPageKeyDecoded was never ported), so feeding pagination.next_key back in queries a garbage key. The REST pagination.key is base64 (grpc-gateway decodes it) so the REST paragraph stands. Fixed in c767aa1.
|
Cross-checked this one against sei-chain v6.6.0 as well. The eth_getProof limits and error strings, the trace endpoint removal semantics (the fail-closed allowlist means "adding them back has no effect" is exactly right), and the gRPC/REST pagination fields all verified exact, so the bulk of this PR is solid. I've fixed the 2 major and 5 minor findings on the branch in c767aa1, the only behavioural one was the |
2 participants
Skill catch-up for v6.6.0.
3 source PR(s) produced changes. Each is a separate commit, so this reviews commit-by-commit.
skill/references/cli/seid-cli.md,skill/references/evm/overview.mdskill/references/pointers/token-factory.mdskill/references/ecosystem/rpc-providers.md,skill/references/ecosystem/node-operations.md,skill/references/cli/seid-cli.md,skill/references/evm/overview.mdReviewer notes
denoms-from-creatorquery (CLI, gRPC, REST). No existing skill file documents this query command at all — token-factory.md covers create/mint/burn/admin operations but omits query commands. Rather than a targetedupdate, anadd_sectionis appropriate to introduce the query along with its new pagination flags. The wasm binding behavior (unbounded GetAllDenomsFromCreator) is an internal implementation detail not exposed via CLI/user-facing tooling, so it does not require skill documentation. No seid CLI reference (seid-cli.md) change is needed since that file focuses on EVM/tokenfactory tx commands, not tokenfactory queries.sei_*(sei namespace) trace endpoints and their allowlist entries; the parallelsei2_getBlockBy{Hash,Number}ExcludeTraceFailblock variants remain and are still listed in DefaultConfig/config templates. Skill files that describe thesei_*deprecated surface generally reference 'traces' or 'filters, logs' collectively rather than naming these two endpoints, so most edits are minor clarifications. There is no dedicated skill file per JSON-RPC method, so nocreateaction is warranted. The two removed endpoints were never explicitly named in the skill files, which reduces the severity of the gap — reviewers may consider some of these updates optional given the endpoints were never individually documented.Flagged by a review of the assembled diff. 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 diff for the three specified issue types:
eth_blobBaseFeeerror message inconsistency: Inevm/overview.mdthe table (Blob opcodes row) and the "Explicitly Unsupported" table give the message as"blobs not supported on this chain", butrpc-providers.mdstates the same message. These agree — however, the message wording is consistent across files, so no contradiction there. (No issue.)denoms-from-creatorpagination — removed vs. configurable: The section says the query "now paginates by default" and adds full pagination flags (configurable), but the trailing HTML comment states "the CosmWasm/wasm binding path returns ALL denoms for a creator unbounded." These describe different paths (gRPC/REST vs wasm), so not a direct contradiction — but note the top of the section says "Previously it returned all denoms for a creator unbounded" as a blanket statement while the wasm path still does. This is a borderline self-contradiction on whether the unbounded behavior was fully replaced.Docker localnet allowlist vs.
sei_signgating:node-operations.mdsays Docker localnet "enables every gated method exceptsei_sign." Consistent internally. (No issue.)Removed endpoints described as still in allowlist: All hunks consistently state
sei_traceBlockByNumberExcludeTraceFail/sei_traceBlockByHashExcludeTraceFailare removed and dropped from the allowlist. No "removed but configurable" contradiction — the docs explicitly say adding them "has no effect." (No issue.)GASLIMIT/ block gas limit value inconsistency: Inevm/overview.mdthe opcode table listsGASLIMIT= 12,500,000 (Sei). Butnode-operations.md's surrounding note references "block gas limit" as governance-adjustable without a conflicting number. No hard second value given in this diff — not a contradiction within the diff.NONE
Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.