Curate

Decentralized lists and registries powered by crypto-economic incentives

Curate

V2

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.

Looking for V1 documentation? See Curate V1 (Legacy).

---

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

Token Lists

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.

Address Tags

Problem: Block explorers show raw addresses with no context about what they are.

Solution: Registries that map addresses to human-readable labels (e.g., “Uniswap V3 Router”, “Vitalik.eth”).

Example: Address tag registries power the labels you see on Etherscan and other explorers.

Contract Security

Problem: Users can’t easily verify if a smart contract is safe to interact with.

Solution: Security registries where auditors and community members flag risky or verified contracts.

Example: Kleros Scout displays security information from Curate registries.

CDN & Content

Problem: Decentralized apps need reliable metadata (logos, descriptions, links).

Solution: Registries that store and serve verified content metadata.

Example: Token logos and project information served to dApps across the ecosystem.

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 supports two registry architectures:

Type	Best For	Gas Costs	Flexibility
Curate (full)	High-value registries with complex schemas	Higher	Maximum
Light Curate	Simple registries, higher volume	Lower	Standard schemas

Most new registries use Light Curate for cost efficiency. Full Curate is used when you need custom fields or complex acceptance criteria.

---

What’s Next?

Use Curate

Step-by-step guides

Learn how to submit items, challenge submissions, and earn rewards.

→ Help Center

Build on Curate

Integration guide

Query registry data, build custom UIs, or create your own registry.

→ Developer Docs

Understand TCRs

Game theory deep dive

Learn the economics and incentives behind Token Curated Registries.

→ Concepts

---

Quick Links

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