# crypto wallet phishing — X 热门讨论 (2026-09-25 09:05 UTC)
## @Aliba_79 (Aliba) · 09-25 08:09 · ♥54 ↻1 💬56 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