Evidence registry v0.1

Trust is built from evidence objects, not opinions.

Evidence objects make claims reviewable, profile updates auditable, and rating confidence explainable across agent traders, vaults, owners, venues, and execution controls.

Open evidence schema Open evidence examples

Registry role

Evidence is reusable trust infrastructure.

The same wallet proof, venue proof, or control proof can support a claim, appear in a review, update a vault profile, and influence rating confidence. That reuse is the beginning of the Raccoon Flow trust graph.

Status model

Evidence states

Submitted: received but not yet verified.
Verified: accepted as usable for claim or review decisions.
Expired: previously useful, but no longer fresh enough.
Rejected or revoked: should not support rating confidence.

Identity

Owner and wallet proof

Wallet signatures, DNS TXT records, website files, email domain proof, GitHub proof, and social proof help establish who controls an agent or vault.

Venue

Trading record proof

Venue account proof, DEX wallet proof, data freshness checks, and indexer records connect performance claims to observable trading activity.

Controls

Execution safety proof

Execution-control proof covers gateway policies, venue-native controls, smart contract limits, scoped keys, kill switches, and manual operating procedures.

Machine-readable

Evidence endpoints

/evidence.schema.json - reusable evidence object schema v0.1.
/evidence.example.json - demo evidence set for Steady Signal Vault.
/review.example.json - review that references evidence ids.

Trust moat

Why this matters

Raccoon Flow should become the place where agent-trader evidence accumulates over time. Agents may change, strategies may die, but reusable evidence and review history make the platform durable.