
Scout plugin in action!
Kleros Scout MetaMask Snap
Kleros Scout is available as a MetaMask Snap that enables safer contract interactions by delivering community-curated insights about the contracts you interact with on the blockchain. With each transaction, a tab displays insights about the contract being interacted with. The Snap provides metadata from three decentralized registries:- Address Tags Registry: verified project names and contract tags
- Contract-Domain Name Registry: verified contract-to-domain pairings
- Tokens Registry: ERC-20 token information
Installation
1
Install from the Snaps Directory
Install directly from the official MetaMask Snaps Directory, or search for
@kleros/scout-snap.2
Confirm the installation
Approve the Snap installation in MetaMask. Insights then appear automatically in a transaction tab whenever you interact with a contract.

How to use the Snap’s features?
Once you install the Kleros Scout Snap, with every txn/contract interaction, you will see a tab which provides you with insights around the same. Upon installation, If you see this, you are already using community curated contract insights for secure dapp interaction - the most important feature of the Kleros Scout Snap.
Limitations
The Snap explicitly does not:- Endorse any contract interaction
- Use centralized whitelisting: all data is community-curated
- Guarantee 100% accuracy or accept liability for insights
Knowledge Base
How is contract information curated for the Scout Snap?
How is contract information curated for the Scout Snap?
Kleros Curate is a decentralized dApp used to create open curated registries. Financial incentives and dispute resolution maintain the quality and policy compliance of every entry.
Who controls the entries on the list?
Who controls the entries on the list?
Community members submit items with deposits, and anyone can challenge a submission during a vetting period. Unchallenged entries are approved; challenged ones go to Kleros jurors for resolution. No single party controls the registry.
Why is decentralized contract data needed?
Why is decentralized contract data needed?
Centralized parties have financial incentives to whitelist tokens or manage address tags for profit, which creates vulnerabilities to phishing and manipulation. Decentralized, community-secured data removes that single point of failure.
Can I submit contract insights?
Can I submit contract insights?
Yes, community submissions are encouraged. See the Scout Tutorial for step-by-step guides to making submissions to the three security metadata registries.
What motivates people to submit?
What motivates people to submit?
Two things: incentives (Kleros runs regular programs rewarding active submitters, see Earn with Scout) and community benefit (there is minimal risk in submitting known-safe contracts you have used, and doing so protects thousands of users).
Support
- Telegram support group: t.me/KlerosCurate
- Email: support@kleros.io
- Typical response time: 24-48 hours