ℹ️ This is not a mandatory upgrade, but we recommend that all
pacific-1andatlantic-2validators and node operators update tov6.7.3. There is no governance proposal and no coordinated chain halt for this update.
v6.7.3 is a patch release on top of v6.7.2. It moves the state sync trust period from config.toml into seid, so every node on a network uses the same value. The trust period must stay shorter than the unbonding time. With the value built into the binary, the network can shorten its unbonding time without every operator editing config.toml.
⚠️ Check Before You Update
seidnow ignorestrust-periodin the[statesync]section ofconfig.toml. State sync uses a trust period of 112 hours onpacific-1,atlantic-2andarctic-1. Ifconfig.tomlsetstrust-periodto another value,seid startlogs a warning that begins withstatesync.trust-period is set in config.tomleach time the node starts. Earlierseidversions wrotetrust-period = "168h0m0s"intoconfig.toml, so most nodes will log this warning. To stop it, remove thetrust-periodline. The node runs normally with or without the line (#4690).- If you use state sync, use a recent trust height. The block at
trust-heightmust be less than 112 hours old. If it is older, state sync fails withold header has expired. Beforev6.7.3, the limit was thetrust-periodvalue, which was 168 hours by default.
✅ How to Update
- Build
v6.7.3withgit fetch --tags && git checkout v6.7.3 && make install. - Stop the node.
- Replace the
seidbinary withv6.7.3. If you use Cosmovisor, replace the binary inupgrades/v6.7/bin/. - Optional: remove the
trust-periodline from the[statesync]section ofconfig.toml. - Start the node.
- Make sure that
seid versionshowsv6.7.3. - Make sure that the node syncs new blocks.
What's Changed
- Backport
release/v6.7: Hard-code the state sync trust period per chain by @seidroid[bot] in #4690 - Backport deterministic simulation limiter test fix to v6.7 by @masih in #4702
Full Changelog: v6.7.2...v6.7.3
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.