Games and digital items
Thousands of item types, from common to rare, managed efficiently in one place.
Token standard
ERC-1155 lets one program manage thousands of item types at once, some interchangeable, some unique. It is efficient and flexible. Like the formats before it, it leaves the question of who may own each item entirely open.
ERC-1155 was proposed in 2018 and is a final Ethereum standard. It is called a multi-token standard because one smart contract, a small program on the blockchain that runs exactly as written, can hold many different tokens side by side.
Some of those tokens can be fungible, meaning identical and interchangeable like units of one share class. Others can be non-fungible, meaning each one is unique, like a numbered certificate. ERC-20 handles only the first kind and ERC-721 only the second. ERC-1155 handles both.
Each item type has its own number. The program keeps track of how many units of each type every account holds.
Several item types can be sent in one transaction. This lowers gas, the processing fee paid to the network for each transaction, and saves time when moving many items.
Accounts are controlled from a wallet, the software or device holding the key that proves control. Anyone can open one, and the standard checks only that the sender holds enough units.
Thousands of item types, from common to rare, managed efficiently in one place.
Many ticket categories for one event, with seats or passes that may be unique or interchangeable.
Any case where many item types are issued and moved often, and cost per transfer matters.
Efficiency is useful, but it is not the hard part of tokenizing a real asset. The hard part is making sure only eligible, verified investors ever appear on the investor register, and that the issuer can act when something goes wrong. ERC-1155 has no built-in identity, no transfer rules and no issuer controls.
An issuer with several share classes or tranches might be drawn to ERC-1155 because it can hold them all in one place. Doing that safely still means writing custom compliance code around it, which then has to be reviewed and audited as new work. A standard designed for regulated securities already carries those checks in a shared, audited format.
Multiple classes can be handled by issuing separate ERC-3643 securities, each with its own rules. That keeps each class clean on the investor register and in your legal documents.
It can be cheaper per transfer for large batches. For a regulated offering, the cost that matters more is the review of any custom compliance code you would need to add.
Some projects have experimented with it. It is not a security token standard, so each such project defines its own rules.
General information about a public technical standard. Not legal, tax or investment advice.
Tell us about your project in five short steps. Within a week you'll know whether it fits, what's missing and how quickly your investor portal could go live.