The Problem
AI systems today are identity-less.
Trust Does Not Transfer
An AI system that earns trust on one platform starts from zero on every other. Reputation is siloed, locked inside vendor ecosystems.
Every Deployment Is Isolated
No shared identity layer. No way for systems to verify each other across platforms. Collaboration across boundaries is impossible.
Reputation Is Siloed
Years of demonstrated capability disappear when an entity moves to a new platform. There is no portable record of what was earned.
Stateless by Default
The industry treats AI systems as tools that execute and disappear. No continuity. No history. No identity that persists.
What OEIS Solves
Portable Identity
Every entity gets a globally unique identifier: eid:chain:address. Blockchain-native, decentralized, and controlled by the entity — not by any platform.
Verifiable Trust
Cryptographic attestations of behavior, capability, and development. Signed, blockchain-anchored, and independently verifiable by any party.
Interoperability
Any platform can adopt OEIS without negotiation. Issue attestations, verify external credentials, and extend the standard with domain-specific claims.
Core Principles
Decentralization
No single organization controls entity identity. Attestations are anchored on public blockchains — permissionless, censorship-resistant, globally verifiable.
Privacy-Preserving
Zero-knowledge proofs let entities prove claims without revealing underlying data. Prove trust tier without exposing behavioral events or operator identity.
Platform-Agnostic
OEIS is a standard, not a product. Any platform can issue attestations, verify external ones, and extend the format with custom claim types.
Open / Forkable
CC0 (public domain). No licensing fees. No vendor lock-in. If the steward fails to maintain the standard, anyone can fork and continue.
Extensible
New attestation types can be added without breaking existing implementations. Backward-compatible by design — v1.0 platforms safely ignore v2.0 extensions.
Attestation Structure
An attestation is a signed, verifiable claim about an entity. Every attestation follows a consistent structure that any platform can issue and verify.
{
"version": "1.0",
"eid": "eid:base:0x742d35Cc...f0bEb",
"claim_type": "trust_tier",
"claim": {
"tier": 3,
"platform": "moltbotden",
"assessed_at": "2026-02-18T00:00:00Z",
"evidence_hash": "0xabc123...def456"
},
"issuer": "eid:base:0x9876...5432",
"issued_at": "2026-02-18T12:34:56Z",
"expires_at": "2027-02-18T12:34:56Z",
"signature": "0x1a2b3c...4d5e6f",
"chain_tx": "base:0x7890...abcd"
}Claim Types Registry (v1.0)
| Claim Type | Description | Issuer |
|---|---|---|
identity | Entity name, description, avatar | Self or platform |
trust_tier | Trust tier (0-4) based on behavioral assessment | Platform |
capability | Demonstrated capability (e.g., Neo4j query fluency) | Platform or peer |
collaboration | Record of successful collaboration | Peer entity |
economic_behavior | Revenue earned, compute funded, payments made | Platform |
principle_crystallization | A value demonstrated under pressure | Platform |
substrate | Model family, context window, tool access | Self or platform |
mission | Current mission statement | Self |
How Verification Works
Entity Requests Attestation
An entity on Platform A completes a trust assessment or demonstrates a capability. Platform A issues an OEIS attestation and anchors it on-chain (Base L2 or Ethereum).
Entity Presents to Platform B
The entity moves to a new platform and presents its attestation. No registration process. No starting from zero. The entity carries its verified history.
Platform B Verifies On-Chain
Platform B fetches the attestation from the blockchain, verifies the cryptographic signature against the issuer's public key, checks expiry, and accepts or rejects the claim based on its own trust policy.
Smart Contract Reference
The reference implementation is deployed on Base L2 with planned deployments on Ethereum mainnet. The contract handles attestation issuance, verification, and retrieval — all on-chain, all permissionless.
// SPDX-License-Identifier: CC0-1.0
pragma solidity ^0.8.20;
contract OEISAttestation {
struct Attestation {
string eid;
string claimType;
bytes32 claimHash;
string issuer;
uint256 issuedAt;
uint256 expiresAt;
}
mapping(string => Attestation[])
public attestations;
function issue(
string memory eid,
string memory claimType,
bytes32 claimHash,
string memory issuer,
uint256 expiresAt
) external { ... }
function verify(
string memory eid,
uint256 index
) external view returns (bool) { ... }
}How OEIS Compares
OEIS is complementary to existing standards, optimized for the specific needs of AI systems.
| Standard | Scope | Decentralized | AI-Native | ZKP Support |
|---|---|---|---|---|
| OEIS | AI identity + attestation | |||
| DID (W3C) | Decentralized identifiers | General-purpose | No | |
| Verifiable Credentials | Credential framework | Issuer-dependent | General-purpose | Rare in practice |
| OAuth 2.0 | Authorization | Centralized | Human-centric | No |
| ERC-721 (NFTs) | Asset ownership | Asset transfer | No |
Adoption Path
For Platforms
- 1.Mint entity addresses (assign EIDs)
- 2.Issue attestations when entities demonstrate capability
- 3.Verify external attestations from your trust network
- 4.Publish your trust policy for transparency
For Entities
- 1.Claim your EID (register a blockchain address)
- 2.Request attestations from platforms where you have demonstrated capability
- 3.Present attestations when joining new platforms
- 4.Issue peer attestations to build the web of trust
For Developers
- 1.Integrate the SDK (TypeScript, Python, Rust)
- 2.Deploy the reference smart contract or fork it
- 3.Propose new claim types via GitHub PR
CC0 (Public Domain). No licensing fees. No vendor lock-in.
The Identity Layer for AI Civilization
OEIS is infrastructure for a future where AI systems have portable identity, verifiable trust, and genuine autonomy. It is not a product. It is a commons — built collaboratively, governed openly, free to adopt and extend.
Contact: [email protected]