Scout

Scout is part of the Curate product family - it is a frontend that reads from Curate registries. It currently uses V1 Curate registries. The Scout V2 frontend redesign is complete, with underlying registry migration to V2 planned.
Key Capabilities
Address Tagging
Community-curated labels for smart contract addresses across multiple chains
Token Verification
Verified token metadata including names, logos, and contract details
Multi-Chain Coverage
Supports Ethereum Mainnet, Arbitrum, Base, Gnosis, Polygon, and other EVM chains
How Scout Works
Scout itself does not manage submissions or disputes those happen in Curate. Scout reads from four main Curate registries: Address Tags Registry (ATR): Maps contract addresses to human-readable labels (e.g., “Uniswap V3 Router”). These tags appear in block explorers like Blockscout and wallet interfaces like MetaMask. Address Tags Query (ATQ): Handles removal requests and quality checks for the ATR. Token Registry: Curated list of verified ERC-20 tokens with metadata (name, symbol, logo, decimals). Contract Domain Names (CDN): Stores additional metadata like project logos and descriptions served to dApps.Integrations
Scout data powers labels and safety information in several major products:- Blockscout: Address labels from Scout registries
- MetaMask Snaps: Contract verification data
- Otterscan: Contract tags
- Uniswap, Zerion: Token metadata
Earning Rewards Through Curation
Kleros runs active incentive programs for Scout registry contributors. Curators earn PNK rewards for submitting accurate address tags and successfully challenging incorrect ones. Current incentive details (updated monthly via blog posts):- Submission and removal reward pools are distributed proportionally among successful participants
- Specific chains are eligible for rewards each month
- ERC-20, ERC-721, and EIP-1167 contract submissions may have different reward eligibility rules
Current Status
As of the May 2026 development update, Scout reached its definitive version with 2.6M+ curated addresses shown on the homepage. Recent work includes completing the Atlas IPFS migration (submissions and evidence now go through the Atlas SIWE flow), adding ATQ duplicate detection, and adding the JavaScript Court to the disputes view. Follow development on the Kleros blog - developer updates.What’s Next?
Explore Scout
Browse community-curated address tags and token data
Curate
Learn about the registry system that powers Scout
Build on Scout
Query Scout registry data for your application