Release 4.6.0

SN34's earlier identity: Filed under SN34 from a source its on-chain identity named before. The identity has changed and no longer names this source, so the item is not listed as news of the subnet on SN34 now.

feat: Discriminator Verticals & Miner Performance CLI Summary Introduces the vertical axis to the discriminator competition (starting with image:human), adds a self-service performance endpoint for miners, adjusts incentive allocations, and cleans up deprecated code. Changes Vertical support in model uploads gascli d push now accepts --vertical human (only valid with --modality image). Client-side guards in both gas/cli.py and push_model.py prevent invalid vertical+modality combinations before hitting the API. gas/protocol/model_uploads.py renamed to gas/protocol/miner_requests.py to reflect its broader scope. Miner performance CLI (gascli d perf) New gascli d perf command lets miners query their own benchmark results via an Epistula-authenticated GAS API endpoint. Output shows SN34 score (with progress bar), MCC, Brier, modality, vertical, and elapsed time for running/queued jobs. Supports --modality and --vertical filters. Core HTTP logic lives in gas/protocol/miner_requests.py; CLI handles wallet loading, auth, and formatting. Incentive allocation adjustment Image allocation increased from 23% → 28.5% to accommodate the new image:human vertical (~17.5% of image rewards). Video allocation adjusted from 29% → 23.5%. Burn, audio, and generator percentages unchanged. Fix: Non-resumable upload flow and silent 409 handling The upload flow (push_model.py / upload_single_modality) had no way to distinguish a genuine failure from "your model was already accepted by the server." Miners who re-ran the script after a partial failure (e.g. chain registration timed out) would hit a 409 from /upload/presigned and receive an opaque error, unable to proceed. What was wrong: The server returns 409 when the file hash is already in an accepted state (uploaded, downloading, validating, examining, or confirmed). Both 409 and genuine errors were handled identically — print("FAILED") and exit — even when the model was already on the server and the miner just needed to retry blockchain r

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.