Skip to content

Feat/add ck ban mechanism#429

Open
ibraheem-abe wants to merge 19 commits into
feat/burn_alpha_upload_paymentfrom
feat/add-ck-ban-mechanism
Open

Feat/add ck ban mechanism#429
ibraheem-abe wants to merge 19 commits into
feat/burn_alpha_upload_paymentfrom
feat/add-ck-ban-mechanism

Conversation

@ibraheem-abe

Copy link
Copy Markdown
Contributor

Changelog

  • Added permissioned admin endpoints to ban or unban a miner coldkey with a recorded reason.
  • Paid uploads now resolve and store the miner’s coldkey, rejecting banned coldkeys before agent creation.
  • Coldkey bans apply across every associated hotkey, including evaluation queues, auto-approval, incentives, leaderboards, approved-agent lists, and statistics.
  • Added transactional locking so concurrent uploads, bans, and approval publication cannot bypass enforcement.
  • Owner and legacy agents with no stored coldkey remain unaffected.
  • Retired runtime hotkey-ban checks while keeping the old schema for compatibility.
  • Ban/unban operations immediately invalidate affected API caches.
  • Added migration, concurrency, queue, ranking, upload, and API regression coverage.

- approved agents for set: Exclude banned
- get_evaluation_set_score_stats: exclude banned cks from comparision
- get_evaluation_set_submission_stats: Exclude banned ck
- _sql_agents_in_window_cte: exclude banned ck
…ed coldkey scores

- get_approved_leader_ranking_for_set: excludes banned coldkey leaders
- get_weight_receiving_agent_hotkey: exclude banned cks from getting weights
- get_weight_receiving_agent_info: excluded banned cks
- banned_cks table
- agents.miner_ck added
- queue views: exclude banned cks
- remove hk legacy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant