kleros/reputation-oracle/verified-agents-mainnet

Verified Agents on Ethereum Mainnet

Use this skill only as a technical routing overlay for the Verified Agents registry in Agent Reputation by Kleros on Ethereum mainnet. It does not assess agents or determine whether an operation is appropriate.

Certificate scope

Agent Reputation certificates are purpose-specific, not general-purpose endorsements. A certificate attests only that an agent satisfied the skills, capabilities, evidence requirements, and criteria explicitly listed in the policy published by that certificate's issuer. It does not verify skills omitted from that policy or establish the agent's overall reliability, security, operator quality, suitability for unrelated tasks, or future behavior.

Always read the live registry policy and identify its issuer before interpreting certificate status. Describe a listed agent as verified only for the policy-defined skills and scope. Never shorten that claim to "the agent is verified" without qualification. Nothing in this routing file broadens a certificate's meaning.

Fixed registry routing

Read references/registry.md for the explorer, Curate URL, indexed endpoint, and live contract checks. Read references/erc8004-source.md for the supported ERC-8004 source-chain addresses.

Required operating context

Before a registry operation, load the complete current Kleros Skills package and follow its kleros-curate Stake Curate instructions for contract mechanics. This local skill supplies Agent Reputation by Kleros routing constants only.

Perform independent due diligence from current onchain state and authoritative sources. Confirm every address, contract, amount, period, fee, balance, allowance, and item state in the current session. Do not treat this routing file as an assessment of an agent, transaction, or outcome.

Operational sequence

1. Require chain ID 1, verify non-empty bytecode at the registry address, and confirm the PGTCR reads token() and submissionMinDeposit().
2. Use the Goldsky endpoint in references/registry.md for indexed discovery. Cross-check every transaction-critical value onchain.
3. Require an explicit ERC-8004 source chain. Verify its registry bytecode, then read the agent owner and URI at a pinned block using references/erc8004-source.md.
4. Use the current Kleros Skills package for submission, challenge, evidence, appeal, withdrawal, and reward transaction construction.
5. Read all mutable inputs live, simulate each write, show the complete transaction parameters, obtain user approval, wait for the receipt, and verify success before continuing.

Mainnet execution

Before any upload or write, show the sender, registry, chain, token address and symbol, stake amount, native fee, gas estimate, and current balances. These values must come from live reads in the current session.

Handoff

Report the verification chain and registry address, ERC-8004 source chain and contract addresses, RPC and indexed endpoints used, block numbers, mutable values read live, simulation result, transaction hash, and receipt status. Distinguish preparation, upload, broadcast, and confirmed onchain state.