What inspired you to build this? "Hey Product Hunt! 👋 I’m HushPay, and I’ve always been a believer in the power of public blockchains—but I’ve never been a fan of 'public' being synonymous with 'doxing.' The inspiration came from a simple lunch with a friend. I paid them back in ETH, and within seconds, they could see exactly how much I had in my main wallet and every other transaction I’d ever made. In the physical world, paying for a coffee doesn't give the barista a peek at your bank statement. I wanted to bring that same basic level of dignity and privacy to Ethereum." What problem were you trying to solve? "The problem is the 'Transparency Trap.' On-chain privacy currently feels like an 'all-or-nothing' game. You either have zero privacy, or you have to use complex mixers that are often stigmatized or difficult to navigate. I wanted to solve the Recipient Privacy problem specifically. Currently, if you want to receive a payment privately, you have to generate a brand new wallet and send the address to the payer manually every single time. By implementing ERC-5564, we’ve automated this. You give out one 'Stealth Meta-Address,' and the protocol handles the rest—generating a unique, unlinkable address for every single incoming transaction." How did your approach or process evolve? "Initially, I thought about building a proprietary privacy layer. But as I dove into the ERC-5564 (Stealth Address) standard, I realized that for privacy to win, it needs to be standardized, not siloed. My process shifted from 'building a private app' to 'building a user-friendly gateway for a new standard.' We spent months iterating on the 'Scanning' experience. Since stealth addresses require the recipient to 'scan' the blockchain to find their funds, we had to work hard to make that process fast and invisible to the user. We moved from a heavy, slow client-side scan to a lightweight, optimized approach that doesn't sacrifice your private keys."

HushPay - Private Transactions using Stealth Addresses (ERC-5564).

Replies