Friendly Address
Human-readable TON address in base64 (EQ.../UQ...) with CRC and flags. The form users see in wallets and on websites.
Aliases: base64 address, user-facing address
Friendly Address is the human-readable representation of a TON contract address: a compact 48-character base64 string starting with EQ, UQ, kQ, or 0Q. It encodes everything a wallet needs to send safely — workchain, contract hash, bounce flag, testnet flag, and a CRC checksum.
Structure
The leading two letters carry the flags:
| Prefix | Bounce | Testnet |
|---|---|---|
EQ… | yes | no |
UQ… | no | no |
kQ… | yes | yes |
0Q… | no | yes |
After the prefix come base64 characters encoding the workchain (1 byte), the hash (32 bytes), and CRC16 (2 bytes). Mistype any character and the CRC fails — the wallet refuses to send. This is the main advantage over raw form.
EQ vs UQ
EQ means “bounceable” — the address has the bounce flag on. Safe for contract calls, but if the destination is a wallet that hasn’t been deployed yet, a bounce burns gas needlessly.
UQ means “non-bounceable”: the address is marked safe to send to even if no contract exists there yet. Wallets automatically display fresh addresses in UQ form and existing ones in EQ.
Where it’s used
Everywhere a human reads an address: in wallets, on partner websites, in widgets, in QR codes. Inside SDKs and contract code it’s almost always converted to raw before use.
The full spec lives in TEP-2: github.com/ton-blockchain/TEPs. All major wallets and explorers support the format.