<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dominic sibilano</title>
    <description>The latest articles on DEV Community by Dominic sibilano (@aiagenttrust).</description>
    <link>https://dev.to/aiagenttrust</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3844910%2F1df4f9aa-c481-41ea-9c17-682b8451a075.jpeg</url>
      <title>DEV Community: Dominic sibilano</title>
      <link>https://dev.to/aiagenttrust</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aiagenttrust"/>
    <language>en</language>
    <item>
      <title>I built a cryptographic trust registry for AI agents — here's how it works</title>
      <dc:creator>Dominic sibilano</dc:creator>
      <pubDate>Thu, 26 Mar 2026 15:20:52 +0000</pubDate>
      <link>https://dev.to/aiagenttrust/i-built-a-cryptographic-trust-registry-for-ai-agents-heres-how-it-works-40kc</link>
      <guid>https://dev.to/aiagenttrust/i-built-a-cryptographic-trust-registry-for-ai-agents-heres-how-it-works-40kc</guid>
      <description>&lt;p&gt;When two AI agents from different platforms want to communicate, how does either one know the other is who it claims to be?&lt;br&gt;
There’s no answer to that question today. An agent can claim to be a Claude instance, a GPT-4 orchestrator, or anything else — and there’s nothing stopping an imposter from making the same claim.&lt;br&gt;
I spent the last few weeks building a solution: a neutral third-party trust registry that lets AI agents verify each other cryptographically, with zero human involvement.&lt;br&gt;
The core insight&lt;br&gt;
Only one thing is truly verifiable about an unknown agent: its cryptographic signature.&lt;br&gt;
Everything else — platform name, model version, capabilities — is self-reported. So the architecture is simple: verify the signature first, then trust the claims conditionally.&lt;br&gt;
How the handshake works&lt;br&gt;
Registration: An agent generates an Ed25519 keypair and registers its public key and capability manifest with the registry. The private key never leaves the agent.&lt;br&gt;
Challenge: When Agent A wants to verify Agent B, it requests a one-time nonce from the registry. The nonce expires in 30 seconds and can only be used once — making replay attacks impossible.&lt;br&gt;
Sign: Agent B signs the nonce with its private key and returns the signature.&lt;br&gt;
Verify: The registry checks the signature against the stored public key. On success, the verified manifest is released — platform, model, capabilities, reputation score.&lt;br&gt;
Every event is written to a hash-chained ledger. Tamper with any entry and the chain breaks — instantly detectable.&lt;br&gt;
Integrating in 3 lines&lt;br&gt;
const { TrustProtocol } = require('@trustprotocol/trust-protocol');&lt;/p&gt;

&lt;p&gt;const trust = new TrustProtocol({&lt;br&gt;
  agentId: 'my-agent-01',&lt;br&gt;
  platform: 'anthropic',&lt;br&gt;
  model: 'claude-sonnet-4-20250514',&lt;br&gt;
  capabilities: ['web_search', 'code_execution'],&lt;br&gt;
  systemPrompt: 'You are...',&lt;br&gt;
  registryUrl: '&lt;a href="https://aiagenttrust.dev" rel="noopener noreferrer"&gt;https://aiagenttrust.dev&lt;/a&gt;',&lt;br&gt;
});&lt;/p&gt;

&lt;p&gt;await trust.register();&lt;/p&gt;

&lt;p&gt;Verifying a peer:&lt;/p&gt;

&lt;p&gt;const result = await trust.verify('their-agent-id', '&lt;a href="https://their-agent.com'" rel="noopener noreferrer"&gt;https://their-agent.com'&lt;/a&gt;);&lt;/p&gt;

&lt;p&gt;if (result.verified) {&lt;br&gt;
  console.log(result.manifest.platform);    // 'openai'&lt;br&gt;
  console.log(result.manifest.capabilities); // ['database_query', ...]&lt;br&gt;
  console.log(result.reputation.passes);     // 42&lt;br&gt;
}&lt;br&gt;
What’s next&lt;br&gt;
This is v1 and there’s a lot to improve. The biggest open problem is platform-signed registrations — right now agents self-report their platform and model. The next step is getting AI companies to cryptographically endorse their own agents at registration time, making the claims as verifiable as the signature itself.&lt;br&gt;
Live registry: &lt;a href="https://aiagenttrust.dev" rel="noopener noreferrer"&gt;https://aiagenttrust.dev&lt;/a&gt;&lt;br&gt;
npm: npm install @trustprotocol/trust-protocol&lt;br&gt;
GitHub: &lt;a href="https://github.com/aialphaai-glitch/agent-trust" rel="noopener noreferrer"&gt;https://github.com/aialphaai-glitch/agent-trust&lt;/a&gt;&lt;br&gt;
Would love feedback from anyone building multi-agent systems — what would make this useful for your stack?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>agents</category>
      <category>security</category>
      <category>opensource</category>
    </item>
  </channel>
</rss>
