Conversation
Stop sending 84% of weights to escrow UIDs. Validators now fetch /current-kings and pay the reigning miner per modality, with last-known fallback if the API is down. Co-authored-by: Cursor <cursoragent@cursor.com>
Testnet 169 is not the hardcoded 379 mapping, and short epochs are needed to verify KOTH weights. Co-authored-by: Cursor <cursoragent@cursor.com>
Bittensor metagraph threads kept the process alive, and a 409 with --skip-chain was treated as failure. Cap chain retries and _exit. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep the current king dominant while paying the previous two distinct crowned hotkeys a residual so near-ties are not winner-take-lane. Co-authored-by: Cursor <cursoragent@cursor.com>
Paying last-3 kings 85/10/5 is a breaking incentive change, so spec_version should move with a major rather than sit on 4.10.0. Co-authored-by: Cursor <cursoragent@cursor.com>
feat: set discriminator weights on current KOTH kings
kenobijon
changed the title
Chain registration is optional. A failed or skipped commitment should not fail the CLI after the model is already in R2 and queued for exam. Co-authored-by: Cursor <cursoragent@cursor.com>
Miners get one image, one video, and one audio slot per registration. Exam failures do not count and a new round does not refill the slot. Co-authored-by: Cursor <cursoragent@cursor.com>
Keep a single Validating.md setup runbook and stop implying the full-benchmark score is TAO emissions. Co-authored-by: Cursor <cursoragent@cursor.com>
Match the tighter upload cap: a key cannot land one model per lane. Co-authored-by: Cursor <cursoragent@cursor.com>
fix: succeed discriminator push after upload; one submission per hotkey
Match the tighter upload cap: a key cannot land one model per lane. Also drop cloud-evaluated wording from the miner guides.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updating to a King of the Hill competition where continuous payouts are made to the king + the past 2 kings for each modality, 85/10/5.
Tested on testnet
Note
High Risk
Validator weight setting now depends on the kings API and hotkey UID resolution; misconfiguration or stale cache directly shifts TAO across miners and burn.
Overview
Release 5.0.0 replaces round-based discriminator escrow payouts with King of the Hill: validators pull kings from
GET /api/v1/validator/kings, cachekings.jsonon restart, and set weights via newbuild_koth_weights(40/40/4/16 lanes; each modality lane split 85/10/5 across current and two prior distinct hotkeys; generators still share 16% by score; missing kings burn). Hardcoded modality escrow SS58 addresses are removed from the validator path.Docs and README now describe one counted discriminator submission per hotkey (any single modality; extra modalities need another hotkey), KOTH dethrone/defense rules, and simplified validator setup (
Validating-New.mdfolded into a shorterValidating.md).Miner push flow gains
--upload-endpoint,--skip-chain, and capped--max-retriesfor chain registration; duplicate-hash 409 uploads count as success; failed or skipped chain writes no longer fail the push after a good upload;gascli d pushpropagates exit codes;push_modelusesos._exitto avoid hanging on Bittensor websockets.Ops:
validator.config.jsprefers explicitNETUIDand forwardsEPOCH_LENGTH. Unit tests cover KOTH weight math and push retry behavior.Reviewed by Cursor Bugbot for commit 00b6b25. Bugbot is set up for automated code reviews on this repo. Configure here.