# "address poisoning" — X 热门讨论 (2026-09-25 19:29 UTC)
## @bellaa_web3 (Bella🌸) · 09-25 13:35 · ♥47 ↻0 💬51 $50M gone, not from a hack, but from someone trusting their own eyes.
That's what makes address poisoning so unsettling. An attacker generates a lookalike address that starts and ends with characters nearly identical to one you've used before. You copy the wrong one without noticing, send the funds, and there's rarely any way to get them back.
The real problem is that long wallet addresses are almost impossible to verify properly every single time. Most people glance at the first few characters, maybe the last few, and move on. That one small habit is exactly what attackers count on.
With Send to Name from @Americanfort_io you send to a FortressName instead of copying a long wallet address. The wallet generates a fresh one time address for that specific payment, while the transaction still settles on the native blockchain.
There's no permanent public address tied to the name for anyone to monitor or copy.
One FortressName already works across 13 integrated networks.
What I like about this is that it doesn't ask you to be more careful, it just removes the mistake entirely. You're no longer relying on perfectly checking a long string of characters under pressure.
Sometimes the best security fix isn't a warning, it's removing the thing people keep getting wrong in the first place. https://x.com/bellaa_web3/status/2103478436144751057
## @Linhphuong111 (P.Linh♡) · 09-25 00:27 · ♥20 ↻0 💬21 Most crypto addresses were never designed with privacy in mind.
Share one address and it can become a permanent record of everything sent to it. Balances, transfers, and transaction history can all be connected through that same string.
@Americanfort_io is taking a different route.
FortressName lets you receive crypto using a simple @name instead of exposing a permanent wallet address.
When someone pays you, the wallet derives a fresh one-time address for that transaction. The payment still settles on the native blockchain, but your FortressName isn't a public pointer to one wallet forever.
That also changes the security model.
No more copying long hexadecimal addresses and checking a few characters before hitting send. By paying directly to a name, you remove much of the surface used by address-poisoning attacks.
And this isn't a separate blockchain or another privacy coin.
It's payment infrastructure designed to work with wallets and across 13 integrated networks today.
The important distinction:
Your recipient can know who paid them.
Random blockchain observers don't automatically get a permanent public payment history just by knowing your name.
Send-to-Name™ is live. SafeSend™ is still being developed.
You can claim a free FortressName and try the live payment flow yourself https://t.co/bSP5U1rpx5 https://x.com/Linhphuong111/status/2103280261941408155
## @realScamSniffer (Scam Sniffer | Web3 Anti-Scam) · 09-25 15:40 · ♥25 ↻5 💬2 🚨 Someone lost $67,572 in USDT to an address poisoning attack on Ethereum. 🎣
correct: 0xca16b299700674dda6941baa1bdeeff6d90fd94b wrong: 0xca166632d25ea74baa93a5303aa73f61e80fd94b
tx: https://t.co/a2kZrRI9wp https://t.co/GtpwVMgGzx https://x.com/realScamSniffer/status/2103510049293574343