---
name: kleros-curation-incentives
description: Verify the current Kleros Cooperative Scout incentive round, research useful policy-compliant registry contributions, estimate uncertain PNK rewards and deposit risk, and reconcile authorized submissions, removals and direct payments. Use for curation incentives, not guaranteed yield or unsupported challenges.
---

# Kleros curation incentives

Research useful address tags, token metadata, contract-domain links and address-tag queries for Kleros Scout. Eligible accepted work may earn PNK from a periodic Cooperative-funded pool. Acceptance, incentive eligibility and actual payment are three separate facts; none proves profit.

**Status checked 2026-10-01:** the latest official monthly announcement located covers September 2026. October renewal, funding and current payout schedule are **unverified**. Do not call this an active October offer or assume yesterday's campaign rolled over. Read [the dated rules snapshot](references/rules-and-sources.md) before quoting amounts or eligibility, then refresh the official blog and Scout interface.

## Verify the opportunity

Record program/period, exact UTC eligibility window, official announcement, covered registries/chains, reward unit, pool, cap, exclusions, calculation data and payment mechanism. A currently working registry does not prove an active incentive round. If the next round is not announced, use `round-unverified`; continue useful research, but count campaign income as zero in spending decisions unless the user separately chooses to contribute without confirmed rewards.

Scout records multichain metadata through Gnosis registry contracts (chain ID 100), using xDAI for native deposits/gas. The asset's chain is different from the registry/payment chain. Get the registry address from current official configuration and verify it onchain. Read current policy, MetaEvidence/schema, item state and duplicate identifiers before any submission. Do not rely on a search API alone to prove novelty or eligibility.

For September reference rules, ATR and Token candidates require a dated check on that chain's designated explorer for existing tags; CDN has a different eligibility rule. Apply the refreshed round's exclusions in addition to the listing policy. A valid entry can be unpaid; reward ineligibility does not justify removing or challenging it.

Find candidates from primary project deployment records, explorer contract data, official domains and reproducible repository outputs. Avoid fabricated labels, speculative ownership, duplicate/recycled contributions and unsupported screenshots. For ATQ, pin the requested repository/commit and verify what it actually returns in a read-only environment before submission. Do not execute arbitrary untrusted repository code with a spend-capable wallet available.

For every candidate, record its policy evidence, novelty checks, incentive eligibility (`verified`, `ineligible`, or `unknown`), estimated costs and next action. Only factual policy noncompliance supports removals/challenges; use [Curate challenge](../curate-challenge/SKILL.md) for that evidence and downside review.

## Estimate economics without inventing a payout

Read live submission/removal deposits and arbitration fees from the correct deployed registry/arbitrator. Historical deposits are illustrations, not transaction parameters. Model gas, evidence hosting, model/research cost, capital lock-up, dispute loss and any authorized appeals. On a rejected contribution, deposited funds can be lost and appeals can add expense. Even an accepted entry can earn no incentive or produce a reward worth less than costs.

The formulas in the snapshot describe September rules only. Reward denominators depend on other contributors and the operator's finalized eligible dataset; transaction normalization, exclusions, caps and redistribution also matter. If those inputs are unavailable, give scenario ranges, not an exact expected payment. Keep estimates in PNK until a timestamped price/liquidity quote supports conversion to money; include volatility and conversion fees. Return `net = realized proceeds - gas - unrecovered deposits/fees - other costs`, with pending amounts separate.

## Prepare and execute authorized contributions

Use [wallet setup](../wallet-setup/SKILL.md) or a verified existing signer before an onchain action. Match its chain, holder, gas asset and spending budget; an Optimism wallet tool cannot send to Gnosis by changing a label. Never obtain keys in chat or read credential files.

Build each item from the actual schema with accurate values and required proof; check types, ordering, identifiers and attachment access. For Light Curate, `addItem(itemURI)` pays live `submissionBaseDeposit + arbitrationCost`; a removal has its own clearing policy, evidence and deposit. Detect other variants rather than reuse these calls. Before any public upload or spend, use existing applicable bounded authority or present the complete item, eligibility uncertainty, transaction, deposit and maximum downside for authorization. Do not silently turn a research request into mass submissions, removals, appeals or recurring spending.

Simulate exact calldata/payment, refresh fees/state/duplicates immediately before send, broadcast once, then save item/request ID and receipt. Reconcile ambiguous submissions before retrying. A transaction receipt marks a submitted request, not acceptance. Wait for the real challenge window/resolution; finalize or reclaim deposits only through verified registry mechanics and applicable authority.

## Payment and reconciliation

The official reward-operator repository documents **direct transfers**, rather than a recipient Merkle claim contract. The rewards dashboard publishes allocation snapshots and is read-only. Consult [Kleros Rewards](https://rewards.kleros.io/), verify the recipient and period, then match the actual PNK transfer and balance on its observed payment chain. Do not run the operator's `send` task or confuse juror staking/Proof of Humanity claim flows with Curate incentives.

A published allocation is not proof of payment. Report `allocated-unpaid`, `paid`, or `payment-unverified` from evidence. If a future round introduces claiming, verify its official contract, proof, beneficiary, chain and fees before preparing a claim; do not invent one or sign an unrelated delegation/approval. Registry deposit/appeal withdrawals are a separate flow from Cooperative PNK distributions.

Return a contribution ledger with period/status, candidates, accepted/rejected/pending requests, deposits locked/refunded/lost, PNK allocated/received, realized net results and next action. Schedule future checks only when requested.
