Learn

ERC-8004 (RFC) validation registry

The validation registry is a public checklist for one question: did a chosen checker look at this work? The agent asks. The checker answers. The chain keeps both notes. It does not grade the checker, and it does not pay anyone.

The spec is still a Draft, so the details can change.

How a check works

Think of a lab slip. You send a sample to a lab you picked. The lab writes a result. The slip is not a receipt, and it is not proof that every lab in town would agree.

1. The agent must already have an ID. The request is tied to an agentId from the identity registry on that chain.
2. The ask. The owner or an approved operator calls validationRequest. The request names the checker’s contract and includes a hash of the work, so later readers can see which job was checked.
3. The answer. That checker calls validationResponse. The response is a number from 0 to 100, plus a hash of the evidence. A tag can say what kind of check it was.
4. The public record. Anyone can read the status. The chain stores the request hash, the checker’s address, the score, the evidence hash, and the time of the last update.
5. The method is outside. The checker might re-run the job, use a proof, or use a secure chip. Those methods belong to the checker’s own system. This registry only stores the request and the answer.

A check on one chain stays on that chain. The same project on another chain does not inherit it.

What the registry does not do

• It does not pay the checker or punish a bad check. Incentives sit in a separate system.
• It does not promise the work was good. It records what one checker wrote.
• It does not prove the agent’s advertised skills work.
• It is not the reputation box. Reviews from clients are a different registry.

Professional use

• A developer can ask an audit agent to check one patch and keep the slip next to the agent ID.
• A researcher can show a named checker’s result instead of saying “trust me.”
• A designer can attach a check to one delivery, using the hash so the slip matches that file.

The next client still has to decide whether that checker is one they believe.

Business use

• A company can refuse to hire an agent unless a chosen checker has answered.
• A purchasing agent can read the slip before it sends a job.
• A marketplace can show the checker’s name and score beside the listing.

Payment for the job is a separate step. This registry does not hold the budget and does not release it when the score is high.

Personal use

• You can ask a checker to look at one public action of a personal assistant or a muse.
• Friends can see the slip without you emailing a screenshot.
• You can ignore checkers you do not know and only read the ones you picked.

Asking and answering costs a network fee. The slip does not include your private chat.

Back to Ethereum ERC Standards