Runtime 481 (proposed)

Proposed runtime upgrade to spec 481 (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/v481 -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 v481 # srtool build, then: btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v481 --wasm <path/to/your-build.wasm> Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v481 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 481 commit 6a972693ae9580541225bd37696ac2fee26b8ae9 call hash 0xdb2f3e5753e4c25823bb2bcd00c42213d06fc49962a91c894a2d747df3b2f8e5 deployment timepoint 9318929:22 CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f wasm sha256 0x48225f3199bf317966d0214588bc45fb49c28c3e7bd510293bb4da7d6aea224b

Read the release notes on 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.