I build full-stack Web3 applications — wallet-connected frontends, the smart contracts and APIs behind them, and everything in between — using React, Next.js, viem/ethers, and Solidity. If you need a dApp that actually ships to production, not just a demo, this is what I do.
What I Build
- Wallet-connected frontends — React and Next.js apps with viem/ethers integration
- DEX and AMM interfaces — token swaps, liquidity pools, PancakeSwap-style forks
- NFT marketplaces and minting dApps — ERC-721/1155 front-to-back
- DeFi dashboards — staking, vesting, and portfolio tracking interfaces
- Backend APIs — indexing on-chain data, caching, and serving it to the frontend
Real Use Cases
- Blockchain and full-stack builds — smart contracts paired with production frontends, end to end
- PancakeSwap-style DEX forks — deployed on BSC, Fantom, and Polygon
- Custom ERC-20 and BEP-20 token launches — paired with the frontend to manage them
- Full-stack Web3 apps — wallet connection, transaction flows, and on-chain data display
Technology
- React and Next.js — production frontend frameworks
- viem and ethers — wallet connection and contract interaction
- Solidity and Foundry — the smart contract layer when the dApp needs one
- PostgreSQL and MongoDB — for indexing and caching on-chain data
Built for Real Users, Not Just a Demo Wallet
A dApp that only works with MetaMask on localhost isn’t finished. I test wallet connection flows, handle failed and pending transactions gracefully, and make sure the frontend doesn’t silently break when a user’s wallet or network doesn’t match what you expected.
FAQ
Do you build the smart contract too, or just the frontend?
Both, or either, depending on what you already have. I can build the full stack end to end, plug a frontend into an existing contract, or just handle contract development if you already have frontend engineers.
Which wallets and chains do you support?
MetaMask, WalletConnect, and Coinbase Wallet cover most users. For chains, I build on Ethereum, BSC, Polygon, and Base most often — I’ll help you pick based on your users’ costs and expectations.
How do you handle failed transactions in the UI?
Every transaction state — pending, confirmed, failed, rejected — gets its own UI feedback. Users should never wonder whether their transaction went through.
Related Reading
- Building a Web3 Product: From Smart Contract to Full-Stack App
- Ethereum vs BSC vs Polygon vs Base: Choosing the Right Chain for Your Web3 Project
- Multi-Signature Wallets: What They Are and When Your Project Needs One
- Smart Contract Security: The Vulnerabilities That Actually Get Projects Hacked
- Choosing a Database for Your Startup: SQL vs NoSQL in Practice
Discuss Your Project
Have a dApp idea — DEX, NFT marketplace, or DeFi dashboard? Get in touch to talk through scope, or reach out via Fiverr if you’d rather start there.