Certificate
Earn the Web3 track certificate by passing the exam and deploying an auditable smart contract to a testnet.
Certificate outline
EXAMPLE
# Web3 certificate - outline ## Part 1 - multiple choice + code reading (30 questions, 75 min) Topics: - Solidity types, storage layout, visibility, modifiers - ERC-20, ERC-721, ERC-1155 mechanics - Reentrancy, integer ops (Solidity 0.8+), signature replay, oracle risk - Foundry testing: unit, fuzz, invariant - Upgradeability: UUPS proxy, storage gaps, initialiser patterns - Wallets, signatures, EIP-712 typed data Passing mark: 70 percent. ## Part 2 - capstone (take-home, ~10 hours) Build, test, and deploy a small contract suite: - ERC-20 token with mint cap and pausable - Vault that accepts deposits + withdrawals - Foundry tests: unit + fuzz + at least one invariant test - Slither run in CI with zero high-severity findings - Deploy to Base Sepolia (or Sepolia), verify on Etherscan - A minimal frontend (viem + wagmi) that connects and reads contract state Submit a Git repo + deployed addresses + verified Etherscan links. ## Grading - Correctness + security (40 percent): no high-severity Slither findings, no reentrancy - Tests (25 percent): coverage > 90 percent, at least one passing invariant - Deployment + verification (20 percent) - Frontend integration (15 percent) ## Tips - Use OpenZeppelin where you can - audited code beats clever code - Foundry invariant tests are worth more than 100 unit tests - Never deploy mainnet for this certificate; testnet only
Why it matters
A contract certificate is only credible if it includes tests, static analysis, and verified deployment. The bar for production deploy is higher - get the workflow right on testnet now so you never wing it on mainnet.
Tip: Tweak the snippet with Try it Yourself », then sit the quiz at the bottom of the page.
Discussion
Loading…