Portfolio
Portfolio Goal
Section titled “Portfolio Goal”The portfolio turns course work into proof that the learner can build and explain a small Ethereum application.
Required Portfolio Items
Section titled “Required Portfolio Items”Each learner or team should submit:
- GitHub repository
- Frontend demo link
- Testnet or L2 testnet contract address
- Block explorer links for deployment and at least one interaction
- README
- Screenshots or a short demo video
- Security risk notes
- AI-assisted development note
README Structure
Section titled “README Structure”A strong README should include:
- Project name
- One-sentence summary
- Problem and user
- Architecture overview
- Contracts
- Frontend workflow
- Deployment network and addresses
- How to run locally
- How to test
- Known risks
- AI assistance record
Minimum Capstone Scope
Section titled “Minimum Capstone Scope”Choose one:
| Project | Minimum Scope |
|---|---|
| Vendor | ERC-20 token, buy/sell flow, approve, inventory, owner withdrawal |
| DEX | ETH/token pool, swap function, price function, LP concept |
Showcase Rubric
Section titled “Showcase Rubric”| Area | What Reviewers Look For |
|---|---|
| Demo | The app can be opened and used on a testnet |
| Contract | The main contract is readable and scoped |
| Frontend | Wallet connection and contract interaction work |
| Testing | Basic happy-path and failure-path tests exist |
| Deployment | Addresses and explorer links are documented |
| Security | Risks are named clearly and honestly |
| Explanation | The learner can explain how the app works |
Demo Day Format
Section titled “Demo Day Format”Suggested demo format:
- 2 minutes: project goal and user
- 3 minutes: live demo
- 2 minutes: contract and frontend architecture
- 2 minutes: risks, tests, and what AI helped with
- 1 minute: next steps
Portfolio Quality Bar
Section titled “Portfolio Quality Bar”The project does not need to be production-ready. It should be small, understandable, deployed, documented, and honest about risks.