From 600bb48050b01087d372eb487fe85b867798421e Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:44:52 +0000 Subject: [PATCH 01/93] docs: 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#3993) --- node/technical-reference.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx index 92c06a4..1589724 100644 --- a/node/technical-reference.mdx +++ b/node/technical-reference.mdx @@ -555,6 +555,14 @@ double-sign-check-height = 0 The `[consensus]` section may still parse a `stateless-leader-election` field, but the field is **deprecated and ignored**. Stateless (seed-based) leader election is always enabled, regardless of the value, so the field has no effect. It remains only for config-parsing compatibility, and you can safely omit it. + + The node config registry now declares the `[consensus]` and `[mempool]` sections, so a newly generated `config.toml` carries their fields. + + For `[consensus]`, the declared settings cover a node's own local behavior: the WAL/log path, the proposer's empty-block policy, the gossip mode, two reactor sleeps, and a local restart (double-sign) check. The settings that have to agree across the validator set are intentionally **not** declared, so the generated file does not offer them. These excluded keys are the unsafe override settings (`unsafe-overrides-enabled`, `unsafe-propose-timeout-override`, `unsafe-propose-timeout-delta-override`, `unsafe-vote-timeout-override`, `unsafe-vote-timeout-delta-override`, `unsafe-commit-timeout-override`, `unsafe-bypass-commit-timeout-override`), the `timeout-*` settings (`timeout-propose`, `timeout-propose-delta`, `timeout-prevote`, `timeout-prevote-delta`, `timeout-precommit`, `timeout-precommit-delta`, `timeout-commit`), `skip-timeout-commit`, and `stateless-leader-election`. Each names a field the node marks deprecated, so writing it would not change the setting. + + For `[mempool]`, `ttl-duration` and `ttl-num-blocks` are declared, but `max-batch-bytes`, `pending-ttl-duration`, and `pending-ttl-num-blocks` are **not** declared, because no code reads them and writing one changes nothing. + + Out-of-process ABCI support was removed. The full node now runs only with Tendermint in-process. External standalone ABCI processes (socket or gRPC) are no longer supported. As a result: From fc6de5e90709dcccadb6bbd80fbabb5c45f2510d Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:46:08 +0000 Subject: [PATCH 02/93] docs: 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#3994) --- node/technical-reference.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx index 1589724..a17fdbe 100644 --- a/node/technical-reference.mdx +++ b/node/technical-reference.mdx @@ -563,6 +563,14 @@ double-sign-check-height = 0 For `[mempool]`, `ttl-duration` and `ttl-num-blocks` are declared, but `max-batch-bytes`, `pending-ttl-duration`, and `pending-ttl-num-blocks` are **not** declared, because no code reads them and writing one changes nothing. + + A newly generated `config.toml` also declares five more sections: `[statesync]`, `[tx-index]`, `[instrumentation]`, `[priv-validator]`, and `[self-remediation]`. + + Most of these carry the same defaults for every kind of node. The `[tx-index]` section is the exception: its `indexer` default varies by mode, set to `[kv]` for full and archive nodes (which serve queries and so index transactions to answer them) and to `[null]` for validator and seed nodes (which serve none). For `[statesync]`, the keys an operator fills together to turn state sync on — `enable`, `use-p2p`, `rpc-servers`, `trust-height`, and `trust-hash` — are declared and written to the generated file as a set; `temp-dir` is declared but omitted from the written template. + + Some fields are intentionally **not** declared, so the generated file does not offer them: `instrumentation.namespace` (the node marks it deprecated and always uses one fixed metric prefix), `self-remediation.p2p-no-peers-available-window-seconds` (no reactor reads it, so a written value changes nothing about when the node restarts), `mempool.max-batch-bytes` (nothing reads it), and the `priv-validator` root directory (`home`), which the node fills from the command line after the file is read. + + Out-of-process ABCI support was removed. The full node now runs only with Tendermint in-process. External standalone ABCI processes (socket or gRPC) are no longer supported. As a result: From 0ab5f887f3e1c4a9b40ceda314e3befb5eaeab8f Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:47:05 +0000 Subject: [PATCH 03/93] docs: 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#4027) --- node/giga-storage-migration.mdx | 30 +++++++++++++++++++++++++++--- 1 file changed, 27 insertions(+), 3 deletions(-) diff --git a/node/giga-storage-migration.mdx b/node/giga-storage-migration.mdx index 06760e2..6209c9a 100644 --- a/node/giga-storage-migration.mdx +++ b/node/giga-storage-migration.mdx @@ -76,9 +76,9 @@ evm-ss-split = true ### Step 2: State sync into the new layout -Giga SS Store is fully compatible with the existing state-snapshot format. On -import, the composite state store routes each snapshot node based on the -importing node's `evm-ss-split`: +Giga SS Store is fully compatible with the existing **P2P state-sync** snapshot +format. On import, the composite state store routes each snapshot node based on +the importing node's `evm-ss-split`: - With `evm-ss-split = true`, EVM snapshot nodes go only into EVM SS, and non-EVM nodes go only into Cosmos SS. @@ -88,6 +88,30 @@ importing node's `evm-ss-split`: Both stores are then fully populated at the snapshot height, so the node can serve reads immediately. +P2P state-sync snapshots (the chunks peers serve over the network) are **not** +layout-sensitive. Giga SS Store only changes how the importing node writes those +nodes onto disk. + +#### Alternative: restore a Giga SS data-directory snapshot + +**Data-directory snapshots** (a tarball of `~/.sei/data`) *are* layout-sensitive. +A tarball taken from a Giga SS node contains `data/state_store/evm/` (and +`data/state_store/cosmos/`) instead of a single mixed Cosmos SS directory. You +can enable Giga SS Store by restoring such a snapshot and setting +`evm-ss-split = true`; you do not need to P2P state sync again. + +The restoring node's `ss-backend`, `evm-ss-separate-dbs`, and any +`ss-db-directory` / `evm-ss-db-directory` overrides must match the node the +snapshot was taken from. Both SS paths are backend-qualified +(`data/state_store/{cosmos,evm}/{backend}`), so a backend mismatch opens empty +directories and the node starts against restored SC with empty SS instead of +refusing to launch. A tarball from a non-Giga node cannot be used this way — +convert those nodes with the state sync flow below. + +Snapshot hosts that publish `data/` tarballs may offer both Giga SS and non-Giga +copies while the fleet migrates. Use a Giga SS snapshot only when you intend to +run with `evm-ss-split = true`. + The [state sync guide](/node/statesync) documents the full flow. The minimal flow for this migration is: From 4bd4559d540a90e82c84632647d506fe767475d8 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:47:46 +0000 Subject: [PATCH 04/93] docs: 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#4004) --- evm/installing-seid-cli.mdx | 17 +++++++++++------ node/index.mdx | 16 ++++++++++------ 2 files changed, 21 insertions(+), 12 deletions(-) diff --git a/evm/installing-seid-cli.mdx b/evm/installing-seid-cli.mdx index f30f135..0451da1 100644 --- a/evm/installing-seid-cli.mdx +++ b/evm/installing-seid-cli.mdx @@ -22,12 +22,15 @@ To install `seid`, find the version that you want on the [sei-chain releases pag - Each release attaches a statically linked `seid` build for `linux/amd64` with no - runtime dependencies: + Each release attaches statically linked `seid` builds for `linux/amd64` and + `linux/arm64` with no runtime dependencies: ```bash VERSION= # e.g. v6.6.1 — see the version table above - FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz # asset filenames omit the leading v + # Pick the asset matching your architecture (asset filenames omit the leading v): + # linux_x86_64 for linux/amd64 + # linux_aarch64 for linux/arm64 + FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz curl -fLO https://github.com/sei-protocol/sei-chain/releases/download/${VERSION}/${FILE} curl -fLO https://github.com/sei-protocol/sei-chain/releases/download/${VERSION}/checksums.txt @@ -39,9 +42,11 @@ To install `seid`, find the version that you want on the [sei-chain releases pag ``` - Prebuilt binaries are attached from `v6.6.1` onward. For earlier versions, build - from source. The binaries are `linux/amd64` only and omit hardware Ledger support. - On other architectures, or if you sign with a Ledger device, build from source. + Prebuilt binaries are attached from `v6.6.1` onward. The `linux/arm64` + (`linux_aarch64`) build is published alongside `linux/amd64` since v6.8.0. For + earlier versions, or for other architectures, build from source. The prebuilt + binaries omit hardware Ledger support, so if you sign with a Ledger device, build + from source. diff --git a/node/index.mdx b/node/index.mdx index 9c42cb4..084630a 100644 --- a/node/index.mdx +++ b/node/index.mdx @@ -117,12 +117,15 @@ For the current recommended version, see the Network Versions table above. - Each release attaches a statically linked `seid` build for `linux/amd64` with no - runtime dependencies. You do not need to install a Go toolchain or shared libraries. + Each release attaches statically linked `seid` builds for `linux/amd64` and + `linux/arm64` with no runtime dependencies. You do not need to install a Go toolchain + or shared libraries. ```bash VERSION= # e.g. v6.6.1 — see the Network Versions table above - FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz # asset filenames omit the leading v + # Pick the asset for your architecture (asset filenames omit the leading v): + FILE=sei-chain_${VERSION#v}_linux_x86_64.tar.gz # linux/amd64 + # FILE=sei-chain_${VERSION#v}_linux_aarch64.tar.gz # linux/arm64 curl -fLO https://github.com/sei-protocol/sei-chain/releases/download/${VERSION}/${FILE} curl -fLO https://github.com/sei-protocol/sei-chain/releases/download/${VERSION}/checksums.txt @@ -138,9 +141,10 @@ For the current recommended version, see the Network Versions table above. Prebuilt binaries are attached from `v6.6.1` onward. For earlier versions, - build from source or use Docker. Prebuilt binaries are `linux/amd64` only and do not - include hardware Ledger support. On other architectures, or if you sign with a Ledger - device, build from source or use Docker. + build from source or use Docker. Prebuilt `linux/arm64` binaries are attached + alongside `linux/amd64` as of v6.8.0. Prebuilt binaries do not include hardware + Ledger support. If you sign with a Ledger device, or need an architecture other + than `linux/amd64` or `linux/arm64`, build from source or use Docker. From 428d4eeb54e0deffbe7b65f60b51a3e98263ffe8 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:48:53 +0000 Subject: [PATCH 05/93] docs: 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#4018) --- evm/evm-parity/evm-compatibility.mdx | 1 + evm/evm-parity/websocket.mdx | 2 ++ evm/reference.mdx | 2 ++ 3 files changed, 5 insertions(+) diff --git a/evm/evm-parity/evm-compatibility.mdx b/evm/evm-parity/evm-compatibility.mdx index 5e31579..34d84db 100644 --- a/evm/evm-parity/evm-compatibility.mdx +++ b/evm/evm-parity/evm-compatibility.mdx @@ -103,6 +103,7 @@ These features are specific to Sei and have no standard Ethereum equivalent. The | Sei precompiles (staking, governance, distribution, P256, JSON, Solo, pointers, and the CosmWasm bridge) | EVM contracts at deterministic addresses. `@sei-js/precompiles` exports the ABIs and contract addresses for use with any standard EVM library. It does not export the retired Oracle and disabled IBC precompiles. | | Pointer contracts (CW20 ↔ ERC-20, CW721 ↔ ERC-721, CW1155 ↔ ERC-1155) | Bridge between CosmWasm and EVM token standards. Standard ERC interfaces work with pointer contracts. To look up a pointer, use `POINTERVIEW_PRECOMPILE_ADDRESS` (`0x…100A`). To register a pointer, use `POINTER_PRECOMPILE_ADDRESS` (`0x…100B`). | | Native address association (EVM ↔ Cosmos address) | Links an EVM address and a Cosmos address for the same account. Some Sei-native flows require this association first. | +| `milliTimestamp` block-header field | A BEP-520-compatible header field returned by `eth_getBlockByHash`, `eth_getBlockByNumber`, and `eth_subscribe("newHeads")`, carrying the block time as a hex quantity of Unix milliseconds alongside the standard seconds-based `timestamp`. Sei commits blocks faster than once a second, so `timestamp` repeats across consecutive blocks; `milliTimestamp` exposes the sub-second precision the underlying header carries. It is not guaranteed unique per block (under Autobahn blocks less than a millisecond apart can tie). The synthetic genesis block returns `0x0`. | ## Unsupported RPC methods diff --git a/evm/evm-parity/websocket.mdx b/evm/evm-parity/websocket.mdx index 9795ae7..f4a764e 100644 --- a/evm/evm-parity/websocket.mdx +++ b/evm/evm-parity/websocket.mdx @@ -111,6 +111,8 @@ const unwatch = client.watchEvent({ - Sei has instant finality, so every block emitted over WebSocket is already final. You do not need to wait for more confirmations before you act on an event. - Sei does not support `newPendingTransactions` subscriptions. You can subscribe only to `newHeads` and `logs`. +- `newHeads` notifications include a Sei-specific `milliTimestamp` field alongside the standard seconds-based `timestamp`. It carries the header time as a hex quantity of Unix milliseconds, giving sub-second precision that the seconds-based `timestamp` cannot, since Sei commits blocks faster than once a second and `timestamp` repeats across consecutive blocks. This field is present under both Autobahn and CometBFT consensus. Note that `milliTimestamp` is not guaranteed unique per block under Autobahn, where consecutive blocks may be spaced less than a millisecond apart. + ## Frame size and concurrency limits WebSocket connections use the same request limits as HTTP JSON-RPC. Operators set them in the `[evm]` section of `app.toml`: diff --git a/evm/reference.mdx b/evm/reference.mdx index 49b295a..c60a3ed 100644 --- a/evm/reference.mdx +++ b/evm/reference.mdx @@ -561,6 +561,8 @@ If a receipt exists but its block height is above the safe-latest watermark, the **Sei-specific behavior:** Under the eth namespace, only EVM transactions are indexed. Synthetic and bank-transfer transactions are excluded. Block number 0 returns a synthetic genesis block, for compatibility with The Graph. Future or non-existent numeric blocks return null. Uncle and PoW header fields (sha3Uncles, nonce, mixHash, difficulty) are placeholders, and the uncles array is always empty (CometBFT consensus). The safe, finalized, and latest tags are equivalent because of instant finality. +Block headers include a Sei-specific `milliTimestamp` field alongside the standard `timestamp`. The standard `timestamp` stays in whole seconds, as every Ethereum client reads it, but Sei commits blocks faster than once a second, so `timestamp` repeats across consecutive blocks. `milliTimestamp` is a BEP-520-compatible companion that carries the header time as a hex quantity of Unix milliseconds, exposing the sub-second precision the Tendermint header already holds. The synthetic genesis block returns `0x0`. Note that `milliTimestamp` is not guaranteed unique per block either: under Autobahn a proposal spaces consecutive blocks by as little as 1µs, so blocks less than a millisecond apart share the same millisecond value. The same `milliTimestamp` field appears in blocks returned by `eth_getBlockByHash` and in `eth_subscribe("newHeads")` notifications. + **Parameters:** | # | Name | Type | Description | From 4f619caa284cc364e160347a994345cbed362bf0 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:50:13 +0000 Subject: [PATCH 06/93] =?UTF-8?q?docs:=20Adds=20capping=20of=20`/store/*/s?= =?UTF-8?q?ubspace`=20ABCI=20queries=20with=20new=20`[state-commit]`=20con?= =?UTF-8?q?fig=20fields=20(sc-subspace-max-pairs,=20sc-subspace-max-bytes,?= =?UTF-8?q?=20sc-subspace-query-max-inflight),=20empty-prefix=20rejection,?= =?UTF-8?q?=20and=20concurrency=20limits=20=E2=80=94=20requiring=20migrati?= =?UTF-8?q?on=20action=20for=20indexers=20issuing=20wide=20prefix=20scans.?= =?UTF-8?q?=20(sei-protocol/sei-chain#4009)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- node/advanced-config-monitoring.mdx | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/node/advanced-config-monitoring.mdx b/node/advanced-config-monitoring.mdx index 8ecf662..4ab3dda 100644 --- a/node/advanced-config-monitoring.mdx +++ b/node/advanced-config-monitoring.mdx @@ -628,6 +628,31 @@ SeiDB can count estimated logical reads and writes on its PebbleDB databases. Th | `pebble_estimated_reads` | Counter | Estimated logical PebbleDB reads. | | `pebble_estimated_writes` | Counter | Estimated logical PebbleDB writes. | + + +## Subspace query metrics + +`/store/*/subspace` ABCI queries are bounded to prevent memory-exhaustion from wide prefix scans. A scan that would exceed the configured pair or byte caps fails with `subspace result exceeds limit`, empty prefixes are rejected, and queries that exceed the SS fast-path concurrency limit are rejected with `subspace query busy`. Indexers and tooling that issue wide `/subspace` queries must narrow their prefixes, shard by sub-prefix, or raise the caps in `app.toml` (#4009). + +| Metric | Type | Description | +| --- | --- | --- | +| `subspace_query_rejected` | Counter | Number of rejected `/subspace` ABCI queries. Labeled by `reason`: `semaphore` (the concurrency limit was exceeded) or `cap_exceeded` (the scan hit the pair or byte cap). | + +Tune the caps in the `[state-commit]` section of `app.toml`. Values `<= 0` resolve to the defaults; there is no unlimited setting: + +| Config key | Default | Description | +| --- | --- | --- | +| `sc-subspace-max-pairs` | `1000` | Maximum number of key/value pairs a `/subspace` scan may return. | +| `sc-subspace-max-bytes` | `4194304` (4 MiB) | Maximum key+value bytes a `/subspace` scan may accumulate. | +| `sc-subspace-query-max-inflight` | `2` | Maximum concurrent unproven `/subspace` queries on the SS fast path. | + +```toml +[state-commit] +sc-subspace-max-pairs = 1000 +sc-subspace-max-bytes = 4194304 +sc-subspace-query-max-inflight = 2 +``` + Both counters have a `db` attribute. Its value is the name of the data directory, so you can tell the FlatKV data DBs, the state store, and the receipt store apart. Turn the counters on per store in `app.toml`: | Config key | Section | Store | From d91f4ec20717a87f8ee5c6f130f088155e765515 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:53:47 +0000 Subject: [PATCH 07/93] docs: 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#4032) --- node/advanced-config-monitoring.mdx | 11 +++++++++++ node/seictl.mdx | 3 ++- 2 files changed, 13 insertions(+), 1 deletion(-) diff --git a/node/advanced-config-monitoring.mdx b/node/advanced-config-monitoring.mdx index 4ab3dda..413aad8 100644 --- a/node/advanced-config-monitoring.mdx +++ b/node/advanced-config-monitoring.mdx @@ -81,6 +81,17 @@ Monitoring is one of the most critical components of network infrastructure. Thi First, install Prometheus: + + + +The application Prometheus sink is off by default. A node whose `app.toml` is generated by v6.8.0 gets `prometheus-retention-time = 0` under `[telemetry]`, which leaves the sink uncreated even though `telemetry.enabled` stays `true`. `GET /metrics?format=prometheus` on the app API server (:1317) then returns `prometheus metrics are not enabled`, and `seid` exports no application Prometheus series. If you scrape application metrics, set a positive `[telemetry] prometheus-retention-time` in `app.toml` (the previous default was `7200`) before generating a new configuration file. Nodes that already have `prometheus-retention-time` written in `app.toml` are unaffected (#4032). + +```toml +[telemetry] +prometheus-retention-time = 7200 +``` + + ```bash wget https://github.com/prometheus/prometheus/releases/download/v2.42.0/prometheus-2.42.0.linux-amd64.tar.gz tar xvf prometheus-2.42.0.linux-amd64.tar.gz diff --git a/node/seictl.mdx b/node/seictl.mdx index f887ae2..7a2f6c8 100644 --- a/node/seictl.mdx +++ b/node/seictl.mdx @@ -351,7 +351,8 @@ minimum-gas-prices = "0.02usei" [telemetry] enabled = true -prometheus-retention-time = 60 +# A positive value is required to start the Prometheus metrics sink; the sink stays off when this is 0. +prometheus-retention-time = 7200 [api] enable = true From 1eac5855ed144fa410f7bcdd79111631ecb6a49a Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:54:37 +0000 Subject: [PATCH 08/93] docs: 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#4062) --- evm/reference.mdx | 4 ++++ node/advanced-config-monitoring.mdx | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/evm/reference.mdx b/evm/reference.mdx index c60a3ed..9ba7b2d 100644 --- a/evm/reference.mdx +++ b/evm/reference.mdx @@ -116,6 +116,10 @@ By default, log filters (`eth_getLogs`, `eth_getFilterLogs`) have these limits. A query over a limit fails with `query matches too many logs`, `query matches too many log bytes`, or `block range too large`. It does not return partial results. Narrow the block range or the filters (address and topics), then try again. + + +Node operators can disable the receipt store by setting `receipt-store.rs-enable = false` in the `[receipt-store]` section of `app.toml` (it defaults to `true`). A node in this mode keeps no receipt history. Because most `eth_*` methods read a block's transactions or receipts, the EVM HTTP and WebSocket RPC listeners refuse to start when the receipt store is disabled; turning it off requires both `evm.http_enabled` and `evm.ws_enabled` to be `false`. On a node that does serve EVM RPC with a receipt-dependent method reaching a disabled store, the receipt-reading methods — including `eth_getLogs`, `eth_getFilterLogs`, `eth_feeHistory`, `eth_getBlockReceipts`, and `eth_getBlockTransactionCountByNumber` / `eth_getBlockTransactionCountByHash` — return an explicit `ErrNotConfigured` error rather than empty or null results, so callers are not silently handed incomplete data. + Real-time subscriptions (`eth_subscribe` for `newHeads` and `logs`) are available over WebSocket only. For transport details, see [WebSocket connections](/evm/evm-parity/websocket). diff --git a/node/advanced-config-monitoring.mdx b/node/advanced-config-monitoring.mdx index 413aad8..a8765a1 100644 --- a/node/advanced-config-monitoring.mdx +++ b/node/advanced-config-monitoring.mdx @@ -672,6 +672,10 @@ Both counters have a `db` attribute. Its value is the name of the data directory | `ss-enable-read-write-metrics` | `[state-store]` | State store, when `ss-backend = "pebbledb"` | | `enable-read-write-metrics` | `[receipt-store]` | Pebble-based receipt store | + +The `[receipt-store]` `enable-read-write-metrics` key is no longer written into the generated `app.toml` template. The config reader still honors `receipt-store.enable-read-write-metrics` if you add it to `app.toml` by hand, but a newly generated file no longer renders it under `[receipt-store]`. + + ```toml [state-commit.flatkv] enable-read-write-metrics = true From 9768a7518d07d5a0b087cf345c7e9db665e7ad67 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:55:31 +0000 Subject: [PATCH 09/93] docs: 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#4012) --- node/technical-reference.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx index a17fdbe..d54a7bb 100644 --- a/node/technical-reference.mdx +++ b/node/technical-reference.mdx @@ -323,6 +323,7 @@ A node starts in Giga mode when `autobahn-config-file` is set in `config.toml`. - **The CometBFT `TxMempool` is not used.** Under Giga, the standard mempool and its gossip reactor are disabled entirely. Transactions route through the Autobahn producer-backed mempool instead. - **Consensus reactor, state sync, and block sync are disabled.** In Giga mode, the node skips the consensus and state-sync reactors entirely. The block-sync reactor still runs without a syncer. State sync and block sync are both forced off, regardless of other configuration. - **Transactions are admitted through the producer mempool.** The RPC broadcast endpoints call the producer's `InsertTx` or `TryInsertTx`, not the CometBFT mempool's `CheckTx`. `BroadcastTx` uses `InsertTx`, which blocks while the mempool is full. The async path calls `TryInsertTx` in the background and returns immediately. As a result, when the mempool is full, the transaction is silently dropped. The `mempool is full` error from `TryInsertTx` never reaches async callers. +- **`broadcast_tx_commit` is not supported under Autobahn.** When Autobahn is active, the Tendermint `BroadcastTxCommit` RPC no longer inserts the transaction into the producer mempool and waits for commit. It now fail-fasts, returning the error `broadcast_tx_commit is not supported on Autobahn; use broadcast_tx_sync` without submitting the transaction at all. Use `broadcast_tx` (CheckTx) instead and confirm inclusion from committed state. Correspondingly, `eth_sendRawTransaction` with `evm.slow` enabled falls back to the `BroadcastTx` (sync) path on Autobahn nodes rather than `BroadcastTxCommit`, so EVM transactions still land. - **Sequential EVM nonce ordering is enforced.** For EVM transactions, the producer mempool admits transactions strictly in nonce order per sender. A transaction whose nonce does not match the next expected nonce is rejected with a `bad nonce` error. Because admission is sequential, the mempool can track pending nonces (`EvmNextPendingNonce`) as callers submit them. The producer enforces these limits on each Autobahn block payload as it fills a block: From 535c2802975d708f166f38acaa1c0fc10d620a23 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 00:57:37 +0000 Subject: [PATCH 10/93] docs: 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#4066) --- evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx | 2 +- evm/precompiles/cosmwasm-precompiles/example-usage.mdx | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx b/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx index 41ce914..99ab17f 100644 --- a/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx +++ b/evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx @@ -9,7 +9,7 @@ keywords: ['cosmwasm precompile', 'ethers.js', 'wasm execution', 'cross-chain co **Deprecation notice (Prop 115)** - Under [governance Proposal 115](https://seistream.app/proposals/115), CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) are disabled chain-wide. The `instantiate()` function on this precompile **reverts** for all callers. Only calls to `execute()`, `execute_batch()`, and `query()` against pre-existing CosmWasm contracts still work. All CosmWasm functionality is deprecated in favor of EVM-only under [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md). + Under [governance Proposal 115](https://seistream.app/proposals/115), CosmWasm code uploads (`MsgStoreCode`) and contract instantiations (`MsgInstantiateContract`) are disabled chain-wide. The `instantiate()` function on this precompile **reverts** for all callers. The `execute_batch()` function is also **disabled** and now fails with the error `wasmd execute_batch is disabled`; use single `execute()` calls instead. Only calls to `execute()` and `query()` against pre-existing CosmWasm contracts still work. All CosmWasm functionality is deprecated in favor of EVM-only under [SIP-3](https://github.com/sei-protocol/sips/blob/main/sips/sip-3.md). The examples on this page attach only native SEI. Do not use the `coins` field to build IBC or tokenfactory integrations. IBC is disabled in both directions. Tokenfactory is not a supported development path. diff --git a/evm/precompiles/cosmwasm-precompiles/example-usage.mdx b/evm/precompiles/cosmwasm-precompiles/example-usage.mdx index 2409fae..efbf9c3 100644 --- a/evm/precompiles/cosmwasm-precompiles/example-usage.mdx +++ b/evm/precompiles/cosmwasm-precompiles/example-usage.mdx @@ -13,6 +13,10 @@ You can use the Sei precompiles like any standard smart contract on the EVM. For example, this page uses [ethers.js](https://docs.ethers.org/v6/) to query an existing CosmWasm contract and execute actions on it. + +The `execute_batch` method on the CosmWasm precompile is disabled and now reverts with the error `wasmd execute_batch is disabled`. Only single `execute` and `query` calls are supported. Integrations that previously batched multiple CosmWasm executions in a single call must send each execution individually. + + ## Setup To install `ethers`, run this command in a terminal in your project directory: From ae824d88c57c4f8cfd695873db698a315b138685 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 06:32:58 +0000 Subject: [PATCH 11/93] docs: 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#3983) --- node/technical-reference.mdx | 2 +- node/troubleshooting.mdx | 3 +++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx index d54a7bb..38ed878 100644 --- a/node/technical-reference.mdx +++ b/node/technical-reference.mdx @@ -198,7 +198,7 @@ The command accepts these flags: - `--db-dir` (`-d`): For FlatKV, the FlatKV data directory. For memIAVL, the memIAVL root directory that contains `current/` and `snapshot-*`. Required unless you use `composite`. - `--flatkv-dir` and `--memiavl-dir`: The two data directories for `--backend composite`. You must set both in that mode. - `--height`: The target version. FlatKV WAL-replays to it, and memIAVL resolves `snapshot-/evm` (`0` selects the `current` symlink). -- `--memiavl-open-mode`: How the command reads memIAVL. `snapshot` (the default) scans the snapshot file at `--height`. It is the fastest mode, but it needs a snapshot at that height, or `--height 0`. `changelog` reads the nearest snapshot at or below `--height` and adds the changelog's EVM writes up to `--height`. `replay` opens the database, replays the changelog to `--height`, and walks the tree. It is about 10 times slower than `snapshot`. `changelog` and `replay` return the same rows. Use one of them when no snapshot exists at `--height`. +- `--memiavl-open-mode`: How the command reads memIAVL. `snapshot` (the default) scans the snapshot file at `--height`. It is the fastest mode, but it needs a snapshot at that height, or `--height 0`. `changelog` reads the nearest snapshot at or below `--height` and adds the changelog's EVM writes up to `--height`. `replay` opens the database read-only and replays the changelog to `--height`, then walks the tree. It is about 10 times slower than `snapshot`. `changelog` and `replay` return the same rows. Use one of them when no snapshot exists at `--height`. On a live node, `replay` can encounter a changelog record that the node is partway through writing. In that case it does not repair (truncate) the torn changelog tail, because doing so could discard a block the node has just committed. Instead it leaves the changelog directory as it found it and fails with an error that tells you to rerun the command; if the failure persists across reruns, the changelog is genuinely corrupt and the node needs attention. - `--memiavl-normalization`: The memIAVL normalization mode. Use `semantic` or `independent` for the raw EVM key-value decoder, or `translator` for the current migration mapping. The default is `semantic`. - `--json`: Print the digest or inspect report as one JSON object on stdout, and the progress messages on stderr. - `--inspect-bucket`: Inspect one normalized bucket (`account`, `code`, `storage`, or `misc`), not the global digest. Inspect mode with `--memiavl-normalization translator`, or with `--details` on the `storage` bucket, requires `--memiavl-open-mode snapshot`. diff --git a/node/troubleshooting.mdx b/node/troubleshooting.mdx index 69ef919..eb00c6d 100644 --- a/node/troubleshooting.mdx +++ b/node/troubleshooting.mdx @@ -151,6 +151,9 @@ seidb evm-logical-digest --backend memiavl --memiavl-open-mode changelog \ --db-dir $HOME/.sei/data/state_commit/memiavl --height 213205000 ``` + +On a live node, `--memiavl-open-mode changelog` can read a changelog record that the node is partway through writing for a block it is committing. A record that ends mid-write is indistinguishable from a genuinely corrupt one, so rather than truncating the changelog tail (which could discard a block the node just committed), the command now leaves the changelog directory untouched and fails with an error that reports the torn tail and asks you to rerun the command. The message reads like `the changelog under ends mid-record, which is what a node writing a block looks like ... rerun this command`. Simply run the command again. If it keeps failing after repeated reruns, the changelog is genuinely corrupt and the node needs attention. + On a node in the middle of the migration, EVM state is split between FlatKV and memIAVL. Use `--backend composite` to digest both together, so you can compare the node with a memIAVL-only node at the same height. Pass the two directories with `--flatkv-dir` and `--memiavl-dir` instead of `--db-dir`: ```bash From c7a228c5bc6a51d56b284cbb7e334aff66e5af9d Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 06:35:20 +0000 Subject: [PATCH 12/93] docs: 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#4045) --- node/technical-reference.mdx | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx index 38ed878..207bdb2 100644 --- a/node/technical-reference.mdx +++ b/node/technical-reference.mdx @@ -48,6 +48,36 @@ The experimental `SEI_CONFIG_MANAGER` environment variable selects how `seid` lo SEI_CONFIG_MANAGER=v2 seid start ``` + + +#### Checking sei.toml before a restart (`seid config check`) + +The `seid config check` subcommand resolves a node's `sei.toml` the same way a boot resolves it and reports every value this binary would refuse, without starting the node. A boot cannot refuse a file: it applies what it can and reports the rest, so a mistyped value becomes a report on a node that has already restarted. Running `config check` first turns that into a failed check instead. It exits non-zero when it finds a problem, so you can gate a configuration rollout on its exit status. + +```bash +# Check the node's sei.toml against this binary without starting anything +seid config check --home +``` + +The command locates the node's config directory from the standard `--home` flag (or the `SEID_HOME` environment variable). A home must be set one of these ways; otherwise the command refuses to run rather than reading `sei.toml` from the working directory, because answering confidently about some other node's file is worse than not answering. + +`config check` resolves `sei.toml` against the environment it runs in. A declared key answered by an environment variable is only visible to the check if that variable is also set where you run the command, so run it in the same environment the node boots in (for example, the same container or service unit) for the most faithful result. It does not start the node and does not generate any files: unlike a normal boot, it never writes `config.toml` or `app.toml`, so you can safely run it against a node you are only asking a question about. + +The report covers every value a boot would refuse or ignore, including: + +- Keys that `sei.toml` writes but no section declares, which have no effect. +- Type mismatches, such as a length of time written as a plain number (which would be read as nanoseconds) or a number larger than the setting can hold. +- Values that decode cleanly but the node's own delivery rules reject (for example, a negative `max-tx-bytes`). +- A disagreement about the kind of node: `sei.toml` records the node mode at its top, and the node's own `config.toml` records a `mode` of its own. When they disagree, the values resolved from `sei.toml` are the answer for one kind of node while the node would run as the other. +- How many of the declared keys the file states, how many are answered by an environment variable or a flag, and how many fall back to the value this binary declares for this kind of node. + +`config check` also surfaces the `SEI_CONFIG_MANAGER` gate state (see above), because that determines whether a boot reads `sei.toml` at all: + +- Unset or `legacy`: the command notes that a boot in the same environment reads none of this file, then reports what it would reach if the gate were set to `v2`. This keeps a passing check from reading as "in use and correct" on a node where a boot ignores the file. +- `v2`: a boot reads the file, so the report reflects what it would use. +- Any other value: the gate is reported as a problem, because a boot refuses an invalid `SEI_CONFIG_MANAGER` value before it reaches the file, and such a node would not start. + + #### Freeze mode (`--freeze-height`) As of v6.6.3, you can put a full node into read-only freeze mode at a specified block height. Use the `--freeze-height` start flag or the corresponding `freeze-height` field in `app.toml`. Freeze mode exists for historical RPC nodes. A node frozen at an upgrade height keeps running the pre-upgrade binary and keeps serving the state that binary produced. It does not shut down at the boundary or execute the upgrade block with code that no longer matches that state. For setup steps and the freeze heights of each network, see [Run frozen nodes](/node/frozen-nodes). From 204a6ffa14d175fc0d86546907ccfc7895f0ef42 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 06:37:14 +0000 Subject: [PATCH 13/93] docs: 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#4080) --- node/giga-storage-migration.mdx | 21 +++++++++++++++++++++ node/node-operators.mdx | 21 +++++++++++++++++++++ node/technical-reference.mdx | 21 +++++++++++++++++++++ 3 files changed, 63 insertions(+) diff --git a/node/giga-storage-migration.mdx b/node/giga-storage-migration.mdx index 6209c9a..a90cefa 100644 --- a/node/giga-storage-migration.mdx +++ b/node/giga-storage-migration.mdx @@ -390,3 +390,24 @@ The supported receipt-store backends are `pebbledb` (also called `pebble`) and removed. The node rejects an unsupported value for `RECEIPT_BACKEND` (or `rs-backend` in `app.toml`) with an error (`unsupported receipt-store backend "parquet"; supported: pebbledb, littidx`). + + + +### Does the receipt store guard against opening it with the wrong backend? + +Yes. The receipt store records which backend owns its directory in a +`receipt-backend.txt` marker file, written on first open. If you later point a +different backend at that same directory — for example opening a `pebble` store +as `littidx` or the reverse — the store refuses to open and fails with a +mismatch error that names both the backend that owns the directory and the one +that was requested, instead of silently presenting an empty store. Point the +configured backend at its own store directory, or configure the backend that +owns the one on disk. + +Directories written before the marker existed carry no marker and are adopted +as-is on the next open: the configured backend is taken to be the owner and the +marker is stamped on the way through, so existing nodes keep working without +intervention. A backend the build does not support, or a config the backend +rejects (such as `ExternalPruning` with the `pebble` backend), is refused before +the directory is touched, so a rejected attempt does not leave a marker behind +that would then refuse the corrected config. diff --git a/node/node-operators.mdx b/node/node-operators.mdx index 052cba2..bd2faa7 100644 --- a/node/node-operators.mdx +++ b/node/node-operators.mdx @@ -130,6 +130,27 @@ defaults to `pebble`. The former `receipt-store.tx-index-backend` config field has been removed. + + +The receipt store records which backend owns its directory in a +`receipt-backend.txt` marker file, written the first time the store is opened. +On every subsequent open, the node checks this marker and 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. The error names +both the backend that owns the directory and the backend that was requested, so +the fix is to either point `db-directory` at the correct backend's store or set +`rs-backend` to the backend that owns the directory. + +For backwards compatibility, a store directory that carries no marker (one +written before markers existed, or a brand-new directory) is adopted by the +configured backend and stamped with the marker on that first open. An +unsupported backend or a config the backend rejects (for example, `pebbledb` +with external pruning enabled) is refused before the directory is touched, so a +rejected attempt never leaves a marker behind that would then refuse the +corrected configuration. + + ### Default configurations This section shows the full unmodified `app.toml`, `config.toml`, and diff --git a/node/technical-reference.mdx b/node/technical-reference.mdx index 207bdb2..797f8b4 100644 --- a/node/technical-reference.mdx +++ b/node/technical-reference.mdx @@ -296,6 +296,27 @@ seidb hashlog compare [--low --high ] [--max-diff - `--full`: Show every column for each block with differences. By default, the command shows only the columns that differ. Use `--full` when the archives hold a different number of records for a block. - `--json`: Print JSON instead of text. + + +#### Offline receipt-store maintenance (littidx backend) + +The receipt store supports offline operations that read or rewind its on-disk data directly, without starting a live store. These operations are supported only for the `littidx` receipt-store backend; any other backend (for example, `pebbledb`) is refused rather than reported as empty, so the store must not be running while an offline operation runs. + +A `littidx` receipt store now records its ownership in a `receipt-backend.txt` marker file in its directory on first open. Opening a store directory with a backend other than the one that owns it fails loudly with a mismatch error instead of presenting a silently empty store. A directory written before markers existed carries no marker and is adopted by the configured backend on its next open. An offline operation checks both the configured backend and this marker, so a `littidx`-configured run pointed at another backend's directory is refused by the marker. + +Two offline entry points are available for a `littidx`-backed receipt store: + +- **`GetRange`** reports the lowest and highest block heights present on disk for the receipt store, without opening it. It returns a flag that is false when no receipts are present. +- **`PruneAfter`** deletes every receipt for a block height greater than the target from the store, without opening it. It rolls back the littdb receipt bodies, deletes the pebble tag-index entries above the target, and moves the store's latest-block metadata back to match. A target at or above the store's head is a no-op. + +`PruneAfter` validates the target before touching any receipt, so a refusal leaves the store's data unchanged. It refuses a target below the store's retention floor (that data has already been pruned) and a target below the oldest receipt still on disk (which would leave no receipt at all); to discard the store entirely, delete its directory instead. + +Underpinning these operations, the offline LittDB rollback utility now lives in the `litt/offline` package (moved from `litt/rollback`) and takes a `*litt.Config` in place of a slice of data directories. Its rollback filter semantics also changed: a table for which the filter never matches any record now retains nothing and is deleted in its entirety — including its gc-watermark — rather than being left unchanged. A filter must therefore not use a never-match to mean "not my table"; every table under the config's paths is subject to it. + + + The database must not be running while any offline receipt-store or LittDB rollback operation runs. These operations take the same directory locks the database uses, so they fail rather than corrupt a live store, and they assume nothing else mutates the data meanwhile. + + ### Autobahn (GigaRouter) config generation When you use the Autobahn (GigaRouter) networking layer, you can generate the Autobahn JSON config from a set of node directories. Each directory must contain `validator_pubkey.txt`, `node_pubkey.txt`, `autobahn_address.txt`, and `evmrpc_url.txt`. Unlike the key files, `evmrpc_url.txt` is not written automatically, so you must create it by hand with the node's EVM RPC URL. If the file is missing, the command fails with an error. The `mempool_size` field is no longer part of `autobahn.json`. Remove it from existing config files. From 39c30b711fd498a86f74f9cf317c1a9954ff188d Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 06:37:40 +0000 Subject: [PATCH 14/93] docs: 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#4083) --- evm/reference.mdx | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/evm/reference.mdx b/evm/reference.mdx index 9ba7b2d..137b171 100644 --- a/evm/reference.mdx +++ b/evm/reference.mdx @@ -88,11 +88,12 @@ Under Autobahn (`AutobahnConfigFile` set), the CometBFT block store is not popul Under Autobahn (`AutobahnConfigFile` set), the CometBFT `BlockStore` and `StateStore` are not populated. These Tendermint RPC endpoints do not return empty or failing responses in this mode. Instead: - `/block` and `/block_by_hash` route through the GigaRouter's in-memory state (the finalized global blocks that the Autobahn data layer retains). -- `/block_results` and `/validators` synthesize their responses (an empty result set and the genesis committee, respectively). +- `/block_results` synthesizes an empty result set. +- `/validators` returns the committee that certified the requested global block. This keeps downstream consumers, including evmrpc, block explorers, and monitoring tools, working without each one branching on the consensus engine. -`/block` and `/block_by_hash` serve responses only for heights that are still inside Autobahn's retained window. Heights pruned per `RetainHeight` are no longer available. `/block_results` and `/validators` do not read the retained block data. They respond for any height up to the current ABCI head. Requests are validated against the current ABCI head, so heights above it return the same `ErrHeightExceedsChainHead`-class errors as the CometBFT path. Pruned heights on `/block` return `ErrHeightNotAvailable`. +`/block` and `/block_by_hash` serve responses only for heights that are still inside Autobahn's retained window. Heights pruned per `RetainHeight` are no longer available. `/block_results` does not read the retained block data; it responds for any height up to the current ABCI head. Requests are validated against the current ABCI head, so heights above it return the same `ErrHeightExceedsChainHead`-class errors as the CometBFT path. Pruned heights on `/block` return `ErrHeightNotAvailable`. | Endpoint | Autobahn behavior | | :- | :- | From 75a0a0ac59e8f996a40d3c88b37078e8eca60c15 Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 12:28:25 +0000 Subject: [PATCH 15/93] docs: 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#4000) --- evm/precompiles/governance.mdx | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/evm/precompiles/governance.mdx b/evm/precompiles/governance.mdx index f76a95e..3af4305 100644 --- a/evm/precompiles/governance.mdx +++ b/evm/precompiles/governance.mdx @@ -32,8 +32,16 @@ Sei governance follows a structured timeline with specific parameters: 1. **Proposal submission:** Submit a proposal with a minimum deposit of 3,500 SEI. 2. **Deposit period:** The proposal has 2 days to accumulate the minimum deposit or reach the expedited threshold. -3. **Voting period:** When the proposal meets the minimum deposit, voting is active for 3 days (1 day for expedited proposals). -4. **Tallying:** The results are calculated from the quorum and voting thresholds. +3. **Voting period:** When the proposal meets the minimum deposit, voting is active for 3 days (1 day for expedited proposals). Once a proposal's voting end time is reached, its electorate is frozen: new votes and deposits are rejected with `ErrInactiveProposal`. +4. **Tallying:** The results are calculated from the quorum and voting thresholds. From the v6.8 upgrade, tallying is incremental — work is bounded per block and a proposal's result may be computed across several blocks rather than in a single end-of-period pass. Before activation, legacy single-pass tallying is preserved. + + +**v6.8 incremental tally changes:** From the v6.8 upgrade, governance uses a bounded, incremental tally: + +- Votes and deposits are rejected once a proposal's voting end time is reached or its electorate snapshot is frozen (`ErrInactiveProposal`), rather than being accepted up to the final tally. +- Casting a vote that creates a new deferred tally record consumes additional gas (`DeferredVoteTallyGas`), so budget extra gas for first-time votes on a proposal. +- When an expedited proposal fails and is converted to a regular proposal, the regular round resumes for the remaining window (`VotingPeriod - ExpeditedVotingPeriod`) measured from the conversion time, instead of restarting the full regular voting period from the original voting start time. + To learn more about the governance process on Sei, read the [governance explainer](/learn/general-governance). From 13d8b5818598d3481e83e27d17ce5f8d7121ac9d Mon Sep 17 00:00:00 2001 From: "seidroid[bot]" <257742136+seidroid[bot]@users.noreply.github.com> Date: Wed, 18 Nov 2026 12:29:22 +0000 Subject: [PATCH 16/93] docs: 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#4098) --- node/snapshot.mdx | 3 +++ node/statesync.mdx | 10 ++++++++++ 2 files changed, 13 insertions(+) diff --git a/node/snapshot.mdx b/node/snapshot.mdx index 129722a..09d5be6 100644 --- a/node/snapshot.mdx +++ b/node/snapshot.mdx @@ -27,6 +27,9 @@ You can download snapshots from these providers: