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.
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).
A compliant miner build for the workload you target (see the Konnex GitHub org).
Uplink and storage suitable for the sensor and policy artefacts your subnet expects.
Next steps
Last updated