# "address poisoning" — X 热门讨论 (2026-09-24 19:58 UTC)
## @mdhafiz001987 (Md Hafiz) · 09-24 19:21 · ♥29 ↻1 💬32 Good night.
Crypto still asks people to treat a wallet address like a password.
Copy forty-two characters. Check the first four. Check the last four. Hope the clipboard was not swapped. Address poisoning works because the payment model is a reusable public string.
AmericanFortress is privacy infrastructure for crypto payments, not a privacy coin and not a new chain. The live product is FortressName plus Send-to-Name™.
You send to @name. The wallet computes a fresh one-time address for that payment. Only the sender and recipient can derive it. Only the recipient can spend it. Settlement stays on the native blockchain.
A FortressName is shareable. The money behind it is not a public directory. The name does not resolve to one permanent wallet, a public balance, or a visible payment history. One name works across 13 integrated networks today.
That is what is live. FortressChat is live too. SafeSend™ is in development. It is designed to shield sender-side balance and source-of-funds information with zero-knowledge proofs, without pooling funds, while the recipient still sees the payment came from @you.
Claim a free lifetime .free FortressName: https://t.co/q9PhSf1dKp
@Americanfort_io
YOUR MONEY. YOUR NAME. NOBODY ELSE'S BUSINESS. https://x.com/mdhafiz001987/status/2103203154951299116
## @MuriscoOfficial (MURISCO) · 09-24 19:31 · ♥24 ↻0 💬26 one of the easiest ways to lose crypto is still one of the simplest things we do:
copy an address, paste it, check a few characters, then hit send.
address poisoning takes advantage of that habit by using lookalike addresses that can appear similar to ones you’ve used before.
@AmericanFort_io takes a different approach with send-to-name™.
instead of sending to a long wallet address, you send to a readable fortressname like @ name. the wallet then generates a fresh one-time address for that payment.
your fortressname doesn’t publicly expose one permanent wallet, balance, or payment history.
less copy-pasting. less reliance on checking the first and last characters. a cleaner way to send crypto.
if you want to explore the system, you can get your fortressname here:
https://t.co/NBQIfdspLh https://x.com/MuriscoOfficial/status/2103205645662994508
## @0x_zozo (ZOZO) · 09-24 19:28 · ♥28 ↻0 💬17 A crypto payment can fail before the transaction even reaches the blockchain
The weak point is often the address itself
Long wallet addresses create room for copy paste mistakes and address poisoning attacks where a look alike address can appear in transaction history and trick someone into sending funds to the wrong destination
@Americanfort_io takes a different approach with Send to Name
Instead of sending to a permanent wallet address, the sender uses a readable FortressName such as @name. The wallet then computes a fresh one time address for that payment
That means the FortressName does not publicly expose one fixed wallet, balance or complete payment history
The payment still settles on the native blockchain
One name works across 13 integrated networks today
And this is not just a naming layer. AmericanFortress is building privacy infrastructure directly into existing wallets through an SDK
Claim a free lifetime .free FortressName: https://t.co/EMfy6MFCz6 https://x.com/0x_zozo/status/2103204969033949501
## @deathv1per (Death Viper ⟠) · 09-24 19:32 · ♥21 ↻0 💬18 Crypto payments have a simple problem that is easy to overlook: the wallet address itself can become a security and privacy risk.
@Americanfort_io approaches this differently with FortressName and Send to Name.
Instead of copying a long address, users can send crypto to a human readable . The wallet generates a fresh one time address for each payment, while the payment still settles normally on the native blockchain.
That changes more than the user experience.
A fixed public wallet can reveal balances, transaction history, and create opportunities for address poisoning attacks. A FortressName is designed so that the name does not publicly expose one permanent wallet address.
The bigger idea is making crypto payments easier without forcing users to give up financial privacy.
And the infrastructure is designed to live inside existing wallets, chains, custodians, and exchanges through an SDK rather than creating another isolated destination.
With one FortressName working across 13 integrated networks today, the focus is not just privacy as a concept, but making safer and more private payments part of the crypto experience people already use.
SafeSend is also being developed to add sender side privacy through zero knowledge proofs, selective disclosure, and proof of source of funds, while keeping the payment accountable to the recipient. It is not live yet.
That combination of usability, privacy, security, and compatibility with existing infrastructure is what makes the approach interesting.
Claim a free FortressName: https://t.co/W8Jpjb4tAO https://x.com/deathv1per/status/2103205851829842258