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

Jetton Master

Master contract of a jetton token on TON. Describes the token (name, symbol, supply), deploys per-holder jetton wallets, and serves discovery requests.

Aliases: jetton minter, master jetton

Jetton Master is the master contract of any jetton token on TON. It carries the token’s metadata (name, symbol, decimals, icon, total supply) and the mint/burn logic. In TEP-74 each holder gets their own wallet contract, and the master coordinates them.

What it stores

  • Token metadata. Name, symbol, decimals, image URL. Metadata often lives in an external cell or off-chain JSON URL.
  • Total supply.
  • Admin / owner address. The party allowed to mint new tokens or update metadata.
  • Jetton-wallet code. The reference code from which each holder’s wallet contract is deployed.

What it does

The master contract barely participates in ordinary transfers — those go directly between jetton-wallets. The master is involved in three cases:

  1. Mint. Owner sends a mint message; master deploys the receiver’s wallet and credits tokens to it.
  2. Discovery. When something needs to learn another holder’s wallet address, it sends provide_wallet_address and gets a reply.
  3. Metadata change. Owner sends change_content; master updates the metadata pointer.

Address and identification

The jetton-master address is fixed — it is “the token’s contract address”. In wallet UIs, explorers, and DEX aggregators a jetton is identified by its master address. When t.me/wallet shows USDT, under the hood that’s a specific master address on basechain.

Security

The master concentrates the riskiest logic: admin keys, mint capability, code mutability. When evaluating a jetton, people check:

  • Who the owner is — a centralised address or a DAO.
  • Whether mint has been renounced.
  • Whether the code matches the reference TEP-74 implementation, without hidden backdoors.

Related terms