Back to portfolio
Technical & SecuritySimulated project
Frontend Web3 Developer portfolio brief
A simulated technical & security exercise for Frontend Web3 Developer. Treat it as realistic practice, not real client or protocol work.
7 deliverables6 tools referenced3 linked interview questions
Objective
Build a small dApp around a real contract
Expected deliverables
Working dAppState matrixWallet integrationComponent setTest planIntegration READMEError-state documentation
Recommended workflow
- Build a small dApp around a real contract
- Document every transaction state
- Test across multiple wallets, networks, and failure scenarios
- Review the result against the rubric, then package it as a case study.
Constraints and safety
- Use only public sources or clearly simulated data.
- Never include seed phrases, private keys, or wallet secrets.
- Redact private user, company, security, legal, or compensation information.
- State every assumption you make.
Tools in practice
- React
- Build wallet-aware interfaces, handle pending and failed transaction states, read contract data, and keep chain state synchronized with the UI.
- TypeScript
- Build wallet-aware interfaces, handle pending and failed transaction states, read contract data, and keep chain state synchronized with the UI.
- Next.js
- Build wallet-aware interfaces, handle pending and failed transaction states, read contract data, and keep chain state synchronized with the UI.
- wagmi or viem
- Build wallet-aware interfaces, handle pending and failed transaction states, read contract data, and keep chain state synchronized with the UI.
- testing tools
- Test wallet connections, network switching, transaction states, accessibility, responsive behaviour, and mocked failure paths.
- Figma and browser tooling
- Develop and review visual work used in working dApp and state matrix.
What a strong submission shows
- A transaction-flow demo
- Complete failure-state coverage
- A responsive wallet-integrated app
- An integration README
Weak submission patterns
- A happy-path mint page
- Copied wallet connection code with no error handling
- Screenshots without a working deployment or repository
Review rubric
- Accuracy of claims and sources
- Relevance to the target role
- Decision quality and trade-offs
- Completeness of the deliverable
- Clarity of communication
- Honest limitations and next steps
Present it as a case study
- Explain the problem, sources, decisions, ownership, constraints, output, review, and what you would change.
- Show the final artifact before the process notes.
- State what you owned and what belonged to other people.
- Label the work as simulated, and keep any real contribution clearly separate.
Interview questions this project helps you answer
How would you represent a transaction that is signed but not finalized?
What should the UI explain before a token approval?
How do you debug a problem that appears only in one wallet and chain?