Skip to content

internet-court/internet-court-skill / vendored/kleros/kleros-curate

kleros-curate

Unverified

Interact with Kleros Curate registries across Ethereum Mainnet, Gnosis Chain, and Sepolia. Use when the user mentions Curate, Light Curate/LightGeneralizedTCR/LGTCR, Stake Curate/PermanentGTCR/PGTCR, Scout, token-curated registry/TCR, token lists, address/CDN tags, Goldsky, MetaEvidence, Verify Your List, or Curate calls such as addItem, removeItem, challengeItem, challengeRequest, and fundAppeal. Covers registry discovery and queries; policy/schema inspection; submissions, removals, challenges, evidence, appeals, rewards, execution; factory deployment; and frontend verification on all three networks. Also trigger for registry/list operations paired with Kleros, arbitrator, dispute, juror, or PNK context, and whenever the user names or tests kleros-curate. Do NOT use for non-Kleros registries or generic IPFS uploads without Curate context; route standalone uploads to kleros-ipfs-upload.

references/verify-your-list.md

View on GitHub
# Verify Your List
<!-- Sources: live Ethereum Mainnet, Gnosis Chain, and Sepolia deployment state and MetaEvidence; repository LGTCR references -->

Use this file when a user wants a Curate registry deployed on Ethereum Mainnet, Gnosis Chain, or Sepolia to
become visible and verified in the Curate frontend. The verification registries on all three supported
networks are `LightGeneralizedTCR`, so this is a narrow overlay on the standard Light Curate submission
workflow, not a separate contract flavor.

List verification is recommended for public registries. Skip it only when the registry is intentionally
private or stealth.

## Canonical verification registries

| Network | Chain ID | Verification registry | Event scan start block |
|---------|---------:|-----------------------|-----------------------:|
| Ethereum Mainnet | `1` | `0xB79B610bB8E5E26e5b93b8d45Cdb34858AfEb190` | `25531707` |
| Gnosis Chain | `100` | `0x2418D887d0d0Fe03b793A6aF4321fa488226A0b5` | `47081664` |
| Sepolia | `11155111` | `0xD965Ce430afE0423Ff19A5eb08F7C5722EFabCaF` | `4049205` |

Select one complete row by chain ID. Never mix an address or scan start block from another row.

Keep these roles distinct throughout the workflow:

- `chainId` — the selected network.
- `verificationRegistryAddress` — the fixed address from the selected row; this is the transaction target.
- `verificationRegistryDeploymentBlock` — the selected row's event scan start block.
- `registryToVerify` — the user's deployed registry on the same selected network; this is a value inside the
  submitted item.json.

The verification target is LGTCR even when `registryToVerify` is a Stake Curate or other policy-eligible
Curate registry. Contract mechanics are determined by the transaction target, so always use the Light Curate
submission path described below.

## Required references

Read these files before preparing a verification submission:

1. `light-curate.md` — LGTCR discovery, submission, simulation, and request lifecycle.
2. `shared-metaevidence.md` — latest applicable registration MetaEvidence and policy retrieval.
3. `shared-item-json.md` — exact-schema item.json construction and validation.
4. `shared-ipfs-upload.md` — single-file paid uploads, CID reuse, and IPFS round-trip verification.
5. `shared-deposits.md` — live LGTCR deposit computation.
6. `shared-abi-fragments.md` — LGTCR read/write signatures and status enum.

Do not cache a MetaEvidence ID, schema, policy, deposit, or item URI in this file. Registry governors can
change them; the latest applicable onchain state is authoritative.

## Standard Light Curate verification flow

1. **Select the network and address roles**:
   - require chain ID `1`, `100`, or `11155111`.
   - load `verificationRegistryAddress` and `verificationRegistryDeploymentBlock` from the same table row.
   - confirm `registryToVerify` is the deployed registry the user wants listed on that same chain, not the
     transaction target.
2. **Verify both addresses on the selected chain**:
   - require non-empty `eth_getCode` for both addresses.
   - confirm `verificationRegistryAddress` exposes the LGTCR hallmark reads from `light-curate.md` and the
     `addItem(string)` interface from `shared-abi-fragments.md`.
   - do not require `registryToVerify` to be LGTCR; determine its type separately and let the live
     verification policy decide whether it is eligible.
