Runtime 471 (proposed)

Proposed runtime upgrade to spec 471 (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/v471 -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 v471 # srtool build, then: btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v471 --wasm <path/to/your-build.wasm> Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v471 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 471 commit c004cebf360f4088187ee49d851dfb1a1eaaf710 call hash 0x0172e44331261849d5bf137cc31e40af430a583e4f8ecf68ac60d2680c7ace91 deployment timepoint 9146159:11 CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f wasm sha256 0x04385dd7ddda37d4f70cd59a0e8360227165a4aefead0203c47adea5fc4b4aeb

Read the github release at Subtensor GitHub ↗

Taosis indexes announcements, articles, posts and releases about Bittensor subnets from their own channels and keeps a record of each. The text above is the source’s; the figures are read from the chain by Taosis.