docs: v6.6.0 catch-up - #61
Conversation
…ionCountByHash now recognize the genesis block hash and return the genesis block (and a tx count of 0), keeping hash-based lookups consistent with eth_getBlockByNumber("0x0"). (sei-protocol/sei-chain#3069)
…ull (instead of an error) for empty or non-existent block hashes, matching Ethereum RPC spec. (sei-protocol/sei-chain#3067)
…the config field 'max-outbound-connections' changed type/behavior and its default logic, and the RouterOptions MaxPeers/MaxConnected/MaxConcurrentDials fields were replaced by MaxInbound/MaxOutbound, affecting node connection tuning. (sei-protocol/sei-chain#3037)
… checks on signature values, access lists, auth lists, and Cosmos wrapper fields, plus a new transaction body bloat rejection that may reject previously-accepted transactions. (sei-protocol/sei-chain#3073)
…des a pub_key field (with a zero/empty public key for non-validator nodes) for CosmJS compatibility, changing the status response output. (sei-protocol/sei-chain#3114)
…tBlockByNumber returns null (not an error) for future/non-existent numeric block heights, and eth_getProof works across additional store backends (tracekv, Giga cache, other proof-capable stores) instead of only classic IAVL. (sei-protocol/sei-chain#3119)
…ctionCountByHash RPC methods now return counts consistent with getBlockByNumber, filtering EVM txs by receipt availability and including wasm execute and bank send messages. (sei-protocol/sei-chain#3125)
…sc-enable-lattice-hash) were removed from the node config TOML template, and split_write mode now requires lattice hash to be enabled. (sei-protocol/sei-chain#3128)
… from 5% to 0% because the Oracle Price Feeder is retired. (sei-protocol/sei-chain#3157)
…arnings urging users to migrate to SeiDB to avoid data corruption or panic. (sei-protocol/sei-chain#3159)
…h requests by forwarding only the allowed subset and merging responses by id, and the HTTP request body limit was lowered from 32MiB to 5MiB to match go-ethereum's default. (sei-protocol/sei-chain#3160)
…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)
… generate an Autobahn (GigaRouter) JSON config from node pubkey files, plus new side-effect files (validator_pubkey.txt, node_pubkey.txt) written when saving keys. (sei-protocol/sei-chain#3220)
…receipt store retention is now always derived from the global `min-retain-blocks` flag. (sei-protocol/sei-chain#3237)
…the node now disables the mempool gossip reactor, consensus reactor, state sync, and block sync, and the Autobahn block producer sources transactions directly from the mempool with new per-block limits (max 2000 txs, ~2MB total). (sei-protocol/sei-chain#3224)
…C 2.0 notification rules: notifications (requests without an id) produce no response entries, so merged batch responses are no longer 1:1 with the request, and an all-notification/empty result returns an empty HTTP body instead of an empty array []. (sei-protocol/sei-chain#3246)
…array [] instead of null when there are no matching logs, aligning with the Ethereum JSON-RPC spec. (sei-protocol/sei-chain#3292)
…ubdirectory layout (data/state_commit, data/state_store, data/ledger, data/tendermint) for new nodes, with automatic backward-compatible fallback to legacy flat paths for existing nodes. (sei-protocol/sei-chain#3155)
…ed, receipt-by-tx-hash lookups that miss the cache now fail fast with an error instead of falling back to a full parquet scan, affecting operators who run nodes with the tx index disabled. (sei-protocol/sei-chain#3294)
…quet (previously unchanged), though callers can still override with an explicit RECEIPT_BACKEND env var. (sei-protocol/sei-chain#3298)
…eturns trace results with detailed timing/store-access profiling, plus a new seidb trace-profile-report CLI command to run it across a block range. (sei-protocol/sei-chain#3267)
…ck_height` field in SyncInfo, and under Autobahn the status endpoint populates height/app-hash from the app layer instead of the CometBFT block store. (sei-protocol/sei-chain#3309)
…l are now treated as normal requests (receiving a response) instead of as notifications; only requests omitting the "id" member are treated as notifications. (sei-protocol/sei-chain#3303)
…ded to sei-tendermint as a temporary disaster-recovery mechanism for chain stalls, requiring validator majority coordination to enable. (sei-protocol/sei-chain#3305)
…ults to true, and the coordination semantics are inverted so validators must coordinate to set it to false. (sei-protocol/sei-chain#3318)
… flag to the `state-size` command for analyzing FlatKV stores. (sei-protocol/sei-chain#3312)
…eprecated and ignored; stateless leader election is always enabled regardless of the value set. (sei-protocol/sei-chain#3319)
…with one extra element (the projected child base fee for the block after the newest block), matching go-ethereum/execution-apis semantics. (sei-protocol/sei-chain#3321)
…/block_by_hash, /block_results, and /validators now serve data via the GigaRouter's in-memory state instead of returning empty/failing responses when the CometBFT BlockStore/StateStore is unpopulated. (sei-protocol/sei-chain#3310)
…aRouter block execution path to prevent valid out-of-order EVM nonce transactions from being evicted and stalling throughput to one tx per block per sender. (sei-protocol/sei-chain#3372)
…nt committee and introduced wireguard size/count limits on consensus protobuf messages, changing acceptance/rejection behavior for oversized network payloads. (sei-protocol/sei-chain#3609)
…ed that gates whether the Unsafe*TimeoutOverride fields take effect, changing how timeout overrides behave on nodes. (sei-protocol/sei-chain#3601)
…nd sei_traceBlockByHashExcludeTraceFail have been removed from the EVM RPC server and legacy sei API allowlist. (sei-protocol/sei-chain#3618)
…ackend-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)
…iles, and the oracle precompile is now retired so its on-chain queries (getExchangeRates, getOracleTwaps) revert with an error. (sei-protocol/sei-chain#3625)
mint broken-links failed: Syntax error - Unable to parse evm/precompiles/distribution.mdx - 167:1-167:364: Expected a closing tag for `<Warning>` (167:1-167:10) before the end of `paragraph` The callout opened inline on 167, a blank line on 168 ended the MDX paragraph, and the closing tag sat on 169 — so the element was never closed within its paragraph. Tag counts balanced 3:3, which is why nothing caught it before the Mintlify parser. Restructured to put the tags on their own lines, the multi-paragraph form MDX accepts and the form already used by the other multi-paragraph Warning in this same file.
Every claim in this catch-up was cross-checked against sei-chain at the v6.6.0 tag (656 claims). This commit fixes the 15 major and 26 minor findings plus adjacent stale text found during verification. Highlights: - restore sc-write-mode / sc-keys-to-migrate-per-block to the app.toml template (still shipped at v6.6.0; #3473 re-added what #3128 removed) - drop references to sei_traceBlockBy*ExcludeTraceFail (removed by #3618) - correct failed-receipt gasUsed claim (v2 fallback writes gasUsed 0 per #3768/#3781, superseding #3383) - FlatKV db label values are account/code/storage/legacy, not *DB - ttl-duration/ttl-num-blocks moved to config.toml sample with real defaults (5s/10) - oracle precompile retirement re-dated to v6.4.0 - distribution setWithdrawAddress example un-inverted - remove nonexistent config keys (sc-read-mode, sc-enable-lattice-hash, evm-ss-write-mode/read-mode, cosmos_only default, mock_balances-* tag) - restore FAQ answer displaced by the FlatKV SC migration section
| `metadata`). Routing is controlled by `sc-write-mode` / `sc-read-mode` | ||
| and defaults to memiavl-only — FlatKV is only opened when one of those | ||
| modes is set to a non-default value. | ||
| `metadata`). Routing is controlled by `sc-write-mode` and defaults to |
There was a problem hiding this comment.
The new text at the top of the page is right, but this older paragraph contradicted it. sc-enable = false panics at startup (app/seidb.go:66-68) so IAVL isn't selectable anymore. Reworded in 46de0dc.
| sc-enable-lattice-hash = false | ||
| # Default: memiavl_only — all EVM state lives in memiavl. Valid values: | ||
| # memiavl_only, migrate_evm, evm_migrated, migrate_all_but_bank, | ||
| # all_migrated_but_bank, migrate_bank, flatkv_only, test_only_dual_write. |
There was a problem hiding this comment.
cosmos_only is just a legacy alias for memiavl_only, which is the actual default (sei-db/config/sc_config.go:63), and sc-read-mode / sc-enable-lattice-hash don't exist as config keys anywhere at v6.6.0. I've replaced this block with the real knobs in 46de0dc.
| # A non-zero value defines the time / number of blocks after which a transaction | ||
| # is removed from the mempool; leaving them unset or set to zero disables TTL-based | ||
| # purging entirely. | ||
| ttl-duration = "5s" |
There was a problem hiding this comment.
ttl-duration and ttl-num-blocks are config.toml keys (sei-tendermint/config/toml.go:378,386), app.toml has no [mempool] section. The shipped defaults are also 5s/10 rather than zero, and since zero now means disabled, anyone copying this sample would switch off TTL purging without realising. Moved and corrected in 46de0dc.
|
|
||
| - Caller reads of not-yet-migrated keys fall back to FlatKV for brand-new keys | ||
| written after the migration started, and to memiavl otherwise. | ||
| - Iteration is served by a merging iterator over both backends (memiavl |
There was a problem hiding this comment.
This behaviour was superseded before the tag was cut. At v6.6.0 iteration merges both backends (CompositeCommitStore.iterate, sei-db/state_db/sc/composite/store.go:859-930) so range scans see the complete key set during a migration. Fixed in 46de0dc.
|
|
||
| ## FAQ | ||
|
|
||
| ### Where do the data files live after migrating? |
There was a problem hiding this comment.
This section landed between the FAQ question "Where do the data files live after migrating?" and its answer bullets, which left "SC data is untouched by this migration" rendering inside the SC migration section where it's wrong. I've moved it in 46de0dc.
| <Warning> | ||
| Sei's continuous integration (CI) pipelines publish testing-only image variants to an internal registry — they are not available on `ghcr.io`. These must **never** be used in production and are compiled with special Go build tags: | ||
|
|
||
| - `mock-*` — built with the `mock_balances` build tag; mocks account balances. |
There was a problem hiding this comment.
No image with this prefix exists. ecr.yml tags the mock_balances build as mock-* (nightly mock-nightly-*), and these publish to the internal ECR rather than ghcr.io. Fixed in 46de0dc.
|
|
||
| | Label | Description | | ||
| | --- | --- | | ||
| | `db` | The data DB the measurement applies to (for example, `account`, `storage`, `code`, or `legacy`). Present on per-DB metrics such as `flatkv_commit_batch_latency`, `flatkv_flush_latency`, `flatkv_num_kv_pairs`, `flatkv_pending_writes`, `flatkv_import_kv_pairs`, and `flatkv_import_worker_flush_latency`. | |
There was a problem hiding this comment.
The label values are the directory constants account/code/storage/legacy (flatkv/store.go:43-46). The *DB spellings only exist in error message strings, so PromQL written from this table would match zero series. Fixed in 46de0dc.
| **Supported.** Returns the number of EVM transactions in a block by number, as a hex quantity. | ||
|
|
||
| **Sei-specific behavior:** Counts EVM transactions only (via getEvmTxCount); synthetic/bank-transfer txs are excluded. Genesis returns 0x0; non-existent/future blocks return null. | ||
| **Sei-specific behavior:** Counts the same transactions that appear in `eth_getBlockByNumber`'s transaction list: EVM transactions are counted only when a receipt exists for them, and synthetic (wasm `MsgExecuteContract`) and bank-transfer (`MsgSend`) txs remain excluded under the eth namespace — they are only included in the `sei_`/`sei2_` count variants. Genesis returns 0x0; non-existent/future blocks return null. Because the receipt store can be configured with a smaller `KeepRecent` than the block/state stores, this method now verifies that the requested block's receipts have not been pruned before counting: if they have, it returns an error of the form `requested height N receipts have been pruned; earliest available is M` rather than a count. This means the call can fail for older blocks even when the block data itself is still available. |
There was a problem hiding this comment.
This was backwards for the eth_ namespace. NewBlockAPI sets includeShellReceipts=false, includeBankTransfers=false (evmrpc/block.go:94-95) so MsgExecuteContract and MsgSend are excluded, only the sei_/sei2_ variants count them. Fixed in 46de0dc.
| | `sei_getTransactionByHash` | Get transaction by hash (includes synthetic txs) | | ||
| | `sei_getTransactionCount` | Get account transaction count | | ||
| | `sei_getTransactionReceipt` | Get transaction receipt (includes synthetic txs) | | ||
| | `sei_getTransactionReceiptExcludeTraceFail` | Get transaction receipt, excluding only txs that never executed. Ante-rejected txs (rejected before reaching the VM, identified by `EffectiveGasPrice == 0` and `GasUsed == 0`) and chain-generated synthetic txs (`ShellEVMTxType`) are filtered out; reverted and out-of-gas transactions are now included, because they ran in the VM and produce real traces. (Previously any receipt with `status=0` was excluded, which over-filtered reverts and OOG failures.) The former `sei_traceBlockByHashExcludeTraceFail`/`sei_traceBlockByNumberExcludeTraceFail` trace endpoints were removed in v6.6.0 (#3618); use the standard `debug_traceBlockByHash`/`debug_traceBlockByNumber` instead. | |
There was a problem hiding this comment.
These endpoints don't exist at v6.6.0, #3618 (also in this PR) removed them and there are zero grep hits in evmrpc/ at the tag. Replaced with a removal note here and in the method table below in 46de0dc.
|
|
||
| Everything that ran in the VM is **included**, even if it failed. Reverted and out-of-gas (OOG) transactions have `Status == 0` but `GasUsed > 0` (intrinsic gas at minimum) and, on chains with a positive minimum gas price, `EffectiveGasPrice > 0`, and produce a real trace (the `REVERT` or OOG condition simply appears inside that trace), so they are returned rather than filtered out. | ||
|
|
||
| <Info>This filter applies to the block endpoints (`sei_getBlockByNumberExcludeTraceFail` and `sei_getBlockByHashExcludeTraceFail`, plus their `sei2_` equivalents) and the receipt endpoint (`sei_getTransactionReceiptExcludeTraceFail`): all of them drop these ante-deferred stub transactions. The former `sei_traceBlockByNumberExcludeTraceFail` and `sei_traceBlockByHashExcludeTraceFail` endpoints were removed in v6.6.0 — use `debug_traceBlockByNumber` or `debug_traceBlockByHash` for block tracing. The regular `eth_getBlockBy*` endpoints continue to **include** them, so a tx that appears in a normal block response may be absent from the `*ExcludeTraceFail` variant. The filter checks the underlying receipt shape (`EffectiveGasPrice` and `GasUsed`) rather than any tracer-reported error field.</Info> |
There was a problem hiding this comment.
Same stale replay issue as the reference page, this block was generated from #3450/#3459 and named the two trace endpoints that #3618 removed. The survivors at v6.6.0 are the sei_/sei2_ block variants and sei_getTransactionReceiptExcludeTraceFail. Fixed in 46de0dc.
|
|
||
| Some EVM transactions pass basic validation and bump the sender's nonce, yet still fail during state transition — for example, a transaction whose gas limit clears the intrinsic-gas check but falls short of the EIP-7623 floor-data-gas requirement (which can occur in normal operation after Pectra). Because these transactions bump the nonce, they are considered to have happened and therefore produce a receipt. | ||
|
|
||
| For such failures, Sei writes a synthetic `status=0` (failed) receipt at the end of the block. The receipt reports a `gasUsed` of 0 and an `effectiveGasPrice` of 0, and carries a `VmError` describing the state-transition reason. `eth_getTransactionReceipt` returns this failed-tx receipt instead of `null`. The `VmError` is stored on Sei's internal receipt record and is not included in the `eth_getTransactionReceipt` JSON response; retrieve it with the non-standard `eth_getVMError` method. |
There was a problem hiding this comment.
The gasUsed equal to gas limit behaviour never shipped. #3768 (backported as #3781, which is in v6.6.0) reroutes giga execution errors to the v2 fallback, and its EndBlock synthetic receipt has gasUsed 0 (x/evm/keeper/abci.go:124-134). The status 0 instead of null part is still correct. Fixed in both this file and reference.mdx in 46de0dc.
| **Address:** `0x0000000000000000000000000000000000001008` | ||
|
|
||
| <Danger>**Deprecation Notice:** The native Sei Oracle is deprecated and will be shut off soon. We strongly recommend migrating to one of the third-party oracle providers, such as [Chainlink](/evm/oracles/chainlink), [Pyth](/evm/oracles/pyth-network), [Redstone](/evm/oracles/redstone), or [API3](/evm/oracles/api3).</Danger> | ||
| <Danger>**Retired as of v6.4.0:** The native Sei Oracle precompile has been retired. On-chain oracle data queries are disabled — calling `getExchangeRates` or `getOracleTwaps` now reverts with the error `oracle precompile is retired; oracle data queries are disabled`. You must migrate to one of the third-party oracle providers, such as [Chainlink](/evm/oracles/chainlink), [Pyth](/evm/oracles/pyth-network), [Redstone](/evm/oracles/redstone), or [API3](/evm/oracles/api3).</Danger> |
There was a problem hiding this comment.
The retirement actually shipped in v6.4.0 (git tag --contains on the #3015 commit), #3625 only regenerated the legacy snapshots. I've re-dated the banner and updated the frontmatter, which was still promising real-time exchange rates, in 46de0dc.
| ``` | ||
|
|
||
| <Warning> | ||
| **Recipient Validation**: The withdrawal address must be able to receive external funds. Through the precompile, an unassociated EVM address is rejected with the error `cannot use an unassociated address as withdraw address`. Separately, the bank module rejects addresses it blocks from receiving external funds with `ErrInvalidRecipient` — for example, the cast address of an EVM account that has since been associated with a different Sei address. Ensure the withdrawal address is associated and permitted to receive funds before setting it. |
There was a problem hiding this comment.
This example was inverted. CanAddressReceive returns true for unassociated cast addresses (x/evm/keeper/address.go:81-87), and via the precompile an unassociated withdraw address is rejected earlier with cannot use an unassociated address as withdraw address. ErrInvalidRecipient is the bank blocked case. Rewritten in 46de0dc.
|
I've done a full review of this catch-up against sei-chain at the v6.6.0 tag, 656 claims checked in total. That surfaced 15 major and 26 minor findings, and I've fixed them all directly on the branch in 46de0dc rather than leaving a to-do list, so each inline comment documents what changed and why. One fix you won't see in the final diff: the bot's commit deleted Three of the majors share one root cause worth a bridge guard: commits generated per source PR were never reconciled against later PRs in the same release. #3473 re-added the config fields #3128 removed, #3618 removed endpoints that the #3450/#3459 text still describes, and #3768/#3781 superseded #3383's receipt behaviour before the tag was cut. A final pass that re-validates each assembled page against the release tag (rather than per PR diffs) would catch this whole class. Two more pipeline notes: the PR table lists 30 source PRs but the diff actually carries content from around 35 (the early commit backlog plus #3611 and #3625 are invisible to anyone reviewing from the table), and several hand-written comments landed inside AUTO-GENERATED blocks where the next regen will clobber them. Also a heads-up for the next catch-up, these were correct at v6.6.0 but have already changed on main: littidx receipt backend (#3620), gov-driven SC migration replacing manual sc-write-mode (#3650), the legacy to misc bucket rename (#3665/#3758), a third ExcludeTraceFail exclusion class (#3871), and JS tracers disabled (#3718). Happy to share the full finding-by-finding report if useful, just let me know! |
monty-sei
left a comment
monty-sei
left a comment
There was a problem hiding this comment.
Approving. Full review against sei-chain v6.6.0 is in the comments above, all findings fixed in 46de0dc and each fix re-verified against source. The drift items called out in my summary are for the next catch-up, not this PR.
2 participants
Documentation catch-up for v6.6.0.
30 source PR(s) produced changes. Each is a separate commit, so this reviews commit-by-commit.
node/advanced-config-monitoring.mdxnode/advanced-config-monitoring.mdx,node/node-operators.mdxevm/reference.mdx,evm/transactions.mdxnode/index.mdxmock_block_validationGo build tag that bypasses AppHash and DataHash block validation, producing a separateseidDocker image taggedmock_block_validation-*for testing environments.node/node-operators.mdx,evm/tracing/index.mdxnode/troubleshooting.mdxseidb import-flatkv-from-memiavlCLI command (plusmemiavl-latest-version) and a newdump-flatkv --bucketoption for migrating/importing EVM state from memiavl into FlatKV, along with the KVImporter Abort/Err lifecycle used by that tool.node/technical-reference.mdx,node/node-operators.mdxevm/reference.mdx,evm/tracing/index.mdxevm/tracing/index.mdx,evm/reference.mdxnode/technical-reference.mdx,node/advanced-config-monitoring.mdxevm/precompiles/distribution.mdxnode/technical-reference.mdxnode/advanced-config-monitoring.mdxevm/differences-with-ethereum.mdxevm/reference.mdxnode/node-operators.mdx,node/technical-reference.mdxnode/node-operators.mdx,node/technical-reference.mdx,node/giga-storage-migration.mdxmigrate-evm-statusCLI subcommand, a newsc-keys-to-migrate-per-blockapp.toml config field, aGIGA_MIGRATE_FROM_MEMIAVLcluster env var, and a-modeflag to the evm_stress tool, all supporting the FlatKV EVM migration flow.evm/reference.mdx,node/advanced-config-monitoring.mdxevm/reference.mdxnode/technical-reference.mdx,node/technical-reference.mdx,evm/reference.mdxnode/index.mdxnode/giga-storage-migration.mdxflatkv_onlyvalue of thesc-write-modeconfig field, enabling nodes to boot directly in the post-migration FlatKV-only steady state with correct state-sync and snapshot behavior.node/node-operators.mdx,node/technical-reference.mdx,node/index.mdxnode/advanced-config-monitoring.mdxnode/node-operators.mdx,node/giga-storage-migration.mdxevm/reference.mdxnode/advanced-config-monitoring.mdxnode/technical-reference.mdxnode/node-operators.mdxunsafe-overrides-enabledwas added that gates whether the Unsafe*TimeoutOverride fields take effect, changing how timeout overrides behave on nodes.evm/tracing/index.mdx,node/node-operators.mdxReviewer notes
GIGA_MIGRATE_FROM_MEMIAVLand the evm_stress-modeflag are test/CI-only tooling not covered in operator docs, so no doc gap is flagged for them beyond the migration-flow context. (2) The new seidb_migration_* metrics could warrant an entry in node/advanced-config-monitoring.mdx if operators are expected to scrape them, but the diff does not indicate these are operator-facing production metrics (migration is a one-time flow), so I did not flag that page — reviewer may reconsider if migration metrics should be documented alongside FlatKV/LittDB metrics. (3) The FlatKV EVM SC migration is a distinct concept from the SS-store migration in giga-storage-migration.mdx; a reviewer may prefer a new dedicated page rather than extending that guide, but no existing page cleanly covers the SC-side FlatKV EVM migration so add_section on the closest page is the conservative call.max_trace_lookback_blocksconfig field (documented in node/advanced-config-monitoring app.toml asmax_trace_lookback_blocks, default 10000, -1 for unlimited). The behavior change is that this guard now applies to all debug_trace* endpoints, not just debug_traceBlockByNumber — worth clarifying in the reference. The evm/tracing/index.mdx overview page lists all trace methods but describes cache behavior, not lookback limits, so it likely does not need an update, though a reviewer may consider adding a note there about historical block rejection.unsafe-overrides-enabledfield and updated override comments will likely appear once regenerated — but the surrounding prose/descriptions of override behavior still need a manual correction. The config.toml content was truncated in the supplied page right at the[consensus]Unsafe Timeout Overrides section, so verify the exact insertion point. node/technical-reference.mdx also shows a partial[consensus]config.toml block but its unsafe-override fields were truncated; if that block lists the override fields it may also need the new field/behavior note. Migration note for reviewers: nodes relying on Unsafe*TimeoutOverride will silently stop applying overrides after upgrade unless they setunsafe-overrides-enabled = true(or onchain params still equal the legacy pacific-1 badParams) — this backward-compat/migration nuance should be called out to operators.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 categories of issues:
sc-keys-to-migrate-per-blockdefault contradiction: Ingiga-storage-migration.mdxit states the default is1024and "must be> 0", but innode-operators.mdxthe entiresc-write-mode/sc-keys-to-migrate-per-blockconfig block is removed from the template. This makes the setting described as both removed (from the app.toml template) and configurable (documented knob in the migration flow). (Category 3)sc-write-moderemoved vs. configurable:node-operators.mdxdeletes thesc-write-modefield (with its valid values) from the app.toml template, whilegiga-storage-migration.mdxdocumentssc-write-modeextensively as an operator-setapp.tomlfield ([state-commit]section) driving the migration. Described as both removed and configurable. (Category 3)FlatKV directory path inconsistency: The
dump-flatkvexamples use two different DB dirs —$HOME/.sei/data/state_commit/flatkv(with underscore) in one example and$HOME/.sei/data/flatkvin another. Alsotechnical-reference.mdxusesdata/state_commit/flatkv. Inconsistent path for the same FlatKV directory. (Category 1)min_valid_per_window/ oracle default:technical-reference.mdxstates the default "changed from 5%" to0%. This is internally consistent (not a contradiction on its own) — noted only if paired elsewhere; no conflicting value appears. (No issue.)evm-ss-db-directorydefault path:node-operators.mdxsays it defaults to<home>/data/state_store/evm/{backend}, consistent withgiga-storage-migration.mdx(data/state_store/evm/{backend}). (Consistent — no issue.)data/autobahnpersistence default: consistently described. (No issue.)GIGA_STORAGE/RECEIPT_BACKENDdefault (pebble) and parquet removal: consistently described across files. (No issue.)Generated by sei-docs-bridge. Every change is a proposal — verify against the source PRs before merging.