pTON

pTON (proxy TON) is a jetton that represents native Toncoin inside DeFi protocols. The best-known consumer is STON.fi, but the idea is general: to make AMM and routing logic uniform, native TON is wrapped into a jetton with the standard TEP-74 interface.

Why it exists

Toncoin is the network’s native asset. It is not a jetton: it has a different accounting model, a different message format, and different fee handling. Jettons follow the TEP-74 standard with jetton-master and jetton-wallet contracts and a predictable transfer interface.

When a DEX builds a pool of the form TOKEN_A / TOKEN_B, it wants both legs to look the same. If one leg is native TON, the protocol has to branch every code path: “if this is TON, send a native message, otherwise send a jetton transfer.” That doubles router complexity, expands the bug surface, and breaks the abstraction.

The fix is to wrap TON in a jetton. The user sends native TON into a wrapper contract, the contract mints an equal amount of pTON, and from then on the AMM works with a regular jetton. On the way out, the user redeems pTON back into native TON.

Where you meet it

• STON.fi — the flagship TON AMM, historically uses pTON for internal routing. Users rarely see it directly: the frontend shows a TON → JETTON swap while the router quietly wraps native TON into pTON behind the scenes.
• Other AMMs and aggregators apply similar patterns, sometimes under a different name or inside their own contracts.

For the end user, pTON is mostly transparent. Swaps and pools are shown in terms of TON and USDT; the wrapping happens inside router contracts.

Parameters

• 1:1 with TON. pTON is minted at a strict 1:1 rate against native TON when you enter and burned 1:1 when you exit. Unlike a liquid-staking token, pTON does not accrue yield — it is purely a technical wrapper.
• Do not confuse with stTON / wstTON or tsTON. Those are LSTs with a slowly drifting redemption rate. pTON is not. If a frontend offers you “wrap your TON and earn interest,” it is something else, not pTON.
• Contract address. Always check the pTON jetton master address against the official documentation of the protocol that issued it. Lookalike jettons with similar tickers do show up on TON.

Risks and notes

• Contract risk. pTON lives in a smart contract; a compromise of that contract could trap or lose the wrapped TON. Major pTON deployments have been audited, but audits are not guarantees.
• Not for long-term holding. pTON is designed as a short-lived in-route token. Holding a large position in pTON for long periods makes no sense — keep native TON or an LST instead.
• Standalone pTON pools are usually a red flag. If you see an exotic pool like pTON / something_obscure, verify it is not a copy-cat token.

pTON is a typical DeFi adapter primitive: it adds a thin layer of complexity at the edges to dramatically simplify the AMM and router code in the middle.