ERC-8041 Fixed-Supply Agent NFT Collection (Fixed-Supply Agent NFT Collections)
Draft · NFTs & multi-token · created 2025-10-11
While the ERC-8004 agent registry allows unlimited registration, this standard enables creating fixed-quantity collections with an issuance cap and a start block, and permanently recording each agent's mint sequence number.
Why it is needed
The ERC-8004 agent registry is an unlimited minting structure in which anyone can freely register an agent. However, there was no standard way to create a limited-edition collection with a fixed quantity like 'Genesis 100', to have one agent belong simultaneously to multiple differently named collections like 'dev-team', to permanently record the mint sequence number (e.g. 5 of 1000), to open minting only from a specific block, or to run a curated drop where the issuer directly controls minting. As a result, each project had to implement collections and sequence numbers in its own way, and wallets or marketplaces could not read or verify them consistently.
What to implement
event CollectionUpdated(uint256 maxSupply, uint256 startBlock, bool open);: Emitted whenever a collection is created or its maxSupply, startBlock, or open value changes.event AgentMinted(uint256 indexed agentId, uint256 mintNumber, address indexed owner);: Emitted when an agent is added (minted) to a collection, announcing the mint number and recipient.function getAgentMintNumber(uint256 agentId) external view returns (uint256 mintNumber);: Returns the sequence number at which the agent was minted in this collection, or 0 if it does not belong to the collection.function getCollectionSupply() external view returns (uint256 currentSupply);: Returns the quantity minted so far in this collection.function contractURI() external view returns (string memory);: Returns a URI for collection-level metadata (name, description, image, etc.) in ERC-7572 format. Implementation is optional.
In depth
The Four Properties a Collection Must Maintain
Every compliant collection contract must maintain maxSupply (the maximum number of agents in the collection), currentSupply (the number minted so far), startBlock (the block number from which minting becomes possible), and open (whether the collection is currently accepting mints). These four values are announced externally via the CollectionUpdated event at creation and whenever they change.
The Required Procedure When Minting an Agent
When minting an agent through a collection contract, the agent must be registered in the ERC-8004 registry, assigned a sequential mint number starting from 1, that number stored internally, the agent's on-chain metadata recorded under a key identifying the collection, and an AgentMinted event emitted.
The Default Key and ERC-8119 Parameter Keys
The primary collection uses the parameterless agent-collection key, which can be found directly without indexing. Additional collections are distinguished using one of the ERC-8119 parameter key formats: agent-collection:label, agent-collection/label, or agent-collection[label]. Since labels are arbitrary values, finding collections other than the primary key requires indexing the agent's metadata keys. A single contract must use one key consistently across all of its mints.
The Collection Metadata Encoding Format
It is recommended (SHOULD) that metadata be encoded via abi.encodePacked by concatenating the collection contract address (20 bytes), the mint number's byte length (1 byte), and the mint number value (variable length). This allows anyone to confirm the collection address an agent belongs to, decode the mint number, and query additional information from the collection contract.
Mint Number Rules
The mint number must start from 1, not 0, must increase sequentially each time an agent is added, must never change once assigned, and must be queryable via getAgentMintNumber().
Supply Management Obligations
The collection contract must prevent minting beyond maxSupply, must accurately track currentSupply, must emit AgentMinted for every successful mint, and must not allow minting before startBlock.
Choices Left to Implementation
Access control over who can mint (owner, public, allowlist, etc.), the payment model (free, paid, etc.), collection state management such as opening/closing or locking, and whether minting is single or batch are not mandated by the standard and are left to each implementation. However, it is recommended (SHOULD) to implement ERC-7572's contractURI() function in order to provide collection-level name, description, image, and similar data.
Proposal status
This standard was authored on 2025-10-11 and is currently in Draft status. Since it has not yet been formally adopted, the details may change or the proposal may be discontinued.
Things to watch out for
- Collection Metadata Can Be Arbitrarily Changed by the Owner: An ERC-8004 agent owner can modify or delete their own agent-collection or agent-collection:label metadata at any time. Therefore, clients must not rely on this metadata alone to confirm collection membership.
- Always Query the Collection Contract Directly: Clients should (SHOULD) use the metadata only as a hint for which collection to check, and must verify actual membership by calling getAgentMintNumber(agentId) directly on the collection contract. Finding labeled collections requires indexing the agent's metadata keys.
- A Mint Number of 0 Is Definitive Proof of Non-Membership: If the mint number returned by a collection contract is 0, this must be treated as definitive proof that the agent does not belong to that collection.