This is a FRAME pallet that defines and implements an interface for managing a set of non-fungible tokens (NFTs). Assets have an owner and can be created, destroyed and transferred.

This package defines a public trait (Rust interface) for working with NFTs: the UniqueAssets trait.

This trait is generic with respect to a type that is used to identify asset owners - the AccountId type. Assets with equivalent attributes (as defined by the AssetInfo type) must have equal AssetIds and assets with different AssetIds must not have equivalent attributes.

• AssetId: a URI for an asset
• AssetInfo: a set of attributes that uniquely describes an asset
• AssetLimit: the maximum number of assets, expressed as an unsigned 128-bit integer, that may exist in this set at once
• UserAssetLimit: the maximum number of assets, expressed as an unsigned 64-bit integer, that any single account may own from this set at once

• total() -> u128: returns the total number of assets in this set of assets
• burned() -> u128: returns the total number of assets from this set that have been burned
• total_for_account(AccountId) -> u64: returns the total number of asset from this set that are owned by a given account
• assets_for_account(AccountId) -> Vec<(AssetId, AssetInfo)>: returns the list of assets from this set that are owned by a given account
• owner_of(AssetId) -> AccountId: returns the ID of the account that owns the given asset from this set
• mint(AccountId, AssetInfo) -> Result<AssetID, DispatchError>: use the given attributes to create a new unique asset that belongs to this set and assign ownership of it to the given account
  • Failure cases: asset duplication, asset limit reached for set, asset limit for this set reached for account
• burn(AssetId) -> DispatchResult: destroy the given asset
  • Failure cases: asset doesn't exist
• transfer(AccountId, AssetId) -> DispatchResult: transfer ownership of the given asset from this set from its current owner to a given target account
  • Failure cases: asset doesn't exist, asset limit for this set reached for target account

The reference implementation defined in this project is referred to as a "commodity" - a unique asset that is designed for frequent trading. In order to optimize for this use case, sorted lists of assets are stored per owner. Although maintaining a sorted list is trivial with Rust vectors, which implement a binary search API that can be used for sorted insertion, it introduces significant overhead when an asset is created because the entire list must be decoded from the backing trie in order to insert the new asset in the correct spot. Maintaining a sorted asset list is desireable for the commodity use case, however, because it allows assets to be efficiently located when destroying or transferring them. An alternative implementation, the Keepsake pallet, is in the works 🚀

Refer to the mock runtime and provided tests to see the NFT implementation in action.

In order to help develop this pallet, it is being consumed by a test project - a work-in-progress update to the original Substratekitties tutorial.

This project was inspired by works such as the following:

• The ERC-721 specification
• OpenZeppelin's ERC-721 implementation
• the original Substratekitties project, by @shawntabrizi
• Substratekitties from SubstrateCourse, by @xlc

Thanks to the following people who helped me overcome my relatively limited understanding of Rust.

• @JoshOrndoff
• @riusricardo
• @rphmeier
• @thiolliere
• @gnunicorn

This project was forked from the Substrate DevHub Pallet Template.