Runtime 488 (proposed)

Proposed runtime upgrade to spec 488 (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/v488 -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 v488 # srtool build, then: btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v488 --wasm <path/to/your-build.wasm> Without --wasm, btcli upgrade check --url https://github.com/RaoFoundation/subtensor/releases/tag/v488 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 488 commit b6a81d144078eac18bd25c3af7cb31579bb670f3 call hash 0x80814f1a10bb2b756945f3433d91d21542f0972c859c6e8d145dd1afd001eb75 deployment timepoint 9442429:7 CI key 5EqaWfYWgPWfXRFaM2hXbATkVGKdEJBznoyEUnVi8aGfN1bA deployment multisig 5CzMP6tiNjKx3YiTbuPebLHZCtuomzTPzEGvG711iemY6u2f wasm sha256 0xfbcacb1d5d6b320c68cf4098465039bd7667772abc542596baf4e2456d5c3c15

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.