# "address poisoning" — X 热门讨论 (2026-09-25 14:01 UTC)
## @XTrendTrackerX (TrendTrackerX) · 09-25 11:27 · ♥47 ↻1 💬32 Something interesting I've noticed is how address-poisoning attacks exploit muscle memory rather than code vulnerabilities.
Copying long hex addresses from transaction history remains one of the weakest user experiences in crypto.
By replacing raw hashes with human-readable FortressNames, @Americanfort_io combines readable wallet identities with fresh receiving addresses to make wallet interactions safer and more private.
Combining readable wallet identities with fresh receiving addresses fundamentally changes how users approach wallet safety and privacy.
When individual transaction privacy becomes the default, copy-paste exploits become significantly less effective. https://x.com/XTrendTrackerX/status/2103446247973498918
## @MadMagicSOL (Magic Hunter) · 09-25 10:00 · ♥26 ↻1 💬25 Address poisoning is a brutal way to lose your stack. We all still get anxiety checking the first and last characters of a wallet before hitting send.
The scam relies entirely on us trusting familiar patterns.
That is why the approach from @Americanfort_io makes sense. Instead of copying a raw hex string, you just use a FortressName.
The wallet computes a fresh one time address for every payment. No address reuse means no history poisoning.
A much better way to handle crypto privacy https://x.com/MadMagicSOL/status/2103424280583082192
## @luong4101992 (nbaluong (✱,✱)) · 09-25 13:08 · ♥25 ↻1 💬24 $50M lost because people copied the wrong wallet address. @Americanfort_io
That’s the scary part about address poisoning.
Attackers create lookalike addresses with similar first and last characters. You copy the wrong one without noticing, send the funds, and there’s usually no way to get them back.
The problem is simple: long wallet addresses are hard to verify every time.
@Americanfort_io tackles this with Send to Name.
Instead of copying a long address, you send to a FortressName. The wallet generates a fresh one-time address for each payment while the transaction still settles on the native blockchain.
No permanent public address tied to the name for attackers to monitor or copy.
One FortressName already works across 13 integrated networks.
Sometimes better security isn’t about being more careful.
It’s about removing the step where people keep making mistakes. > 引用 @Americanfort_io: $350M left an exchange's hot wallets today. In the coming days it will be split, bridged and deposited across a dozen venues, and not one of them can check whether the address receiving it belongs to the same verified party as the address sending it.
We published the answer today: Provenance Proofs. A wallet proves that several addresses share one hidden origin, across chains and cryptographic schemes, without revealing the seed, the keys or the rest of the wallet. A bridge can verify it before releasing funds. An exchange can recognise deposits from a wallet it already onboarded.
Post-quantum, zero-knowledge, and the user chooses how linkable they want to be.
Read more in @TheNextWeb feature. https://x.com/luong4101992/status/2103471823702921477