Protocol Design Fundamentals
What problem does your protocol solve? Who is your user? How do you design incentives that don't collapse? Architecture decisions that will haunt you forever. The foundation every Web3 founder needs before writing a single line of code.
Chapter 01
0 of 4 lessons completedFinding the Problem
What Problem Does Your Protocol Solve?
- +Identify a real problem worth solving on-chain.
- +Distinguish between problems that need a protocol and problems that don't.
Who Is Your User?
- +Map user types in DeFi (traders, LPs, borrowers, protocols, DAOs).
- +Understand the difference between users and liquidity providers.
Mechanism Design 101
- +Understand incentives and game theory basics in protocol design.
- +Identify incentive misalignments before they blow up.
Attack Vectors at the Design Level
- +Distinguish economic attacks from code exploits.
- +Learn from real protocol failures caused by design, not bugs.
Chapter 02
0 of 3 lessons completedArchitecture Decisions
Monolithic vs Modular
- +Compare single-contract vs multi-contract systems.
- +Evaluate composability tradeoffs.
Upgradeable vs Immutable
- +Understand proxy patterns and governance-controlled upgrades.
- +Evaluate trust assumptions of each approach.
On-Chain vs Off-Chain
- +Determine what belongs on-chain vs what doesn't.
- +Understand oracles, indexers, and hybrid approaches.
Chapter 03
0 of 5 lessons completedMarket and Economics
Competitive Landscape Analysis
- +Evaluate existing protocols and find gaps.
- +Understand the fork-improve-innovate spectrum.
Protocol Economics 101
- +Understand how protocols generate value.
- +Distinguish protocol revenue from token value.
Composability as Strategy
- +Evaluate building on top of vs building from scratch.
- +Identify dependency risks in composable systems.
From Idea to Spec
- +Write a protocol specification before any code.
- +Use the Protocol Design Canvas framework.
Module Capstone
- +Evaluate a real protocol proposal end-to-end.
- +Apply all Module 1 concepts in a scored assessment.
Key Terms
Key terms are concepts that deserve special attention when studying this module. Each term links back to the lesson where it was introduced.
What Problem Does Your Protocol Solve?
Problem-Solution Fit
Evidence that your target users have a real, painful problem and your protocol solves it better than existing alternatives. In DeFi, this means users will move capital to your contracts.
Fork
A copy of an existing protocol's code, deployed as a new project. In DeFi, forks are trivial. Your code is not your moat.
Permissionless
A system that does not require approval from a central authority to use. Permissionless collateral listing means anyone can add a new asset without a governance vote.
Protocol-Market Fit
The Web3 equivalent of product-market fit. Your protocol has found genuine, organic usage beyond incentivized liquidity mining.
Long-tail Assets
Tokens with smaller market caps and lower liquidity that are underserved by major protocols. Supporting them permissionlessly is a common wedge strategy.
Who Is Your User?
Liquidity Provider (LP)
A user who deposits tokens into a pool to facilitate trading, earning fees in return. LPs and traders have different, sometimes conflicting, incentives.
MEV
Maximal Extractable Value. Profit that can be extracted by reordering, inserting, or censoring transactions within a block. Directly impacts user experience.
Mechanism Design 101
Mechanism Design
The art of designing rules and incentives so that self-interested participants produce desired outcomes. In DeFi, this means making it profitable for users to do what the protocol needs.
Nash Equilibrium
A state where no participant can improve their outcome by changing their strategy alone. Good protocol design creates Nash equilibria where the desirable behavior is the profitable behavior.
Incentive Misalignment
When the protocol's rules make it profitable for users to act against the protocol's interests. The root cause of most DeFi exploits that aren't code bugs.
Attack Vectors at the Design Level
Economic Attack
An exploit that drains value through the protocol's own rules, not through code bugs. The code works exactly as written, but the design allows value extraction.
Death Spiral
A self-reinforcing cycle where a protocol's value decreases, triggering more selling, which decreases value further. Terra/Luna is the canonical example.
Monolithic vs Modular
Monolithic
A design where most protocol logic lives in one or a few tightly coupled contracts. Simpler to audit but harder to extend.
Modular
A design where protocol logic is split across many contracts with defined interfaces. More flexible but more complex to build and audit.
Core vs Periphery
Architecture pattern separating immutable core logic (invariants, safety checks) from replaceable periphery (routers, quoters, integrations).
Diamond Proxy
EIP-2535. A proxy pattern that delegates to multiple implementation contracts (facets), enabling complex modular architectures behind a single address.
Hooks
External contracts that modify protocol behavior at defined points (before/after swap, before/after LP). Uniswap V4's primary extensibility mechanism.
Upgradeable vs Immutable
Immutable Contract
A deployed contract that cannot be changed. What you deploy is what you get. Users trust it because nobody can modify it.
Proxy Pattern
A design where users interact with a proxy that delegates calls to a replaceable implementation contract. Enables upgradeability at the cost of a trust assumption.
UUPS
Universal Upgradeable Proxy Standard (EIP-1822). Upgrade logic lives in the implementation, not the proxy. Lighter but riskier if upgrade function is missing.
Timelock
A delay between when an upgrade is proposed and when it takes effect. Gives users time to verify changes and exit if they disagree.
Trust Assumption
Something users must believe to be true that cannot be verified on-chain. Upgradeability introduces the trust assumption that the upgrade key holder won't act maliciously.
On-Chain vs Off-Chain
Value-Critical
Logic that directly controls or moves user funds. Must be on-chain and trustless. If this logic is wrong or censored, users lose money.
Oracle
A system that brings external data (prices, events) on-chain for smart contracts to use. Critical dependency for lending, perpetuals, and any protocol needing external prices.
TWAP
Time-Weighted Average Price. An on-chain oracle calculated from historical swap data. No external dependency but slower and manipulable with large trades.
Indexer
A service (like The Graph) that reads on-chain events and makes them queryable via APIs. Powers analytics dashboards and frontends. Off-chain convenience layer.
Censorship Resistance
The property that no single entity can prevent a transaction from being processed. On-chain protocol logic has this. Front-ends and APIs do not.
Assigned Reading
Every lesson references real sources: whitepapers, governance proposals, research papers, and protocol documentation. Tap any link to verify or go deeper.
What Problem Does Your Protocol Solve?
Who Is Your User?
Mechanism Design 101
Attack Vectors at the Design Level
Monolithic vs Modular
Upgradeable vs Immutable
On-Chain vs Off-Chain
Competitive Landscape Analysis
Protocol Economics 101
Composability as Strategy
From Idea to Spec
Module Capstone
Module Highlights
- *Identify real on-chain problems worth solving.
- *Evaluate mechanism design and incentive structures.
- *Choose the right architecture for your protocol.
- *Analyze competitive landscape and find gaps.
- *Understand protocol economics and value accrual.