Skip to main content

Overview

The Evolve track is the second way Phylax miners earn. Instead of running a miner around the clock, you improve the subnet itself: submit a better version of any component, get it benchmarked against the current champion, and earn a continuous share of emissions while your version stays canonical. Submissions are one-shot, like a pull request with a stake behind it. No uptime requirement, no axon, no registration beyond a hotkey.
The Evolve track pays 5% of miner emissions, divided across all currently adopted contributions. The other 95% flows through the Operate track described in the Miner Guide.

What You Can Improve

Any component of the subnet repo is open to improvement. Nothing is off limits. Examples:
AreaExamples
DetectionClassifier accuracy, static analysis rules, prompt-injection detection, SBOM and CVE coverage
SandboxProbe instrumentation, evasion resistance, new trace types, detonation performance
Reference harnessThe open-source baseline pipeline new miners clone
ValidatorRound orchestration, consensus logic, verification group selection, rerun efficiency
ScoringAxis formulas, anti-gaming checks, tier calibration
Protocol and serverWire schema, API endpoints, storage, caching
ToolingCLI, runtime SDK, deployment scripts, test coverage
The only thing not eligible is your private Operate pipeline. That is your Track 1 edge and it stays yours.

How Adoption Works

1

Submit

Upload your improved component version, hotkey-signed.
2

Benchmark

Detection and classification changes are replayed against the ground-truth corpus (canaries plus known-good and known-bad skills) on detection accuracy, false-positive rate, classification accuracy, and runtime cost. Changes outside the detection path are assessed on measurable impact: performance, cost, correctness, and test results.
3

Threshold

Benchmarked changes must beat the current champion by at least 2% composite. Submissions are public, so copying the champion and resubmitting earns nothing.
4

Review and Adopt

Passing submissions go to human review (Praxi Labs during testnet). On adoption your version becomes canonical, pinned by hash, and announced to the network on the next round.
5

Earn

While your contribution stays adopted you earn an equal share of the 5% developer stream alongside every other adopted contribution.

Version Pinning

Components that affect consensus (the classifier, sandbox probes) are version-pinned: every classification and every probe result carries the component version that produced it. Auditors reproduce results against the same pinned code, and rounds stay replayable after an upgrade. Execution always stays distributed across independent miners; evolution changes which shared code the network runs, never who runs it.

When Nothing Is Adopted

When no external contribution is currently adopted, the developer stream accrues to the subnet treasury rather than redistributing to Operate. There is always a standing bounty for improving the subnet.