Runtime 470 (proposed)

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

Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v470 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	470
commit	923fd1fa7d6eadad3ec16f3941826b86c9c3aa1d
call hash	0x745e9d813d1965c56f9ab1b15eafc1a953128c19f0caa9e7776e688a6b1b1f8a
deployment timepoint	9136280:19
CI key	5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA
deployment multisig	5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f
wasm sha256	0xe5abec692e3988352da818823d9729f139820e205ea17048f93816974106c005