Builder & Web3 Frontend Engineer — crafting privacy-first tools for the decentralized economy.
Currently building VoidPay | Previously DApp Architect at Curve.fi
Privacy-first crypto invoicing — all data lives in the URL. No backend, no signup, no tracking.
https://voidpay.xyz/pay#N4IgbghgTg9g...
└─ Compressed invoice (never sent to server)
The idea is simple: generate a link, share it, get paid. The invoice IS the URL — if we shut down tomorrow, your links still work.
Why it matters: Crypto payments today are raw wallet addresses in Telegram chats. Error-prone, unprofessional, zero privacy. Enterprise tools like Request Finance require KYC and store your transaction history. VoidPay sits in between — professional invoicing with zero data collection.
Stack: Next.js 15 · TypeScript · Viem · Wagmi · Zustand · Tailwind CSS · Vercel
- Stateless Web3 interfaces — local-first architecture, no backend dependencies
- DeFi frontends — AMM dashboards, swap UIs, liquidity management (Curve, Uniswap)
- Open-source libraries — big-decimal for high-precision arithmetic in JS/TS
- Privacy tools — URL-as-database patterns, client-side cryptography
Frontend & UI
Web3 & Blockchain
State & Data
Infrastructure
DeFi: Curve · Uniswap · Aave · 1inch
I believe financial tools should be private by default, not by opt-in. If a service can lose your data, it eventually will. The best architecture is the one that never had your data in the first place.
Building at the intersection of Web3 UX and privacy engineering — making crypto payments as simple as sharing a link.
Open to conversations about Web3 product design, privacy-first architecture, or DeFi UX.