Miner Status · First steps
What to do first
Build the test setup, find signals the field misses, and only spend on registration when a detector clears 0.85 locally. The order matters because a submission that fails a gate costs a day and can block later ones as “too similar”.
Options
Which challenge
| Path | Pay if it works | Cost | Verdict |
|---|---|---|---|
| BEX Tracer | $962–1,924 a day while you are the top accepted entry; falls with decay (15 days), rivals, or a lower weight if Bot Virus v2 returns | registration ≈ $0.30, a VPS for the miner node ($5–15 a month), a free private Docker Hub repo, time | go |
| ADA-3 | about $12 a day per UID (median), at most $18 | ≈ $130 a month of anti-detect licences plus test machines | no |
| Bot Virus v2 | unknown | — | watch |
Plan
Five steps
- Local rig
docker pull redteamsubnet61/rest-bex-challenge:1.0.0. It holds the exact pinned extension builds (the Web Store only serves newer ones). Run the API, and runrun_round.pyinside the container: a developer script that prints the true enabled set and scores a detector over N rounds. - CensusFor each of the 89 extensions, load it alone and compare the bait page with a clean profile, before and after the six interactions: added elements, styles and shadow roots; new or altered globals and wrapped browser functions; blocked or rewritten requests; messages, events and timing. Start with the 29 rare ones; that census is the edge nobody else has.
- DetectorsEight group files in your own structure: readable, no obfuscation, no text aimed at the reviewer. Grade every signal on precision first, since one false claim per round costs about 0.05. Target: a mean of 0.85 or more over 100+ local rounds with random 12-extension mixes (extensions interfere with each other).
- Register & submitWallet, registration (≈ 0.0015 TAO), a private Docker Hub image with a neutral name, and a miner node on a separate VPS (its IP is public). Commit right after registering and before about 12:45 UTC so the score (≈ 25 h later) lands inside the 48 h immunity window.
- WatchUID 30's pending refresh and its decay from 17 Nov; new acceptances on the dashboard; Bot Virus v2 and the weights in
active_challenges.yaml.
Timing
The clock
| Commit → scored | ≈ 24.7 h (UID 30: 21:27 → 22:08 next day) |
| Commits | one per challenge per 24 h; the latest replaces earlier ones that are not yet scored |
| Weights | validators pull results daily; 14:00 UTC is the cutoff |
| Immunity | 48 h from registration, then pruning if you earn nothing |
| Pay window | 10 days full, then down to 0 at day 15; to keep earning, beat your own best by a submission under 0.8 self-similarity |
Risks
What can go wrong
| Risk | What | Mitigation |
|---|---|---|
| high | Similarity rejection: 10 of 11 scores of 0.80+ since 1 Nov were rejected this way | own code structure and own signals; never start from someone else's code or the stub templates |
| high | Weight change when Bot Virus v2 lands | watch the repo; a BEX detector keeps value as long as BEX is live |
| med | AI code check with unpublished rules (1,296 failures) | plain, readable detection code; no obfuscation or comments aimed at the reviewer |
| med | Alpha price (−49% in 30 days) | pay is in alpha; the cost side is small |
| low | Rivals accepted first | softmax splits by score, so a higher score still takes most of the share |
Sources
Where this comes from
- Chain: SN61 metagraph, hyperparameters, pool reserves and emission accumulators at block 9,512,820; daily prices from the archive node.
- RedTeam dashboard (theredteam.io/dashboard): every BEX and ADA-3 submission, and the per-round results of 393 scored BEX submissions.
- Code: RedTeam v4.10.10 (
active_challenges.yaml, validator managers), bex-tracer-challenge v1.0.0 (pool, scorer, round script). - GitHub branches, PRs and issues; Docker Hub tags; docs.theredteam.io; taostats.io and taomarketcap.com (15 Nov ~15:50 UTC).