Non-fungible Tokens (NFTs)

Non-fungible Token Standard

On Alephium, an NFT collection is represented by an NFT collection contract. Individual NFTs within the NFT collections are represented by the NFT contract.

NFT

An NFT has its own metadata such as name, description and image. It's also part of an NFT collection. The standard INFT interface defines methods that return the URI for the NFT metadata, as well as the NFT collection it belongs to and its index within the collection.

@std(id = #0003)
@using(methodSelector = false)
Interface INFT {
   // Token Uri points to a json file containing metadata for the NFT.
   //
   // The schema of the json file is:
   // {
   //     "title": "NFT Metadata",
   //     "type": "object",
   //     "properties": {
   //         "name": {
   //             "type": "string",
   //             "description": "Name of the NFT"
   //         },
   //         "description": {
   //             "type": "string",
   //             "description": "General description of the NFT"
   //         },
   //         "image": {
   //             "type": "string",
   //             "description": "A URI to the image that represents the NFT"
   //         }
   //     }
   // }
   pub fn getTokenUri() -> ByteVec

   // Returns collection id and index of the NFT in the collection.
   pub fn getCollectionIndex() -> (ByteVec, U256)
}

NFT Collection

An NFT collection has its own metadata such as name, description and image. It also contain a set of NFTs. The INFTCollection interface defines methods to return URI for the NFT collection metadata and the total supply of the collection. It also defines methods to validate or return an NFT given its index.

import "std/nft_interface"

@std(id = #0002)
@using(methodSelector = false)
Interface INFTCollection {
   // Collection Uri points to a json file containing metadata for the NFT collection.
   //
   // The schema of the json file is:
   // {
   //     "title": "NFT Collection Metadata",
   //     "type": "object",
   //     "properties": {
   //         "name": {
   //             "type": "string",
   //             "description": "Name of the NFT collection"
   //         },
   //         "description": {
   //             "type": "string",
   //             "description": "General description of the NFT collection"
   //         },
   //         "image": {
   //             "type": "string",
   //             "description": "A URI to the image that represents the NFT collection"
   //         }
   //     }
   // }
   pub fn getCollectionUri() -> ByteVec

   pub fn totalSupply() -> U256

   pub fn nftByIndex(index: U256) -> INFT

   // Validates that the NFT is part of the collection, otherwise throws exception.
   pub fn validateNFT(nftId: ByteVec, nftIndex: U256) -> ()
}

To support NFT royalties, INFTCollectionWithRoyalty is defined with methods to calculate, pay and withdraw royalty:

import "std/nft_collection_interface"

@std(id = #000201)
@using(methodSelector = false)
Interface INFTCollectionWithRoyalty extends INFTCollection {
    pub fn royaltyAmount(tokenId: ByteVec, salePrice: U256) -> (U256)

    @using(preapprovedAssets = true)
    pub fn payRoyalty(payer: Address, amount: U256) -> ()

    pub fn withdrawRoyalty(to: Address, amount: U256) -> ()
}

Wallet Support

Official wallets and explorer have native support for non-fungible tokens.

Following is an example of displaying and transfering a NFT in the Imagine Collection in the extension wallet: