Cacheon is an inference-throughput competition built around SGLang and designed to operate as a Bittensor subnet. Miners submit inspectable GPU-kernel contributions at registered boundaries in a validator-owned model. Validators admit those contributions through a typed, isolated pipeline and reward only improvements that reproduce under the registered throughput and quality policy.
This repository—published as latent-to/cacheon—contains
the miner SDK and examples, validator and chain control plane, evaluation
runtime, settlement and incentive machinery, and chain-independent engine
release tooling.
Important
Cacheon is pre-release software. Implemented paths, retained empirical evidence, and production readiness are separate claims. Start with the validator first hour for what a deployment must prove.
| Goal | Documentation |
|---|---|
| Understand the system | Concepts and architecture overview |
| Understand why miners participate and how rewards work | How miners earn rewards |
| Build a miner contribution | Miner guide |
| Operate a validator | Validator guide |
| See what a crown does and does not authorize | After a crown |
| Review trust boundaries | Security model |
| Contribute to the repository | Contributing |
The canonical documentation source lives under docs/ in this
repository and is rendered at cacheon.ai/docs.
Python 3.11 or newer is required.
python3 -m venv .venv
source .venv/bin/activate
python -m pip install -e ".[cpu,dev]"
python -m cacheon.cli slots
python -m cacheon.cli scan examples/miner_silu_torch
python -m cacheon.cli verify examples/miner_silu_torch \
--device cpu \
--dtype float32scan and verify are development checks. They do not establish serving
throughput, end-to-end quality, settlement eligibility, or a production
release. Those decisions belong to the validator-owned qualification path
described in the documentation.
- The validator owns the model, workload, references, timing, outputs, and reward policy. A miner contribution owns only its registered target.
- Candidate build and execution run in validator-owned, no-egress OCI workers; wallet and chain-signing authority remain outside candidate lifetimes.
- A single passing qualification is not a crown. Settlement requires an independently reproduced pair bound to the same contribution and evaluation context.
- Evaluation acceptance and serving are different decisions. Nothing in the repository turns a crown into a release; that is a maintainer decision made outside it.
See the product model and slot contract for the normative invariants.
python -m pytest -q testsDocumentation checks are described in Contributing.
The repository is licensed under Apache-2.0. Miner submissions are governed separately by the draft submission terms; those terms require legal review before production use.