3. **Fetch the latest registration MetaEvidence** from `verificationRegistryAddress` using
   `shared-metaevidence.md`. Fetch and read its `fileURI` policy, then extract `metadata.columns` verbatim.
   Do not assume the deployment-time MetaEvidence is still current or that all three networks share a schema.
4. **Check policy compliance and duplicates** for `registryToVerify`. Validate every requirement in the
   selected registry's live policy. When duplicate entries are forbidden, use onchain state:
   - scan `NewItem` logs from `verificationRegistryDeploymentBlock` through `latest` on the selected chain.
   - decode every item ID and item URI, fetch each item JSON, and compare its schema-designated registry
     address to `registryToVerify` after case-insensitive EVM address normalization. The item ID is derived
     from the item URI, so one guessed item ID cannot rule out the same address under another CID.
   - for every address match, call `getItemInfo` and the latest `getRequestInfo` as described in
     `light-curate.md`. Decode LGTCR status using `shared-abi-fragments.md`; do not guess numeric enum values.
     Treat a registered item or unresolved request as an existing or active submission.
   - if an indexer or frontend search is used for convenience, cross-check it against the onchain log scan.
   Stop if compliance or duplicate status cannot be established.
5. **Build item.json** using `shared-item-json.md`:
   - deep-copy the live `metadata.columns` without edits.
   - put `registryToVerify` in the unique field designated by the live schema for the registry address.
   - make `Object.keys(values)` exactly match the column labels and order.
   - stop if the schema does not unambiguously identify where the registry address belongs.
6. **Get approval before the paid upload**. Show the selected chain, both address roles, live policy summary,
   fetched columns, compliance check, duplicate check, and complete item.json. Upload only after approval.
7. **Upload and round-trip item.json** using `shared-ipfs-upload.md`. The upload request must contain only
   this one file. The resulting `/ipfs/<CID>` must fetch back to the approved JSON.
8. **Compute the LGTCR submission value live** using `shared-deposits.md`, then simulate this exact call on
   the selected chain:

   ```text
   chain: chainId
   to: verificationRegistryAddress
   call: LightGeneralizedTCR.addItem("/ipfs/<CID>")
   msg.value: live LGTCR submission value in the selected chain's native token
   ```

9. **Get final onchain approval**. Show the selected chain, both named addresses, item URI, live deposit
   inputs, final `msg.value`, and successful simulation result. Submit only after the user approves.
10. **Verify the receipt and track the request**. Confirm the emitted item data resolves to the approved JSON
    and record the item ID and request state. A successful submission is pending, not yet verified.
11. **Finalize and confirm visibility**. After an unchallenged challenge period, simulate and call
    `executeRequest(itemID)`, then confirm the item is registered onchain. Check the accepted item at
    `https://curate.kleros.io/tcr/<chainId>/<verificationRegistryAddress>` and confirm the listed registry is
    discoverable in the frontend. If onchain state is registered but the UI has not caught up, report frontend
    indexing as pending and do not resubmit. If challenged, follow the LGTCR dispute workflow. Never claim
    verification is complete from the submission receipt alone or invent an indexing ETA.

## Stop conditions

Stop instead of uploading or submitting if:

- the target chain is not Ethereum Mainnet, Gnosis Chain, or Sepolia, or the chain is unclear.
- `verificationRegistryAddress` or its scan start block does not exactly match the selected table row.
- either address is missing, is on a different chain, or has no code on the selected chain.
- the fixed verification target does not behave as `LightGeneralizedTCR`.
- the latest registration MetaEvidence or policy cannot be fetched and parsed.
- `registryToVerify` does not clearly satisfy the live policy.
- an accepted or active duplicate exists, or duplicate status cannot be established when the policy forbids it.
- the live schema is missing or does not unambiguously accept `registryToVerify`.
- item.json validation or its IPFS round trip fails.
- the live deposit cannot be computed or the exact `addItem(string)` simulation fails.
- the user has not approved the paid upload and the final onchain transaction.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 323kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 323kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 323kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall