ERC-1155: Multi-Token Standard
ERC-1155 packs both fungible and non-fungible token types into a single contract. Originally built for gaming (one contract holds 1000 different sword types + a fungible gold currency), it's now common across DeFi for batch operations.
Neo Approach: Composition
There is no dedicated multi-token NEP. Instead, Neo recommends composition: deploy a single NEP-17 per fungible type, use NEP-11 with decimals() > 0 for divisible non-fungibles. Batch transfers compose at the application layer — Neo's multi-call transaction format lets one signed tx invoke many contracts atomically.
For a true multi-token use case in a single contract, the C# tab below shows a Neo port of ERC-1155 — works, but composition is usually cleaner.
Live on Neo TestNet
Both implementations deployed on Neo N3 TestNet.
| Implementation | TestNet Address | Contract Hash |
|---|---|---|
Solidity (neo-solc) | Nh1cqvGbsjE3FFhuZRWMytSskeYqs1FTPb | 0xf1d7867c…224d0317 |
Neo C# (nccs) | Nh4WdHEoVHQiBL3GoCfM98AkWMnwqumFW6 | 0xef019e6f…a8ba86bd |
Verified: deployer claim, ownership semantics. Per-id balance and batch transfer flows validated by the assertion script in deployments/manifest.json. docs/standards-mirror/deployments/erc-1155/.
