# "address poisoning" — X 热门讨论 (2026-09-26 06:56 UTC)

## @tausif_khan099 (Tausif) · 09-26 04:32 · ♥102 ↻0 💬128 one thing I like about @Americanfort_io is that it separates your public identity from ur transaction history.

with send to name, u can share one public name, while every payment creates a unique stealth address between the sender and recipient.

that means: > no address reuse > less wallet exposure > better protection from phishing and address poisoning

the part I find most interesting is Provenance Proofs.

a wallet can prove related addresses come from the same hidden origin without revealing your seed phrase, private keys, or complete wallet history.

built with zero knowledge, post-quantum security and user-controlled linkability, it feels like a practical approach to privacy.

be public by name. stay private by transaction https://x.com/tausif_khan099/status/2103704331870666811

## @M_zekks (Master Zeks👑) · 09-26 04:46 · ♥44 ↻9 💬34 Good Morning, my desired FortressName is Anonymous Tiger

Please don’t ask me why I chose it

What you should be bothered about is the lore behind a FortressName; I’ll help you out

~It all starts from the vision powering @Americanfort_io, a privacy infrastructure for crypto payments

~The goal is to allow you send crypto to a readable “name” rather than a long wallet address

That way, issues like address poisoning becomes a thing of the past when dealing with AmericanFortress

In essence, AmericanFortress is a 3 way process. Get a name, send money to a fellow name, get maximum privacy while at it

Ce Fini > 引用 @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/M_zekks/status/2103707825952243758

## @MadMagicSOL (Magic Hunter) · 09-26 04:00 · ♥20 ↻0 💬20 Address poisoning only works because we trust our eyes to verify long wallet addresses. It is a massive user experience failure.

That is what @Americanfort_io is fixing with Send to Name.

Instead of copying a 42 character string, you send assets to a readable FortressName. The system generates a fresh one time address in the background so your financial history stays private.

Skipping the clipboard risk entirely is exactly how onchain payments should work https://x.com/MadMagicSOL/status/2103696067342536905