Level 3 · How it worksThe village#222

ERC-721 and ERC-1155 explained: a numbered deed, or a whole drawer of them

ERC-721 is the standard for one-of-a-kind tokens: each token ID has exactly one owner. ERC-1155 lets one contract keep many kinds of token at once, unique and interchangeable. In both, what the blockchain records is who owns which token ID; the picture usually lives somewhere else.

The baker's voucher page says "Rosa: 3". Any three vouchers will do; they're all the same. The village clerk's deed book is different. It says "Plot 17: Anna." Not a plot. Plot 17, the one by the well.

Bread vouchers are interchangeable. Deeds aren't. Ethereum has a standard for each, and a third that keeps both kinds in one drawer.

ERC-721 is the deed book: every token has its own number and exactly one owner. ERC-1155 is the drawer: one contract, many kinds of token, some unique, some by the dozen. In both, the notebook records who owns which number. Rarely the thing itself.

What it is

ERC-721 was created on 24 January 2018 by William Entriken, Dieter Shirley, Jacob Evans and Nastassia Sachs. Its summary: "A standard interface for non-fungible tokens, also known as deeds." The key line: "NFTs are distinguishable and you must track the ownership of each one separately" (EIP-721). Each token gets "a unique uint256 ID inside the ERC-721 smart contract".

ERC-1155 was created on 17 June 2018 by Witek Radomski, Andrew Cooke, Philippe Castonguay, James Therien, Eric Binet and Ronan Sandford. It is "A standard interface for contracts that manage multiple token types", and "Both fungible and non-fungible tokens can be stored in the same smart-contract" (EIP-1155).

How it works

The difference is in what each list keeps.

  • An ERC-20 list says: address, amount. "Rosa: 3."
  • An ERC-721 list says: token ID, owner. "Token 17: Anna." Its ownerOf function returns "The address of the owner of the NFT".
  • An ERC-1155 list says: address, token ID, amount. "Rosa, ticket type 2: 3. Anna, deed type 9: 1."

Now a real ERC-721 contract, read on Etherscan on 19 November 2026 (an example, not a recommendation). The BoredApeYachtClub contract was created on 22 April 2021 in block 12,287,507 (Etherscan). Etherscan lists it as ERC-721 with a total supply of 10,000 and 5,614 holders (Etherscan).

  1. 10,000 rows. The contract holds 10,000 token IDs, each pointing to one owner address.
  2. 5,614 owners. 10,000 / 5,614 = about 1.78 tokens per holding address on average. Some addresses hold one, some many.
  3. The picture. Each ID also has a tokenURI: "A distinct Uniform Resource Identifier (URI) for a given asset", which "may point to a JSON file" describing it (EIP-721). The notebook keeps the address of the description, not the image. "Where the picture actually lives" follows that link to the end.

Now the drawer. Say the village fair issues one ERC-1155 contract with two kinds: type 1, entry tickets, 500 of them; type 2, a single prize deed. Anna buys 3 tickets and wins the deed. One call to safeBatchTransferFrom, which moves several "_ids" at once, sends her both in a single transaction. Under the older standards that would be two separate contracts and two transfers.

That's the point of 1155. Its authors note that ERC-20-style designs "require deployment of separate contracts per token type", which leaves "a lot of redundant bytecode on the Ethereum blockchain" (EIP-1155). One drawer is cheaper than a shelf of boxes.

Why it matters

  • Ownership you can check. Anyone can ask the contract who owns token 17 and get the same answer in every house. Ben can claim he owns it. The notebook disagrees.
  • Rights are what the code and the issuer say. The standards record ownership of an ID. Whether that ID gives you any rights to a picture, a ticket or a plot depends on the issuer's terms, not on the standard.
  • Games and tickets got simpler. One 1155 contract can hold a game's coins, swords and one-off trophies together.

Where people get it wrong

  • "I own the picture." You own a token ID in a contract. The image is usually stored elsewhere, at the address the contract points to.
  • "An NFT can't be copied." The token ID can't be duplicated within its contract. Anyone can deploy another contract with the same name and the same pictures.
  • "ERC-1155 tokens are all NFTs." Some are, some aren't. One contract can hold both.
  • "The standard protects my rights." It records who holds which ID. Nothing more.

Check the contract and the ID

Before you accept or buy any NFT, find two things on a block explorer: the contract address and the token ID. Compare the contract with the address the issuer publishes on its official site. Then open the tokenURI and see where the description actually points.

Two collections can share a name, a logo and every picture. Only one of them is the deed book; the other is the stranger at the gate with a photocopier.

Frequently asked questions

What is the difference between ERC-721 and ERC-1155?

ERC-721 is a standard for unique tokens: each token ID has exactly one owner. ERC-1155 lets a single contract manage many token types at once, both unique and interchangeable, and move several of them in one transaction.

Who created the ERC-721 standard?

EIP-721 was created on 24 January 2018 by William Entriken, Dieter Shirley, Jacob Evans and Nastassia Sachs. It describes non-fungible tokens as deeds whose ownership must be tracked one by one.

Does an NFT store the image on the blockchain?

Usually not. An ERC-721 token normally carries a tokenURI that points to a description file, which in turn points to the image. The blockchain records who owns the token ID.

What is a token ID?

A token ID is the number that identifies one token inside an ERC-721 or ERC-1155 contract. Together with the contract address, it names one specific token.

Why was ERC-1155 created?

Its authors wanted one contract to handle many token types, because earlier standards needed a separate contract for each, which wasted space on the blockchain. ERC-1155 also lets several token types move in a single batch transfer.

Sources

  1. William Entriken, Dieter Shirley, Jacob Evans, Nastassia Sachs, ERC-721: Non-Fungible Token Standard (created 24 January 2018)
  2. Witek Radomski, Andrew Cooke, Philippe Castonguay, James Therien, Eric Binet, Ronan Sandford, ERC-1155: Multi Token Standard (created 17 June 2018)
  3. Fabian Vogelsteller and Vitalik Buterin, ERC-20: Token Standard
  4. Etherscan, BoredApeYachtClub (BAYC) token page (read on 19 November 2026)
  5. Etherscan, BAYC contract creation transaction, block 12,287,507 (22 April 2021)

Read next.