NFT Collection

NFT Collection is the contract that describes a non-fungible token collection on TON. Each collection is a separate smart contract that holds shared metadata and deploys an individual NFT Item contract per mint. The architecture parallels jetton master / jetton wallet, but for NFTs.

What it stores

• Collection metadata. Name, description, shared icon, link to off-chain JSON.
• Owner address. Who can mint new items.
• next_item_index. Counter for the next NFT in the collection.
• Royalty params. Royalty rate and recipient (per TEP-66).
• NFT Item code. Reference code from which each individual NFT is deployed.

What it does

• Mint. Owner or a signed bot sends mint; the collection deploys a new NFT Item with the appropriate metadata.
• Get methods. get_collection_data, get_nft_address_by_index, get_nft_content — the standard set explorers and marketplaces rely on.
• Royalty info. royalty_params returns the rate and recipient. Marketplaces (Getgems, Disintar) call it to split revenue correctly.

Standards

To stay compatible with the rest of the ecosystem, a collection contract should follow:

• TEP-62 — base NFT standard (collection and item structure).
• TEP-64 — metadata standard (JSON format: name, image, attributes).
• TEP-66 — royalties standard (how marketplaces should pay them).

Without these, the NFTs won’t display correctly in wallets or trade on marketplaces.

Identification

In wallet UIs and explorers a collection is identified by its contract address. Public collections (Anonymous Telegram Numbers, .ton domains, Notcoin Vouchers) are all specific collection contracts with widely known addresses.