# "address poisoning" — X 热门讨论 (2026-09-25 03:04 UTC)
## @GookieNft (Gookie 🥷) · 09-25 02:06 · ♥50 ↻6 💬53 Good morning
it's way too late, but i keep thinking about one simple question from @Americanfort_io :
what if your payment name didn't have to become a map of your wallet?
i used to think a public crypto name and a private transaction history were impossible to separate.
share the name, and people can trace the wallet.
hide every address, and you make payments harder to identify later.
AmericanFortress is taking a different approach.
with a FortressName, you keep one @name while each payment gets a fresh one-time address.
only the sender and recipient can derive that address, and only the recipient can spend the funds.
the payment still settles on the native blockchain.
that means your public name does not simply point everyone to one fixed wallet, balance, and payment history.
and there is another part i like:
Send-to-Name™ removes the copy-paste step that makes address poisoning possible.
instead of checking seven characters and hoping you got it right,
you send to @name.
one FortressName already works across 13 integrated networks.
SafeSend™ is still in development, so i'm not treating its future privacy features as something you can use today.
for now, the live idea is already simple:
one name for you.
a fresh address for each payment.
less information tied to one public wallet.
that's a much nicer way to think about crypto payments.
would you rather share one name than keep sharing one wallet address? @NucleusCodes > 引用 @GookieNft: See y'all at Dawn
Crypto payments have one tiny habit that causes big problems: we keep reusing the same address.
Put one wallet address online and it can slowly become a public record of your balance, payments, and transaction history.
@AmericanFort_io takes a different route.
It is privacy infrastructure for crypto payments, not another chain or privacy coin.
Send-to-Name™ is live today. SafeSend™ is still in development, so this post is only about the product you can actually use now.
With a FortressName, you send to an @name instead of copying a long wallet address.
For each payment, the wallet computes a fresh one-time address.
Only the sender and recipient can derive that address, and only the recipient can spend the funds. The payment still settles normally on the native blockchain.
Your FortressName can be public without becoming a public pointer to one fixed wallet, balance, or payment history.
There is also a simple security benefit.
Address poisoning relies on people copying addresses and checking only a few characters before sending. A readable name removes that copy-paste step.
You send to @name.
Not seven characters you hope you checked correctly.
One FortressName currently works across 13 integrated networks, and AmericanFortress is designed to sit inside existing wallets rather than force users onto another chain.
And privacy here does not mean anonymity.
The person you pay still knows the payment came from your name. The goal is to stop outside observers from getting a permanent public map of your funds through one reusable address.
A crypto name should make sending easier without making your finances easier to follow.
Claim your free FortressName:
https://t.co/fThoE7j4PE
@Americanfort_io https://x.com/GookieNft/status/2103305128254054481
## @habibk79 (Habibk.HK 🍌) · 09-25 01:57 · ♥43 ↻9 💬45 Crypto users often think checking the first and last few characters is enough before sending funds.
But address poisoning and phishing can turn that habit into a costly mistake with losses reportedly reaching $50M.
That’s where @Americanfort_io takes a different approach.
Instead of relying on users to recognize long wallet addresses, its Send to-Name TM system generates a unique stealth address for every transaction, known only to the sender and recipient.
No repeated addresses. No easy address-copy traps. No guessing from matching characters.
Sometimes, better security starts by removing the risky step entirely.
........... @Americanfort_io https://x.com/habibk79/status/2103302776642228254
## @ramseyfox1 (Crypto Lord 🪙) · 09-25 00:23 · ♥29 ↻0 💬30 GM CT
Can you say it back?
Crypto still treats a 42 character address like something you can safely eyeball. That is how address poisoning works. You copy, you miss a lookalike, the funds leave.
@Americanfort_io replaces that step with a FortressName. You send to @name. Send-to-Name is live. Each payment gets a fresh one time address. Your name can be public without publishing one permanent wallet.
Private is not anonymous. You and the person you paid still know each other. Outsiders do not get your balance history. SafeSend is coming, not live. One name works across 13 networks.
Claim a free name: https://t.co/YcDg3ZBdzP https://x.com/ramseyfox1/status/2103279119035146587