8004 on Solana

March 4, 2026 · View on GitHub

The trust layer for AI agents. Identity and reputation—on-chain.

Programs (Devnet)

Program	Address
agent-registry-8004	`8oo4J9tBB3Hna1jRQ3rWvJjojqM5DYTDJo5cejUuJy3C`
atom-engine	`AToMufS4QD6hEXvcvBDg9m1AHeCLpmZQsyfYa5h9MwAF`

Programs (Mainnet)

Program	Address
agent-registry-8004	`8oo4dC4JvBLwy5tGgiH3WwK4B9PWxL9Z4XjA2jzkQMbQ`
atom-engine	`AToMw53aiPQ8j7iHVb4fGt6nzUNxUhcPc3tbPBZuzVVb`

Highlights

SEAL v1 (Solana Event Authenticity Layer): Trustless on-chain hash computation
ATOM Engine: Hardened EMA arithmetic, tier vesting, platinum loyalty gate
Hash-chain integrity: Rolling digests for feedback, response, and revoke events
Single-collection architecture: All agents in one Metaplex Core collection

See CHANGELOG.md.

Architecture

Two core modules (Identity + Reputation) with an external reputation engine (ATOM).

Validation module archived for future upgrade.

+-----------------------------------------------------------------+
|              agent-registry-8004 (Devnet)                        |
|         8oo4J9tBB3Hna1jRQ3rWvJjojqM5DYTDJo5cejUuJy3C            |
+-----------------------------------------------------------------+
|  +---------------+ +------------------+                          |
|  | Identity      | | Reputation       |                          |
|  +---------------+ +------------------+                          |
|  | Agent NFTs    | | SEAL v1 Events   |                          |
|  |  (Core)       | | Hash-Chains      |                          |
|  | Metadata PDAs | | seal_hash        |                          |
|  +---------------+ +------------------+                          |
+-----------------------------------------------------------------+
          |                    |
          | CPI                | Events
          v                    v
+-----------------------------------------------------------------+
|                    atom-engine (ATOM)                            |
|         AToMufS4QD6hEXvcvBDg9m1AHeCLpmZQsyfYa5h9MwAF            |
+-----------------------------------------------------------------+
|  HLL[256] + ring buffer[24] + tier vesting + quality/risk       |
+-----------------------------------------------------------------+
          |                    |
          |                    v
          |     +---------------------------------+
          |     |           Indexer               |
          |     |   (Supabase / Substreams)       |
          |     +---------------------------------+
          |     | Events → DB (seal_hash stored) |
          |     | Hash-chain verification        |
          |     | REST API for queries           |
          |     +---------------------------------+
          |                    |
          v                    v
+-----------------------------------------------------------------+
|                      Metaplex Core                               |
|         (Single Collection + Agent Assets)                       |
+-----------------------------------------------------------------+

SEAL v1 - Trustless Integrity

The program is the sole source of truth. On-chain seal_hash computation ensures both client-submitted data and indexer-stored data can be verified at any time against the blockchain.

Client ─┐
        ├──► Program (seal_hash on-chain) ──► Hash-Chain ──► Verifiable
Indexer ┘         ▲ source of truth

See docs/SEAL.md for full specification.

Features

Module	Description
Identity	Metaplex Core NFTs, PDA metadata, immutable option
Reputation	Feedback (0-100), revoke, responses, SEAL v1 integrity
ATOM Engine	Sybil resistance (HLL), burst detection, trust tiers (0-4)

ERC-8004 Compliance

Aligned with the ERC-8004 spec, with an explicit Solana profile.

Current documented compatibility profile:

appendResponse() is permissionless.
feedback_index is intentionally a global per-agent counter (0-based), not a per-client 1-based counter.
Per-client sequencing is derived off-chain by the indexer from canonical on-chain events.

Rationale for keeping global per-agent indexing:

No extra on-chain per-client counters or migration complexity.
Deterministic single sequence for hash-chain/event ordering per agent.
Lower implementation and audit risk for the current architecture.

Module	Functions
Identity	`register()`, `setAgentURI()`, `setMetadata()`, `setAgentWallet()`
Reputation	`giveFeedback()`, `revokeFeedback()`, `appendResponse()`

