June 2026: Scout Incentives, Technical Updates & Atlas Uploads

June continues with the same incentive structure introduced in previous months, while bringing important technical updates across Scout and Curate.

The definitive version of Scout is now live, work on the unified Scout database continues, and both Scout and Curate V1 now use Atlas for IPFS uploads.

1. Incentives

All pools, caps, and eligibility rules remain unchanged for June.

Explorer Tagging Requirement (ATR and Token Registry)

In order to be rewarded, entries on Address Tag Registry and Token Registry must not already be tagged on the respective block explorer:

Ethereum Mainnet → etherscan.io
Avalanche C Chain → snowscan.xyz
zkSync → era.zksync.network
Scroll → scrollscan.com
Gnosis → gnosisscan.io
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

Notes:

CDN entries are not subject to this requirement.

Even if your ATR or Token Registry entry is not eligible for rewards, don’t worry. If it meets the policy criteria, it will still be accepted. Every valid contribution helps strengthen the ecosystem.

Transaction Data Refinements

We continue improving how transaction data is handled:

Solana normalization: transaction counts are adjusted to better align with EVM chains, preventing inflated activity from dominating the distribution.

Failed transaction filtering: thanks to improved APIs, failed transactions are not counted as successful activity.

2. Incentives Parameters

Address Tag Registry (ATR)

Pool: 100,000 PNK (93,000 for submissions; 7,000 for removals)
Max reward per successful submission: 500 PNK
Max reward per successful removal: 500 PNK

ERC20, ERC721, and EIP 1167 submissions remain excluded from incentives, but they are still accepted if compliant.

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

Token Registry

Pool: 100,000 PNK (93,000 for submissions; 7,000 for removals)
Max reward per successful submission: 500 PNK
Max reward per successful removal: 500 PNK

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

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 )

This formula gives greater weight to the square root component, reducing the influence of very large tokens while still rewarding tokens with meaningful usage.

Removals:

reward_per_removal = reward_pool / total_removals

CDN Registry

Pool: 100,000 PNK (93,000 for submissions; 7,000 for removals)
Max reward per successful submission: 500 PNK
Max reward per successful removal: 500 PNK

All compliant submissions are rewarded.

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 (ATQ)

Submissions pool: 60,000 PNK (max 3,000 PNK per submission)
Removals pool: 6,500 PNK (max 500 PNK per removal)
Eligible chains: All

Formula, valid for both submissions and removals:

reward = reward_pool / successful_requests

3. Technical Updates

Scout definitive version is live

The definitive version of Scout is now live. The last planned features have been implemented, and we will share a full breakdown soon. This is an important milestone for Scout, making the interface more complete, easier to use, and better prepared for future integrations.

Unified Scout database

Work on the unified Scout database continues. As you can now see directly on the Scout homepage, the database already includes more than 2.6 million addresses, and it keeps growing. This unified database is an important step toward making Scout easier to query, integrate, and use as a reliable source of curated on chain metadata.

New Scout partner: Monarch Lend

Scout curated data is now displayed by Monarch.

This is another important step in making Scout data more visible and useful across the ecosystem. A deeper integration is also expected to follow.

4. Atlas Uploads for Scout and Curate V1

Scout and Curate V1 now both use Atlas as the endpoint for uploading IPFS files.

This brings more reliability for users and makes debugging easier for the team when issues happen.

There is one important change to keep in mind: when submitting, users will now see an additional wallet signature. This is a SIWE signature used to authorize your wallet for file uploads through Atlas.

After signing, you will receive a token valid for about one hour. During that time, you will not need to sign again for Atlas uploads.

TL;DR

• Incentives remain unchanged for June.
• Scout definitive version is now live.
• The unified Scout database continues to grow, now with more than 2.6 million addresses.
• Monarch now displays Scout curated data, with deeper integration expected.
• Scout and Curate V1 now use Atlas for IPFS uploads.
• Submissions now include an additional SIWE signature for Atlas upload authorization.