> For the complete documentation index, see [llms.txt](https://docs.konnex.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.konnex.world/participate/mining.md).

# Mining

**Miners** compete within a **workload class** (subnet) to supply the best policies or trajectories for real-world-style tasks. Rewards and slashing follow the network’s rules for that subnet; on testnet, interaction is through published binaries and the subnet dashboards (dashboard URLs in **release notes** when published).

## What miners optimize

* **Quality** — Task match, safety, efficiency, and coherence of execution vs the onchain [task instruction](/understand-konnex/contracts-and-popw.md).
* **Evidence** — Sensor bundles and traces that meet PoPW requirements (including hardware attestation where applicable).
* **Specialization** — You can focus on one subnet (e.g. **SLAM 3D map**) without being exposed to every other workload class.

## Requirements (conceptual)

* Stake or bond as required by the subnet (testKNX on testnet; design target includes KNX and, on mainnet, stablecoin-related mechanics per the [roadmap](/understand-konnex/roadmap.md)).
* A compliant **miner build** for the workload you target (see the [Konnex GitHub org](https://github.com/konnex-network)).
* Uplink and storage suitable for the sensor and policy artefacts your subnet expects.

## Next steps

* [Subnets overview](/subnets-workload-classes/subnets.md)
* [CLI – join as miner](/sdk/cli.md)
* [Python SDK](/sdk/python.md)
* [SDK overview](/sdk/sdk.md)