Account identity
Aperture derives and validates the public account under TON rules. It does not assign a generic address from another network family.
Supported production mainnet
TON in Aperture.
A network-aware home for TON—with TON addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
TON is not just a ticker.
The Open Network uses accounts that exchange asynchronous messages. Address presentation can include network and bounceability flags even when the underlying account identity is the same.
Address format. A workchain plus account identifier, commonly encoded as a user-friendly base64url address with bounceable or non-bounceable flags.
Bounceable and non-bounceable address forms have operational meaning. Use the form Aperture produces for the selected receive or send context.
Native asset and tokens
Aperture’s current catalog labels the native wallet asset GRAM and uses TON for market-rate lookup. Jetton identity comes from the exact master contract, not from a displayed symbol.
Fees and transaction state
The native TON network asset pays computation, storage, forwarding, and message-related fees. Message delivery and resulting account transactions should be reviewed as network state, not assumed from submission.
Mainnet boundary
This catalog entry is TON mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.
Receive safely
The network is part of the address.
In Aperture, choose TON and the exact asset before copying an address or QR code. The sender, exchange, or bridge must use the same mainnet. A matching symbol, logo, or familiar-looking string does not prove compatibility.
- Confirm the receive screen says TON.
- Copy or scan the complete address; do not retype it.
- Check whether the sending service requires an additional memo, tag, or network-specific field.
- For a new route or meaningful amount, consider a small test transfer first.
- Keep the receive screen available until the sender has verified the same network.
Send deliberately
Review what the signature will authorize.
Aperture keeps asset selection, recipient validation, amount, fee review, authorization, broadcast, and finality as distinct stages. Before authorizing a transaction on TON, review the full recipient, the TON amount, and the network fee together.
Blockchain transfers may be irreversible. Aperture cannot cancel a confirmed transaction, recover an incorrect destination, or move an asset that was sent through the wrong network.
Transaction signing happens on the device. Public account data, fee requests, transaction history, and the signed transaction may reach network infrastructure; the private signing key is not part of the broadcast payload.
Verify independently
Use the right source for the right question.
Network documentationUnderstand TON protocol rules
Public block explorerInspect TON public chain state
Aperture JournalHow accounts and networks stay separate
Aperture JournalReceive crypto safely in Aperture
External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.
Aperture for iPhone and iPad
One interface. 25 mainnets. No blurred boundaries.
Use TON alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.