# "address poisoning" — X 热门讨论 (2026-09-25 03:37 UTC)
## @OGFIGO (OG FIGO 🚢) · 09-24 19:16 · ♥262 ↻0 💬255 Crypto still treats a payment address like a public mailbox.
You publish one string. Anyone who pays you reuses it. Explorers then attach a balance and a history to that string. Naming systems that resolve to one fixed wallet make that worse, because the readable name becomes a pointer to the same mailbox forever.
@Americanfort_io is built around a different job. It is privacy infrastructure for crypto payments, not a new chain and not a privacy coin. Send-to-Name™ is live. SafeSend™ is still in development, so this is only about what you can use now.
The live product is a FortressName. You send to an @name instead of pasting a long address. The wallet computes a fresh one-time address for that payment. Only the sender and the recipient can derive it, and only the recipient can spend it. Settlement still happens on the native chain.
The name does not publicly expose a fixed wallet, a balance, or a payment history. That last part is the split people miss. The name can be public. The money path is not supposed to be a permanent lookup.
It also cuts a real attack. Address poisoning works because people check the first and last characters of a copied string. A look-alike address with the same seven characters has already drained large sums. Sending to a name removes the copy-paste surface that attack needs. You are not matching hex. You are paying @name.
One FortressName works across 13 integrated networks today. It ships as infrastructure meant to sit inside wallets people already use, not as another destination app you have to migrate into.
Private here does not mean the other person cannot see who paid them. The recipient still knows the payment came from your name. Outside observers do not get a public index of your funds from the name itself.
Claim a free FortressName if you want to test the live path:
https://t.co/aCfoPTFgLq
@Americanfort_io https://x.com/OGFIGO/status/2103202053233189185
## @jabosiswanto94 (Jabo) · 09-25 02:51 · ♥43 ↻1 💬42 gm crypto bros 🙌 the way address poisoning works is deceptively simple, and seeing @Americanfort_io tackle the root cause puts the blame where it belongs.
scammers run bots that watch high volume wallets 24/7
the moment you send a transaction, the bot generates a vanity address sharing the exact first and last characters of your recipient.
then it sends dust to your wallet so that fake address sits right at the top of your transaction history.
they count on human habit.
someone opens their wallet, copies the top address from recent history, glances at the four outer characters, and hits send.
$50m gone in a single click.
americanfortress cuts off that attack surface with Send-to-Name™
you send to a readable @name/handle instead of pulling hex strings from your clipboard.
the wallet computes a fresh one-time stealth address for each payment behind the scenes.
attackers cannot poison your history because there is never a static public address to clone.
settlement happens natively across 13 integrated chains, without revealing the recipient's balance or portfolio to the world.
hackers exploit our reliance on copy-paste. taking away the copy-paste step takes away the scam.
set up my handle on https://t.co/lvauW6cDjG earlier, definitely worth locking in your name. > 引用 @jabosiswanto94: remember that whale who lost $50m because an address shared the same first and last few characters? i've been thinking about how @Americanfort_io handles that whole problem
a scammer generated a look-alike address, sent a tiny transfer to his wallet, and waited
the victim copied the address straight from his recent tx history, glanced at the ends, and sent everything to the wrong person
checking four characters at each end has always been a broken security routine
americanfortress handles this with Send-to-Name™
instead of dealing with raw hex strings, you send directly to an @name
every time you make a transfer, the wallet derives a fresh one-time stealth address on the native chain
only the sender and receiver can derive and spend it
outside observers on the explorer only see a normal transfer going to a clean, fresh address
your fortress name never attaches your total balance or full payment history to one permanent public wallet
and it is already live across 13 chains
giving people a readable name while keeping payments private fixes the real root cause
grabbed my handle earlier on https://t.co/lvauW6cDjG before someone else took it https://x.com/jabosiswanto94/status/2103316466657530267
## @0xEhiya (Ehiya 🍌) · 09-25 02:52 · ♥32 ↻7 💬31 Good Morning X!
i used to think crypto privacy was mostly about hiding the transaction.
then i looked closer at @Americanfort_io .
the bigger problem is the address itself.
a normal wallet address can become a permanent public mailbox. reuse it enough and people can connect the dots between your balance and payment history.
FortressName takes a different approach.
i send to an @name, and the wallet generates a fresh one-time address for that payment.
the name stays public.
the wallet behind each payment does not become one permanent public pointer.
that also makes sense to me from a security angle.
address poisoning depends on making me copy and compare a long string of characters. sending to an @name removes that copy-paste step.
i checked the live product myself, and Send-to-Name™ is already usable across 13 integrated networks.
SafeSend™ is still in development, so i’m only talking about what actually works today.
that’s the part i find interesting:
privacy here isn’t another chain i have to move to.
it’s infrastructure sitting on top of the chains i already use.
if you want to see the live flow, you can claim a free FortressName:
https://t.co/AGn7JGRL6F
@Americanfort_io https://x.com/0xEhiya/status/2103316724187840530