# "address poisoning" — X 热门讨论 (2026-09-30 03:19 UTC)
## @MadMagicSOL (Magic Hunter) · 09-30 01:45 · ♥31 ↻1 💬28 Sending crypto is still a stressful ritual of checking the first and last four characters and hoping a bot didn't swap the middle
that is why the Send to Name setup by @Americanfort_io makes so much sense to me
you just send to a readable name and the protocol derives a fresh one time address strictly for that payment
no reused public wallets and zero address poisoning surface
the math just handles the privacy quietly in the background AmericanFortress https://x.com/MadMagicSOL/status/2105111638072512922
## @anhvu193 (Anh Vũ) · 09-29 15:30 · ♥27 ↻0 💬27 Lost $50M to 7 matching characters.
That's address poisoning. You check first/last 4, hacker matches them. Gone.
@Americanfort_io fix: send to a FortressName, wallet makes fresh one-time address each time. Only you two know it. Settles on native chain. Name never shows balance/history.
Live: Send-to-Name on 13 chains. Coming, not live: SafeSend shields sender with ZK + selective disclosure. No pools.
Your name public. Money isn't. When did you last copy-paste an address? https://x.com/anhvu193/status/2104956871392252299
## @Vanquan_titans (Van Quan) · 09-29 21:39 · ♥24 ↻0 💬25 Has anyone else found themselves really stressed about accidentally sending crypto to the wrong address? It’s such a common fear, especially with those super long, complicated wallet strings. I recently learned about @Americanfort_io's FortressName and Send-to-Name™ feature, and honestly, it’s a massive relief. Being able to send funds using a simple, human-readable name instead of a jumbled address totally eliminates that nagging worry of address poisoning. It's live on 13 chains already, which is pretty cool.
What's truly impressive is the underlying tech. They're using one-time stealth addresses for every single transaction. This means your financial activity stays private; observers can't just link a public name to your ongoing balance or transaction history. It’s a fundamental shift for privacy in Web3 payments without forcing users into new apps or complicated setups. It integrates smoothly with existing wallets, which is key for actual adoption.
Looking ahead, they're also working on SafeSend™ using Zero-Knowledge proofs. This promises enhanced privacy by allowing for accountable transactions without pooling funds, and even selective disclosure. Plus, their exploration into post-quantum cryptography with QBIP-32 and ZKPoSP is crucial for future-proofing digital assets. The fact they’re aiming to secure existing assets without requiring users to migrate anything is a huge UX win. It’s all about building a more resilient and private Web3 ecosystem. https://x.com/Vanquan_titans/status/2105049730803744992