Closed ra-phael closed 2 years ago
As with ERC1155:
A single contract is needed to efficiently manage both fungible and non-fungible tokens:
<uint128: base token id><uint128: index of non-fungible>
A base (default) URI can be provided for all token types relying on substitution, e,g "https://token-cdn-domain/{id}.json"
Batch operations for minting and burning are possible
The "ERC1238URIStorage" extension enables specific URIs per token id which override the base URI.
The Badge contract is provided as a simple example that makes use of ERC1238 and ERC1238URIStorage
Badge
As with ERC1155:
A single contract is needed to efficiently manage both fungible and non-fungible tokens:
<uint128: base token id><uint128: index of non-fungible>
A base (default) URI can be provided for all token types relying on substitution, e,g "https://token-cdn-domain/{id}.json"
Batch operations for minting and burning are possible
The "ERC1238URIStorage" extension enables specific URIs per token id which override the base URI.
The
Badge
contract is provided as a simple example that makes use of ERC1238 and ERC1238URIStorage