Curate

Introduction

Curate is a decentralized system for creating community-curated lists on the blockchain. Anyone can submit items, challenge entries, and participate through economic incentives. When disputes arise, they’re resolved through Kleros Court. This page covers both V1 (Classic and Light Curate on Ethereum / Gnosis Chain) and V2 (Arbitrum).

Smart Contracts

Core contract interfaces and data structures

Curate Classic (V1)

V1 integration guide - full TCR

Light Curate (V1)

V1 integration guide - simplified TCR

Registries

Registry reference

V1 - Curate Classic and Light Curate (Ethereum / Gnosis Chain)

Curate Classic is the full Token-Curated Registry, and Light Curate is the simplified, higher-volume variant. Both are on Ethereum and Gnosis Chain and are eligible for direct integration by third-party developers. Full V1 integration guides are available: see the Curate Classic and Light Curate subpages. For V1 contract addresses, see Deployment Addresses.

V2 - Curate V2 (Arbitrum)

The sections below document Curate V2 technical details. Technical notes for integrators:

Evidence handling: Curate V2 does not use a separate Evidence Module; evidence submission is handled directly by the CurateV2 and CurateFactory contracts
Subgraph: the schema includes dedicated fields for requester and challenger evidence
Frontend stack: the interface uses Tailwind CSS and the shared components library, including the shared file viewer
Developer documentation: basic developer documentation is available in the Curate V2 GitHub repository

Deployment

Arbitrum One (Production)
Arbitrum Sepolia (Testnet)

Component	Purpose
CurateV2	Implementation contract
CurateFactory	Deploys new registries via ERC-1167 proxies
CurateView	Batch query helper

Deploy your own registry through the CurateFactory contract. Each registry is an independent ERC-1167 minimal proxy.

Key Improvements from V1

Feature	V1	V2
Deployment	Full contract per registry	ERC-1167 minimal proxy pattern
Governance	Single governor role	Separate governor and relayer roles
Arbitration	Parameters can change during dispute	Versioned arbitration parameters preserved
Queries	Individual calls	Enhanced batch queries via View contract

System Architecture

Item Lifecycle

Items in Curate V2 follow a state machine with four possible states:

Status Definitions

Status	Description
Absent	Item does not exist in the registry
RegistrationRequested	Item submission pending, can be challenged
Registered	Item is active in the registry
ClearingRequested	Removal pending, can be challenged

Challenge Mechanism

Request Submitted

User submits item (registration) or removal request with required deposit.

Challenge Period

Anyone can challenge during the challenge period by paying the challenge deposit.

Dispute Created

If challenged, a dispute is created in Kleros Court.

Resolution

Winner receives both deposits. Loser forfeits their deposit.

Economic Model

Deposits Required

Action	Deposit Type
Submit item	Submission deposit + Arbitration cost
Remove item	Removal deposit + Arbitration cost
Challenge submission	Submission challenge deposit + Arbitration cost
Challenge removal	Removal challenge deposit + Arbitration cost

Example Flow

User submits item:
  Pays: submissionDeposit + arbitrationCost

Someone challenges:
  Pays: challengeDeposit + arbitrationCost

Contract holds: submissionDeposit + challengeDeposit
Arbitrator gets: 2 × arbitrationCost

Winner receives: all held deposits

Role Permissions

Governor

Change arbitrator and arbitration parameters
Update base deposits
Modify challenge period duration
Set connected lists
Update list metadata
Add/remove items directly (bypass challenge period)

Relayer

Add items directly (bypass challenge period)
Remove items directly (bypass challenge period)
Useful for automated integrations

Public

Submit item requests
Submit removal requests
Challenge requests
Execute unchallenged requests
Submit evidence

Arbitration Parameter Versioning

Key Insight: arbitrationParamsIndex ensures disputes use the arbitration settings that were active when the request was created, even if governance later changes them.

struct ArbitrationParams {
    IArbitratorV2 arbitrator;
    bytes arbitratorExtraData;
    EvidenceModule evidenceModule;
}

This prevents governance from affecting ongoing disputes by changing arbitrator settings mid-dispute.

Use Cases

Token Lists

Community-curated lists of legitimate tokens, filtering out scams

NFT Collections

Verified collections and authenticity registries

Address Tags

Label addresses with warnings, categories, or metadata

Content Moderation

Decentralized content curation and filtering

Stake Curate

Stake Curate is part of the Curate product family. It uses V1 Kleros Court on Gnosis Chain for dispute resolution. Unlike traditional Curate, where deposits are returned after listing, Stake Curate keeps deposits locked - anyone can challenge at any time, and challengers earn bounties. It launched in January 2026, with its first use case being Battle-Tested DeFi Vaults.

Scout

Scout is the primary frontend for the Curate-based address tag registries. It reached its definitive version in May 2026 with over 2.6 million curated on-chain addresses. For technical details, chain support, partners, and the GTCR Indexer, see the Scout page. The GTCR Indexer schema was extended with challenge transaction hashes, challenge dates, and appeal transaction hashes (v0.1.7, April 2026), with an Envio branch maintained alongside the main branch.

Resources

GitHub Repository

Smart contracts and deployment scripts

Live Application

Production Curate interface

Discord Community

Get help from the community

Getting Started

V2 Architecture

Arbitrable Apps

Products

Cross-chain

Examples

Subgraph & Data

Introduction

Smart Contracts

Curate Classic (V1)

Light Curate (V1)

Registries

V1 - Curate Classic and Light Curate (Ethereum / Gnosis Chain)

V2 - Curate V2 (Arbitrum)

Deployment

Key Improvements from V1

System Architecture

Item Lifecycle

Status Definitions

Challenge Mechanism

Economic Model

Deposits Required

Example Flow

Role Permissions

Arbitration Parameter Versioning

Use Cases

Token Lists

NFT Collections

Address Tags

Content Moderation

Stake Curate

Scout

Resources

GitHub Repository

Live Application

Discord Community

​Introduction

Smart Contracts

Curate Classic (V1)

Light Curate (V1)

Registries

​V1 - Curate Classic and Light Curate (Ethereum / Gnosis Chain)

​V2 - Curate V2 (Arbitrum)

​Deployment

​Key Improvements from V1

​System Architecture

​Item Lifecycle

​Status Definitions

​Challenge Mechanism

​Economic Model

​Deposits Required

​Example Flow

​Role Permissions

​Arbitration Parameter Versioning

​Use Cases

Token Lists

NFT Collections

Address Tags

Content Moderation

​Stake Curate

​Scout

​Resources

GitHub Repository

Live Application

Discord Community

Introduction

V1 - Curate Classic and Light Curate (Ethereum / Gnosis Chain)

V2 - Curate V2 (Arbitrum)

Deployment

Key Improvements from V1

System Architecture

Item Lifecycle

Status Definitions

Challenge Mechanism

Economic Model

Deposits Required

Example Flow

Role Permissions

Arbitration Parameter Versioning

Use Cases

Stake Curate

Scout

Resources