chore: bump sei-config v0.0.16 → v0.0.17 (atlantic-2 mint genesis fix)#191
Conversation
Picks up sei-config #23, which translates atlantic-2's embedded mint genesis from the legacy Version2Minter schema to v3 so the v6.5.0 seid binary can load it via mint.InitGenesis (the prior v2 schema panicked: cannot unmarshal "0.000000000000000000" into uint64). Verified against seid v6.5.0: the corrected atlantic-2 genesis boots through InitChain and begins block-sync from height 1. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
PR SummaryMedium Risk Overview The new Rollout: deploying this image updates genesis only on fresh configure-genesis runs—existing Retain PVCs keep on-disk genesis until manually refreshed. Reviewed by Cursor Bugbot for commit fab04d7. Bugbot is set up for automated code reviews on this repo. Configure here. |
Summary
sei-configdependency v0.0.16 → v0.0.17, picking up sei-config #23.version.jsonv0.0.52 → v0.0.53.Why
sei-config #23 translates atlantic-2's embedded mint genesis from the legacy
Version2Minterschema to v3. The prior v2 schema (last_mint_amount: "0.000000000000000000", a Decimal) panicked v6.5.0'smint.InitGenesis:This blocked the atlantic-2 archive (which block-syncs from genesis and therefore exercises InitGenesis, unlike state-syncing nodes).
Verification
Ran the corrected genesis through the actual v6.5.0 binary (
seid init+seid start): InitChain completes,ABCI Replay Blocksproceeds, node reaches height 1 and begins block-sync. No panic.Rollout note
Bumping
SEI_SIDECAR_IMAGEto this seictl release will not rewrite genesis on already-bootstrapped Retain PVCs (the configure-genesis marker skips re-writes — see #190, closed won't-fix). The atlantic-2 archive's on-disk genesis will be refreshed manually as part of the rollout.Test plan
SEI_SIDECAR_IMAGEin platform overlaysarchive-0-0-0boots pastmint.InitGenesisand block-syncs🤖 Generated with Claude Code