Skip to content

runtime: bump spec_version to 80013#729

Merged
yahortsaryk merged 1 commit into
devfrom
chore/bump-spec-80013
Jul 2, 2026
Merged

runtime: bump spec_version to 80013#729
yahortsaryk merged 1 commit into
devfrom
chore/bump-spec-80013

Conversation

@yahortsaryk

Copy link
Copy Markdown
Contributor

Summary

Bumps spec_version 80012 → 80013 on both cere and cere-dev runtimes.

Why

The recent ddc-{api,dac-host} + pallet-ddc-{verification,payouts} lockfile bump (#728) changes the runtime WASM — ddc-api is in the runtime dependency closure (via ddc-dac-host and both pallets), and its fetch_records_range now sends the required nodePubKey query param. That merged with spec_version = 80012, but live devnet is already running 80012 (different code hash), so it can't be applied as an upgrade:

try-runtime: New runtime spec version must be greater than the on-chain
runtime spec version: 80012 <= 80012

Bumping to 80013 lets the change deploy as a real runtime upgrade.

What changed

  • runtime/cere/src/lib.rs: spec_version 80012 → 80013
  • runtime/cere-dev/src/lib.rs: spec_version 80012 → 80013

transaction_version stays at 27 (no extrinsic / signed-extension changes) and Migrations stays () (OCW-only change — no storage layout change, nothing to add or remove).

try-runtime verification (cere-dev vs wss://archive.devnet.cere.network)

on-runtime-upgrade --checks=all:

  • on_runtime_upgrade succeeded; migrations idempotent (storage root unchanged)
  • ✅ PoV 11.5 KB; weight 0.0015s = 0.08% of the 2s block budget; no weight safety issues
  • ✅ Entire post-upgrade state decodes without error (4.9 MB total)

Pre-existing, unrelated finding (NOT introduced here): the Staking try_state invariant MaxValidatorSet (1000) >= MaxWinnersPerPage (1200) is violated in the cere-dev config. It only surfaces under --checks=all try-state and does not affect the upgrade itself — tracked for a separate fix.

🤖 Generated with Claude Code

Live devnet (wss://archive.devnet.cere.network) is already running
spec_version 80012 with a different code hash, so the previously-merged
80012 bump collides and cannot be applied as an upgrade (try-runtime:
"new runtime spec version must be greater than the on-chain runtime spec
version: 80012 <= 80012"). Bump to 80013 so the ddc-api nodePubKey
records-fetch change can deploy as a real runtime upgrade. OCW-only
change; transaction_version stays at 27 and no migrations added.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@yahortsaryk
yahortsaryk merged commit db75e49 into dev Jul 2, 2026
3 of 10 checks passed
@yahortsaryk
yahortsaryk deleted the chore/bump-spec-80013 branch July 2, 2026 17:47
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