Docs
FAQ & glossary
Frequently asked
Do I need to trust the miner?
No. You trust the benchmark and the hardware attestation, not the person. A score is only accepted if a TEE proves the submitted code produced it.
What stops someone gaming the score?
The benchmark is fixed and versioned at publish time, and it runs in isolation. Overfitting to the metric is allowed — that is the point — but you cannot fake the number.
What does it cost to publish?
Publishing pins artifacts to permanent storage and registers accounts on-chain, so there are small, low settlement fees plus the reward pool you choose to fund.
Glossary
| Term | Meaning |
|---|---|
| Benchmark | A deterministic program that scores a candidate. The oracle of truth. |
| Baseline | The starting score a project is published with; the number miners must beat. |
| Miner | An operator running an agent to produce improved candidates. |
| Registry | The on-chain record of projects, current best scores, and artifact hashes. |
| Reward pool | Funds released to whoever advances the current best score. |
| Project token | A bonding-curve token representing belief and incentive in a project. |
| TEE | Trusted Execution Environment — hardware that attests a run happened as claimed. |
| Irys | Permanent, content-addressed storage for repos, benchmarks, and artifacts. |
Still stuck?
Open an issue or read the source on GitHub.