The problem Private-Pay solves

Financial Privacy is Broken

Real-Life Story

Alice, a legendary dev, won the ETHIndia Hackathon and received $3,000 in prize money.

Bob, another participant who also won at the same hackathon, had a co-founder who wasn't trustworthy — the co-founder refused to admit receiving any prize money. Bob messaged all 3 winners asking for the organizer's wallet address. 1/3 winner shared it. On the explorer, that single address made it trivial to see who received what. Bob quickly inferred that $9,000 had been split among three people and, in a couple of minutes and with basic intelligence tools like Arkham, Dune Analytics, etc. linked every wallet to its owner.

That's a serious concern. Nobody wants the wallet that holds their real funds to be exposed. Bob — or anyone with the same info — could target those people for their own benefit.

The Core Issues

❌ Payments on public blockchains are NOT private

• Traceable through tools like Arkham Intelligence
• Trackable via Dune Analytics and explorers
• Identifiable by anyone with basic skills

❌ Results:

• Fear of transacting
• Inconvenience for legitimate users
• Financial loss from targeted attacks
• Privacy violations for everyone

✅ The Solution: PrivatePay

Where every transaction is fully private, anonymous, unidentifiable, and untrackable.

Core Benefits (current implementation)

• ✨ Sender privacy: Your wallet is never linked to the transaction
• ✨ Receiver privacy: Recipients' identities remain hidden
• ✨ Observer blindness: Third parties see nothing linkable
• ✨ Simple UX: Like Stripe links, but every transaction is a new, invisible wallet

Key Features (current)

🔒 Infinite Untraceable Stealth Accounts

• Each payment generates a fresh stealth sub-account
• Unlimited transactions, unlimited mixers
• One single DarkPool

💼 Static Payment Links

• Share a single payment link (e.g., amaan.privatepay.base)
• Each access generates a unique stealth address
• No complex setup required

🔐 Complete Unlinkability

• Sender cannot identify receiver
• Receiver cannot identify sender
• Observers see nothing linkable

Challenges I ran into

The ultimate challenge was to figure out how the single darkpool mixer mechanism would work with a combination of multiple architectures of Tornado Cash + ZCash + Elliptic Curve Diffie-Hellman (ECDH) + secp256k1 + BIP 0352 / EIP 5564.

It took time, a day was devoted to research, and I finally found a way to build the most innovative architecture.