News·Subtensor GitHub·Aug 27, 2026, 19:01 UTC

Runtime 450 (proposed)

Proposed runtime upgrade to spec 450 (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/v450 -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 v450 # srtool build, then: btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v450 --wasm <path/to/your-build.wasm> Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v450 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 450 commit 9540b3af59179b88af99f8e0d03add5d96512e3f call hash 0x094724f9011e4ef1e126dca2633d9fc8c3e0ba632fb1b93088ed4634aeab7d58 deployment timepoint 8938375:18 CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f wasm sha256 0xf779e18b5882a7349f8776319d2280947aefa883f8f438a94aff871bbcc13434

Read the github release at Subtensor GitHub ↗

Taosis indexes announcements, articles 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.