Coin Brief ENDE

Cosmos SDK retracts v0.55.0 and v0.54.0-0.54.4 over fee grant entries that fail on expiry

The Cosmos SDK team released v0.55.1 and v0.54.5 on 14 November and retracted earlier versions on both lines. According to the release notes, v0.55.0 and v0.54.0 to v0.54.4 are retracted, and chains on the 0.54 line can move to v0.54.5 instead. Both new releases are state breaking and require a coordinated chain upgrade.

The reason is a bug in the fee allowance expiry queue of the x/feegrant module. Chains that upgraded from v0.53.x or earlier can hold entries in the fee allowance expiry queue that are stored with an empty value. The keeper cannot decode such an entry, so the module's EndBlocker returns an error at the first block after one of those grants expires. The new releases add a store migration, raising the module's consensus version from 2 to 3, which rewrites the affected entries. It runs through RunMigrations in the chain's upgrade handler.

The notes are specific about who is exposed. A chain is affected if it upgraded from v0.53.x or earlier and still has unexpired fee grants with an expiration date that were created before that upgrade. Such chains must run the migration before the earliest of those grants expires. Chains that started on v0.54 or later are not affected. The upgrading guide explains how to check a chain.

v0.55.1 is otherwise a small patch release. It moves to IAVL v1.2.9, in which importing a malformed snapshot returns an error instead of panicking, and to Go 1.26.11 with patched versions of dependencies including klauspost/compress, grpc, golang.org/x, pion and OpenTelemetry. v0.54.5 adds the same feegrant migration as a backport, plus a bump of the Ledger library.

The release appears alongside a governance vote on the Cosmos Hub to fix broken governance queries, which The Defiant reported on 14 November.

Cosmos SDK retracts v0.55.0 and v0.54.0-0.54.4 over fee grant entries that fail on expiry
Cosmos SDK retracts v0.55.0 and v0.54.0-0.54.4 over fee grant entries that fail on expiry — Coin Brief

Why it matters

The failure mode is a time bomb: nothing goes wrong until a specific grant reaches its expiry, and then the module's end-of-block logic returns an error. Because the deadline is set by data already on each chain, every validator set built on an affected version has to find its earliest qualifying grant and schedule the upgrade before that date, not at its convenience.

Written by Victoria Shinder.