The Ligate docs.
Everything you need to build on the Ligate sovereign rollup — Proof of Prompt receipts, Kleidon SDKs, node operator guides, and the reference for both protocols.
This is the developer documentation for Ligate Labs. It is early. Some pages are drafts, some are empty outlines. We're filling it in as the devnet firms up — the goal is that by mainnet, every surface a developer touches is documented, with runnable examples.
Start here
Getting started
Install the CLI, claim $LGT from the faucet, ship your first attestation. End-to-end in under five minutes.
Devnet
Network details, RPC endpoints, chain ID, faucet. Everything you need to point a local wallet at Ligate.
Proof of Prompt
The on-chain receipt spec for AI interactions. Fields, canonical encoding, attestor quorum, verification.
SDKs
Client libraries for Python, TypeScript, Rust, and Go — plus Unity C# and Unreal C++ for Kleidon.
By product
Themisra
Hash any prompt + output pair, quorum-attest it on-chain, verify it anywhere. Model-agnostic (Claude, GPT, Gemini, Llama, any OpenAI-compatible endpoint).
Kleidon
Four products: Passify (subscription NFTs), SkinsVault (game assets), TokenForge (currencies), MintMarket (white-label marketplace). One SDK, one dashboard.
Run infrastructure
Node operators
Hardware requirements, Docker image, stake + slashing, Grafana dashboard. Run an attestor on devnet and earn testnet $LGT.
Status
Per-component state of Ligate services. Updated in real time post-mainnet.
Stay current
Release notes live on the main site at ligate.io/changelog. Research posts and specs-in-draft on the blog. Questions → hello@ligate.io; RFCs → GitHub.