# "address poisoning" — X 热门讨论 (2026-09-24 21:04 UTC)
## @AzadWeb3 (Azad) · 09-24 20:03 · ♥109 ↻2 💬119 Good night everyone
Crypto payments still have a simple privacy problem: one address can become a permanent record of everything sent to it.
@Americanfort_io approaches that differently with Send-to-Name™.
You can send to a FortressName like @name instead of pasting a long wallet address. The wallet generates a fresh one-time address for that payment, while settlement still happens on the native chain.
The name stays public, but it does not point outsiders to a fixed wallet, balance or payment history.
There is a practical benefit too. Paying a name removes the copy-paste step that makes address-poisoning attacks possible.
One FortressName currently works across 13 integrated networks, and the system is designed to work inside wallets rather than forcing users into another app.
Send-to-Name™ is live. SafeSend™ is still in development.
If you want to test the live path, you can claim a free FortressName:
https://t.co/cmVybfK1WJ https://x.com/AzadWeb3/status/2103213646876979587
## @0xcatuchiha (0x) · 09-24 19:35 · ♥29 ↻2 💬33 one wrong copy paste can send your crypto to the wrong wallet.
that’s one reason address poisoning remains a problem in crypto.
attackers can create look alike addresses that resemble ones you’ve used before, hoping you copy the wrong address.
@Americanfort_io takes a different approach with fortressname.
instead of copying a long wallet address, you can send to an @ name.
behind the scenes, the wallet generates a fresh one time address for that payment.
only the sender and recipient can derive that address, while only the recipient can spend the funds.
the payment still settles normally on the native blockchain.
there’s another part i found interesting.
a fortressname doesn’t publicly expose one fixed wallet, balance or payment history.
so the readable name makes the payment easier to address without simply attaching your identity to one permanent wallet.
that’s the part worth paying attention to.
americanfortress isn’t just putting a name on a wallet address. it changes how the payment is addressed underneath.
fortressname and send to name are live.
safesend is still in development, so i wouldn’t treat it as a live feature yet.
you can claim a free fortressname:
https://t.co/iMk78z60l7 https://x.com/0xcatuchiha/status/2103206811662991522
## @elcord0 (eL Cord) · 09-24 19:29 · ♥21 ↻3 💬23 $50M lost to seven matching characters.
That’s the problem with how we send crypto today. We copy long addresses, check the first and last few characters, and hope we didn't fall for a look alike address.
Address poisoning exploits exactly that habit.
AmericanFortress takes a different approach with FortressName + Send to Name.
Instead of copying:
"0x8F...92A"
you send to:
"@name"
The wallet generates a fresh one time address for each payment, so you're not relying on manually checking a long address, and the recipient doesn't have to expose one permanent receiving address.
That distinction matters.
A normal ENS style name can point back to the same fixed wallet. @Americanfort_io Name is designed around fresh payment addresses, helping reduce public linkage between payments, balances and transaction history.
Then there's SafeSend™, which is still in development.
It is designed to protect sender side financial information using zero knowledge proofs without pooling or mixing funds. It aims to support proof of source of funds and selective disclosure when information actually needs to be revealed.
That's also why AmericanFortress talks about privacy rather than blanket anonymity.
The recipient can still know the payment came from "@you", while an outside observer doesn't automatically get the same financial picture.
And the bigger infrastructure matters too: QBIP-32 / ZKPoSP for its post quantum direction, plus an SDK that lets wallets and applications integrate the technology instead of forcing users into another ecosystem.
For me, the interesting question isn't “is crypto private?”
It's:
How much information should a payment expose, and how much of the security burden should users have to handle themselves?
@Americanfort_io is trying to solve both at the payment layer.
Try Send to Name and see what the blockchain actually reveals. https://x.com/elcord0/status/2103205280536207534
## @0xMek_ (mek0) · 09-24 19:26 · ♥20 ↻0 💬17 50 million dollars lost to seven matching characters.
@Americanfort_io built a fix for this. here's the problem first
address poisoning: an attacker creates a wallet address that matches the first and last characters of one you use, then sends you a tiny "dust" transaction so it shows up in your history. next time you copy an address from there, you copy theirs.
the problem isn't careless users. a 42-character random string is a bad way to address money. nobody verifies it, we just skim it.
@Americanfort_io send-to-name™ removes that step completely:
→ you send to an @name, not a wallet address → your wallet computes a fresh one-time address for every payment → only you and the recipient can derive it, only the recipient can spend it → the payment still settles normally on the native chain bonus: a fortressname doesn't publicly point to one fixed wallet, so sharing your name doesn't expose your balance or payment history. live today across 13 integrated networks. https://x.com/0xMek_/status/2103204386851668423
## @waahid99 (Nishat.eth 👀) · 09-24 19:22 · ♥21 ↻2 💬4 Crypto payments have a simple privacy problem that most people overlook.
Your wallet address can become a permanent record of where money is received, how much sits there, and what transactions happened around it.
@Americanfort_io takes a different approach with FortressName.
Instead of sharing the same wallet address every time, you share an name. Each payment generates a fresh one-time address behind the scenes while settlement still happens on the native network.
So your public name does not become a permanent pointer to one wallet.
There is another useful benefit too.
Sending to an name removes the need to copy and compare long hexadecimal addresses, reducing the surface for address-poisoning attacks.
Send-to-Name™ is already live across 13 integrated networks.
No new chain. No separate privacy coin. Just a different way to handle crypto payments.
https://t.co/lc5QlYPF45 @Americanfort_io https://x.com/waahid99/status/2103203355862712539