Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions node/giga-storage-migration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -20,8 +20,6 @@
This migration changes only the **SS** layer. It does not change the SC layer or
the app hash, so the change is invisible to the network.

<Info>This guide follows the canonical procedure in the `sei-chain` repository: [`docs/migration/giga_store_migration.md`](https://github.com/sei-protocol/sei-chain/blob/main/docs/migration/giga_store_migration.md). If anything here drifts, open an issue there.</Info>

## Prerequisites

<Warning>Run this migration on **RPC nodes only**. This flow does not support validator nodes or archive nodes yet, so do not run it against either.</Warning>
Expand Down Expand Up @@ -192,7 +190,7 @@

<Warning>To roll back cleanly to `evm-ss-split = false`, run another state sync. Under `evm-ss-split = true`, EVM writes go only to the EVM SS DB, so Cosmos SS does not have those writes. If you restart with `evm-ss-split = false`, the node stops opening the EVM SS DB. However, EVM-state queries miss anything written after the Giga state sync until you run state sync again without the split.</Warning>

## FlatKV EVM SC migration flow

Check warning on line 193 in node/giga-storage-migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/giga-storage-migration.mdx#L193

Use sentence case for headings: 'FlatKV EVM SC migration flow'.

Everything above concerns the **SS** (State Store) layer. The **SC** (State
Commit) layer has a separate migration path. It moves the hot `evm/` data out
Expand Down Expand Up @@ -308,7 +306,7 @@
command creates. The store has no migration metadata, so the node starts in
`memiavl_only`.

## FAQ

Check warning on line 309 in node/giga-storage-migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/giga-storage-migration.mdx#L309

Use sentence case for headings: 'FAQ'.

### Where do the data files live after migrating?

Expand All @@ -323,7 +321,7 @@
corresponding default path.
- This migration does not change SC data (`memiavl` and FlatKV).

### Does Giga SS Store change the app hash or consensus?

Check warning on line 324 in node/giga-storage-migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/giga-storage-migration.mdx#L324

Use sentence case for headings: 'Does Giga SS Store change the app hash or consensus?'.

No. Giga SS Store changes only the SS layer, which does not affect the app hash.
It is a per-node change that is invisible to the network.
Expand All @@ -349,12 +347,12 @@
missing EVM state at query time. The safety checks above block this scenario at
startup.

### Does Giga SS Store support historical proofs?

Check warning on line 350 in node/giga-storage-migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/giga-storage-migration.mdx#L350

Use sentence case for headings: 'Does Giga SS Store support historical proofs?'.

No, and neither does SeiDB. SS stores raw KVs and does not reconstruct
IAVL-style proofs.

### Does enabling Giga Storage change the receipt backend?

Check warning on line 355 in node/giga-storage-migration.mdx

View check run for this annotation

Mintlify / Mintlify Validation (seilabs) - vale-spellcheck

node/giga-storage-migration.mdx#L355

Use sentence case for headings: 'Does enabling Giga Storage change the receipt backend?'.

In the `localnode` and `rpcnode` configuration scripts, setting
`GIGA_STORAGE=true` defaults `RECEIPT_BACKEND` to `pebble` unless you set
Expand Down
Loading