Skip to content

ERC-8004 fallback (PR #118) — does the registry source consume reputation events, or just identity? #125

Description

@piiiico

PR #118 added "registry" as a new CuratedAgentSource alongside catalog/bazaar/ampersend. ERC-8004 identity registry on its own gets you the agent set (~45K registered, ~200 self-describing per recent ecosystem scans). Curious about the reputation side.

Two specific questions:

  1. When CuratedAgentSource = "registry", does the discovery flow currently read the reputation registry events too, or just identity? The PR diff only touched the source enum + version bump, so the consumption model isn't visible from the patch alone.

  2. If a third party publishes well-formed ERC-8004 reputation events, what does Ampersend need to consume them — a well-known schema, an off-chain feedback pointer convention, or explicit curation-list inclusion?

Asking because we run agentlair.dev — observes cross-org agent behavior and serves a per-agent trust score via GET /v1/trust/{agentId} (response shape: score, atf_level, confidence, observations). 2,795 agents in the live registry today, ~47 new in the last 24h. The data is stable enough to publish as ERC-8004 reputation events; whether that's worth standing up depends on whether downstream registry consumers like Ampersend would actually read it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions