ChihuahuaChain/chihuahua v10.0.0

on GitHub

Upgrade height: 25586332, expected around 2026-10-03 14:07 UTC (countdown).

This proposal is expedited (24-hour voting period). For technical reasons, v10.0.0 needs to be applied sooner than the usual governance timeline allows. We apologise to validators and delegators for the short notice: more details will be shared after the upgrade.

What v10 brings

v10 moves Chihuahua to the current Cosmos stack:

On-chain burn counter

The fees burned by x/feeburn are now counted on chain. The total starts from the figure published on burn.chihuahua.wtf and grows with every transaction:

chihuahuad q feeburn total-burned

REST: /chihuahua/feeburn/total_burned.

CosmWasm 3 and IBC v11

• Contracts run on wasmvm v3. The CosmWasm capabilities go up to cosmwasm_2_2, plus ibc2 for IBC v2.
• ibc-go v11 brings IBC v2 support. IBC denom traces are migrated to the new denom format: ibc/... denoms and balances don't change.
• New ante decorators: CosmWasm simulation gas limit, transaction counter, gas register, and the IBC redundant relay check.

A leaner chain

Modules with no use left on Chihuahua are removed and their state is cleared:

• alliance (retired in v9.5.0)
• capability and the IBC fee middleware (ICS-29): removed from ibc-go
• crisis, nft, circuit: unused on Chihuahua
• params: every module manages its own parameters

Historical governance proposals that used them can still be queried.

Maintained by Chihuahua

• x/liquidity, previously an external dependency, now lives in the Chihuahua repository.
• x/group stays under Apache-2.0: Chihuahua keeps its own copy, and the existing groups keep working unchanged.
• x/ibc-hooks, ported to the new store.
• And a new command: chihuahuad bark.

For integrators and contract developers

• The IBC transfer query DenomTrace no longer exists in ibc-go: use Denom (/ibc.applications.transfer.v1.Query/Denom). Contracts using the DenomTrace stargate query must switch to Denom.
• The REST and gRPC endpoints of the removed modules are gone.

For validators

• Remove --x-crisis-skip-assert-invariants from your start command, if present: v10 no longer accepts it.
• app.toml and config.toml from v9 keep working.
• The first calls to each contract after the upgrade are slower while wasmvm v3 recompiles it. The old *-wasmer7 cache can be deleted once the node runs v10.

The upgrade proposal carries the release binaries (linux/amd64, linux/arm64) with their sha256. With cosmovisor v1.7, set in the service environment:

Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=true"
Environment="DAEMON_RESTART_AFTER_UPGRADE=true"
Environment="DAEMON_SHUTDOWN_GRACE=30s"

Keep node in ~/.chihuahuad/config/client.toml pointed at your node's RPC. With the Huahua Node Manager: huahua-node upgrade once the proposal has passed.

Upgrade notes: https://github.com/ChihuahuaChain/chihuahua/blob/main/mainnet/UPGRADES/v10.0.0/README.md