# "address poisoning" — X 热门讨论 (2026-09-27 09:44 UTC)
## @YaldaMasoudi (itsYalda) · 09-27 08:58 · ♥27 ↻0 💬31 ☀️GM X family ☀️
Crypto trained users to verify an address by checking the first and last few characters
That habit is exactly what address poisoning exploits
A readable name can remove the copy paste problem. but a static alias creates another one: a permanent public map from identity to wallet
The more interesting part of @Americanfort_io ’s Send to Name™ design is the separation between identity and destination
You share one reusable FortressName. In compatible transaction flows, it can resolve to a transaction specific receiving address instead of publishing one permanent name to wallet directory
The UX improvement isn’t just making an address easier to read
It’s making the same address unnecessary to reuse
A readable identity shouldn’t become a readable balance sheet https://x.com/YaldaMasoudi/status/2104133474152042786
## @zyro_eth (ᴢʏʀᴏ) · 09-27 05:07 · ♥28 ↻0 💬25 One thing about crypto that still feels unnecessarily risky is simply sending a payment.
Long wallet addresses are easy to copy, paste, and get wrong, which is where issues like address poisoning can happen.
@Americanfort_io approaches this with Send-to-Name™.
Instead of using a long wallet address, you can send to a readable FortressName while a fresh one-time address is generated for each payment.
Your FortressName doesn’t publicly expose one permanent wallet, balance, or payment history.
The payment still settles on the native blockchain, and one FortressName works across 13 integrated networks.
@Americanfort_io is making the payment experience easier to use without making your on-chain activity a permanent public profile.
Claim a free FortressName: https://t.co/gw0HsMf7sh https://x.com/zyro_eth/status/2104075389995810817