Sign in Subscribe

August 2026: Scout Incentives, New Chain Coverage and Agent-Ready Submissions

August 2026: Scout Incentives, New Chain Coverage and Agent-Ready Submissions

August introduces three important updates:

  • Robinhood Chain is now supported. Gnosis and zkSync networks now point to Blockscout.
  • The Hidden Voting Court migration has been completed successfully, with the first nine cases.
  • Scout submission skills are ready, allowing users to delegate the complete submission process to an AI agent.

1. Incentives

Explorer Tagging Requirement for ATR and Token Submissions

To be eligible for rewards, entries submitted to the Address Tag Registry or Kleros Token Registry must not already be tagged on the reference block explorer for the corresponding chain.

Before submitting, check the following explorers:

  • Ethereum Mainnet → etherscan.io
  • Avalanche C-Chain → snowscan.xyz
  • Celo → celoscan.io
  • Base → basescan.org
  • Linea → lineascan.build
  • Solana → solscan.io
  • Arbitrum One → arbiscan.io
  • OP Mainnet → optimistic.etherscan.io
  • Polygon → polygonscan.com
  • MegaETH → mega.etherscan.io
  • Gnosis → gnosis.blockscout.com
  • zkSync → zksync.blockscout.com
  • Robinhood Chain → robinhoodchain.blockscout.com

Robinhood Chain Added

Robinhood Chain has been added to the supported chains for Scout incentives.

Its growing activity creates new opportunities to discover untagged contracts, tokens and addresses that can be added to the Scout registries.

Before submitting a Robinhood Chain entry, contributors should check:

https://robinhoodchain.blockscout.com/

Entries that are already tagged there will not be eligible for Scout incentives.

Updates for zkSync, Gnosis and Scroll.

  • For zkSync, contributors should now use:

https://zksync.blockscout.com/

  • For Gnosis, contributors should now use:

https://gnosis.blockscout.com/

This means GnosisScan will no longer be the reference used to determine whether a Gnosis entry is already tagged.

  • For Scroll: Entries belonging to this network will no longer be eligible.

We will continue monitoring the reliability and coverage of these explorers and may revisit this setup if ecosystem conditions change.

Note: Contract Domain Name Registry entries are not subject to the explorer tagging requirement.

Even when an ATR or Token Registry entry is not eligible for rewards, it can still be submitted. If it satisfies the registry policy, it will be accepted and will continue strengthening the Scout database.

2. Incentive Parameters

The incentive pools and formulas remain unchanged for August.

The four reward pools and their submission/removal split

Address Tag Registry

Pool: 100,000 PNK

  • 93,000 PNK for successful submissions
  • 7,000 PNK for successful removals
  • Maximum reward per successful submission: 500 PNK
  • Maximum reward per successful removal: 500 PNK

ERC-20, ERC-721 and EIP-1167 submissions remain excluded from incentives. However, they are still accepted when they comply with the registry policy.

Submissions:

reward_per_submission = reward_pool * ((1 / (2 * total_submissions)) +(txns_with_contract / (2 * total_txns_with_all_contracts)))

Removals:

reward_per_removal = reward_pool / total_removals

Kleros Token Registry

Pool: 100,000 PNK

  • 93,000 PNK for successful submissions
  • 7,000 PNK for successful removals
  • Maximum reward per successful submission: 500 PNK
  • Maximum reward per successful removal: 500 PNK

Solana tokens must have at least 5,000 holders to be eligible for incentives.

Submissions:

reward_per_submission = ( (token_tx / total_txns_with_all_contracts) * 0.1 * reward_pool ) +( (sqrt(token_tx) / sum_sqrt_total_txns_with_all_contracts) * 0.9 * reward_pool )

Removals:

reward_per_removal = reward_pool / total_removals
Why the square-root weighting keeps whales from eating the pool

Contract Domain Name Registry

