Skip to content

Evidence AgentsAvailability: In development

How audit evidence is collected and released.

Evidence Agents help gather published audit reports and their sources. AI output is never shown as verified coverage: human-reviewed release and deterministic matching against deployed code decide what counts.

Explore EvidenceSee How It Works

AI helps find and organize sources. It never decides coverage.

Anything an agent extracts stays a candidate until it passes the checks below and people release it.

FIG 1Evidence candidate, as produced

Evidence candidate, as produced

public/evidence/demos/candidates/aave-v4-chainsecurity.json

{"schemaVersion": "poa-evidence-candidate-v1","origin": {"publisher": "ChainSecurity","fetchedAt": "2026-11-13T04:42:08Z","contentSha256": "2caa833f0b2b9ddc…"},"reviewedCode": {"reviewedCommit": "cdacec509e4f848b…","deploymentAddress": "0xabd0e26fe17bde4f1f1187ed8aa80c274e03d8b5"},"claims": [{"kind": "reviewed_revision","statement": "The report lists commit cdacec50 among the reviewed code versions.","locator": "page:6;section:Assessment Overview","evidenceLevel": "ai_extracted"},{"kind": "included_contract","statement": "The report lists SpokeInstance.sol in scope.","locator": "page:5;section:Scope","evidenceLevel": "ai_extracted"},],"codeLinkage": {"status": "deployed_code_matched","matchQuality": "exact_match"},"publicationState": "candidate"}

Gate report

validate_candidate.py --document --text

  1. G0Source, origin and file hash recordedpassed
  2. G1Every claim quoted and located in the reportpassed
  3. G2Reviewed commit is an exact hashpassed
  4. G3Compiler and settings pinnedpassed
  5. G4Deployed code matched to the buildpassed
  6. G5Scope, exclusions and limits consideredpassed
  7. G6Firm signatureblocked

    Blocker: firm_attestation_missing. No authenticated firm signature; publisher claims are not firm attestations.

  8. G7Superseded by a later changenot applicable

Result: stays a candidate. Every claim is AI-extracted and no firm has signed it, so it cannot be shown as firm-attested coverage.

The validator checks the record itself. Fetching the source, building the code and matching the deployment are done by separate tools, recorded in the candidate.

02A real pass

Public reports in, cited file bindings out.

One collection pass over public audit reports for the protocols in the explorer. Each binding names a file the report covers, with the page and a hash of the exact quote. None of it is released.

One binding, as recorded
In audit scopeAckee Blockchain
“The main logic of the protocol is in the Safe.sol contract.”
File named
Safe.sol
Page
14
Quote SHA-256
76c0d4e775…8e43b2
Report SHA-256
bd64303f4a…68072a

Ackee Blockchain · Safe smart account 1.4.0 audit

ReportProtocolBindingsChecks passedCandidate
Ackee BlockchainSafe smart account 1.4.0 auditsafe41 of 7JSON
CertoraEigenLayer redistribution slash delay v1.13.0eigenlayer22 of 7JSON
CertoraLido V3 auditlido23 of 7JSON
ChainSecurityCode Assessment of the Euler Vault Kit Smart Contractseuler343 of 7JSON
OpenZeppelinComet Asset Extension Auditcompound31 of 7JSON
ABDK ConsultingAave v3.5 code auditaave32 of 7JSON
MixBytesAave v3.7 security auditaave13 of 7JSON
BlackthornSecurity Review For Aave v3.4aave32 of 7JSON
CertoraAave v3.3 formal verification and manual reviewaave11 of 7JSON
ABDK ConsultingAave V3 smart contract auditaave11 of 7JSON
Trail of BitsAave V3 Security Assessmentaave12 of 7JSON
OpenZeppelinCompound III Auditcompound23 of 7JSON
CertoraEigenLayer Slashing (V1.0.0) formal verificationeigenlayer22 of 7JSON
CertoraSafe Smart Account v1.3.0 security reviewsafe11 of 7JSON
OpenZeppelinUniswap V4 Periphery and Universal Router Audituniswap12 of 7JSON

Each cell is one check, in order: passed (filled), blocked (orange), not applicable (empty). Every report is blocked at the firm signature and the code match.

Result: in audit scope for the files named, cited and hashed. Code match not yet checked, and no release.

  • Recorded data
  • 15public reports
  • 61cited file bindings
  • 7protocols
  • generated13 Nov 2026

03

From a published report to the wallet panel

Each stage records what it used, so a reader can trace a wallet result back to the report text and the code it describes.

  1. 01

    Find sources

    Published audit reports, the protocol's repositories and its deployment records. The auditor's own publication is preferred over a copy. A search result is a lead, not evidence.

    Who does it
    AI-assisted collection and people
    What is recorded
    origin.urlorigin.publisher
  2. 02

    Preserve the original

    The report file is stored once, by its hash, with where it came from and when it was fetched. Later steps cite this exact file.

    Who does it
    Collection tooling
    What is recorded
    contentSha256fetchedAt
  3. 03

    Extract and cite

    Dates, the reviewed commit, contracts and functions in scope, exclusions and findings are read out of the report. Every claim carries the exact quote and page it came from; a claim without a citation is dropped.

    Who does it
    AI-assisted extraction, checked by people
    What is recorded
    quotepagereviewedCommit
  4. 04

    Check before release

    Every candidate goes through the same checks. Is the source the publisher's own? Is every quote in the document? Is the reviewed commit exact? Does the build reproduce, and does the deployed code match it? A step that is not done is recorded as a blocker, never skipped.

    Who does it
    Deterministic checks
    What is recorded
    blockerscodeLinkage.status
  5. 05

    Release

    Imported evidence is released only after independent human review. Audits that an approved audit firm pushes from its own tooling are released by the firm's attestation plus automated code checks, with no AI on that path.

    Who does it
    People, or an approved audit firm
    What is recorded
    releaseIdreleasedAt
  6. 06

    Match live code

    For each transaction, deterministic code compares the deployed code on the call path with released reviews. A part is Reviewed only when its exact code and function match a released review. Changed code reads Changed since review; anything without a released review stays Coverage unknown.

    Who does it
    Deterministic matcher
    What is recorded
    REVIEW_COVEREDCHANGED_SINCE_REVIEWREVIEW_COVERAGE_UNKNOWN

04

Who decides what

Collection can speed up finding sources. It has no say in the result.

Finding reports and sourcesDecided by: AI-assisted collection and people
Turning report text into claimsDecided by: AI-assisted extraction, every claim cited and checked
Whether evidence is releasedDecided by: Independent human review, or an approved firm's own attestation
Whether a transaction is coveredDecided by: The deterministic matcher, from released evidence only

Candidate evidence is labelled as such

Candidate evidence is labelled as such

Until it is released, collected evidence appears as “Candidate evidence · not approved” and never counts as coverage in the Explorer or the wallet.

Audit firms publish without agents

Approved audit firms push their audits by REST API or MCP from their own tooling. The release states whether the live code matches the audited commit.

  • Auto-released: approved audit firm + automated checks (no PoA human review)
  • Released after independent PoA review

Availability

Availability: In development

AI-assisted collection is in development. Today evidence reaches the Explorer through human-reviewed imports and approved audit firms.