Skip to main content
T TON Adoption
RU
← Glossary
NODE/03 · Term

NFT on TON

Non-fungible tokens following the TEP-62 standard. Each NFT is its own smart contract, sitting under a collection contract — the architectural mirror of the jetton model.

Aliases: ton nft, tep-62

NFTs on TON follow the TEP-62 standard. Architecturally they are the non-fungible cousins of jettons: each individual NFT is a separate smart contract owned by its holder, and a parent collection contract ties them together with shared metadata and minting logic.

Architecture

A typical TON NFT project deploys:

  • One NFT Collection contract — holds the collection name, image, royalty rules, and the index counter.
  • One NFT Item contract per token — stores the current owner, the item’s index, and a pointer to its metadata.

Compare with Ethereum’s ERC-721, where a single contract holds a mapping of tokenId → owner. The TON model trades a bit of deployment overhead (more contracts) for parallelism (transfers don’t contend on a shared mapping).

Metadata

Metadata can live on-chain (inside the contract’s data cell), or off-chain at an HTTPS or IPFS URL referenced from the contract. Most production collections use off-chain JSON for cost, with the contract storing only the URL.

The schema is a TEP-64 JSON file:

{
  "name": "TON Diamonds #42",
  "description": "...",
  "image": "https://.../42.png",
  "attributes": [{ "trait_type": "Color", "value": "Blue" }]
}

Royalties (TEP-66)

TEP-66 extends TEP-62 with a royalty record on the collection contract: a royalty recipient address and a basis-points percentage. Marketplaces that respect TEP-66 (Getgems, Disintar, Fragment) deduct the royalty automatically on every secondary sale. Wallet-to-wallet transfers, of course, bypass marketplaces and pay no royalty — same caveat as on Ethereum.

Major use cases

  • Telegram Usernames — @username handles tokenised on Fragment.
  • Anonymous Numbers — TON-based phone numbers, also via Fragment.
  • TON DNS / .ton domains — each domain is an NFT under TEP-81 (NFT-DNS extension).
  • Notcoin Vouchers, TON Diamonds, Anatoly Plays — collectible art and game assets.
  • Mini App rewards — Notcoin, Hamster Kombat and others issued NFT badges to players.

Marketplaces

By 2026 the dominant venue is Getgems, with secondary activity on Disintar and Fragment (the latter operated by the TON Foundation for Telegram-native assets). Volume sits in the millions of TON per month, far below Ethereum’s NFT market in absolute terms but with much lower fees per trade — typically 0.05–0.1 TON.

Wallet support

Tonkeeper, MyTonWallet, Tonhub and the Telegram wallet all display NFTs natively — collections appear under a separate tab, transfers cost the usual TON message fee. Sending an NFT is a regular transfer opcode message to the item contract; the new owner is the message destination.

Practical notes

  • Always verify the collection contract address before buying — copycat collections with the same name are common.
  • Royalty enforcement is a soft convention; transfers can bypass it.
  • Burning is supported but uncommon; “burn” usually means transferring to a known dead address.

Related terms