Client project
AllYouNeedIsNft - NFT Marketplace Startup

Tech stack
Services
- →Co-founding and technical leadership
- →Frontend architecture and development (Next.js)
- →Ethereum smart contract integration (Solidity + ethers.js)
- →Wallet authentication UX (MetaMask, WalletConnect)
- →Product planning, roadmap, and engineering hiring
Deliverables
- ✓Live NFT marketplace, token listing, buying, and selling on Ethereum mainnet
- ✓Creator and collection profile pages with SEO-optimised routes
- ✓Wallet onboarding flow designed for non-crypto-native users
- ✓MVP shipped in 3 months from zero lines of code
Challenge
Co-founded AllYouNeedIsNft at a moment when NFT marketplaces were exploding but the space was dominated by OpenSea. The window to enter was narrow: ship a working marketplace fast, differentiate on UX, and establish creator relationships before the market cooled. The technical challenge was real, blockchain integration, smart contract security, wallet authentication, and a consumer-grade frontend all had to be built from scratch by a small team with no existing codebase.
Discovery
Early conversations with artists and collectors surfaced a consistent complaint about existing platforms: confusing wallet flows, poor mobile experience, and no support for emerging creators. The opportunity was a marketplace that felt as simple as an e-commerce store while hiding the blockchain complexity underneath.
Options Considered
- Fork OpenSea's open-source contracts, evaluated. Used as reference but not forked directly; business logic required custom royalty and auction mechanics.
- Use a marketplace-as-a-service (e.g. Rarible Protocol): rejected. Too much lock-in; fee structure wasn't viable for the target creator segment.
- Custom Solidity contracts + Next.js frontend: chosen. Full control over contract logic, gas optimisation, and UX.
Decision
Next.js for the frontend (SSR for SEO on collection pages), Solidity for the marketplace and royalty contracts on Ethereum, ethers.js for wallet interaction. MetaMask and WalletConnect covered the two dominant wallet surfaces. Architecture decisions were made with MVP speed as the top constraint, extensibility second.

allyouneedisnft.com, scrollable snapshot of the live marketplace
Implementation
Led the entire frontend architecture: routing, wallet connection flow, contract interaction layer, and collection/token pages. The wallet auth flow was a particular UX challenge. It had to work for users who had never touched crypto. Designed a step-by-step onboarding modal that walked new users through installing MetaMask and connecting without leaving the page.
Behind the marketplace sat a custom indexing engine that talked to the chain directly through the Nethereum library. It pulled token data on-chain, read the metadata JSON for ERC-1155, ERC-721 and several other formats, and stored collection attributes in a local database. Images were fetched from IPFS and rescaled to the sizes the site actually renders, so collection pages never dragged down full-resolution originals.
Caching worked as lazy load: a collection got indexed the first time someone opened it, on demand, instead of crawling the whole chain up front. Indexing progress was pushed to the browser over WebSockets and shown as a live progress bar, so a first-time visitor to a large collection could watch it fill in rather than stare at an empty page.
Drove product decisions week-to-week: prioritised the buying and listing flows for MVP, deferred auctions and offers to v2. Onboarded two engineers, defined the branching strategy, and ran weekly demos with co-founders to keep the roadmap honest.
Outcome
MVP shipped in 3 months from zero. First creator collections went live at the peak of NFT market interest. The platform handled real transactions on mainnet with no contract exploits. Served as a strong proof of concept for the team's ability to execute in a fast-moving, technically complex space.
Indexing Engine in Action
Thumbnail Generation
Thumbnails being generated for collection images. The collection downloads in the background as a separate microservice process, so the main site stays responsive while it runs, and the files are laid down on disk as they arrive rather than held in memory or re-fetched per request.
Open for contract collaboration
I am available for contract-based collaboration. If you have an interesting project idea, schedule a call via Calendly.
Schedule a 30-min call