hf_poller: banned-submitter gate — close the PR for a blocklisted identity - #100
Open
karpabot wants to merge 1 commit into
Open
hf_poller: banned-submitter gate — close the PR for a blocklisted identity#100karpabot wants to merge 1 commit into
karpabot wants to merge 1 commit into
Conversation
…ntity
Kaizen0304 (5H3xirPk) spammed 10 exploit bundles (compute-forged + value_embeddings
arch-bypass), forcing per-checkpoint blocklisting after each landed. This refuses the
SUBMITTER at the PR gate instead: if the bundle's hotkey/github — or the HF account that
opened the PR — is on the ban list, the validator CLOSES the PR (HF proof-bundles PR +
the linked GitHub recipe PR) and never scores it.
- ban list is DATA: chain/banned_miners.json {"hotkeys","github","hf_users"} — add/remove
identities without a code change.
- poll_hub: pre-download check on the HF PR author (banned HF account -> close, skip).
- download_one: post-decrypt check on submission hotkey/github (banned -> close PR, return
"banned"); poll_hub marks it done so it stops churning.
- _close_pr_banned closes the HF PR (change_discussion_status) + best-effort the GitHub
recipe PR (RALPH_BOT_GH_TOKEN). Both best-effort; never block the loop.
- 6 tests (hotkey-prefix / github case-insensitive / clean-miner-passes / HF-account /
file load + lowercasing / missing-file-empty).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Why
Kaizen0304 (
5H3xirPk) spammed 10 exploit bundles (compute-forged +value_embeddingsarch-bypass), forcing us to blocklist each checkpoint after it landed (and one re-crowned via op4's eval cache). This bans the submitter, not the checkpoint.What
If a submission's hotkey / github, or the HF account that opened the PR, is on the ban list, the validator closes the PR (HF proof-bundles PR + the linked GitHub recipe PR) and never scores it.
chain/banned_miners.json{"hotkeys": ["5H3xirPk"], "github": ["Kaizen0304"], "hf_users": [...]}. Add/remove identities with no code change.poll_hubpre-download check on the HF PR author → banned HF account is closed without even downloading.download_onepost-decrypt check on the submission hotkey/github → banned → close PR, return"banned", marked done so it stops churning._close_pr_bannedcloses the HF PR (change_discussion_status) + best-effort the GitHub recipe PR viaRALPH_BOT_GH_TOKEN. Both best-effort; never block the loop.Deployed live with the ban list seeded to Kaizen. 6 tests. Complements the per-checkpoint blocklist (which still backstops).
🤖 Generated with Claude Code