Getgems: complete guide to the TON NFT marketplace

Getgems is the best-known NFT marketplace in the TON ecosystem and, in practice, the entry point for most users encountering on-chain collectibles for the first time. The marketplace launched in 2022 and by 2026 has accumulated historical volume comfortably above $50M, supporting three asset classes: standard NFT collections, .ton domains and upgraded Telegram gifts. This guide walks through the interface, the economics, the typical buy and sell flows, and the risks worth understanding before connecting a wallet.

Unlike specialised Telegram-gift marketplaces (Portals, Tonnel, MRKT), Getgems is not a single-niche venue. It is the “general” NFT marketplace of TON, where art collections, club utility NFTs, domains and gifts coexist. That generality is both a strength (everything in one place) and a trade-off (for active gift trading, dedicated venues have deeper orderbooks).

Connection and account

Getgems does not use email and password. Your account is the TON wallet address bound through TON Connect. Flow:

1. Open getgems.io (memorise this URL — it is the only official domain).
2. Click “Connect wallet”.
3. Pick the wallet: Tonkeeper, MyTonWallet, Tonhub, Telegram Wallet or any TON Connect-compatible app.
4. Confirm the connection in the wallet app.
5. After connecting you have a profile with purchase history, listings, offers and per-collection activity.

Getgems does not request any “approve all” signature for connection itself: TON Connect does not grant the site spending rights. Any specific transfer — NFT or TON — requires a separate signed transaction.

What you can buy

Getgems supports several asset classes:

1. Art collections and generative series. Classical Web3 NFTs — image or animation with rarity attributes.
2. Utility NFTs. Club membership tokens, Telegram-bot passes, in-game artefacts.
3. .ton domains. Registration and trading of names through TON DNS. Getgems has a dedicated tab with premium domains and auctions.
4. Upgraded Telegram gifts. Gifts from Telegram that went through the on-chain upgrade trade on Getgems like ordinary NFTs, though for a deeper orderbook the community more often uses Portals or Tonnel.

Buying an NFT: step by step

1. Find the collection. Use search or the Discover tab. Collections with a Getgems verification mark have passed a basic vetting — not an audit, but it filters out impostors.
2. Check the contract. Click the collection address, open it in an explorer (Tonviewer or TonScan) and compare it with the address published on the project’s official Telegram channel. Impostors cluster around well-known projects.
3. Inspect the specific item. Price, traits, ownership history, royalty.
4. Buy. “Buy now” builds a transaction: you sign a TON transfer to the marketplace smart contract, which atomically sends the NFT to you and the TON to the seller, net of fees.
5. Wait for confirmation. Usually 5–15 seconds. The NFT appears in your profile and in your wallet.

Selling an NFT: step by step

1. Open your Getgems profile. Find the NFT in your inventory.
2. Listing. Click “List for sale” and set a TON price.
3. Sign the listing. This is a transaction that escrows the NFT to the marketplace smart contract. After this the NFT temporarily leaves your wallet.
4. Wait for a buy or an offer. A buyer can purchase at the listed price or submit a lower offer — you decide whether to accept.
5. On settlement TON minus 5% (Getgems fee) minus the collection royalty is delivered to your address automatically.
6. Cancel a listing is a separate transaction; the NFT returns from escrow to you.

Fee structure

The collection royalty is a percentage routed to the collection creator on every secondary sale. On TON the royalty is enforced by the collection’s smart contract, not by a “gentleman’s agreement” of the marketplace, so circumventing it by selling outside is technically hard (though possible with custom contracts).

.ton domains on Getgems

A world of its own. .ton domains are NFTs in a dedicated TON DNS space. Getgems supports:

• Browsing and substring search across domains.
• Registering new names (if not taken) via the TON DNS auction mechanism.
• Listing existing domains on the secondary market.
• Binding DNS records to addresses and sites after purchase.

Worth remembering: when ownership changes through a sale, DNS records may reset if they were hard-bound. The buyer receives a “clean” domain and configures resolution themselves.

Security: common traps

1. Drainer clones. Already covered. Only getgems.io.
2. Impostor collections. A copycat with the same name as a popular collection but a slightly different contract address. Signs: no verification, low trading volume, brand-new items in the last few days. Always verify the collection address against the project’s official channels.
3. Phantom offers. Sometimes a seller is sent a “high-price offer” whose payload secretly requests a group-withdrawal approve. Only sign standard Getgems offers and verify the transaction details inside the wallet.
4. Social media. “Exclusive mint” in a Telegram channel with a link to an unknown site is almost always a drainer. A legitimate mint usually launches through the project’s own channel and official domain.
5. Faked verification. A grey checkmark is not a green checkmark. Verify.

When Getgems is not the best fit

• Active trading of upgraded TG gifts. Portals and Tonnel offer a deeper orderbook and tighter spreads on gifts. Getgems has liquidity but on average worse execution.
• High-volume jetton swaps. Getgems is an NFT marketplace; for token swaps use STON.fi or DeDust.
• Large-collection private sales. Wholesale deals more often happen OTC via Telegram escrow bots than as public listings.

Bottom line

In 2026 Getgems is the foundation of the TON NFT segment: a generalist marketplace with TON Connect onboarding, transparent fees and three asset classes under one roof. For buyers it offers a familiar shop UX; for sellers, a clean listing flow and automated settlement. The security rule for using it is the rule for the whole ecosystem: type the URL by hand (getgems.io), verify the collection address in an explorer and never sign an “approve” with an opaque payload. Within those constraints the risk is manageable and the surface area is broad.