@@ -77,7 +77,7 @@ The Operate section covers topics related to running Sei infrastructure. This is
 **Contents include:**
 
 - **Node Operations**: Overview, Seictl setup, statesync, snapshot sync, node types, troubleshooting, API configuration, validators, oracle price feeder
-- **Advanced Operations**: Configuration & monitoring, RocksDB backend, technical reference
+- **Advanced Operations**: Configuration & monitoring, Giga SS Store migration, technical reference
 
 ## Style Guidelines
 
 
@@ -339,7 +339,6 @@
             "group": "Advanced Operations",
             "pages": [
               "node/advanced-config-monitoring",
-              "node/rocksdb-backend",
               "node/giga-storage-migration",
               "node/technical-reference"
             ]
@@ -899,6 +898,11 @@
       "destination": "/node",
       "permanent": true
     },
+    {
+      "source": "/node/rocksdb-backend",
+      "destination": "/node/node-operators#move-off-rocksdb",
+      "permanent": true
+    },
     {
       "source": "/node/oracle-price-feeder",
       "destination": "/learn/oracles",
 
@@ -12,7 +12,7 @@ The `seid` CLI is the command-line tool for interacting with the Sei blockchain.
 
 ## Prerequisites
 
-- Go 1.23+ (build from source only): Installation instructions are available [here](https://go.dev/doc/install). The prebuilt binary has no prerequisites.
+- [Go 1.25.6 or later](https://go.dev/doc/install) is required only when building from source. Check the `go.mod` at the release tag you check out below (e.g. [`v6.6.1`](https://github.com/sei-protocol/sei-chain/blob/v6.6.1/go.mod)) for its exact requirement. Prebuilt binaries have no prerequisites.
 
 ## Installation
 
 
@@ -171,7 +171,6 @@ Sei supports full nodes (recent state, consensus relay), archive nodes (complete
 - [Swagger API Documentation](https://docs.sei.io/node/swagger): Learn how to enable and access Swagger API documentation for your Sei node. Configure the swagger endpoint in app.toml and view interactive API docs.
 - [Sei Validator Operations Guide](https://docs.sei.io/node/validators): Learn how to set up and maintain a validator node on Sei Network, including hardware security configuration, key management, monitoring practices, and governance participation requirements.
 - [Sei Node Advanced Configuration & Monitoring](https://docs.sei.io/node/advanced-config-monitoring): Optimize your Sei node's performance with advanced system configurations, monitoring setup with Prometheus and Grafana, and effective alerting strategies for maintaining reliable node operations.
-- [RocksDB Backend Setup & Performance](https://docs.sei.io/node/rocksdb-backend): Build and enable the RocksDB backend for seid to significantly improve iteration-heavy operations and traceBlock latency, especially on long-history RPC and archive nodes.
 - [Giga SS Store Migration Guide](https://docs.sei.io/node/giga-storage-migration): Migrate a Sei RPC node to Giga SS Store: split EVM state into a dedicated state-store backend so non-EVM modules stop paying EVM write amplification.
 - [Sei Technical Reference](https://docs.sei.io/node/technical-reference): Access detailed command syntax, configuration parameters, and troubleshooting procedures for node operators and validators running Sei network infrastructure.
 
 
@@ -15,7 +15,7 @@ After migration the SS layer is repartitioned into two cooperating stores:
 | Layer | Cosmos backend | EVM backend |
 |---|---|---|
 | **SC** (State Commit, app hash) | `memiavl` | FlatKV |
-| **SS** (State Store, historical queries) | single MVCC DB (PebbleDB or RocksDB) | dedicated EVM SS MVCC DB(s) under `data/evm_ss/` |
+| **SS** (State Store, historical queries) | single PebbleDB MVCC database | dedicated EVM SS MVCC databases in the configured EVM SS directory |
 
 Only the **SS** layer changes for this migration. SC layer config is untouched
 and `memiavl` remains the authoritative source for the app hash, so this is
@@ -43,9 +43,6 @@ local data directory and imports a fresh snapshot into the new layout.
 
 - EVM reads are served exclusively from a dedicated EVM SS database.
 - Non-EVM modules no longer pay write amplification for EVM state.
-- A backend change (PebbleDB ↔ RocksDB) can be combined with the same state
-  sync, since `ss-backend` drives both the Cosmos SS MVCC DB and every EVM SS
-  sub-DB.
 
 ## What's different about EVM SS
 
@@ -69,8 +66,7 @@ sc-enable = true
 [state-store]
 ss-enable = true
 
-# DBBackend for the Cosmos SS MVCC DB and for every EVM SS sub-DB.
-# Supported: pebbledb, rocksdb. Default pebbledb.
+# Use PebbleDB for the Cosmos SS MVCC DB and every EVM SS sub-DB.
 ss-backend = "pebbledb"
 
 # Route EVM state to the dedicated EVM SS backend.
@@ -80,14 +76,7 @@ ss-backend = "pebbledb"
 evm-ss-split = true
 ```
 
-If you want to switch SS backend in the same step:
-
-- **PebbleDB → RocksDB**: set `ss-backend = "rocksdb"`, build `seid` with
-  `-tags rocksdbBackend`, and install RocksDB per the
-  [RocksDB Backend Guide](/node/rocksdb-backend). `ss-backend` drives both the
-  Cosmos SS MVCC DB and every EVM SS sub-DB, so a single setting flips both.
-- No data migration tool is needed across backends — the state sync populates
-  the new layout.
+<Warning>Keep `ss-backend = "pebbledb"` during this migration. RocksDB support for the state store will be removed. No target release has been published. If the node already uses RocksDB, follow [Move off RocksDB](/node/node-operators#move-off-rocksdb).</Warning>
 
 ### Step 2: State sync into the new layout
 
@@ -175,10 +164,9 @@ flipping `evm-ss-split` from `false` to `true` without state syncing.
 
 1. **EVM SS directory missing or empty** (before the EVM SS is opened). When
    `evm-ss-split = true`, the composite state store refuses to proceed if
-   Cosmos SS already has committed history but the EVM SS directory
-   (`data/evm_ss/` by default) does not exist or is empty. Failing before
-   the sub-DBs are opened means a rejected config does not leave a confusing
-   empty `data/evm_ss/` behind.
+   Cosmos SS already has committed history but the configured EVM SS directory
+   does not exist or is empty. Failing before the sub-DBs are opened means a
+   rejected config does not leave a confusing empty directory behind.
 2. **EVM SS DB empty post-open, pre-recovery.** Belt-and-suspenders for (1)
    when the directory exists but its DBs are empty. The WAL only covers the
    last `KeepRecent` blocks, so replay cannot rebuild a fresh EVM SS from
@@ -190,18 +178,19 @@ flipping `evm-ss-split` from `false` to `true` without state syncing.
 
 If any check fires, the correct fix is either (a) complete the state sync
 described above, or (b) set `evm-ss-split = false` and restart. If
-`data/evm_ss/` is stale from a failed attempt, remove it before state syncing.
+the configured EVM SS directory is stale from a failed attempt, remove it
+before state syncing.
 
 ## Rollback
 
 To roll back:
 
 1. Set `evm-ss-split = false` in `app.toml`.
-2. Restart the node. The EVM SS DB under `data/evm_ss/` is no longer opened
-   but stays on disk until manually removed.
+2. Restart the node. The EVM SS DB is no longer opened but stays on disk until
+   you remove it.
 
 To fully reclaim the disk used by EVM SS, stop the node and delete
-`data/evm_ss/` after reverting the setting.
+the configured EVM SS directory after reverting the setting.
 
 <Warning>Cleanly rolling back to `evm-ss-split = false` requires another state sync. Under `evm-ss-split = true`, EVM writes go only to the EVM SS DB, so Cosmos SS will not have those writes. Restarting with `evm-ss-split = false` stops opening the EVM SS DB, but EVM-state queries will miss anything written after the Giga state sync until you re-state-sync without the split.</Warning>
 
@@ -316,16 +305,15 @@ and bytes migrated.
 
 ### Where do the data files live after migrating?
 
-As of Sei v6.6, new nodes use a structured subdirectory layout. Existing nodes
-with legacy flat paths automatically keep using them (the legacy path takes
-precedence when present).
-
-- Cosmos SS data lives under `data/state_store/cosmos/{backend}` on new nodes
-  (e.g. `data/state_store/cosmos/pebbledb` for the default `pebbledb` backend).
-  Existing nodes with legacy `data/pebbledb/` continue using it.
-- EVM SS data lives under `data/state_store/evm/{backend}` on new nodes
-  (e.g. `data/state_store/evm/pebbledb`). Existing nodes with legacy
-  `data/evm_ss/` continue using it.
+- Cosmos SS data uses `data/pebbledb/` in the legacy layout and
+  `data/state_store/cosmos/pebbledb/` in the current layout.
+- EVM SS data uses `data/evm_ss/` in the legacy layout and
+  `data/state_store/evm/pebbledb/` in the current layout.
+- Nodes created before the layout change keep their legacy paths automatically
+  (a legacy directory takes precedence when present); new nodes use the
+  current layout.
+- A non-empty `ss-db-directory` or `evm-ss-db-directory` overrides the
+  corresponding default path.
 - SC data (`memiavl` + FlatKV) is untouched by this migration.
 
 ### Does Giga SS Store change the app hash or consensus?
 
@@ -63,20 +63,34 @@ timedatectl
 
 ##### Install Go
 
-Only needed if you build `seid` from source — the prebuilt binary and Docker
-install paths in the next step don't require Go.
+You need Go only if you build `seid` from source. The prebuilt binary and Docker
+install paths in the next step do not require it.
 
-Suggested Version: Go 1.24.x (required for seid v6.3+)
+Current `seid` releases require Go 1.25.6 or later. Check the `go.mod` at the release tag
+you check out
+(e.g. [`v6.6.1`](https://github.com/sei-protocol/sei-chain/blob/v6.6.1/go.mod)) for its
+exact requirement.
 
 ###### Installation Steps
 
 ```bash
-# Check for existing Go installation
+# Check for existing Go installations — more than one entry means another copy
+# may still win on your PATH after this install
+which -a go
 go version
 
-# Download and install Go 1.24.x
-wget https://go.dev/dl/go1.24.5.linux-amd64.tar.gz
-sudo tar -C /usr/local -xzf go1.24.5.linux-amd64.tar.gz
+# Bumping Go? Change these two lines only
+GO_TARBALL=go1.25.6.linux-amd64.tar.gz
+GO_SHA256=f022b6aad78e362bcba9b0b94d09ad58c5a70c6ba3b7582905fababf5fe0181a
+
+curl -fLO https://go.dev/dl/${GO_TARBALL}
+
+# Verify integrity before trusting the archive (go.dev/dl publishes a SHA256 per file
+# at ${GO_TARBALL}.sha256), then replace any previous installation — extracting over
+# one leaves stale files behind
+echo "${GO_SHA256}  ${GO_TARBALL}" | sha256sum -c - \
+  && sudo rm -rf /usr/local/go \
+  && sudo tar -C /usr/local -xzf ${GO_TARBALL}
 
 # Add Go to your environment variables
 echo 'export PATH=$PATH:/usr/local/go/bin' >> $HOME/.bashrc
@@ -85,6 +99,16 @@ source $HOME/.bashrc
 # Verify installation
 go version
 ```
+
+<Note>
+  `sudo rm -rf /usr/local/go` is the replacement step [Go's install
+  docs](https://go.dev/doc/install) prescribe, but it only clears a tarball install. A
+  package-manager Go (`/usr/lib/go-*`, Homebrew) survives it and can still shadow
+  `/usr/local/go/bin/go` — if the final `go version` reports the old release,
+  `which -a go` lists every copy on your `PATH`. If the extraction itself fails, the
+  verified tarball is still in your working directory: re-run the `sudo tar` command
+  rather than starting over.
+</Note>
 </Step>
 
 <Step title="Install Sei">
@@ -114,12 +138,10 @@ See the Network Versions table above for the current recommended version.
     ```
 
     <Info>
-      Prebuilt binaries are attached from `v6.6.1` onward — for earlier versions, build
-      from source or use Docker. They are `linux/amd64` only, omit hardware Ledger
-      support, and don't include the optional
-      [RocksDB state-store backend](/node/rocksdb-backend). On other architectures, or
-      if you sign with a Ledger device, build from source or use Docker; a
-      RocksDB-enabled `seid` must be built from source.
+      Prebuilt binaries are attached from `v6.6.1` onward. For earlier versions,
+      build from source or use Docker. They are `linux/amd64` only and omit hardware
+      Ledger support. On other architectures, or if you sign with a Ledger device,
+      build from source or use Docker.
     </Info>
 
     <Note>
@@ -408,8 +430,8 @@ seid query staking validator $(seid keys show <your_key> --bech val -a)
   <Card horizontal title="Configuration & Monitoring" icon="gauge-simple-high" href="/node/advanced-config-monitoring">
     Optimize your node's performance with advanced settings and monitoring tools.
   </Card>
-  <Card horizontal title="RocksDB Backend" icon="database" href="/node/rocksdb-backend">
-    Run with RocksDB instead of the default backend.
+  <Card horizontal title="Giga SS Store Migration" icon="database" href="/node/giga-storage-migration">
+    Move EVM historical state into dedicated state-store databases on supported RPC nodes.
   </Card>
   <Card horizontal title="Technical Reference" icon="terminal" href="/node/technical-reference">
     Detailed technical specifications, API endpoints, and commands for node operators.
 
@@ -2,7 +2,7 @@
 title: 'Sei Node Operations Guide'
 sidebarTitle: 'Overview'
 description: 'Detailed guide for running and maintaining Sei nodes. Learn about configuration management, database maintenance, service management, and update procedures.'
-keywords: ['sei node', 'blockchain node', 'node configuration', 'seidb', 'node maintenance', 'system operations']
+keywords: ['sei node', 'blockchain node', 'node configuration', 'seidb', 'node maintenance', 'system operations', 'rocksdb']
 ---
 
 This guide covers the detailed operational aspects of running a Sei node,
@@ -25,6 +25,15 @@ $HOME/.sei/config/
 └── priv_validator_key.json  # Validator private signing key (if running as a validator)
 ```
 
+The state-store databases live outside the config directory:
+
+- Cosmos SS uses `$HOME/.sei/data/{backend}` in the legacy layout and
+  `$HOME/.sei/data/state_store/cosmos/{backend}` in the current layout.
+- EVM SS uses `$HOME/.sei/data/evm_ss` in the legacy layout and
+  `$HOME/.sei/data/state_store/evm/{backend}` in the current layout.
+- Non-empty `ss-db-directory` and `evm-ss-db-directory` settings override
+  those locations.
+
 The snippets below are opinionated tuning recommendations layered on top of
 the defaults. For the *full* unmodified `app.toml`, `config.toml`, and
 `client.toml` shipped by the latest tagged `seid` release, jump to
@@ -91,6 +100,8 @@ sc-enable = true
 [state-store]
 # Historical SS layer for queries. Required for any node serving RPC.
 ss-enable = true
+# State-store backend. Use PebbleDB; RocksDB support will be removed.
+ss-backend = "pebbledb"
 # 0 = keep everything; 100,000 is roughly 28 hours of pacific-1 history.
 ss-keep-recent = 100000
 
@@ -115,6 +126,8 @@ The full unmodified `app.toml`, `config.toml`, and `client.toml` produced by
 `seid init` against the latest tagged `seid` release. Use these as the
 canonical reference for every available knob and its default value.
 
+<Warning>The generated `app.toml` below mirrors the latest tagged release and may still list RocksDB as a state-store option. Do not use RocksDB for new or resynced nodes. RocksDB support for the SeiDB state store will be removed. No target release has been published.</Warning>
+
 <Tabs>
   <Tab title="app.toml">
 
@@ -1429,9 +1442,8 @@ legacy single-database IAVL store with separate hot- and historical-data tiers:
    migration mode or `flatkv_only`.
 2. **State Store (SS)** — versioned raw key/value pairs used for historical
    queries. Required for any node that serves RPC. The default backend is
-   **PebbleDB**; **RocksDB** is available for iteration-heavy workloads such
-   as archive nodes or RPC nodes that run a lot of `debug_trace*` (see the
-   [RocksDB Backend Guide](/node/rocksdb-backend) for build instructions).
+   **PebbleDB**. Do not use RocksDB for new nodes. If you already use RocksDB,
+   follow [Move off RocksDB](#move-off-rocksdb) before support is removed.
 
 The legacy IAVL backend has been fully removed. Setting `sc-enable = false`
 makes the node panic at startup with `SeiDB state-commit (SC) must be
@@ -1487,7 +1499,7 @@ snapshot-keep-recent = 2
 # serving RPC must keep it on.
 ss-enable = true
 
-# pebbledb (default) or rocksdb (faster iteration, archive-friendly).
+# Use PebbleDB. RocksDB support will be removed.
 ss-backend = "pebbledb"
 
 ss-async-write-buffer = 100
@@ -1515,6 +1527,59 @@ Setting small (more frequent) pruning intervals may collide with
 snapshot creation. Too-large (less frequent) intervals mean pruning takes
 longer overall, which can cause missed blocks and excessive resync time.
 
+#### PebbleDB version encoding
+
+Fresh PebbleDB state stores use descending-version MVCC encoding. Sei includes
+the version in each key and sorts newer versions first. This lets
+latest-version reads reach the newest visible value without scanning older
+versions. The store records this format with the `s/_mvcc_descending` sentinel
+key, which `seid` detects automatically when it opens the database.
+
+PebbleDB state stores created by older builds use ascending-version encoding.
+`seid` detects these stores and opens them in compatibility mode without an
+error. They remain on the slower ascending read path. Rebuild the state store
+through [state sync](/node/statesync) with a current `seid` release to adopt
+descending encoding. A filesystem snapshot preserves the source store's
+encoding, so confirm its encoding with the snapshot provider.
+
+### Move off RocksDB
+
+<Warning>RocksDB support for the SeiDB state store will be removed. No target release has been published. Check the [Sei release notes](https://github.com/sei-protocol/sei-chain/releases) before every upgrade.</Warning>
+
+RocksDB and PebbleDB use different on-disk formats. Changing
+`ss-backend = "rocksdb"` to `ss-backend = "pebbledb"` against the same data
+does not convert the store. Rebuild the state store instead.
+
+For a non-archive node:
+
+1. Stop `seid` and back up the validator key, validator state, node key,
+   configuration, and genesis file that you need to preserve.
+2. Check `ss-db-directory` and `evm-ss-db-directory` in `app.toml`. An empty
+   value uses a path under `$HOME/.sei/data`. If either setting points
+   elsewhere, move the old RocksDB data out of the active path and keep it
+   with the backup. Clearing `$HOME/.sei/data` does not clear a custom
+   directory.
+3. Set `ss-backend = "pebbledb"`, then rebuild through
+   [state sync](/node/statesync) or a provider-confirmed
+   [PebbleDB snapshot](/node/snapshot).
+4. Confirm the startup log reports `"SeiDB SS is enabled"` with the PebbleDB
+   backend. Test the RPC methods your node serves before you delete the old
+   RocksDB backup.
+
+<Danger>Do not use state sync or a pruned snapshot to migrate an archive node. Both start from a recent height and discard the earlier state-store versions that an archive node must retain.</Danger>
+
+There is no documented in-place migration for a RocksDB archive node. Build a
+separate replacement from a trusted full-history PebbleDB source. Keep the
+RocksDB node on a compatible `seid` release until the replacement has caught
+up and you have tested historical queries at old heights. If you cannot obtain
+a full-history PebbleDB source, do not wipe the existing archive data. Contact
+the [Sei Tech Chat](https://t.me/+KZdhZ1eE-G01NmZk) before you upgrade.
+
+PebbleDB can be slower for iteration-heavy historical queries, including
+`debug_trace*` requests. Descending-version encoding improves recent reads,
+but it does not remove the cost of long-history iteration. Benchmark the
+replacement under your trace workload before you cut over.
+
 ### Giga Storage and Giga Executor
 
 These are two **separate** opt-in features that ship in newer `seid`