Solana Architecture

Pattern	Implementation
Feedback/Response/Revoke	Event-only with hash-chain proof
Metadata	Separate PDAs per entry
Agent IDs	Metaplex Core asset pubkey

Events-Only Integrity Note

Feedback, revoke, and response are intentionally events-only. For production reads, consumers must use the verified indexer pipeline, not raw event streams.

The maintained indexer enforces the critical checks:

Revocation with missing parent feedback is marked ORPHANED
Revocation with seal_hash mismatch vs stored feedback is marked ORPHANED
Response with missing parent feedback is marked ORPHANED
Response with seal_hash mismatch vs stored feedback is marked ORPHANED

Reference implementation: 8004-solana-indexer

Formal Verification (Kani)

Kani checks in this repo are development-time only and are not deployed on-chain.

Scope: local Rust proof harnesses for reputation invariants
Build gating: compiled only with #[cfg(kani)]
Runtime impact: none
IDL/ABI impact: none

Run locally:

cargo kani -p agent-registry-8004

Beyond the Spec

Feature	What it brings
ATOM Engine	Sybil resistance, burst detection, 5-tier trust
SEAL v1	On-chain hash of feedback parameters for integrity verification
Immutable Metadata	Lock critical data forever

Get Started Fast

Component	What you get
TypeScript SDK	Full client library
Indexer	Query all events

Costs

Operation	Rent (SOL)
Register Agent	~0.006
Initialize ATOM Stats	~0.005
Give Feedback	~0.000005

Quick Start

Clone, build, test—you're up in minutes:

git clone https://github.com/QuantuLabs/8004-solana.git
cd 8004-solana
./scripts/setup-atom-engine-dep.sh
yarn install
anchor build
anchor test

Reproducible Build Note (Mainnet Hash)

agent-registry-8004 intentionally depends on atom-engine via a local path: ../../../8004-atom/programs/atom-engine.

This path layout is required to reproduce the current mainnet binary hash. Switching to a git dependency or changing the path location changes the rebuilt .so hash.

Use ./scripts/setup-atom-engine-dep.sh to provision ../8004-atom at the expected revision before running anchor build or cargo build-sbf.

Mainnet Binary Hash Reference

As of 2026-03-04, the expected agent-registry-8004 mainnet executable hash is:

5aeae715714861fd43ac09d80bc51f70836b27a325a2c2131374121c6c05a5c8

Verify directly from chain:

solana program dump --url mainnet-beta 8oo4dC4JvBLwy5tGgiH3WwK4B9PWxL9Z4XjA2jzkQMbQ /tmp/agent_registry_8004_mainnet.so
shasum -a 256 /tmp/agent_registry_8004_mainnet.so

Verify local reproducible build:

./scripts/setup-atom-engine-dep.sh
cargo build-sbf --manifest-path programs/agent-registry-8004/Cargo.toml
shasum -a 256 target/deploy/agent_registry_8004.so

solana-verify is optional. For binary integrity, solana program dump + shasum is sufficient.

Devnet Setup

After deploying the programs to devnet, initialize the registry (one-time setup by the upgrade authority):

# Set environment variables
export ANCHOR_PROVIDER_URL="https://api.devnet.solana.com"
export ANCHOR_WALLET="$HOME/.config/solana/id.json"

# Run the init script (creates config + base collection)
npx ts-node scripts/init-devnet.ts

This creates:

Config PDA: Global registry config (authority, collection mint)
Base Collection: Single Metaplex Core collection for all agent NFTs

Account	Current Devnet Address
Config	`EJ3UN1Rp9QCqe5xjHMuoxTmRWm6KBYrxSeATtheFmgZb`
Base Collection	`C6W2bq4BoVT8FDvqhdp3sbcHFBjNBXE8TsNak2wTXQs9`

Note: Only the program upgrade authority can call initialize.

Documentation

Roadmap

v0.4.0 - ATOM Engine + Multi-collection
v0.5.0 - ATOM v0.2.0 + Canonical dedup
v0.5.1 - Security hardening
v0.6.0 - SEAL v1 (trustless on-chain hash)
Substreams indexer
Mainnet deployment