Scout Incentives, Policy and Parameters Updates August 2025

Attention, Curators! In response to feedback from the community, we are rolling out the largest ever set of updates to both the incentives and parameters of the Kleros Scout Registries! The goal? Make participation cheaper, focus rewards on high-impact submissions, improve policy clarity, increase fairness in the way we distribute incentives and source more submissions that are useful to new partners!

1. Registry Parameters (Address Tag, Token, CDN): reducing barriers

In response to frequent feedback from curators, we're lowering economic barriers to make it easier for more contributors to join.

With AI tools now supporting curators, the volume of reviewed and submitted assets can significantly increase. This boost in efficiency allows us to reduce the submission deposit. Accordingly, the bounty amount has also been adjusted (as it is tied to the submission amount), but we believe it reflects the effort required for each validated entry. Plus, more entries= more opportunities of spotting faulty submissions! 👀.

Here is a summary:

Submission Parameters

Removal Parameters

2. Monthly Incentives: boosting submissions, rewarding removals and new criteria

As part of the ongoing evolution of Kleros Scout, we’re introducing two key updates to the incentive program for August. These changes are designed to support broader participation, improve data quality, and ensure the registry continues to meet the growing demands of our partners across the Web3 ecosystem.

Increasing number of entries

Max reward per successful submission: 500 PNK

The price of PNK has nearly doubled in the past month, so this change keeps the dollar value of rewards roughly the same (around $12 per submission as of today).

Our goal is to remain the leading decentralized source of contract metadata. The more entries we get, the stronger the case to keep funding it. With AI speeding up the process, this cap change lets more users contribute efficiently.

Keeping high quality: introducing removal request rewards!

Another frequently requested feature is now live: incentives for valid removal requests.

Starting this month, 7% of each registry’s reward pool (7’000 PNK per registry) will be allocated to removals.

• Maximum reward per successful removal: 500 PNK
• Reward formula: reward_per_removal = reward_pool / total_removals

This update encourages curators to help clean up outdated, duplicate, or low-quality entries, making our registries more trustworthy and useful for all partners and users.

Incentive Recap

• Monthly pool 300’000 PNK
  • 100’000 PNK (of whom 7’000PNK to Removal request) Address Tag Registry. 
  • 100’000 PNK (of whom 7’000PNK to Removal request) Token Registry
  • 100’000 PNK (of whom 7’000PNK to Removal request) CDN Registry
• Formula:
  • reward per submission = reward_pool * ((1 / (2 * total_submissions)) + (txns_with_contract / (2 * total_txns_with_all_contracts)))
• Solana tokens: min 5’000 Holders
• Awardable chains: Avalanche C-Chain; zkSync; Scroll; Gnosis; Celo; Base; Solana; Arbitrum One; OP Mainnet.
• In order to be rewarded, entries (on Address Tag Registry, Token Registry and CDN  Registry) must not already be tagged on the respective block explorer of the etherscan family:
  • Avalanche C-Chain → snowscan.xyz
  • zkSync → era.zksync.network
  • Scroll → scrollscan.com
  • Gnosis → gnosisscan.io
  • Celo → celoscan.io
  • Base → basescan.org
  • Solana → solscan.io
  • Arbitrum One → arbiscan.io
  • OP Mainnet → optimistic.etherscan.io

3. Policy Updates: Address Tag Registry

Clarification on Naming Criteria and Duplicates:  

This update clarifies that entries sharing the same identifiers (Project Name, Public Name Tag, Public Note, Website) but for different contract addresses are not considered duplicates and must be accepted, provided they comply with the policy’s naming criteria.

The goal is to prevent unfair rejections when a submitter follows the naming rules of the policy. As long as the submitter correctly applies the naming criteria, a new submission should not be treated as a duplicate or be rejected solely because the project reuses names for different contracts. The goal is to avoid penalizing valid submissions that happen to share names or identifiers with other addresses due to project practices outside the submitter’s control.

TL;DR

• New Parameters:
  • Deposits for Submission or Removal requests: reduced from 60 to 50 xDai.
  • Bounty for successful submission challenges and successful removal challenges will be 30 xDai.
  • Bounty for unsuccessful Removal Challenges removed.
• New parameters will be online on Friday 1st August.
• Max reward per entry: 500 PNK.
• Introducing removal rewards (7% of each registry’s monthly pool), Max 500 PNK per removal.
• For Address Tag Registry: two entries with different addresses will not be considered duplicates. Even if the rest of the fields are the same.
• Detailed definition of an active project (Address Tag, Tokens, CDN)