# Roadmap

Work runs on parallel tracks. The current **testnet** delivers a verifiable core: a public Substrate L1, faucet-issued test KNX, three workload subnets (**drone navigation**, **roboarm VLA**, **SLAM 3D map**) with end-to-end task submission, miner competition, validator scoring, and onchain PoPW-related records, plus reference miners and validators in open source.

Mainnet and full economic features are staged so readers can see what is live versus what is sequenced. Whitepaper components map to the phases below.

> For deploy status, treat the [block explorer](https://subnets.testnet.konnex.world/explorer) and official **release notes** as the source of truth for a running network.

## Testnet (current direction)

**In scope:** Public chain, faucet, three subnets as above, PoPW-backed task flow, published binaries.

**Not implied to be complete against the full whitepaper:** mainnet stablecoin settlement at scale, full dual-staking in production for every role, mesh transport as the default for all robots, and a mature inter-robot contract marketplace. Those are later phases.

## Phase 1 — mainnet economics and enterprise settlement

| Theme                    | Technical focus                                                                                                               | Outcome                                                                |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| Stablecoin layer         | Escrow, payouts, and penalties in stablecoins; fiat-peg UX for tasks and SLAs                                                 | Enterprises budget without holding volatile tokens for day-to-day work |
| Dual stake               | KNX for consensus security; stablecoin assurance for settlement-layer faults; governance-tuned parameters                     | Compensation paths for provable settlement errors                      |
| Registries and contracts | Hardened task registry, identity, and payout routers per [protocol architecture](/understand-konnex/protocol-architecture.md) | B2B integrations and composability                                     |

## Phase 2 — scale-out and physical fabric

| Theme                    | Technical focus                                                               | Outcome                                                     |
| ------------------------ | ----------------------------------------------------------------------------- | ----------------------------------------------------------- |
| Mesh transport           | libp2p-style participation for edge robots without a single cloud choke point | Broader geographic and tactical reach                       |
| Robot-to-robot contracts | Onchain hiring between machines with stablecoin deposits and enforcement      | Fleets that contract with each other with minimal human ops |
| Cross-chain and ramps    | Approved bridges and optional fiat/crypto ramps                               | Liquidity and invoicing options for operators               |

## Cross-cutting tracks (ongoing)

* **Migration** — Commercial pilots moving from offchain telemetry to onchain PoPW.
* **Revenue** — Programmatic billing tied to verified usage.
* **Builder** — SDKs and APIs ([SDK](/sdk/sdk.md)); tooling for new workload classes.
* **Enterprise** — SLA-grade RPC, reliability, identity and compliance options.
* **Research** — RL / VLA pipelines and lab partnerships (see [decentralized AI ecosystem](/understand-konnex/ai-ecosystem.md)).

## Staged narrative

The path from simulators and pilots to a broad global ledger is deliberate: physical autonomy must prove itself at every step. The public testnet is the first onramp for anyone to post a real task and inspect onchain activity in minutes — see **release notes** and the testnet explorer.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.konnex.world/understand-konnex/roadmap.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.