sei-protocol/sei-chain v6.7.1 on GitHub

ℹ️ This is not a mandatory upgrade, but we ask all pacific-1 validators and node operators to update to v6.7.1 before the FlatKV migration starts (~17:00 UTC on 9 October 2026, when the migration proposal passes). atlantic-2 has already migrated, so operators there can update at their convenience. There is no governance proposal and no coordinated chain halt for this update.

v6.7.1 is a patch release on top of v6.7.0. It has eight fixes and one removal. Most fixes are for the EVM migration, which moves EVM state from memIAVL to FlatKV. Other fixes make state sync and seid rollback safer. v6.7.1 also removes the deprecated seid export command.

🎯 Who Should Update


🛡️ Validators	Requested before the migration on `pacific-1`. `v6.7.1` fixes data races and rollback problems in the state commit store.
🖥️ RPC, full and archive nodes	Requested before the migration on `pacific-1`. `v6.7.1` also fixes wrong contract nonces in the state store after state sync.
🌐 Networks	`pacific-1` before the migration starts. `atlantic-2` at your convenience.
⏱️ Downtime	The node stops only for one restart. There is no coordinated halt.
🔗 Compatibility	There are no consensus-breaking changes, and the AppHash does not change. Nodes on `v6.7.0` and `v6.7.1` stay in consensus, so `v6.7.0` nodes do not halt, but they do not get the fixes below.

⚠️ Check Before You Update

v6.7.1 removes seid export. Make sure that your scripts and tools do not use seid export. seid init, collect-gentxs and genesis import do not change (#4489).
Check pinned write modes. This applies only if you set sc-write-mode-enable-auto = false and pin sc-write-mode to evm_migrated, all_migrated_but_bank or flatkv_only. If the pinned mode does not agree with the migration state on disk, the node does not start. Before, the node started and then diverged from the network. To correct this, set sc-write-mode-enable-auto = true in the [state-commit] section of app.toml (#4503).

✅ How to Update

If your node has not reached the `v6.7` upgrade height

You can use v6.7.1 for the v6.7 upgrade instead of v6.7.0. On pacific-1, the upgrade height is 236450000 (proposal #125). Before the upgrade, do the checks in the v6.7.0 release notes.

Build v6.7.1 with git fetch --tags && git checkout v6.7.1 && make install. You can also use a pre-built binary below.
Do not stop the node or start v6.7.1 before the upgrade height.
When the chain halts at the upgrade height, replace the seid binary with v6.7.1.
Start the node.
Make sure that the node syncs new blocks after the upgrade height.

💡 Cosmovisor users: To use v6.7.1 for the upgrade, put the v6.7.1 binary in upgrades/v6.7/bin/ before the upgrade height. If a v6.7.0 binary is already there, replace it with v6.7.1. Cosmovisor changes the binary at the upgrade height.

You can also do the upgrade with v6.7.0, then update to v6.7.1 with the steps in the next section.

If your node runs `v6.7.0`

Build v6.7.1 with git fetch --tags && git checkout v6.7.1 && make install.
Stop the node.
Replace the seid binary with v6.7.1. If you use Cosmovisor, replace the binary in upgrades/v6.7/bin/.
Start the node.
Make sure that seid version shows v6.7.1.
Make sure that the node syncs new blocks.

💡 State sync during the EVM migration: If the node did a state sync during the EVM migration, do a state sync again after you update. The earlier state sync can leave nonce 0 for some contracts in the state store. The update does not correct these values. On atlantic-2, the EVM migration ran from 1 to 2 October 2026.

What's Changed

Backport release/v6.7: fix(seidb): keep the memIAVL nonce when state sync restores a mid-mig… by @seidroid[bot] in #4465
Backport release/v6.7: Make the composite store router an atomic pointer by @seidroid[bot] in #4473
Backport release/v6.7: Re-derive the composite write mode on rollback by @seidroid[bot] in #4486
Backport release/v6.7: Validate module names in the memiavl snapshot importer by @seidroid[bot] in #4474
Backport release/v6.7: Remove genesis export by @seidroid[bot] in #4489
Backport release/v6.7: Make the composite store flatKV and write mode atomic by @seidroid[bot] in #4485
Backport release/v6.7: Resolve composite iteration duplicates to memiavl, matching Read by @seidroid[bot] in #4499
Backport release/v6.7: Refuse pinned write modes that disagree with persisted migration by @seidroid[bot] in #4503
Backport release/v6.7: Guard FlatKV rollback floor by @seidroid[bot] in #4502
Backport release/v6.7: Update v6.7 change log in prep to cut v6.7.1 patch by @seidroid[bot] in #4506
Bump version to v6.7.1 in prep for patch release by @alexander-sei in #4482

Full Changelog: v6.7.0...v6.7.1

Experimental Pre-built Binaries

Pre-built statically-linked seid binaries attached below for linux/amd64
and linux/arm64.

Verify your download:

sha256sum -c checksums.txt --ignore-missing

For Docker images, see ghcr.io/sei-protocol/sei.