Mechanism diagrams

How each subnet's incentive mechanism actually works, drawn from source pinned at a commit. Hover a block to read it, click to pin it, and use the trace to walk one scoring round end to end.

• Apex netuid 1 — a published formula, an unread orchestrator, and a validator running GPUs
• Pareton netuid 10 — everything up to the scoreboard, and then the scoreboard's blank
• Minos netuid 107 — a re-run genomics benchmark on a live reward curve
• Zeus netuid 18 — what the score actually measures, and who bends it
• Targon netuid 4 — GPU auctions gated by hardware attestation
• Hone netuid 5 — a puzzle leaderboard where most of every round is thrown away on purpose
• lium.io netuid 51 — why being rented outweighs being attested
• Bitsec.ai netuid 60 — what is isolated, what is re-scored, what is not checked
• RedTeam netuid 61 — who judges whether an attack actually worked
• Chutes netuid 64 — what the chain's own pointer does and doesn't contain

Subnets absent from this list are absent for a reason stated in their dossier: no published repository, an unreachable one, or — for eight of the cohort — no licence at all, which means the code may be read on GitHub but not legally quoted here.