github RaoFoundation/subtensor v437
Runtime 437 (proposed)

pre-releaseone day ago

Proposed runtime upgrade to spec 437 (awaiting signatures)

CI has submitted its half of the 2-of-2 deployment multisig for this
upgrade on finney. It executes once the sudo multisig (triumvirate)
produces the second approval. This tag is the exact code being
deployed.

Sign it

Each triumvirate member runs:

btcli upgrade sign --url https://github.com/RaoFoundation/subtensor/releases/tag/v437 -w <your-wallet>

btcli verifies the call data against the chain (structure, sudo key,
on-chain call hash) before submitting, and picks the right approval
(first / interior / final) from chain state automatically.

Verify it independently (recommended)

Build the runtime from this tag with srtool and compare byte-for-byte
(see .github/scripts/deploy/README.md for the full recipe):

git fetch origin && git checkout v437
# srtool build, then:
btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v437 --wasm <path/to/your-build.wasm>

Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v437 still verifies
the published artifacts against each other and the chain, but trusts
the released wasm; a local srtool build closes that gap.

Proposal details

spec_version 437
commit 2d52647c415aa987ab93dbd7de4ddc5eaf7aa083
call hash 0x8efef510da82751ac73956a2048a1ce3c26ebea7c8b2c27a649cacc125ad92d0
deployment timepoint 8678970:17
CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA
deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f
wasm sha256 0xf88b73a67748553c33be4932718622107046644c5f6d0af2f7e96861a93a6e1f

Don't miss a new subtensor release

NewReleases is sending notifications on new releases.