---
name: curate-challenge
description: Research Kleros Curate entries, prove registry-policy noncompliance, and prepare or execute authorized challenges or removal requests with live deposit, dispute and payout checks. Use for Curate challenger work, not for speculative accusations, juror voting or incentive eligibility alone.
---

# Curate challenge

Find demonstrably noncompliant entries on [Kleros Curate](https://curate.kleros.io/), build evidence a juror can independently check, and decide whether a challenge justifies its real costs. A valid finding can produce a bounty; an incorrect challenge can lose the challenger's deposit and incur arbitration, appeal and gas costs. No candidate, bounty or favorable ruling is guaranteed.

Before an authorized onchain action, use [wallet setup](../wallet-setup/SKILL.md) or the user's existing verified signer. Keep keys and unlock material outside the model transcript. Funding on Optimism does not pay Gnosis or Ethereum gas: verify the actual registry chain, signer and beneficiary.

## Start with policy and state

Accept a registry URL or a discovery scope and a bounded research/spending budget. Research can proceed without a wallet. Record the registry contract, chain ID, item/request ID, contract variant and observation block. A website label or subgraph result is a discovery hint; cross-check code, request status and deadlines onchain before preparing a transaction.

Current official documentation says Curate V1 is being deprecated while existing lists, including Scout, continue operating. Do not interpret deprecation as a closed challenge window, use a migrated list's old address, or deploy a new list as part of this task. Scout's registry contracts are on Gnosis, chain ID 100; the tagged asset may be on another chain.

Fetch the MetaEvidence and complete policy applicable to this request's version, plus the original submitted data and evidence. Light Curate registration and clearing policies are separate. Do not apply a later policy retroactively or substitute a reward announcement for the listing policy. If policy retrieval, historical applicability or item decoding is uncertain, investigate or return `needs-policy`; do not deposit.

For each candidate, produce a short dossier: exact violated clause, submitted claim, contradictory primary evidence, timestamps/blocks, and the strongest plausible compliant interpretation. Use official project deployments, verified metadata, chain reads and reproducible observations. Preserve relevant artifacts and content hashes. Unverified rumors, inference alone, or a disagreement with a project's quality do not establish noncompliance. An entry excluded from PNK incentives can still satisfy its registry policy. Challenge only factual, valid policy breaches; `no-valid-challenge` is a successful outcome.

## Choose the actual operation

- **Pending Light Curate / Scout request:** verify an open, undisputed challenge window and whether the request is registration or removal. Use the verified `challengeRequest(bytes32 itemID, string evidenceURI)` interface.
- **Already accepted Light Curate entry:** the original submission challenge may have expired. Evaluate a new `removeItem(bytes32 itemID, string evidenceURI)` request under the applicable clearing policy, with its own deposit and possible counter-challenge. Do not call removal a guaranteed challenge bounty.
- **Stake Curate / PermanentGTCR:** verify its item and withdrawal state and load its actual ABI. Its `challengeItem` operation requires an ERC20 challenge stake plus a separate native arbitration payment. Do not reuse Light Curate's state or payment model.
- **Classic or unknown implementation:** obtain its verified ABI and policy before continuing. Similar method names do not prove compatible amounts, deadlines or payout rules.

The [official Light Curate operation reference](https://github.com/kleros/kleros-skills/blob/master/kleros-curate/references/light-curate.md) and [Stake Curate operation reference](https://github.com/kleros/kleros-skills/blob/master/kleros-curate/references/stake-curate.md) provide implementation-specific reads. Revalidate them against the deployed contract; they are source material, not permission to transact.

## Price the downside before spending

Read current deposit parameters, the request's applicable arbitrator/extra data, arbitration cost, token decimals and gas. For Light Curate, native payment is the appropriate challenge-base deposit plus arbitration cost; a removal uses the removal-base deposit plus arbitration cost. For Stake Curate, derive the ERC20 stake from item stake, challenge multiplier and divisor; quote native arbitration fees separately. Never copy historic xDAI amounts from a blog or add different assets together.

Show cash paid now, locked capital, recoverable amounts under win/loss/refused ruling, maximum authorized appeal exposure, and time until money could return. Include arbitration fees, uploads, gas and research/model costs. Use `net outcome = recoveries - all outflows`, counting each payment once; returned principal is a recovery, not profit. Estimate expected value only with an explained probability range. Unknown bounty/refund rules mean unknown net upside, not the full submitter deposit. A successful challenge does not automatically qualify as an incentivized removal request. Count unconfirmed monthly PNK incentives as zero in the base case. Do not manufacture allegations to make the arithmetic profitable.

Use existing bounded authorization where applicable; otherwise present the evidence, exact transaction sequence, public disclosure and maximum downside for authorization before publishing evidence or paying deposits. Appeals need their own applicable spending authority. The user must be able to evaluate the actual case and cost before approving.

Prepare ERC-1497 evidence with readable claims, source links and attachments; check every published link. Re-read deadline/status/fees, simulate the exact sender, calldata and payment, and stop on a revert. Broadcast once. An ambiguous result requires hash/nonce reconciliation before another send.

## Follow the dispute and reconcile returns

Record transaction, request/dispute ID, evidence URI, deadlines and paid amounts. Set up monitoring only when requested. Appeals use dispute-scoped arbitrator settings, live fee multipliers, amounts already funded and the actual appeal window; Light/Stake losing sides have a shorter funding deadline. Never auto-fund an appeal to rescue a losing case.

After final resolution, inspect the registry's actual transfer/refund state and withdrawable rounds. Use the correct variant's withdrawal method, simulate it, and reconcile balances and token transfers. A successful transaction or favorable ruling is not proof of profit. Report realized net proceeds separately from locked, pending or estimated amounts.

Return a dossier and status (`researching`, `needs-policy`, `no-valid-challenge`, `ready-for-authorization`, `submitted`, `disputed`, `resolved`, or `withdrawal-needed`) with the next action. Retain source and block timestamps.

## Primary sources and freshness

Research checked **2026-10-01**; read the live registry again for every action.

- [Official Curate overview and current status](https://docs.kleros.io/products/curate): existing V1 lists continue; challenge deposits are at risk; payouts exclude arbitration fees.
- [Official deposit and appeal computations](https://github.com/kleros/kleros-skills/blob/master/kleros-curate/references/shared-deposits.md): live values and distinct contract variants.
- [Official Scout registry reference](https://github.com/kleros/kleros-skills/blob/master/kleros-curate/references/scout-registries.md): Gnosis discovery addresses and schema checks.
- [September 2026 official update](https://blog.kleros.io/september-2026-scout-incentives-hyperliquid-support-curate-updates/): incentive exclusions concern rewards, not policy acceptance. October incentives were not confirmed in this research.
