Remove crisis module code and store by codchen · Pull Request #3510 · sei-protocol/sei-chain

codchen · 2026-05-27T03:15:38Z

Summary

remove x/crisis from the Sei app wiring and delete the sei-cosmos/x/crisis module plus its crisis protobuf definitions
remove stale crisis wiring from wasmd/simapp test harnesses, local genesis setup, state-dump tooling, and module lists
confirmed crisis does not have a dedicated rootmulti KVStore: its former state was params-subspace data under the params store, so this PR does not add a StoreUpgrades deletion for crisis

Test Plan

go test ./app
go test ./app ./app/legacyabci ./cmd/seid/cmd ./sei-wasmd/app ./sei-wasmd/x/wasm/keeper ./sei-ibc-go/testing/simapp/... ./sei-db/tools/cmd/seidb/operations
4-node Docker upgrade test: started the pre-removal parent binary 5ac709d, let the chain run, passed the software upgrade at height 306, restarted all validators on the crisis-deletion binary, and verified all nodes reached height 366 with catching_up=false and matching app hash 60C93CD1D72AD425D3FD862D115D722B098FEC48A28FD795C466807403F4648A

Drop x/crisis from the Sei app module manager, init-genesis order, end blocker, invariant registration, init flags, and app-owned keeper state. Crisis has no dedicated mounted KV store in app/app.go, so the rootmulti store key list is unchanged. Also decouple crisis package tests from the full app now that App no longer exposes CrisisKeeper. Tested with: go test ./app ./app/legacyabci ./cmd/seid/cmd ./sei-cosmos/x/crisis/... Upgrade tested with a 4-node Docker cluster: started from the pre-removal binary, passed software upgrade v99.0.1-crisis-removal at height 342, restarted all validators on the removal binary, and verified all nodes reached height 514 with catching_up=false and matching app hash A53F9F78B05C8F6C07247186EF5BFB89D5BCFE7535AE52E54895B57E1844485E.

cursor · 2026-05-27T03:16:22Z

PR Summary

High Risk
Drops runtime and export invariant checks and requires a coordinated upgrade to delete the crisis store; mis-handled upgrades or lingering genesis references could break nodes.

Overview
This PR removes the Cosmos x/crisis module from Sei and from vendored sei-cosmos: the keeper, module manager wiring, end-block invariant checks, genesis/export invariant assertions, CLI flags (x-crisis-skip-assert-invariants), protos, and the whole sei-cosmos/x/crisis tree are deleted.

The main app, legacyabci, export, seid, wasmd, and IBC simapp no longer register crisis, pass invCheckPeriod, or call RegisterInvariants / AssertInvariants. Local genesis and state-dump / seidb module lists drop crisis. Docs in sei-cosmos/x/README no longer list crisis.

Operational impact: periodic and export-time invariant enforcement that could panic the chain is gone; operators lose crisis invariant-broken and related genesis tuning unless handled elsewhere in an upgrade (per PR notes, the on-chain crisis KV store is removed at upgrade height).

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

github-actions · 2026-05-27T03:17:16Z

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

Build	Format	Lint	Breaking	Updated (UTC)
`✅ passed`	`✅ passed`	`✅ passed`	`✅ passed`	May 29, 2026, 3:44 AM

codecov · 2026-05-27T03:19:13Z

Codecov Report

❌ Patch coverage is 33.33333% with 2 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.25%. Comparing base (5ac709d) to head (0001bf8).
⚠️ Report is 47 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/seid/cmd/root.go	0.00%	1 Missing ⚠️
sei-ibc-go/testing/simapp/app.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3510      +/-   ##
==========================================
- Coverage   59.30%   59.25%   -0.06%     
==========================================
  Files        2127     2129       +2     
  Lines      175876   176767     +891     
==========================================
+ Hits       104305   104745     +440     
- Misses      62473    62888     +415     
- Partials     9098     9134      +36

Flag	Coverage Δ
sei-chain-pr	`49.45% <33.33%> (?)`
sei-db	`70.41% <ø> (ø)`

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

Files with missing lines	Coverage Δ
app/app.go	`64.69% <ø> (-4.71%)`	⬇️
app/export.go	`0.00% <ø> (ø)`
app/legacyabci/end_block.go	`100.00% <ø> (ø)`
sei-ibc-go/testing/simapp/export.go	`0.00% <ø> (ø)`
sei-ibc-go/testing/simapp/simd/cmd/root.go	`66.87% <100.00%> (-0.21%)`	⬇️
sei-wasmd/app/app.go	`84.07% <ø> (-0.51%)`	⬇️
sei-wasmd/app/export.go	`12.24% <ø> (+0.12%)`	⬆️
cmd/seid/cmd/root.go	`25.09% <0.00%> (+0.09%)`	⬆️
sei-ibc-go/testing/simapp/app.go	`76.31% <0.00%> (-1.08%)`	⬇️

... and 12 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.

masih · 2026-05-28T11:03:45Z

@@ -170,8 +169,7 @@ func initRootCmd(rootCmd *cobra.Command, encodingConfig params.EncodingConfig) {
 	rootCmd.AddCommand(server.RosettaCommand(encodingConfig.InterfaceRegistry, encodingConfig.Marshaler))
 }

