# "address poisoning" — X 热门讨论 (2026-09-25 08:32 UTC)
## @AkadexCrypto (Akadex ⚓) · 09-25 04:53 · ♥344 ↻34 💬261 Good Morning Creators ☕
Starting up this blessed Friday with a new project that I really love the utility/usecases they brought to us, @Americanfort_io is live with a 15k in USDT to top 100 on nucleus contribution leaderboard.
$50M lost to seven matching characters.
That says a lot about how fragile crypto payments can be.
Address poisoning works because we copy long wallet addresses, then check a few characters before sending. Attackers can create lookalike addresses and place them in your transaction history.
AmericanFortress takes a different approach with FortressName.
Instead of copying: 0x8F...29A
you send to: @name
The system resolves the payment to a fresh address for that transaction, removing the copy-paste step and avoiding one permanent receiving address.
So the security model becomes much simpler: Readable name → fresh address → payment
You shouldn't need to memorize seven characters to know you are sending to the right place.
Send to the name, not the hex.
Pivot now to @Americanfort_io 🫵 https://x.com/AkadexCrypto/status/2103347175174308110
## @Realboybr (Realboy) · 09-25 04:58 · ♥253 ↻2 💬272 Public blockchains solved settlement. They didn’t solve exposure.
Every wallet address you publish becomes a permanent lookup. Balance visible. Transaction history visible. Every counterparty connected. A naming system that resolves to one fixed wallet makes it worse the readable name becomes a pointer to the same public record forever.
@Americanfort_io is built around fixing that specific problem. Send-to-Name is live now. You pay @name instead of pasting a long address. The wallet computes a fresh one-time stealth address for that payment only sender and recipient can derive it, only recipient can spend from it. Settlement happens on the native chain. The name doesn’t expose a fixed wallet, balance, or history to outside observers.
That distinction matters. The name can be public. The money path isn’t a permanent lookup.
It also removes a real attack surface. Address poisoning works because people check the first and last characters of a copied string a look-alike with matching characters has drained large sums. Sending to a name eliminates the copy-paste step that attack requires entirely.
Zero-knowledge proofs for proving what needs to be proven without handing over the full dataset. Quantum resistance in the roadmap. ZK-PoSP for proving control without exposing the original seed.
Privacy from observers. Proof between parties. Compliance without unnecessary exposure. One FortressName working across 13 integrated networks.
Privacy built into the identity layer before the transaction not patched in after.
https://t.co/hnAdlcRybB
@Americanfort_io https://x.com/Realboybr/status/2103348328100483195
## @Aliba_79 (Aliba) · 09-25 08:09 · ♥41 ↻1 💬39 I used to think crypto privacy was only for people with something to hide
Then I noticed the contradiction . We redact bank statements . We paste wallet addresses into bios , invoices , and group chats Anyone can look up a balance , a history , and every counterparty . Not because we want to flex Because public chains work that way , and the UX still asks us to copy a hex string and hope we didn’t get poisoned
That’s when @Americanfort_io became more than another privacy by default line
FortressName is not a nickname for your wallet Most readable names still resolve to one fixed address Easier than hex Same open window into the wallet FortressName splits the layers : the @-name is what you share Underneath , it is not supposed to be one permanent public wallet glued to that name
Send-to-Name is the layer that is actually usable now . You type an @-name The wallet computes a one-time address for that sender–recipient pair On-chain observers see a fresh address A compatible recipient wallet can still show who paid No pool . No mixer Phishing and address poisoning live on a simple fact : people reuse addresses and trust the clipboard Remove the hex-paste step and half those attacks lose their favorite door
SafeSend is the part campaigns usually get wrong It is not a cute hide button The design is a ZK layer on the transaction itself : less public exposure of balances and source of funds , without pooling money , without a viewing-key back door You choose what to disclose , to whom , and when Their site frames it as a one-toggle Untraceable Quantum Send Credit where it’s due : this layer is still being built , and the wallet is in beta Don’t write it as if every chain already has the switch on
Three layers , three different holes A public name without one-time addresses becomes a map of the wallet One-time addresses without a sender-side layer still leak the tap Hide everything with no selective disclosure and counterparties can’t verify anything That’s the bind the industry keeps hitting
I’m not selling a finished product . macOS beta . SafeSend is roadmap Quantum-resistant work is research , not a spell The product question is still the right one : sending money should feel like sending money , not like publishing a financial map
Which one are you actually willing to live with ?
A. Public @-name , wallet not on display B. Hide everything , even from the counterparty C. Public chain , accept being watched
Reply with a letter . Mechanism : https://t.co/expH2a0YjX
claim a name : https://t.co/pbdABG1VtV > 引用 @Americanfort_io: █▀▀▀▀▀▀▀█ █ 🛡️ █ █▄▄▄▄▄▄▄█ Public Names. Private Transactions.
With our Send-to-Name™ tech, every transaction automatically generates a unique stealth address known ONLY to the sender and recipient.
No address reuse. No address poisoning. No phishing. The math does the heavy lifting. You just enjoy the privacy. https://x.com/Aliba_79/status/2103396538277855478
## @webxiv (web) · 09-24 20:24 · ♥25 ↻2 💬23 Copying a wallet address is still one of the easiest ways to lose money in crypto.
You can check the first few characters. You can check the last few. And still miss a look-alike address.
That’s why I like the idea behind @Americanfort_io Send-to-Name™.
Instead of copying a long address, you send to a Fortress Name.
The wallet generates a fresh one-time address for that payment, while the recipient’s name doesn’t publicly expose a fixed wallet, balance, or payment history.
Less copy-pasting. Less room for address poisoning. https://x.com/webxiv/status/2103218950028816842