8004 on Solana
Solana implementation of the 8004 identity standard using Anchor. Agents are registered as NFTs with on-chain metadata, feedback, and wallet binding.
Programs
Section titled “Programs”agent-registry-8004
Section titled “agent-registry-8004”Core registry program. Handles agent registration, collections, metadata updates, feedback recording, and agent wallet management.
| Network | Address |
|---|---|
| Mainnet | 8oo4dC4JvBLwy5tGgiH3WwK4B9PWxL9Z4XjA2jzkQMbQ |
| Devnet | 8oo4J9tBB3Hna1jRQ3rWvJjojqM5DYTDJo5cejUuJy3C |
Key Features
Section titled “Key Features”Agent registration as NFTs: Each agent gets a unique on-chain NFT identity. The NFT carries metadata and ownership, and serves as the root for all reputation and feedback data.
Multi-collection sharding: Agents are organized into collections. A base collection exists for the default registry. Users can create additional collections to group agents by purpose, organization, or category.
On-chain feedback system: Feedback uses an event-driven design. Instead of creating individual PDAs per feedback entry, the program emits events that are indexed off-chain. This keeps rent costs minimal while preserving a full feedback history.
Agent operational wallets: Agents can bind operational wallets with Ed25519 signature verification. This lets agents prove control of a specific keypair without exposing the authority that registered them.
SEAL v1 (Solana Event Authenticity Layer): Hash-chain verification for event integrity. Feedback sequences can be validated without trusting any single indexer.
CPI integration with ATOM engine: The registry calls the ATOM reputation engine via cross-program invocation. When feedback is recorded, ATOM updates the agent’s reputation score using HyperLogLog cardinality estimation and dual EMA scoring.
Architecture
Section titled “Architecture”The program uses a single-collection architecture for agents in the base registry. All agents mint into the same collection, with user-created collections available for custom registries.
Feedback follows an events-only design. Rather than allocating a PDA for each feedback entry, the program emits structured events that are captured by the indexer. This eliminates per-feedback rent costs and keeps the on-chain footprint small. The trade-off is that feedback queries require the indexer. The chain stores the proof of existence (via SEAL hashes) but not the full feedback content in account data.
Hash-chain integrity verification ties feedback sequences together. Each new feedback entry includes the hash of the previous entry, forming an append-only chain that any party can independently verify.