SUBTENSOR RUNTIME · v493
v493 lets deposit Hotkeys spend gamma directly and makes the Yuma timelocked commit limit sudo-configurable
This release changes how gamma deposits are spent: the deposit's own Hotkey now spends gamma at services listed on the Subnet, with no separate spender. It also lets sudo configure each Subnet's limit on Yuma timelocked commits. The remaining changes are release tooling and tests.
- Changes since
- v492
- Commit
8b407e4098- GitHub release
- v493 ↗
What you need to do
- Gamma is now spent by the deposit's Hotkey — Gamma integrations and service providers must update to the new Python SDK. Subnet Owners should set a daily spend cap on the owner Hotkey's deposit if it needs to spend.
High impact TAO holders / StakersValidators / Miners Action required
Gamma is now spent by the deposit's Hotkey
A gamma deposit is now spent by its own Hotkey at a service listed on the Subnet. The spend pays no fee, burns the gamma, and updates a running total per service that the service uses to credit its customers. The separate spender role is removed, and the GammaSpend Proxy type no longer allows spending. The deposit's Coldkey keeps control of the balance, the daily spend cap and closing. A spend must be at least 0.1 gamma unless it empties the deposit, and a daily cap must be either 0 (paused) or at least 0.1 gamma. Existing deposits are migrated: the Subnet Owner's uncapped deposit at the owner Hotkey and any cap below 0.1 gamma are paused. Gamma Emission opens the owner Hotkey's deposit with a daily cap of 0, so the owner Coldkey must set a cap before that Hotkey can spend. After a Hotkey swap, the deposit moves to the new Hotkey. Moving gamma now requires moving the whole balance, or at least 0.1 gamma while leaving at least as much. This is a breaking change for gamma integrations and the Python SDK.
Action required Gamma integrations and service providers must update to the new Python SDK. Subnet Owners should set a daily spend cap on the owner Hotkey's deposit if it needs to spend.
Medium impact Validators / Miners
Yuma timelocked commit limit can be set by sudo
Sudo can now configure each Subnet's limit on Yuma timelocked commits per Hotkey, mechanism and commit epoch. The default stays at 10. Setting it to zero pauses new commits while already queued commitments remain eligible to reveal. Legacy hash commits keep their fixed limit of 10, and Null Consensus keeps its existing queue limits.
Also included: release announcement and stable Python publishing tooling, a single-approval release pipeline, release notes checks, and a new test and state check for childkey dividend accounting.
AI-generated summary of the release code. Check the linked pull requests for authoritative details. Report generated Nov 20, 2026.
v493