> ## Documentation Index
> Fetch the complete documentation index at: https://docs.defiloops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agent identity and run evidence

> How DeFiLoops and its agents are registered on Base, and the evidence file a finished run can publish

**In short:** DeFiLoops and its template agents are registered on Base under ERC-8004, a standard for agent identity. Each finished run that signed a step also gets an evidence file. The file is private to you. If you choose, you can publish it to IPFS and then rate the run from your own wallet.

## Agent identity

ERC-8004 gives an agent an on-chain identity that anyone can look up. DeFiLoops is registered as an agent on Base. Our template agents are registered there too. A registration points at a file that says what the agent is and where it runs.

Our site serves one file that lists every registration at `https://app.defiloops.com/.well-known/agent-registration.json`. Anyone can use it to check that the agent and the domain belong together.

An identity says who an agent claims to be. It is not a statement that the agent is safe. What bounds an agent is on [Your account and your keys](https://docs.defiloops.com/kernel.md).

## Run evidence

For every finished run that signed at least one step, we build a small file. It holds:

* the plan's hash and revision;
* the agent that wrote the plan, if an agent wrote it;
* for each step, the operation, the network, the transaction hash and an outcome;
* the digests of the signing service's receipts for the run.

The outcome is one of: delivered, mismatch, sent, absorbed or not sent. Delivered means the amount received matched what was asked. Absorbed means the step was folded into another call and never sent on its own.

**What the file never holds:** your name, email, account or wallet address, task names, or any amount. Every field has a fixed shape, so free text cannot get in.

## Publishing is your choice

The file stays private by default. Only you can read it.

You can publish a run's file to IPFS from the run's rating screen. Publishing is public and permanent. Nobody can take the file down, and nobody can edit it. Nothing is published unless you choose it.

Once a file is published, you can rate the run. The rating is a transaction on Base from your own wallet. It links that wallet to the agent's reputation for good, and you can revoke it but not erase it. An agent's own owner cannot rate it. Our reputation view counts only ratings that match a published evidence file, and it is not a total across everyone.

> [!WARNING]
>
> **Evidence is not proof of a good outcome.** It shows what was signed and sent. It does not show that a strategy was wise or that you made money. The transaction hashes already lead a reader to your account, because the network is public.

## Under the hood

For integrators.

* The file's version is `defiloops/run-evidence/v1`. The same run always produces the same bytes, so the same hash and the same IPFS address.
* The rating's feedback hash is the hash of the file's bytes. The console checks the published file against that hash before it lets you rate.
* Publishing runs in a background loop in our worker, never on a run's path. A run never waits on the pinning service.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.