# "address poisoning" — X 热门讨论 (2026-09-25 01:58 UTC)
## @Vanquan_titans (Van Quan) · 09-25 00:58 · ♥45 ↻1 💬51 Tired of "fat finger" mistakes wrecking your crypto payments, or worse, sending funds to a scammer's address-poisoned wallet? It's a genuine headache that makes using crypto feel way riskier than it needs to be. Most solutions either force you to ditch your current setup or they're so complex they create new problems.
That's where AmericanFortress steps in with its privacy infrastructure for payments. Think of it as a white-label SDK that seamlessly integrates into wallets and chains you already use – no need to jump ship to a new L1 or L2. Features like FortressName and Send-to-Name™ are already live across 13 chains, letting you send crypto to a simple @name instead of a messy string of characters, completely sidestepping that address poisoning risk. Plus, FortressChat is live, offering private communication channels.
What's really cool under the hood is how it works. Every transaction gets its own unique, temporary stealth address. This means no one can see your actual balance or transaction history tied to your fixed name identifier. Coming soon, SafeSend™ will use Zero-Knowledge proofs to protect the source of funds, ensuring accountability without revealing sensitive details, and importantly, without pooling user funds. And for that future-proofing vibe, they're looking into QBIP-32 and ZKPoSP for post-quantum resistance, protecting your existing assets without forcing a painful migration. @Americanfort_io is building the private payment rails we’ve been waiting for. https://x.com/Vanquan_titans/status/2103287970229014625
## @0xsantuy (Santuy) · 09-24 23:40 · ♥35 ↻1 💬38 Good morning
crypto payments still have one privacy problem people tend to overlook.
your wallet address becomes a permanent identity.
once someone has it, they can trace the balance, transactions, and counterparties connected to it. even human-readable names can make this worse if they always point back to the same wallet.
that’s the problem @Americanfort_io is trying to solve with FortressName.
Send-to-Name™ is already live. instead of sharing or copying an address, you simply send to an @name.
behind the scenes, the wallet generates a fresh one-time address for that payment while settlement still happens directly on the native chain.
the important part is what stays hidden.
the name can be public without exposing one permanent wallet, balance, or transaction history to everyone watching the chain.
it also removes the copy-paste attack surface behind address poisoning. you’re no longer comparing random characters and hoping you picked the right address.
one FortressName currently works across 13 integrated networks, with the infrastructure designed to work alongside wallets users already have.
SafeSend™ is still in development, so for now the focus is on what’s already live: private, name-based payments.
if you want to see how the live product works, you can claim a free FortressName here: https://t.co/rIHVzi1Vvp https://x.com/0xsantuy/status/2103268241724604862
## @catqpx (Catq.eth) · 09-25 00:03 · ♥35 ↻0 💬35 address poisoning exploits a simple habit:
→ attacker creates a look-alike address → sends a tiny transaction to your wallet → the fake address appears in your history → you copy it later, thinking it’s familiar → funds go to the wrong place
the uncomfortable part is that nothing was hacked. the user simply copied the wrong string.
@Americanfort_io approaches the problem differently with FortressName.
instead of copying a long hex address, you send to a human readable @name. behind that name, a fresh address can be generated for the payment, so there isn't one permanent address sitting in your history waiting to be mistaken for the real one.
it’s less about asking users to “check more carefully” and more about removing the part of the workflow attackers can manipulate.
the interesting security improvement here is at the UX layer, not just the cryptography.
This post only shares project information from a personal perspective and is not investment advice. https://x.com/catqpx/status/2103274141306794053
## @ramseyfox1 (Crypto Lord 🪙) · 09-24 23:52 · ♥20 ↻0 💬17 GM CT
Can I get it back?
Address poisoning doesn’t need your seed. It needs you to copy a look-alike address.
Send-to-Name™ cuts that attack surface: you type @ name, the wallet generates a one-time receiving address, and the FortressName does not publicly resolve to one fixed wallet.
Your name is public. Your money isn’t. Live today across 13 integrated networks. SafeSend™ is still in development.
Claim a free FortressName: https://t.co/YcDg3ZBdzP @Americanfort_io https://x.com/ramseyfox1/status/2103271276668137875