Using emoji names

The NFT layer

Every name is a TEP-62 NFT. The NFT is the ownership object itself, not a receipt for it — so any standard TON marketplace can trade a name with no special support.

Every emoji name is minted as a TEP-62 NFT. That is not a certificate that points at the real ownership record somewhere else — the NFT is the ownership object. Transfer it and the name has moved.

Contract addresses

These are the canonical mainnet contracts. Anything claiming to be Emojiverse at a different address is not us.

RegistrarEQChShhe…wLTmGUq0

NFT collectionEQCgVvls…rAJEmoji

The collection address was mined for its vanity suffix — it ends in Emoji — and every item address derives from it. Full addresses, copy-ready:

Registrar:      EQChShhe8ylCH3lJ4QnP6HugcPYx1IjoqeTw8IOPwLTmGUq0
NFT collection: EQCgVvls0cAemQI5KuWlr-jyfoXenhxoiKzFotSlrAJEmoji

Transferability

A name transfers like any other TON NFT — a standard transfer message to the item contract. No allowlist, no lockup, no protocol-side veto.

What makes it a name rather than a picture is what happens alongside the transfer:

The item records the new owner and emits an ownership-sync message.
The collection authenticates it by re-deriving the item's address from the name hash. A rogue contract deployed anywhere else fails this check, so only the genuine item for that name can move it.
The registrar updates the registry, and pushes the new owner out to every registered resolver.
The resolver wipes the records. This is the important one — see below.

Wipe-on-transfer

When a name changes hands, its resolver records are erased.

This closes the failure that makes name markets dangerous: you buy 🚀🌙, the NFT lands in your wallet, and the name goes on resolving to the seller's address — so anyone who sends funds to the name sends them to the person who just sold it.

It cannot happen here. A sold name resolves to nothing until the new owner sets a record. That is stricter than ENS, and the strictness is the feature.

Renewal does not wipe Only a change of owner clears records. Renewing a name — including a renewal paid by someone else — leaves your records exactly as they are.

Secondary market

Names trade on standard TON NFT marketplaces. GetGems is the primary venue.

→ The Emojiverse collection on GetGems

Verify before you buy Check that any listing belongs to the canonical collection address above — …rAJEmoji — before you bid. A listing under any other collection is not an Emojiverse name.

Royalty is set on the collection following TEP-66, so marketplaces read and honour it automatically.

What a marketplace sees

Field	Value
`index`	The name hash — deterministic, so an item address is derivable from the name alone
`collection_address`	The Emojiverse collection
`owner_address`	Current holder
`individual_content`	The per-item metadata suffix, concatenated onto the collection's base URI
`get_tier`	The pricing tier (1 = Mythic … 7 = Common), readable directly from the item

Tier being on the item matters for anyone building a marketplace view: rarity is one call to the NFT, with no second lookup against the registrar.

A name is a lease, and the NFT does not say so loudly The item is a plain TEP-62 NFT. It does not implement the .ton DNS-item read interface, so a domain-aware marketplace has no standard way to discover that there is a term attached, and it will render the name as an ordinary collectible.

If you are buying on a secondary market, check expiresAt(nameHash) on the registrar before you bid. A name three days from the end of its grace period looks identical to a freshly renewed one in a marketplace listing. Improving this signalling is on the roadmap and is tracked as an open item in the audit register.

Repair path

If a name's registry owner and NFT owner ever disagree — a message dropped, a partial sequence — anyone can send ResyncOwner to the item, and it re-pushes the truth to the registrar and resolvers. It can only ever re-assert the item's actual owner, so it is safe to expose as a public "fix my name" button.