github RaoFoundation/subtensor v448
Runtime 448 (proposed)

pre-release7 hours ago

Proposed runtime upgrade to spec 448 (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/v448 -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 v448
# srtool build, then:
btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v448 --wasm <path/to/your-build.wasm>

Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v448 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 448
commit e18ca67f1a00b35c7d5986888d1cc388da8c095f
call hash 0x9d88f00d8bfb6dfe7517081f1c87ee2897156bbfe4763763f7e7669d4f01683b
deployment timepoint 8894660:28
CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA
deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f
wasm sha256 0xecc799f5e38a26fb7abcb68d8f51ccc63ef41342c351334b0dd5f13c00ae4ed0

Don't miss a new subtensor release

NewReleases is sending notifications on new releases.