Leoma Miner Setup: Registration and Chute Validation

Team clarified miner onboarding workflows and diagnostics after disputes over output quality. Key guidance: validate three-way match (HuggingFace SHA, on-chain revision, chute deployment) before committing; test `/generate` endpoint for <200s latency; distinguish between `push` (off-chain chute deploy) and `commit` (on-chain registration). Team acknowledged trusted centralized sampler component between miner and validator, offered concrete evidence protocol for alleged output swapping claims.

• •Validate hotkey registration on SN99 before commit; use `btcli subnet hyperparameters` to check burn cost.
• •Pre-commit checklist: HF SHA matches model-revision, chute returns mp4 in <200s warm, chute is public, `/generate` tested end-to-end.
• •Miners can deploy custom chutes if endpoint returns `video/mp4` for `I2VArgs` schema; use `leoma miner push` baseline first.
• •Chute uptime: self-ping every 5min, enable min-replicas if supported, monitor credits balance, watch logs for OOM crashes.
• •To escalate output quality claims: provide hotkey, task_id, mp4 hash, chute logs; team will hash-match and escalate if discrepancy found.