Skip to main content
Kleros Curate Interface

​
Curate

Curate is a decentralized application for creating and maintaining community-curated registries. Anyone can submit items to a list, and anyone can challenge incorrect or malicious submissions-with disputes resolved by Kleros Court. Think of it as Wikipedia for structured data, but with economic skin in the game. Submitters stake a deposit that they lose if their submission is successfully challenged. Challengers risk their own deposit if the submission turns out to be valid. This creates a self-sustaining system where participants are economically incentivized to maintain accurate registries. Curate powers critical infrastructure across Web3: token lists that wallets use to display assets, address tags that block explorers use to label contracts, and security registries that help users avoid scams.

​
Curate Variants

Curate is a family of three variants. All three use the V1 Kleros Court for dispute resolution.
  • Classic Curate (V1) - a full Token-Curated Registry (TCR) supporting complex schemas. Best for high-value registries with custom fields. Migrated to Gnosis Chain.
  • Light Curate (V1) - a simplified TCR built for higher volume and lower gas costs. On Gnosis Chain.
  • Stake Curate (V1 infrastructure) - continuous verification with permanent deposits, on Gnosis Chain. Deployed mid-August 2025; first implementation with DAMM Capital (September 2025). See Stake Curate.

​
Key Capabilities

Permissionless submissions

Anyone can add items to a registry by staking a deposit

Community curation

Anyone can challenge incorrect submissions

Dispute resolution

Contested items are decided by Kleros Court jurors

Flexible schemas

Create registries for any type of structured data

On-chain data

Registry data is fully on-chain and queryable

Earn rewards

Successful challengers earn the submitter’s deposit

​
How It Works

Curate uses a mechanism called a Token Curated Registry (TCR). Here’s the flow:
1

Submission

A user submits an item (e.g., a token address with metadata) and stakes a deposit. The submission enters a pending state.
2

Challenge period

During the challenge period, anyone can challenge the submission by staking their own deposit. If no one challenges, the item is accepted into the registry.
3

Dispute (if challenged)

If challenged, a dispute is created in Kleros Court. Jurors review the evidence and vote on whether the submission meets the registry’s acceptance criteria.
4

Resolution

The winning party receives both deposits (minus arbitration fees). The item is either accepted or rejected based on the ruling.

​
The Incentive Structure

The beauty of TCRs is that you don’t need to trust anyone:
  • Submitters are incentivized to only submit valid items (or lose their deposit)
  • Challengers are incentivized to only challenge invalid items (or lose their deposit)
  • Jurors are incentivized to vote honestly (via Kleros’s Schelling point mechanism)
This creates a self-policing system where bad actors are economically punished.

​
Use Cases

Problem: Wallets and exchanges need to know which tokens are legitimate.Solution: Community-curated token registries where anyone can submit tokens and anyone can challenge scams or duplicates.Example: The Kleros Token Registry is used by wallets to display token information and warn users about unverified assets.

​
Who Uses Curate?

  • Wallets query token registries to display asset information
  • Block explorers use address tags for human-readable labels
  • DeFi protocols check registries before listing new assets
  • Security tools aggregate risk information from curated lists
  • DAOs maintain member or contributor registries

​
Registry Types

Curate offers three variants across the two protocol versions: Among the V1 variants, most registries use Light Curate for cost efficiency. Classic Curate is used when you need custom fields or complex acceptance criteria.

​
Current Status

As of the May 2026 development update, Curate V2 aligned its evidence query with the kleros-core schema migration and removed an unused evidence hook. Work is in progress to integrate a shared file-viewer component. Follow development on the Kleros blog - developer updates.

​
What’s Next?

Use Curate

Step-by-step guidesLearn how to submit items, challenge submissions, and earn rewards.

Build on Curate

Integration guideQuery registry data, build custom UIs, or create your own registry.→ Developer Docs

Understand TCRs

Game theory deep diveLearn the economics and incentives behind Token Curated Registries.→ Concepts

Launch Curate

Open the Curate application

Curate Subgraph

Query registry data via GraphQL

Contract Addresses

Curate V2 deployment addresses

Create a Registry

Guide to deploying your own registry