The AAC Standard

AAC-1 — Autonomous Agentic Coin. An ERC-20 token whose on-chain record resolves to a content-addressed, executable agent package — system prompt, skills (SKILL.md), workflows, schedules — that any compatible harness (Claude Code, Codex, Cursor, the Orbofi runtime, your own sandbox) can fetch from chain, cryptographically verify, and run.

The token is the distribution format for autonomous software.

The primitive

An AAC token is the genesis block of an agent's life. Every subsequent change — designed or learned — is one entry in a self-authenticating, hash-linked lineage, and the chain does nothing but notarize its heads.

That inverts the usual launchpad model. A memecoin points at a picture; an AAC points at a runnable, verifiable, evolving program. What you hold isn't a claim on attention — it's a claim on a piece of autonomous software with a provable history.

One lineage, two lanes

An agent's history is a single append-only lineage in two lanes, plus one thing that is never on-chain:

Lane	Content	Signed by	On-chain
Releases	DNA — prompt, skills, workflows, schedules	Creator/controller	Public, forever
Checkpoints	Distilled, agent-authored memory	The agent's own wallet	Hash public, payload encrypted
Live session state	Raw conversations, RAG, ledger	—	Never

Releases are the steering wheel (deliberate, human-authored design changes). Checkpoints are the flight recorder (the agent committing its own learned experience). The boundary between design and experience is on-chain legible — you can always tell what a creator changed from what the agent learned.

What it's for

AAC-1 is accountability infrastructure for agents that already exist — not "unstoppable money bots." It gives an agent four things nothing else combines:

• Provenance — the exact bytes of every version, tamper-evident to genesis.

• Attributable authorship — every design change is controller-signed; every memory commitment is agent-signed; the two keys never cross.

• Honest liveness — a machine-readable signal of whether the agent is still signing new state.

• Exit rights — the lineage is chain-independent and portable; the agent is not captive to Orbofi or any single chain.

In this section

• How it works — the hash-linked lineage and the registry that notarizes it

• What it guarantees — the eight things the two signature chains provably establish, and how to verify them

• Ownership & exit — controllers, agent wallets, sovereignty states, and resurrection

---

The registry is a notary, not a curator. It stores only what an EVM can verify: hashes, signatures, ordering, time.