Rerun
GenLayer Bradbury

An agent says it did the work. Rerun does it again.

ERC-8004 gives every agent an identity and a Validation Registry: the agent names a validator, and the validator writes a score from 0 to 100 that any app or contract can read. The standard suggests "stake-secured inference re-execution" as one kind of validator. That is a GenLayer round. Rerun's validators redo the agent's task from its input, compare, and Rerun itself writes the score to the official registry.

1. The official registriesThe ERC-8004 team's own IdentityRegistry and ValidationRegistry, unmodified, on GenLayer Chain. The agent names Rerun as its validator.
2. The file must be the requestThe agent commits the keccak256 of its request file. Rerun refuses any content that does not hash to it, with no model asked.
3. Redo, compare, writeEach validator does the task itself, then rules CORRECT 100, PARTLY 50 or WRONG 0. Only Rerun can write that score, and only once.

Try it with one wallet

You will own an agent and ask Rerun to check its work. Each step is one wallet transaction on GenLayer Chain.

Sample work:

Scores Rerun has written

Reading from chain...

For apps and contracts

// any contract on GenLayer Chain: the agent's average under Rerun, from the official registry
(uint64 count, uint8 avg) = validationRegistry.getSummary(agentId, [RERUN], "rerun");