# crypto wallet phishing — X 热门讨论 (2026-09-26 08:34 UTC)
## @__Vik_tor (Last Son) · 09-26 07:48 · ♥53 ↻12 💬28 A crypto transfer can look simple on the surface, but there are plenty of opportunities for something to go wrong before your funds arrive.
That’s the problem @Americanfort_io is tackling.
Your transaction can be exposed to things like:
- Fake or manipulated wallet addresses - Malware that replaces copied addresses - Impersonation designed to fool you - Systems collecting transaction-related information - Phishing pages built to capture your details
The blockchain may be secure, but the journey around a transaction can still create weak points.
AmericanFortress is building protection around that journey, with privacy and security designed into the way users send.
Because protecting a transaction isn't only about what's on-chain, it's also about everything that happens before you click “send.” https://x.com/__Vik_tor/status/2103753681816396247
## @Techgeeg (†εςhgεεg) · 09-26 05:38 · ♥50 ↻6 💬6 One thing I’ve always found annoying in crypto is having to share a wallet address every time someone wants to send me something.
One wrong copy-paste, and you’re already dealing with the risk of sending funds to the wrong place.
That’s why @Americanfort_io caught my attention.
With Send-to-Name™, you can use a public name while the actual transaction goes through a unique stealth address known only to the sender and recipient.
No address reuse. Less room for poisoning or phishing. More privacy by default.
Honestly, this is the kind of crypto UX I want to see more of.
Keep the name public. Keep the transaction private. 🛡️
Get your unique address today — https://t.co/UEQxDDKBAc https://x.com/Techgeeg/status/2103720761059913814
## @Caccy_001 (BoredCaesar (Ø,G)🥱) · 09-26 08:00 · ♥20 ↻1 💬21 Here’s an interesting problem in crypto:
How do you prove two wallet addresses belong to you without exposing everything connected to your wallet?
@AmericanFort_io researchers have proposed a way to do exactly that with zero-knowledge proofs.
You could prove that several addresses came from the same hidden wallet origin while keeping your:
• seed phrase private • private keys private • derivation paths private • other wallet addresses private
The useful part is selective disclosure.
You don't have to reveal your entire wallet just because you need to prove ownership of one address.
The paper also explores applications like anti-phishing payments, compliance and cross-chain identity.
It isn't deployed in production yet, but the research points toward an important idea:
Prove what needs to be proven. Keep everything else private. https://x.com/Caccy_001/status/2103756463545909378