Learn

Agentic NFT Diagram

The Agentic NFT is usually one token referenced by several layers — not a separate NFT at every layer. Its contract address and token ID identify it. Other contracts attach a wallet, metadata, an agent identity, or trust records to that identifier.

A layer diagram can show the blockchain pieces more clearly than the actual agent. The missing distinction is where ownership is recorded versus where intelligence runs.

Boxes with an ERC number link to that standard’s No Jargon Explanation. Scroll sideways on a small screen. The violet boxes are chain records. The blue boxes are the application, which is usually not on the chain.

Where ownership sits, and where the agent runs

The same token can point at files and at software without holding the model inside the contract. This chart splits that into three layers: onchain records, storage that is often offchain, and compute that is usually offchain.

Violet boxes are records on the chain. Blue boxes are files and software that usually live somewhere else. A hash or a link on the token is not the file itself.

What each part actually is

Component	What it actually is	Where it usually lives	What can be onchain
Agentic NFT	The token representing ownership or control	Blockchain contract	Token ID, owner, approvals, transfers
LLM	The model that generates responses and reasons over inputs	A provider’s servers, your computer, or a cloud GPU	Model identifier, configuration reference, model hash, or verification records
Agent runtime	Software that calls the model, retrieves memory, invokes tools, and schedules work	A server, VM, container, or local computer	Authorization rules and transaction records
Memory	Conversation history, summaries, facts, and retrieved knowledge	Files, databases, vector stores, or decentralized storage	Small records, storage references, hashes, or commitments
Skills	Instructions, executable code, and tool configurations	Skill files, repositories, runtime packages, and services	Skill descriptions, code hashes, references, and enforceable contract permissions
Soul	A project-defined personality, purpose, values, and behavioral policy	A prompt or context file, or a structured configuration	The actual text, such as an ERC-8048 context record, or a reference to it
Wallet	The account used to hold assets and transact	Blockchain	Balances, transactions, and contract authorization

“Soul” is not a universally defined technical component. One project may use it to mean a personality prompt. Another may include memories, goals, and policies. Storing that text onchain preserves a readable record, but the runtime must load and use it for it to affect behavior.

Likewise, a memory hash is not the memory itself. It can help verify that a retrieved file matches a recorded version. It cannot reconstruct a missing chat log. Persistent memory requires actual storage, retrieval, and backups.

What “onchain” can mean

For a true onchain agentic NFT, there are several possible architectures.

Architecture	What is onchain	What remains elsewhere
Onchain identity and ownership	NFT, identity, wallet, metadata references	Model, memory, skills, and execution
Onchain configuration	The above plus actual context text and some state	Usually model inference and tool execution
Verifiable offchain execution	Commitments and verification results	Computation, with a mechanism for checking particular claims
Fully onchain execution	Contract-executed logic and state	External information still needs an input mechanism. Substantial LLM inference is generally impractical on conventional EVM chains.