Standards supported by TesseractX
TesseractX supports a broad set of NFT standards, but support does not mean every standard is automatically implemented by every collection contract. This page separates live marketplace behavior, application integrations, adapter compatibility and creator contract extensions.
ERC 721
Unique NFTs
The base standard for unique, individually owned NFTs.
ERC 1155
Multi edition assets
One contract can issue many token types with multiple copies of each token ID.
ERC 6551
Token bound accounts
Gives an NFT its own smart wallet so it can own tokens and other NFTs.
ERC 5773
Multi asset NFTs
Lets one NFT expose multiple renderable assets or media representations.
ERC 6220
Equippable NFTs
Defines slots and parts so child assets can be equipped to a parent NFT.
ERC 6454
Transfer restrictions
Lets a token report whether it can be transferred in a given context.
ERC 7409
Emotable NFTs
A standard model for reactions and emotes associated with NFTs.
ERC 7508
On chain attributes
A model for mutable or queryable NFT attributes managed on chain.
ERC 7590
Fungible assets in NFTs
A composable pattern for NFTs that can hold ERC 20 value or fungible inventory.
ERC 4907
NFT rentals
Separates an NFT owner from a temporary user with an expiry time.
ERC 2981
Royalty information
Standardizes how a collection reports its royalty recipient and amount.
ERC 404
Hybrid fractional assets
An experimental hybrid model combining fungible balances with NFT behavior.
The base standard for unique, individually owned NFTs.
How TesseractX uses it
TesseractX indexes, displays, transfers, lists and settles ERC 721 assets. ERC 6551 composability also binds token accounts to ERC 721 parent tokens.
Creator use case
Use this for unique art, characters, bases and one of one component assets.
One contract can issue many token types with multiple copies of each token ID.
How TesseractX uses it
TesseractX settlement supports ERC 1155 transfers and partial unit fills where an order is configured for them.
Creator use case
Use this for editions, consumables, game items and component assets with supply greater than one.
Gives an NFT its own smart wallet so it can own tokens and other NFTs.
How TesseractX uses it
TesseractX can create and resolve token bound accounts, deposit owned NFTs into them and use them as the foundation of composable bundles and builders.
Creator use case
Use this when a parent NFT should carry equipment, inventory or other nested assets with it.
Lets one NFT expose multiple renderable assets or media representations.
How TesseractX uses it
TesseractX includes multi asset rendering, reveal handling and an ERC 5773 adapter interface. A collection contract must implement the actual on chain semantics if it wants full ERC 5773 behavior.
Creator use case
Use this for NFTs that can switch between image, 3D, audio, video, ticket or document representations.
Defines slots and parts so child assets can be equipped to a parent NFT.
How TesseractX uses it
TesseractX provides named equip slots, fixed parts, layered previews and an ERC 6220 adapter interface. Collections requiring strict on chain equip enforcement must implement that logic in their contracts.
Creator use case
Use this for characters with heads, bodies, legs, clothes, weapons, accessories and other slot based components.
Lets a token report whether it can be transferred in a given context.
How TesseractX uses it
TesseractX includes transferability awareness in its NFT model, UI and settlement adapter source. Enforcement depends on the collection and active validator configuration.
Creator use case
Use this for locked identity items, achievements or assets whose transfer rules change over time.
A standard model for reactions and emotes associated with NFTs.
How TesseractX uses it
TesseractX currently provides an emotable interaction layer in the app. These reactions are not presented as proof that the underlying collection contract implements ERC 7409 on chain.
Creator use case
Use the interaction pattern when community reactions are part of the NFT experience.
A model for mutable or queryable NFT attributes managed on chain.
How TesseractX uses it
TesseractX has an attribute authoring experience aligned with ERC 7508 concepts. A collection needs compatible contract logic for attributes to be truly on chain under this standard.
Creator use case
Use this pattern for evolving stats, levels, states or attributes that should be contract readable.
A composable pattern for NFTs that can hold ERC 20 value or fungible inventory.
How TesseractX uses it
TesseractX can deposit and display ERC 20 balances held by an ERC 6551 token bound account. This provides the user experience for fungible value traveling with a composable NFT.
Creator use case
Use this for characters, vaults or bundles that should carry fungible assets with the parent NFT.
Separates an NFT owner from a temporary user with an expiry time.
How TesseractX uses it
TesseractX includes an ERC 4907 extension scaffold and client helpers. It is not a standalone deployed rental contract, so a creator collection must implement the extension for live rental behavior.
Creator use case
Use this for games, memberships or utility NFTs that can be rented without transferring ownership.
Standardizes how a collection reports its royalty recipient and amount.
How TesseractX uses it
The hardened TesseractX settlement source includes bounded ERC 2981 royalty resolution. Runtime use depends on the deployed settlement configuration, while signed order consideration remains the authoritative payout structure for a listing.
Creator use case
Use this to expose portable royalty information to marketplaces that honor ERC 2981.
An experimental hybrid model combining fungible balances with NFT behavior.
How TesseractX uses it
TesseractX contains an ERC 404 bundle integration stub, but no standalone ERC 404 bundle deployment is configured. It should be treated as an advanced creator integration rather than a default live standard.
Creator use case
Use only when your own audited collection architecture intentionally uses an ERC 404 implementation.
Building a standards rich collection
The collection creator should be able to choose the capabilities it needs before deployment. TesseractX will only register a newly created collection after the contract deployment is confirmed on chain. Advanced standards that require contract behavior must be present in the deployed collection contract rather than represented only by database metadata.
Open collection creator