The roadmap, in public.
Seven phases. What we're shipping now, what's next, and what's further out. Updated as reality negotiates with the plan.
What we ship, and when we admit it moved.
The smallest honest surface
A chat that works, a receipt that verifies, an SDK you can hold in your hand. No chain of our own yet — we rent one. Kleidon ships as a skeleton we can point at.
- Rust/Axum backend with Anthropic API integration
- Proof of Prompt spec v0.1 (hash + timestamp + quorum)
- Native chat UI with per-message proof display
- Privy auth (email + wallet sign-in)
- Temporary proof storage on Solana / Ethereum testnet
- Kleidon SDK v0: Passify contracts + operator dashboard skeleton
Feedback loops
Prompt engineering becomes a game you can win. Battles, tournaments, leaderboards, a discovery feed that tells you what's working — and a Unity / Unreal path for the studios waiting on Kleidon.
- AI Battles (1v1 prompt competitions)
- Daily prompt challenges + leaderboards
- AI model tournaments (Claude vs GPT vs Gemini)
- Prompt discovery feed + upvoting
- Share results to X / socials
- Kleidon JS/TS SDK + Unity C# + Unreal C++ SDKs
- SkinsVault dynamic metadata pipeline
Sovereign day
The rollup goes live, the token launches, every receipt we issued on a borrowed chain migrates home. Ligate becomes the substrate instead of a promise about one.
- Sovereign SDK rollup on Celestia Mocha
- Custom transaction types: SubmitPrompt, ClaimProof, CreateBattle
- Sequencer + 2–3 full nodes deployed
- $LGT token launch + distribution
- Transaction fee split live (40% sequencer, 30% nodes, 20% treasury, 10% burn)
- Native indexer, Swagger API docs, Grafana monitoring
- MintMarket full white-label, operator analytics dashboard
- Kleidon mainnet deployment on Ligate
Prompt engineering becomes a job
Composable prompts earn royalties downstream. Bounties flow the other direction. NFTs move between wallets without losing provenance. If you're good at writing prompts, you can make a living writing prompts.
- Prompt marketplace (buy/sell/license)
- Prompt NFTs with utility (own = right to use + earn)
- Prompt chains with royalties (composable prompts, downstream earnings)
- Prompt bounties (companies post challenges, creators solve)
- Prompt staking (prediction market for quality)
- Prompt fingerprinting + anti-plagiarism
- Creator analytics + royalty payment system
Private by proof
The receipt still verifies when the prompt can't be read. ZK redaction lands, and IP-sensitive AI usage gets a chain it can finally run on.
- Confidential Prompts via SP1 or RISC Zero
- Redactable receipts (prove consistency without revealing content)
- ZK proving pipeline + Boundless integration
- Privacy toggle in UI (public / private per message)
- ZK-verified quality scores
The surface enterprises pay for
The EU AI Act and its successors turn verifiable AI from nice-to-have into must-have. Team Workspaces, verifiable agents, API gateway — the compliance surface priced by the seat.
- Team Workspaces with admin dashboards and compliance reporting
- AI Output Disputes (immutable record for conflict resolution)
- Verifiable AI Agents (full audit trail for autonomous actions)
- AI Detector / Proof of Human
- API Gateway (middleware for developers)
- Custom model integrations
- Enterprise billing (USD + $LGT)
Where the edges get interesting
Kleidon deploys wherever your users already are. Governance goes to the token holders. The academy ships, the mobile app ships, the sequencer decentralises. Everything that was "later" becomes "now."
- Hyperlane bridge to Ethereum, Base, Polygon
- Solana support for Kleidon (SPL tokens, Anchor contracts, Phantom)
- Operators choose deployment chain at setup
- Prompt DAOs, prompt inheritance, prompt insurance
- Real-time collaboration (Google Docs for prompting)
- Learn-to-Earn academy + mobile app
- Decentralize sequencing + community-run full nodes
- DAO governance for protocol upgrades
Four labels, each meaning something specific.
Code merges weekly. Design partners welcome. The dates here are real ones.
Spec is in draft. Engineering kicks in the moment the current phase lands.
Committed work. Dates slip only when upstream learnings say they should — and when they do, we say so here.
Directional. Revisited quarterly against what customers actually ask for, not what reads well on a deck.
The roadmap moves. So do we.
Every phase gets revised against what devnet operators, design partners, and the community actually need. File an RFC on GitHub, or tell us directly.