LigateLabs
GitHub ↗
Start here · 5 min

Getting started.

Install the Ligate CLI, claim testnet $LGT from the faucet, and ship your first Proof of Prompt attestation. End-to-end in under five minutes.

Heads up
Preview only. The CLI, faucet, and attestor network are under active development. Devnet target Q2 2026. The commands below show the DX we're building — they do not work today. Email hello@ligate.io to join the early access list.

1. Install the CLI

One-line install, planned for macOS, Linux, and Windows (WSL).

$ curl -s https://ligate.io/install | sh
$ ligate --version
ligate-cli 0.x.x-devnet

2. Sign in

Authentication runs through Privy — sign in with either an email address or a wallet. No MetaMask popups required.

$ ligate auth login --email you@yours.com
✓ Check your email for a sign-in link
✓ Signed in as 0x7d2a...c91e

3. Claim testnet $LGT

Every new account gets 1000 $LGT from the faucet per day. You need gas to submit an attestation transaction.

$ ligate faucet claim
✓ 1000 $LGT sent
  tx     0xbcf4...d08a
  block  1,481,203
  explorer https://explorer.devnet.ligate.io/tx/0xbcf4d08a

4. Your first attestation

The basic shape of a Proof of Prompt: hand the CLI a prompt, a model, and (optionally) a response file. It hashes everything, submits the receipt to the chain, waits for the attestor quorum, and returns a verifiable receipt ID.

$ ligate attest \
  --model claude-4.7-opus \
  --prompt "Write a recursive descent parser in Rust" \
  --output ./response.md

✓ attestation 0x91c4...ea3d anchored (celestia-mocha)
  quorum      42/62 attestors signed
  gas         0.0009 $LGT
  block       1,481,207

Verify it

Anyone can verify a receipt. Verification checks three things: that the blob is anchored on Celestia, that the attestor quorum met threshold, and that the BLS aggregate signature is valid.

$ ligate verify 0x91c4...ea3d
✓ receipt anchored (celestia-mocha block 1,481,207)
✓ attestor quorum met (42/62 signed, threshold 42/62)
✓ BLS aggregate valid
Note
The receipt's prompt_hash and output_hash are SHA-256 over canonical UTF-8 bytes. See the Proof of Prompt spec for the exact canonicalisation rules.

What's next

You've run an end-to-end attestation. A few places to go from here: