Add giga.storage.receipts to toggle the Autobahn receipt store

[masih]

On an Autobahn node the receipt store is always open: AutobahnStorageConfig applies validator mode and then re-enables receipts, because the node's EVM-only RPC serves eth_getTransactionReceipt, eth_getLogs, eth_feeHistory and block encodings from it. [giga.storage] mode therefore only decides whether the state store opens, and there is no way to run a validator that neither serves EVM queries nor pays for the receipt store, nor to see from app.toml that receipts are on at all.

This adds receipts = true|false to [giga.storage], defaulting to true so every existing layout is unchanged. buildGigaStorageConfig applies it after mode selection, so mode and receipts compose freely (validator + receipts is today's default; full + no receipts is state store only). When the store is disabled the node logs that and does not start the EVM-only RPC, since every registered namespace reads the store; the storage manager already returns a nil ReceiptDB() in that case. The executor's store-backed path also required a receipt store, so it now treats it as optional and skips SetReceipts when none is configured; otherwise a receipt-less node could open but never finalize a block. Tests cover the new key in the reader and registry, the composed layouts in buildGigaStorageConfig, that prepareApplication opens no receipt store when the flag is off, and that the EVM-only application finalizes and commits a block carrying a transaction without one.

Turning receipts off and later on again would leave a receipt head well below the block and state heads, which recovery takes as the convergence height and either rewinds state or refuses to start, and receipt lag alone cannot tell that off period from a crash with async receipt writes still queued. So the transition is refused up front: OpenDBWithRecovery fails with an actionable error when receipts are disabled while the store on disk holds receipts, telling the operator to move the directory away or enable receipts again. Nothing is deleted automatically; a store that was opened but never written does not block the switch. The key's documentation says so.

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[github-actions]

The latest Buf updates on your PR. Results from workflow Buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Sep 25, 2026, 3:20 PM

[codecov]

Codecov Report

❌ Patch coverage is 71.42857% with 8 lines in your changes missing coverage. Please review.
✅ Project coverage is 66.49%. Comparing base (b9f0e8f) to head (6235848).
⚠️ Report is 4 commits behind head on main.

Files with missing lines	Patch %	Lines
sei-tendermint/node/node.go	0.00%	6 Missing ⚠️
giga/evmonly/giga_store.go	83.33%	1 Missing ⚠️
sei-db/bootstrap/recovery.go	90.90%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4333      +/-   ##
==========================================
- Coverage   67.58%   66.49%   -1.09%     
==========================================
  Files        2190     2069     -121     
  Lines      168242   156250   -11992     
==========================================
- Hits       113708   103900    -9808     
+ Misses      54524    52340    -2184     
  Partials       10       10              

Flag	Coverage Δ
sei-chain-pr	84.64% <71.42%> (?)
sei-db	74.50% <ø> (ø)
sei-db-state-db	?

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
giga/config/config.go	82.60% <100.00%> (+1.07%)	⬆️
sei-tendermint/node/setup.go	67.14% <100.00%> (+0.07%)	⬆️
giga/evmonly/giga_store.go	96.51% <83.33%> (+1.42%)	⬆️
sei-db/bootstrap/recovery.go	88.17% <90.90%> (+0.36%)	⬆️
sei-tendermint/node/node.go	75.00% <0.00%> (-0.33%)	⬇️

... and 121 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[cursor]

PR Summary

Medium Risk
Changes startup recovery, block finalization without receipts, and RPC availability—operators disabling receipts with stale on-disk data get a hard startup failure by design.

Overview
Adds giga.storage.receipts (default true) so operators can turn the receipt store off independently of giga.storage.mode. buildGigaStorageConfig sets ReceiptDBConfig.Enable from this flag; validator + no receipts and full + receipts are both valid combinations.

When receipts are disabled, the node does not start the EVM-only RPC (it depends on the store), and store-backed execution commits state without calling SetReceipts if no receipt store is configured—so blocks can still finalize. Startup refuses to run with receipts off while the receipt directory still has history (ErrReceiptStoreDisabledWithHistory), directing the operator to move the directory or re-enable receipts.

Config reading, app.toml template, registry keys, and tests cover the new setting, composed layouts, recovery guard, and an EVM-only app path without a receipt store.

^{Reviewed by Cursor Bugbot for commit 6235848. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 26277da. Configure here.}

[seidroid]

The new giga.storage.receipts key is read, templated and tested correctly, but setting it to false stops the node from finalizing any block. The evmonly executor still requires a receipt store and returns an error when it is missing.

Findings: 1 blocking | 1 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.
• 1 blocking issue(s) flagged inline on specific lines.

Non-blocking

• [suggestion] TestPrepareApplicationReceiptsOffOpensNoReceiptStore only checks that ReceiptDB() is nil after construction. Add a test that runs InitChain and finalizes at least one block (even an empty one) with receipts disabled. That test would have caught the executor failure, and it is the behaviour the new flag needs to guarantee.

[masih]

@seidroid review

[seidroid]

The previous blocker is fixed: the executor now treats the receipt store as optional, and a test now finalizes and commits a block without one. One new problem comes from exposing the toggle. If an operator turns receipts off and later back on, the old receipt head drags the startup recovery target down, which can roll state back a long way or stop the node from starting.

Findings: 1 blocking | 0 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.
• 1 blocking issue(s) flagged inline on specific lines.

Non-blocking

• None at the file/PR level.

[masih]

@seidroid review

[seidroid]

The earlier problem is fixed: turning receipts off and back on for longer than rollback_window no longer rolls state back or stops the node from starting. But the fix treats "more than rollback_window behind" as "receipts were disabled". With a small or zero window, an ordinary crash, where the async receipt queue simply lags, now deletes the whole receipt store.

Findings: 1 blocking | 1 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.
• 1 blocking issue(s) flagged inline on specific lines.

Non-blocking

• [suggestion] The in-window half of the previous on → off → on finding is still there. If receipts are off for fewer than rollback_window blocks (default 1000) and then turned back on, recoveryTarget still uses the old receipt head as the target, so recovery still silently rolls block and state stores back by up to that many blocks. If this is intended, document it on the receipts key. If not, fix it with the same explicit marker suggested inline, and add a restart test for a short off stretch.

[masih]

@seidroid review

[seidroid]

The PR adds a giga.storage.receipts toggle. Every earlier finding is fixed: the executor now runs without a receipt store, and startup refuses to run with receipts disabled while the receipt directory still holds data, so there is no stale-head recovery and no automatic deletion. I found no new issues.

Findings: 0 blocking | 0 non-blocking | 0 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• None at the file/PR level.

Superseded: latest AI review found no blocking issues.