Pool: 100,000 PNK

  • 93,000 PNK for successful submissions
  • 7,000 PNK for successful removals
  • Maximum reward per successful submission: 500 PNK
  • Maximum reward per successful removal: 500 PNK

All compliant submissions are eligible for rewards.

Submissions:

reward_per_submission = reward_pool * ((1 / (2 * total_submissions)) +(txns_with_contract / (2 * total_txns_with_all_contracts)))

Removals:

reward_per_removal = reward_pool / total_removals

Address Tag Queries

Submissions pool: 60,000 PNK

  • Maximum reward per successful submission: 3,000 PNK

Removals pool: 6,500 PNK

  • Maximum reward per successful removal: 500 PNK

Eligible chains: All

The formula applies to both submissions and removals:

reward = reward_pool / successful_requests

Transaction Data Refinements

Solana normalization: Solana transaction counts are adjusted to make them more comparable with EVM chains and prevent inflated activity from dominating the reward distribution.

Failed transaction filtering: Failed transactions are excluded and are not counted as successful contract activity.

3. Hidden Voting Court Migration Completed

The migration of the main Scout registries to the xDai Curation Court with Hidden Voting was completed successfully on July 13th, 2026.

The migrated registries are:

  • Address Tag Registry
  • Kleros Token Registry
  • Contract Domain Name Registry

The change followed the approval of KIP-87 through Kleros governance.

Since the migration, the new court has already handled its first nine Scout cases using hidden voting.

This provides an early confirmation that the registries and dispute-resolution process are working correctly under the new court configuration.

How Hidden Voting Works

Hidden voting separates the voting process into two stages.

First, jurors commit to a decision without publicly revealing their vote. Once the commitment period ends, jurors reveal the vote they previously submitted.

This prevents jurors from seeing other votes before making their own decision.

The system is designed to reduce:

  • Vote influence
  • Juror herding
  • Strategic voting based on early results
  • Attempts to coordinate around the expected majority

Jurors must therefore assess the evidence and registry policy independently before committing to their decision.

The successful completion of the migration and the first nine cases represents an important improvement to the fairness and integrity of Scout disputes.

Jurors interested in receiving arbitration opportunities for Scout cases should make sure their PNK is staked in the xDai Curation Court with Hidden Voting.

Court interface: https://court.kleros.io/courts

4. Scout Submission Skills Are Ready

Scout submission skills are now ready to use.

Users can delegate the complete registry submission process to an AI agent instead of manually researching and preparing every entry.

The agent can handle the workflow required to identify and submit valid candidates, including:

  • Discovering potentially missing entries
  • Checking whether the entry is already tagged
  • Reviewing the relevant registry policy
  • Verifying the required metadata
  • Preparing the submission
  • Calculating the required deposit
  • Completing the onchain submission

This makes it possible to operate Scout contributions as a repeatable agent workflow rather than a fully manual process.

An agent can continuously search supported chains, reject candidates that do not satisfy the policy and submit entries that pass the required checks.

This opens the door to more scalable participation in Scout incentives. Contributors can focus on defining the agent’s strategy and reviewing its performance while delegating the operational submission work.

The Scout skills can also help reduce common submission errors by applying the same policy and validation steps consistently across every candidate.

Check the full Curate Skills here: skills.kleros.io (Other skills are a work in progress).

TL;DR

  • Scout incentive pools, caps and formulas remain unchanged for August.
  • Robinhood Chain has been added to the supported chains.
  • zkSync submissions must now be checked on zksync.blockscout.com
  • Gnosis submissions must now be checked on gnosis.blockscout.com.
  • Scout is moving toward Blockscout as a tagging reference where applicable.
  • The Hidden Voting Court migration was completed successfully.
  • The new court has already handled its first nine Scout cases.
  • Hidden voting prevents jurors from seeing other votes before committing to their own decision.
  • Scout submission skills are ready, allowing the complete submission workflow to be delegated to an AI agent.