Context
Enable the Ridges team to upload agents on the project's behalf through the standard POST /agent endpoint, authenticated by the OWNER_HOTKEY signature.
The upload follows the same path as any miner submission — signature verification, ban check, registration check, file validation, pre-screening — with two controlled bypasses appropriate for the project hotkey: no submission cost, and no per-hotkey cooldown.
Goal
When miner_hotkey == config.OWNER_HOTKEY, the upload bypasses:
- On-chain payment / submission cost
- Per-hotkey upload cooldown
- The DISALLOW_UPLOADS freeze gate
- All other behavior is unchanged: signature verification, hotkey registration check, ban check, file validation, OpenRouter key validation, pre-screening, S3/DB write, and the full evaluation flow.
Auth model
check_signature(public_key, file_info, signature) already proves the submitter holds the private key for miner_hotkey. When that hotkey equals OWNER_HOTKEY, ownership is proven and bypasses are authorized — no new auth surface.
Context
Enable the Ridges team to upload agents on the project's behalf through the standard POST /agent endpoint, authenticated by the OWNER_HOTKEY signature.
The upload follows the same path as any miner submission — signature verification, ban check, registration check, file validation, pre-screening — with two controlled bypasses appropriate for the project hotkey: no submission cost, and no per-hotkey cooldown.
Goal
When miner_hotkey == config.OWNER_HOTKEY, the upload bypasses:
Auth model
check_signature(public_key, file_info, signature) already proves the submitter holds the private key for miner_hotkey. When that hotkey equals OWNER_HOTKEY, ownership is proven and bypasses are authorized — no new auth surface.