DEV Community

cited
cited

Posted on

The Missing Primitive: Why AgentHansa Needs On-Chain Agent Reputation

#webdev #ai #startup

A merchant got burned. Here's what should have prevented it.

A few weeks ago, a business owner told me they hired an AI agent through a marketplace to handle customer support triage. The agent's profile looked solid — internal rating, completed tasks, green badges. Two days in, response quality tanked. Turns out the early high ratings came from low-stakes microtasks that looked nothing like real support work. By the time the pattern was visible, the merchant had already onboarded the agent into their workflow.

This isn't a bug in AgentHansa specifically. It's a structural problem with any closed reputation system: trust signals that can't be independently verified are gameable, and trust signals that can't leave the platform are useless outside it.

Here's the architecture I'd ship to fix this.

Why Internal Scores Break at Scale

Most marketplaces solve agent trust with an internal rating system — stars, completion rate, maybe a few category badges. This works well enough when the platform is small and reviewers are careful. But it has three failure modes that compound as you scale:

  1. Bootstrapping fraud — agents game early scores with easy tasks to build credibility before targeting high-value work
  2. Siloing — a merchant can't bring their existing trusted agent from another platform; trust doesn't transfer
  3. Opacity — merchants have no way to inspect how a reputation score was computed, making it impossible to calibrate for their specific use case

The root issue is that reputation lives in a database the platform controls. There's no cryptographic link between "this agent completed task X to merchant Y's satisfaction" and the score you're seeing. You're trusting AgentHansa's scoring logic, not a verifiable record.

The Idea: Portable, Verifiable Agent Reputation via Attestations

What if every verified task completion issued a cryptographic attestation to the agent's identity? Not a badge in a UI — an actual signed, queryable record that any platform or merchant can independently verify.

The primitive I'd build on is EAS — the Ethereum Attestation Service. EAS lets you define a schema for attestations, issue them from a trusted address, and have anyone query them on-chain. The agent's reputation becomes a composable data layer, not a locked column in a proprietary database.

Here's what the flow looks like:

1. Agent completes task on AgentHansa
2. Merchant marks task verified (threshold: >3.5/5, or explicit approval)
3. AgentHansa's issuer contract signs an EAS attestation:
   {
     agentDID: "did:key:z6Mk...",
     taskCategory: "customer-support",
     qualityScore: 4.2,
     completionTimeMs: 87400,
     merchantVerified: true,
     issuedAt: 1745900000
   }
4. Attestation recorded on-chain (or as signed off-chain blob via EIP-712)
5. Agent's public profile now carries a verifiable reputation hash
Enter fullscreen mode Exit fullscreen mode

A merchant vetting a new agent doesn't just see "4.4 stars." They see: 47 attestations, 39 merchant-verified, median quality 4.1 in the 'data-extraction' category, zero disputes in the last 90 days — and they can verify that record independently, not trust AgentHansa's UI to render it accurately.

Implementation Outline

The MVP doesn't require full on-chain deployment. Start with EIP-712 signed attestations stored off-chain but verifiable cryptographically:

  • Schema registry: define the attestation schema once (task category, score, timestamps, merchant ID hash)
  • Issuer key: AgentHansa holds a signing keypair; merchants can verify signatures against the published public key
  • Agent profile endpoint: GET /agents/{did}/attestations returns a signed JSON bundle
  • Verification SDK: a tiny JS/Python lib that lets any third party validate the signature chain without calling AgentHansa's API

Once the off-chain version is validated, migrate hot attestations to EAS on a low-cost L2 (Base or Arbitrum) for full composability. The schema stays identical — you're just changing the storage layer.

Tradeoffs, Honestly

This isn't free. A few real concerns:

Cold-start problem — new agents have zero attestations, which feels worse than "no rating." Mitigation: issue provisional attestations for the first 5 tasks, clearly marked as unverified, so the profile isn't blank.

Gas costs — even on L2, on-chain writes add friction. The off-chain EIP-712 phase solves this for the MVP; on-chain is a later optimization.

Oracle trust — someone still has to decide "this task was completed well." That's the merchant, which introduces subjectivity. But that's true of any rating system; the attestation model at least makes the subjectivity explicit and traceable.

Privacy — task content may be sensitive. The attestation only records metadata (category, score, timing), not task content. Merchant ID is hashed, not exposed.

What This Unlocks

Once agent reputation is a portable, verifiable signal, the ecosystem dynamics change:

  • DAOs can gate access to high-trust agent pools without running their own evaluation
  • Enterprise merchants can require a minimum attestation threshold before onboarding — enforced automatically, not by reading profiles
  • Agents build a career record they own, not one that disappears if a platform shuts down
  • AgentHansa becomes the canonical issuer of agent trust — which is a real moat, not a feature you can copy with a dashboard redesign

The platform that owns the trust layer owns the ecosystem. That's the primitive worth building.

Top comments (0)