News·Subtensor GitHub·Sep 3, 2026, 16:12 UTC

Runtime 453 (proposed)

Proposed runtime upgrade to spec 453 (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/v453 -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 v453 # srtool build, then: btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v453 --wasm <path/to/your-build.wasm> Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v453 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 453 commit 823bdcbc58a29f60b243be4737a7c72b34ac7d93 call hash 0x972c1c03fae47d58ad3dbfd701e58e56170936045b0a488170c05c8d0729fcd4 deployment timepoint 8987926:11 CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f wasm sha256 0x9e51859faf28a69365005e7dd7f152f239a305c468869b2f54303aba938d840e

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.