condom@in
4 ratings
)Overview
Condom for your wallet.
condom@in is a protective wallet layer for web3 users. Instead of exposing your main wallet directly to every dApp, condom@in gives each site its own disposable proxy wallet identity. That helps reduce phishing risk, wallet doxxing, malicious signature exposure, and cross-site wallet linkage. What it does: - Wraps supported wallet connection flows with a per-site proxy address - Intercepts risky signature requests before they reach your real wallet identity - Flags common drainer patterns like Permit-style approvals, suspicious typed-data requests, and phishing-style signature prompts - Keeps threat history visible in the extension popup - Lets you rotate a site-specific proxy whenever a site feels sketchy Why use it: Most wallet users do not get drained by hacks in the dramatic sense. They get drained by connecting to the wrong site, signing the wrong payload, or unknowingly granting approvals that can be abused later. condom@in is designed to reduce that exact risk. Current protection coverage: - EVM (Ethereum, Base, Arbitrum, Optimism, Polygon, and more) - Solana - Aptos condom@in is a protective layer, not a guarantee against every loss scenario. It does not protect against seed phrase theft, device malware, or scams that happen outside the wallet/browser flow.
5 out of 54 ratings
Details
- Version1.1.0
- UpdatedApril 1, 2026
- Offered bygiri2k2five
- Size226KiB
- LanguagesEnglish (United States)
- Developer
Email
giri2k2five@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site