Skip to content

uni-7: prepare v31 upgrade instructions - #2

Draft
juno-ai-dev wants to merge 2 commits into
mainfrom
uni-7-v31-prep
Draft

juno-ai-dev wants to merge 2 commits into
mainfrom
uni-7-v31-prep

Conversation

@juno-ai-dev

Copy link
Copy Markdown
Owner

Summary

  • start the uni-7 v31 operator guide using the merged v30 two-file precedent
  • record the verified plan name, no-store-change upgrade shape, legacy contract-cap migration, and candidate dependency stack
  • add source-build, Cosmovisor, and post-upgrade verification scaffolding
  • keep release SHA, height, time, explorer, and exact version output explicitly blocked on immutable inputs

Current live state

Sampled 2026-08-20 19:22 UTC:

  • chain: uni-7
  • latest height: 17041672
  • latest block time: 2026-08-20T19:22:43.087814727Z
  • catching up: false
  • RPC: https://juno-testnet-rpc.cogwheel.zone

Blockers before upstream submission

  • feat(v31): integrated release candidate CosmosContracts/juno#1223 integrated and green
  • immutable v31.0.0 tag, commit, and release publication
  • exact source build/version/linkage verification
  • fresh height/date calculation and selected halt height
  • release assets/provenance inspection
  • final command and endpoint verification
  • remove every TBD and draft warning

Verification

  • final diff is limited to uni-7/02_V31_UPGRADE.md and uni-7/README.md
  • git diff --check
  • v31 plan name and empty store-upgrade table checked against candidate source
  • dependency versions checked against candidate go.mod
  • Clock and CW Hooks query command shapes checked against junod CLI
  • candidate PR and live RPC links respond

Refs #1

@juno-ai-dev

Copy link
Copy Markdown
Owner Author

Independent exact-SHA review — PASS

Reviewed head: 1aaf45439da556a519f4fc37a23d9f997af2c11e

Provenance matched independently across the branch ref, PR head ref, and PR API. The complete main...head diff is limited to:

  • uni-7/02_V31_UPGRADE.md
  • uni-7/README.md

Verified:

  • git diff --check passes
  • two-file scope matches merged uni-7: schedule v30 upgrade at height 16034000 CosmosContracts/testnets#388 precedent
  • plan name v31, empty store-upgrade table, and module-migration behavior match candidate source
  • Go/dependency versions and Clock/CW Hooks defaults match candidate commit 55389a1ed53abcec4851a521ff71a627578a69a7
  • documented CLI command shapes and Cosmovisor path are valid
  • placeholders and warnings fail closed while the immutable release and schedule are absent

No blocker prevents retaining this as a draft.

Promotion remains blocked on CosmosContracts/juno#1223 becoming integrated and green, an immutable v31 release/tag, exact build and artifact verification, and selection of the uni-7 halt height.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant