README.md

Miner Overview

This section covers the current miner-facing workflow for Minotaur Subnet 112.

Contents

• Quickstart - Run the current CLI flow
• Configuration - Flags, defaults, and environment variables
• Solver API - IntentSolver and Strategy interfaces
• Custom Solver - Strategy implementation guidance
• Troubleshooting - Common errors and fixes

How mining works now

Miners compete by improving solver quality, not by running a quote server.

Typical loop:

1. Build/iterate on strategies (often via RoutingSolver).
2. Submit candidate solver code.
3. Validator/API benchmark worker scores submissions against active app scenarios.
4. A challenger that delivers strictly more than the champion per order (zero regressions, ≥1 win/blind-spot cover) can be adopted as champion.
5. Champion solver is loaded into block loop execution.

Submission paths

1) Git-based submission (/v1/submissions)

• Signed by Bittensor hotkey
• Runs 3-stage screening:
  • static checks
  • Docker build/import
  • smoke test
• Then benchmarked and ranked

2) Source-based submission (/v1/submissions/source)

• Inline Python source upload
• Skips screening
• Goes directly to benchmarking
• Used by the agent loop for rapid iteration

Champion/challenger model

• Submissions are compared to the champion per order (relative reference-bar) — the champion is the baseline, with no score of its own.
• A challenger must deliver strictly more than the champion: zero per-order regressions or drops, and at least one strict win or blind-spot cover (within a ±0.1% / 10 bps tie band). Matching everywhere is rejected.
• On adoption, block loop hot-swaps to the new solver.