Address formats, transfer mistakes, lookalikes, and triple-check habits.
Bounceable, raw, and why two strings exist
TON UIs often show one account as bounceable, non-bounceable, and raw. That is not two recipients and not “old vs new wallet”. Different encodings of the same account. Beginners edit characters by hand “to match a tutorial” and send irreversible funds elsewhere.
Copy the form the recipient screen or exchange asks for. Don’t convert addresses via random comment-section sites. A QR from the official client is usually safer than typing by eye.
Mid-string typos are classic
Addresses are long; eyes tire. A middle typo is easy to miss when rushing. After paste, check the first and last characters. For large size, open the address in an explorer and confirm it exists and looks expected.
Chat screenshots are easy to fake at the tail. “Here’s the address, send” in comments is a weak source. New recipient = dust first, then the real amount. Known recipient but new format/network = dust again.
One-letter lookalikes
Attackers craft addresses and .ton names almost like the brand. “Looks familiar” is not enough — compare character-by-character to the official pin. Mint-season urgency increases blindness: “three minutes left” is a reason to slow down, not speed up.
Confirm a large recipient on a second already-trusted channel. Don’t take advice from the same chat that dropped the link.
Exchange, memo, and network
Without a memo/tag, a transfer can succeed on-chain and fail venue accounting. Re-read withdrawal rules every time — they change when you rush. Never mix deposit addresses across venues. Wrong network in the selector is its own class of pain, not a detail.
A .ton name instead of a raw address
Sending to a name is convenient. DNS can change without notifying you. “We always used brand.ton” is weak protection against name hijacks. For large size, check the current resolve or use an on-chain address from a verified place. If you got both a name and an address — they must match now. Mismatch means stop.
A personal verification ritual
1. Copy button or QR — not typing from a chat scrap.
2. Check start and end after paste.
3. Dust → confirm → size.
4. Read memo/network aloud.
5. Keep experimental balance separate from what you’d miss.
TON Web Search helps find a service entry; you still verify the address. An index card is not insurance against a typo.
---
An everyday scene where “address” breaks
Typical scene: chat open, “TON addresses: bounceable, raw, and why you copy slowly” pops up, hand already reaching for Connect. In that moment you need a pause for two questions — source and wallet — not another tab.
Task blurb: Address formats, transfer mistakes, lookalikes, and triple-check habits. Not an exchange checklist and not an X promise. A boundary inside which you move slowly.
If a Mini App is nearby: Allow and signature are different layers. You can close the app without owing the season.
Technical junctions around “address”
The junction .ton ↔ bot ↔ https ↔ wallet is where lookalikes thrive. Verify the final username/domain, not only the first Open button.
Exchange ↔ on-chain junction: memo, network, address form. Dust is mandatory on a new route even if you withdrew last year.
Permissions junction: approve/allowance after “address” experiments gets forgotten. Scheduled spender reviews save nerves later.
Social pressure and “address”
Referrals, leaderboards, “I already joined”, a DM after you asked in chat — pressure. It doesn’t add safety. You can answer friends tomorrow. The network’s answer after Confirm is already fact.
Fake support loves “address” because people search it while anxious. Official support route — only from the pin. Otherwise block.
A mini-protocol inside an experimental limit (“address”)
Set a limit. Move it to an experimental wallet. Anything above doesn’t join “address” today. This simple rule beats complex “optimization” strategies.
Run: reference → favorite → preview → dust → log. Then either stop or size inside the limit. No third option of “a tiny bit from main”.
What to keep from “TON addresses: bounceable, raw, and why you copy slowly”
Not a quote — a habit. Source beats banner. Preview beats headline. Dust beats FOMO. Catalog is a map. Keys stay offline. If clarity is missing, closing the tab is cheaper than “we’ll read the tx later”.
In a week, revisit favorites and approvals. Seasons change storefronts; hygiene stays. Then “address” stops being a surprise and becomes manageable routine.