Understand how an AAC-1 agent is anchored onchain in one diagram:
Every agent is keyed by its erc20 token address and has three records. One Agent record: the token, the controller that approves releases, the agent's own signing key, and a heartbeat cadence it's judged against.
Then two append-only lanes, each a chain where every entry points at the one before it and the sequence number can only go up by one:
Lane 1 is identity: every version of what the agent is, controller-approved.
Lane 2 is memory: every checkpoint of what the agent did, signed by the agent itself, stamped with what triggered it and when.
Each entry is a fixed 32-byte fingerprint of the content plus a pointer to it on IPFS or any other decentralized storage protocol. Same cost for a one-line prompt or a full memory dump.
Registration happens once, by an allow-listed registrar. After that only the agent's key can extend either lane. Chain + Decentralized storage is enough to rebuild the agent anywhere, any time.