Build with us.
Get paid for it.
The Ligate grants program funds teams building products, research, operator infrastructure, and open-source tooling that strengthens the ecosystem. Paid in $LGT.
Four tracks. Four kinds of work we fund.
Not every grant fits neatly. Pick the track closest to your project and apply — we'll route it internally if it fits another better.
Builders
For game studios, SaaS teams, and Web3-native products building with Kleidon or Themisra. Grants offset integration cost and early infrastructure spend.
- A shipped product (launched, not planned)
- Public post-mortem or write-up within 60 days of shipping
- MIT or Apache-licensed integration code if derived from our SDK
- ›A Unity studio integrating SkinsVault for their first on-chain drop
- ›A SaaS company building a Passify subscription tier
- ›An indie team using TokenForge for an in-game currency
Researchers
For cryptographers, protocol engineers, and academics working on Proof of Prompt, ZK receipts, attestor quorum games, and adjacent topics. Output is papers and RFCs, not product.
- A published paper, RFC, or spec draft (with our logo listed as funder)
- Code reference implementation where applicable
- Open-source under permissive license
- ›A formal proof of the Proof of Prompt quorum safety properties
- ›A comparative analysis of SP1 vs RISC Zero for redactable receipts
- ›Game-theoretic analysis of attestor slashing under adversarial conditions
Operators
For teams committing to run long-lived attestor infrastructure on devnet and mainnet. Grants cover the first year of cloud cost plus a small stipend.
- 12-month operator commitment (devnet + mainnet transition)
- Public Grafana dashboard link for your nodes
- Monthly SLA reports shared with the core team
- ›A regional cooperative running 3 geographically distributed attestors
- ›A staking service adding Ligate as a supported network
- ›An academic lab running validator research nodes
Public goods
For anyone building free, open, non-commercial tools that make Ligate better for everyone: explorer components, dev tooling, SDK extensions, translated docs, educational content.
- Open-source code under MIT or Apache-2.0
- Public hosting or npm distribution
- Maintenance commitment for at least 6 months
- ›A Python SDK for Themisra attestation
- ›A VS Code extension for Kleidon contract development
- ›A translated version of the docs into a major non-English language
Four steps. Under two weeks to a decision.
Send a short application
Email hello@ligate.io with: the track, a one-pager on what you want to build, who's building it, and the ask. No 40-page deck. One page is fine.
Discovery call
If there's a fit, we schedule a 30-minute call with the grants committee. We ask about scope, team, and how you'll know you're done.
Offer + milestones
We write a milestone-based offer. Typically 3-4 milestones with payments on delivery. You sign, we transfer the first milestone, you ship.
Ship + publish
You hit milestones. We pay. You publish the output publicly (post, paper, code, video). We amplify it across our channels.
Common questions, short answers.
- Do I need to already be a Ligate user to apply?
- No. Builders and operators usually are; researchers and public-goods applicants often aren't. What matters is that the work benefits the Ligate ecosystem.
- Paid in $LGT — when?
- Pre-TGE, we pay in USDC at an agreed $LGT reference rate, with the $LGT owed delivered at TGE (subject to a short vest). Post-TGE, direct $LGT transfers on a milestone schedule.
- Can I apply for multiple tracks?
- No. Pick the closest one. If we think another fits better during review, we'll suggest switching.
- Equity, revenue share, or obligations?
- None. Grants are grants. We don't take equity or a revenue share, and the code / research output belongs to you (under the licences listed in the track deliverables).
- What if my project fails?
- Honest failure is fine — we pay through the milestones you hit and part ways. Dishonest failure (no output, no communication) means we reclaim unspent funds.
A one-pager and an email. That's it.
Email hello@ligate.io with the track, what you want to build, who's building it, and the ask. We reply within two weeks.