-func addModuleInitFlags(startCmd *cobra.Command) {
-	crisis.AddModuleInitFlags(startCmd)


This would break the startup for anyone setting the flag.

Perhaps a more graceful approach is to print a WARNING saying this is noop, and flag will be removed in the next release.

Alternatively a more meaningful fatal error to point them to some TBD comms (e.g. release notes) that would explain the module removal).

masih · 2026-05-28T11:10:23Z

 		app.SetStoreLoader(upgradetypes.UpgradeStoreLoader(upgradeInfo.Height, &storeUpgrades))
 	}
+
+	if (upgradeInfo.Name == "v6.6.0") && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {


Going forward since v6.5, upgrade names will follow v<major>.<minor> format. No more repetitive .0 suffix.

Suggested change

if (upgradeInfo.Name == "v6.6.0") && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {

if (upgradeInfo.Name == "v6.6") && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {

masih · 2026-05-28T11:20:20Z

 		}
 	}
 	app.UpgradeKeeper.SetModuleVersionMap(ctx, app.mm.GetVersionMap())
 	return app.mm.InitGenesis(ctx, app.appCodec, genesisState, app.genesisImportConfig)


Genesis JSON import skips over unknown module names. but streaming genesis would i think panic because it seem to directly index modules by name and proceed to initialise.

If I haven't missed anything, we would then need to skip over removed modules here.

masih · 2026-05-28T14:05:02Z

+
+	if (upgradeInfo.Name == "v6.6.0") && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {
+		storeUpgrades := storetypes.StoreUpgrades{
+			Deleted: []string{crisisStoreKeyName},


But there is no such key name and this would result in an error i believe.

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 0001bf8. Configure here.}

cursor · 2026-05-29T03:46:30Z

 		EvmKeeper:        &app.EvmKeeper,
 	}
 	app.EndBlockKeepers = legacyabci.EndBlockKeepers{
-		CrisisKeeper:  &app.CrisisKeeper,


Streaming genesis panics on removed crisis module data

High Severity

Removing crisis from the module manager causes a nil-pointer panic in streaming genesis import. The streaming genesis path in the module manager directly indexes m.Modules[moduleName].InitGenesis(...) without checking existence. The existing chain genesis JSONs (arctic-1, atlantic-2, pacific-1) still contain "crisis" entries, so any node bootstrapping via streaming genesis from these files will panic when m.Modules["crisis"] returns nil. The non-streaming path safely skips unknown modules, but the streaming path does not.

^{Reviewed by Cursor Bugbot for commit 0001bf8. Configure here.}

philipsu522

In the past, when updating some fields for modules I believe we saw some incompatibilities. For this particular PR, in the genesis file we see:
https://github.com/sei-protocol/chain-configs/blob/main/pacific-1/genesis.json#L715

We should probably test workflows like state sync'ing with the new binary and the genesis file

codchen added the app-hash-breaking label May 27, 2026

Remove crisis module code and store

f76f011

codchen changed the title ~~Remove crisis module from app wiring~~ Remove crisis module code and store May 28, 2026

cursor Bot reviewed May 28, 2026

View reviewed changes

Comment thread app/app.go Outdated

Set crisis removal upgrade to v6.6.0

4972f18

masih reviewed May 28, 2026

View reviewed changes

Remove crisis store deletion hook

0001bf8

cursor Bot reviewed May 29, 2026

View reviewed changes

philipsu522 approved these changes May 29, 2026

View reviewed changes

philipsu522 reviewed May 29, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Remove crisis module code and store#3510

Remove crisis module code and store#3510
codchen wants to merge 4 commits into
mainfrom
codex/remove-crisis-app-module

codchen commented May 27, 2026 •

edited

Loading

Uh oh!

cursor Bot commented May 27, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented May 27, 2026 •

edited

Loading

Uh oh!

codecov Bot commented May 27, 2026 •

edited

Loading

Uh oh!

Uh oh!

masih May 28, 2026

Uh oh!

masih May 28, 2026

Uh oh!

masih May 28, 2026

Uh oh!

masih May 28, 2026

Uh oh!

cursor Bot left a comment

Uh oh!

cursor Bot May 29, 2026

Uh oh!

philipsu522 left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

	if (upgradeInfo.Name == "v6.6.0") && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {
	if (upgradeInfo.Name == "v6.6") && !app.UpgradeKeeper.IsSkipHeight(upgradeInfo.Height) {

Conversation

codchen commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test Plan

Uh oh!

cursor Bot commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

PR Summary

Uh oh!

github-actions Bot commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented May 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

Uh oh!

masih May 28, 2026

Choose a reason for hiding this comment

Uh oh!

masih May 28, 2026

Choose a reason for hiding this comment

Uh oh!

masih May 28, 2026

Choose a reason for hiding this comment

Uh oh!

masih May 28, 2026

Choose a reason for hiding this comment

Uh oh!

cursor Bot left a comment

Choose a reason for hiding this comment

Uh oh!

cursor Bot May 29, 2026

Choose a reason for hiding this comment

Streaming genesis panics on removed crisis module data

Uh oh!

philipsu522 left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

codchen commented May 27, 2026 •

edited

Loading

cursor Bot commented May 27, 2026 •

edited

Loading

github-actions Bot commented May 27, 2026 •

edited

Loading

codecov Bot commented May 27, 2026 •

edited

Loading