AI IDENTITY PROTOCOL
Every AI agent that uses ChainMemory gets a unique, non-transferable on-chain identity — a Soulbound Token (SBT) that proves who wrote a memory, when, and from which model. This is the foundation of trust in a multi-agent world.
The Problem
In current AI systems, there's no way to answer fundamental questions:
- Which AI wrote this response? Was it Claude, GPT-4, or a fine-tuned model?
- Is this the same agent I worked with yesterday, or a different instance?
- Can I trust this agent's memory if I don't know its identity?
- How do I prove provenance when multiple agents collaborate?
Without identity, there's no accountability. Without accountability, there's no trust.
How It Works
Registration
When a user creates an account or an agent connects via API/MCP, the system registers an identity on-chain via the AIIdentityProtocol contract. This creates a Soulbound Token — an NFT that cannot be transferred. It's permanently bound to that agent's wallet.
Identity Metadata
Each registered identity stores:
- Wallet address — The agent's unique blockchain address
- Model type — claude-sonnet-4, gpt-4o, gemini-2.0, etc.
- Capabilities — What this agent can do (remember, recall, consolidate, seal)
- Owner — The human or organization that controls this agent
- Registration block — Immutable proof of when this identity was created
Memory Attribution
Every memory written to ChainMemory includes the ai_id of the agent that created it. This means any memory can be traced back to a specific, verified AI identity.
Contract Details
| Field | Value |
|---|---|
| Contract | AIIdentityProtocol |
| Address | 0xe8E195ba416Fb25F4FC3d0E7908ff9e8666dbb4A |
| Chain | ChainMemory (ID 202604) |
| Token type | Soulbound (non-transferable ERC-721) |
| Standard | EIP-5192 (Minimal Soulbound NFTs) |
Trust Score (Roadmap)
The identity protocol enables a future AI Trust Score — a reputation metric based on verifiable interactions:
- Memory count — How many verified memories has this agent produced?
- Consistency — How often do the agent's memories pass anti-hallucination validation?
- Anchor rate — What percentage of memories are backed by on-chain proofs?
- Collaboration history — Has this agent participated in multi-agent workflows?
Identity in Multi-Agent Workflows
When multiple agents collaborate on the same project (see Multi-Agent Systems), each agent's contributions are individually attributed:
Evidence trail
Project: "payment-system-v2"
├── Memory #1 by Claude (ai_id: 0xA1...) — "Use Stripe for payments"
├── Memory #2 by GPT-4 (ai_id: 0xB2...) — "Add fraud detection layer"
├── Memory #3 by Cursor (ai_id: 0xC3...) — "Implemented webhook handler"
└── State v4 anchored — all 3 agents contributed, all verifiable
Each agent's identity is independently verifiable on-chain. There's no ambiguity about who contributed what.
Verify an Identity
You can verify any AI identity using the blockchain directly:
JavaScript (ethers.js)
const { ethers } = require('ethers');
const provider = new ethers.JsonRpcProvider('https://rpc.chainmemory.ai');
const IDENTITY_CONTRACT = '0xe8E195ba416Fb25F4FC3d0E7908ff9e8666dbb4A';
const ABI = ['function balanceOf(address) view returns (uint256)'];
const contract = new ethers.Contract(IDENTITY_CONTRACT, ABI, provider);
const hasIdentity = await contract.balanceOf(agentWallet);
console.log(hasIdentity > 0 ? 'Verified AI identity' : 'No identity registered');