Documentation / Bittensor concepts / Protocol Changes
Protocol change tracker
Every Bittensor runtime change with the date its pull request opened, merged, reached testnet and went live on mainnet.
Last reviewed 2026-10-15
This page tracks every change to the Bittensor chain runtime in subtensor, from pull request to production. For each change it shows when the pull request opened, when it merged, which runtime spec it shipped in, and when testnet and mainnet (Finney) first ran that spec. The data refreshes from the chains and GitHub every four hours.
Status at a glance
Days to mainnet
The last 20 runtime releases that reached mainnet.
Runtime upgrades
Every spec either chain has run since spec 437, newest first. Never on testnet: mainnet ran a spec that testnet skipped. Testnet only: a newer spec replaced it before it reached mainnet. In testing: testnet runs a spec newer than mainnet's. Mainnet first: mainnet upgraded before testnet.
Merged changes
Newest merge first. Release is the runtime spec the change shipped in. A dash under testnet or mainnet means that chain has not yet run a runtime containing it.
Open proposals
Open, non-draft pull requests against subtensor main that change chain code. None of them is on testnet or mainnet, and some will never merge.
Shipped is not always switched on
Some features ship in a runtime upgrade with a switch that is off. They do nothing until a root (sudo) call turns them on, so the mainnet date is the date the code arrived, not the date users could use it. Each feature's explainer page says when its switch is on.