Proposed runtime upgrade to spec 464 (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/v464 -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 v464
# srtool build, then:
btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v464 --wasm <path/to/your-build.wasm>
Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v464 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 | 464
|
| commit | 5cd66b8597b3ce5f9f2bade2b11c91af57df923d
|
| call hash | 0x2a1878ded7c768f03dff0271ed43447587bdd969a1575fcef9bcccceaf09a86c
|
| deployment timepoint | 9087523:10
|
| CI key | 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA
|
| deployment multisig | 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f
|
| wasm sha256 | 0x56bbc410e2b03d9d5216e1ac911e995e96e400ae8205e0bbbfdc741fbc36ce3c
|