On this page
The essentials
- UQ… and EQ… with the same middle are one wallet written two ways. The money arrives in the same place.
- The first letter tells the network what to do with a transfer if the recipient is not active yet: send it back (EQ) or leave it at the address (UQ).
- The network standard recommends giving wallets a UQ receiving address. That is usually what you see on the Receive screen.
- An address starting with k… or 0Q… is for the test network. Real GRAM is never sent there.
- The 0: format has no checksum and will not catch typos. Copy addresses, do not retype them.
The exchange gives you a deposit address, and it starts with EQ. Your wallet shows your own address, and it starts with UQ. The explorer opens a third version: a long string beginning with a zero and a colon. The first two look suspiciously alike towards the end, but not quite, and it is unclear which one is "real".
All three are. They are the same address written in different ways, much as one date can be written "4 November" or "04/11".
Unlike a date, though, the first letter of a TON address is not just decoration. It tells the network what to do with a transfer when the recipient has never used their wallet.
- 48 characters
- The length of a regular TON address such as UQ… or EQ…
- 4 statuses
- An address can have on the network: nonexistent, uninitialised, active, frozen.
The basics
One address, several ways of writing it
Every TON wallet has a raw address: a chain number (usually 0), a colon and a long hexadecimal number. That is the canonical form the blockchain itself sees.
People are shown a friendlier form: 48 characters that pack in the same chain number, the same long number, a couple of service flags and a checksum. The flags set the first letter, and the checksum changes the last few characters. That is why the UQ and EQ forms of one wallet share almost the whole middle and differ at the start and the end.
Starts with | What it is | Where you will see it |
|---|---|---|
UQ… | Friendly form, no bounce (non-bounceable) | Receiving addresses in wallets |
EQ… | Friendly form, bounce on (bounceable) | Exchange, smart contract and token addresses |
0:… | Raw form, no checksum | Explorers, technical fields |
kQ… | Bounceable, test network only | Developers' test wallets |
0Q… | Non-bounceable, test network only | Developers' test wallets |
The friendly form comes in two encodings: one with "/" and "+", the other with "_" and "-". Both are valid, and wallets have to accept both.
The bounce flag
What U and E mean
Picture a courier arriving at an address where nobody is home and the flat has not even been moved into yet. There are two options: take the parcel back to the sender or leave it by the door. The first letter of the address is the instruction for exactly that case.
- EQ — "return to sender". If the recipient cannot accept the transfer, the network sends the money back.
- UQ — "leave it by the door". The money stays at the recipient's address, even if there is no wallet there yet.
If the recipient is an ordinary wallet that is already working, there is no difference: the transfer arrives whichever form you use. The instruction only matters when nobody is home.
The TEP-2 network standard recommends giving wallets a non-bounceable receiving address, UQ, and keeping bounceable EQ addresses for smart contracts with logic of their own. That is why your wallet usually shows you UQ, while an exchange or a service often sends EQ.

The important part
When nobody is home: address statuses
A TON wallet is a smart contract, and it does not appear on the blockchain straight away. Every address has a status, visible in an explorer:
Status | What it means | What happens to a transfer |
|---|---|---|
nonexist — does not exist | Nothing has happened at this address yet | EQ: returns to the sender. UQ: stays at the address, status becomes uninit |
uninit — not initialised | There is money at the address, but the wallet is not deployed yet | EQ: returns. UQ: credited |
active | An ordinary working wallet | Arrives with either form |
frozen | Storage debt passed 0.1 GRAM, the contract is stopped | The contract does nothing until the owner restores it. Check with the recipient before sending |
A new wallet becomes active the first time it sends something. Until then it can only receive, and it is for exactly these addresses that the first letter decides the transfer's fate.
Example
Worked example: the numbers are made up
A friend has just installed a wallet and sent you the address. They have not sent anything yet, so the explorer shows the status as nonexist. You transfer 10 GRAM to them.
If you pasted the address as UQ…, the 10 GRAM stay at their address, the status becomes uninit and your friend sees the money in their wallet. Their first outgoing transfer activates the wallet.
If you took the same address in its EQ… form, the transfer comes back to you minus the network fees. The money is not lost, but your friend did not get it and you paid for the attempt.
If a transfer to a new recipient came back by itself, first check which form of the address you pasted. How to spot a returned transfer in the history is covered in "How to read a TON transaction".
Common puzzles
Why "my address" looks different in different places
Apart from UQ and EQ, there are three other reasons one person's addresses do not match. People often mistake them for a format difference.
- Different wallet versions. One phrase can open wallets of different versions, such as W5 and v4R2, and each version has its own address. These are not two forms of one address but two different addresses. More in "Wallets, addresses and recovery phrases".
- A token wallet. Everyone who holds USDT or another TON token has a separate small contract for that token, with its own address. In an explorer it is easy to mistake it for yours. How to tell them apart is in "How to check a TON jetton".
- The test network. An address starting with k… or 0Q… exists only on the test network. Mainnet apps should refuse to send to it.
Two minutes
How to check an address before sending
- Copy the whole address. Do not retype it by hand or piece it together.
- Open an explorer such as tonviewer.com and paste the address into search. The explorer shows the status, balance and other forms of the address.
- Look at the status. Active means the transfer arrives with either form. Nonexist or uninit means the recipient is new: use the UQ form their wallet shows.
- Compare the start and end of the address with what the recipient sent. If they sent UQ and the explorer shows EQ, compare the middle: it should match.
Important
The checksum catches typos, the raw format does not
The friendly form of an address carries a checksum. If one character is wrong, the wallet should warn you and refuse to send. The raw 0:… form has no such protection: a single wrong character can send money somewhere it cannot come back from. Use UQ… and EQ… addresses for transfers and leave the raw form to explorers.
Questions
Which address format should I give an exchange or a friend?
The one your wallet shows on its Receive screen. It is usually UQ, and it works for any transfer to your address.
Why does the exchange deposit address start with EQ?
That is normal: an exchange may use the bounceable form for its address. Send to the address exactly as the exchange shows it, and do not forget the comment if the deposit screen asks for one. More in "Memos in TON transfers".
Can I turn an EQ address into UQ myself?
Technically it is the same address with a different flag, and explorers show both forms. But you cannot swap the letters by hand: the checksum changes too. Take the form you need from an explorer or your wallet.
What happens if I send GRAM to a test network address?
A mainnet app should refuse the transfer. If an address starts with k or 0Q and someone asks you to send real GRAM to it, it is either a mistake or a scam.
The first letter of a TON address looks like a technical detail, and usually that is all it is. Money sent to a working wallet arrives whichever form you use.
It matters in one case: when the recipient is new and has never sent anything. Remember that one rule, check the address status in an explorer, and UQ and EQ will stop worrying you.


