# NEAR ## ERC888 Multi-Dimensional Token Standard This standard is for multi-dimensional tokenization, which utilizes identifiers to refer to balances & data.\ This standard has been implemented on NEAR This standard was referenced to ERC1633 but merged to EIP1178 Multi-class Token Standard ### ERC888 "Token data structures with balances specified by unique identifiers create emergent properties within crypto economic systems that introduce valuable approaches to mechanism design and contract development. Multidimensional tokens involve layers of information and functionality, create interdependent curation markets, and give rise to integrated information across networks." - ERC Author ## EIP1178 Relates to ERC720 ### Simple explanation * Standard interface for multi-class fungible tokens. * Allows for implementing a standard API for multi-class fungible tokens (henceforth referred to as “MCFTs”) within smart contracts. * Provides basic functionality to track and transfer ownership of MCFTs. ### Limitations before this standard " The design of this project was motivated when I tried to create different classes of fungible ERC-721 tokens (an oxymoron) but ran into gas limits from creating each token individually and maintaining them in an efficient data structure for access. Using the maximum gas amount one can send with a transaction on Metamask (a popular web wallet), I could only create around 46 ERC-721 tokens before exhausting all gas. This experience motivated the creation of the multi-class fungible token standard." - EIP Author ### Further reading Relates to ERC720 * Multi-Class token Standard implementation: * Merge source: * Multi Dimensional Token Standard draft: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://nft-standards.gitbook.io/nft-standards-wiki/non-eth-nft-standards/near.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.