Runtime 442 (proposed)

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

Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v442 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	442
commit	ec112cb0e68469fa1c5e5ae67dece043033f6673
call hash	0xc8f2b6a35cfc950b845a7cd7671dbb9e79d50ed204254f5dce4ce319220359af
deployment timepoint	8770539:17
CI key	5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA
deployment multisig	5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f
wasm sha256	0xc270fcf24b177b737c9da73a1caf5960e0bba04de17f18ec5342d06fefd685b6