The financial applications built in early periods established the primitives that everything since has been assembled from.
Overcollateralised lending
Borrowing against deposited assets exceeding the loan value.
Which substituted for credit assessment where identity does not exist.
The liquidation mechanism, incentivising anyone to close unhealthy positions, was the essential innovation.
Automated market making
Pricing by formula over pool reserves rather than by matching orders.
Which made on-chain exchange practical given block times and gas costs.
The constant product formula was simple enough to be gas-efficient and produced usable prices.
Collateral-backed stable value
Tokens maintaining a peg through overcollateralised debt positions.
Which demonstrated a decentralised approach to stable value that survived subsequent volatility.
Emergency shutdown mechanisms and governance-set parameters were tested under stress.
Flash loans
Uncollateralised borrowing within a single transaction.
Which was only possible because transactions revert atomically.
Legitimate uses in refinancing and arbitrage exist alongside their role in attacks.
Composability
Protocols calling each other, allowing complex positions from simple components.
Which is the distinctive property of these systems.
It also propagates failures between protocols that had no direct relationship.
The stress tests
A sharp market decline with network congestion produced liquidation failures.
Which exposed the dependency of liquidation mechanisms on block space availability.
Auction parameters and liquidation designs were revised in response.
Governance experiments
Token-based voting on parameters and upgrades.
Which produced both functioning governance and documented attacks.
Timelocks and quorum requirements emerged from that experience.
What persists
Every substantial protocol today is built from these primitives, refined rather than replaced.
Oracle dependency
Every lending and derivative protocol requires external price data.
Which became apparent as a systemic dependency early.
The infrastructure providing it developed into a sector in its own right.
Gas cost constraints
Every design decision was shaped by execution cost.
Which favoured simple formulas over sophisticated ones.
Cheaper execution environments have subsequently permitted more complex designs.
Permissionless listing
Anyone can create a market for any asset.
Which is the defining property and removes all gatekeeping.
It places the entire assessment burden on the individual participant.
Front-running discovery
The visibility of pending transactions became an exploitable property.
Which was identified in these early systems and developed into a substantial economy.
Protective routing and batch designs emerged in response.
The design inheritance
Current protocols are refinements of these primitives rather than replacements for them.
Yield sources
Lending interest, trading fees, and token incentives.
Which are three different things frequently reported as one number.
Distinguishing them is the first step in assessing any advertised return.
Liquidation infrastructure
Automated systems monitoring and closing unhealthy positions.
Which is what makes uncollateralised risk manageable without identity.
Competition between liquidators is what ensures the mechanism actually operates.
Governance token distribution
Issuing control rights to users rather than selling them.
Which was intended to decentralise and frequently concentrated instead.
Distribution outcomes are measurable on chain.
Emergency mechanisms
Shutdown procedures and pause capabilities tested under real stress.
Which proved necessary and are a centralisation trade-off.
The durable insight
Composable financial primitives with transparent rules are genuinely novel; the risks they carry are largely conventional ones in new form.
What was genuinely new
Financial primitives that anyone can inspect, combine and build on without permission.
The risks — leverage, liquidity mismatch, correlated collateral, oracle dependency — are conventional risks appearing in a new setting.
Both halves of that description are accurate and are frequently reported separately.
What to check in any protocol
Where the yield comes from, what the price oracle is, who can upgrade the contracts and what the liquidation mechanism does under congestion.
Four questions answerable from documentation and chain data.
Protocols that answer them clearly are generally the ones that have thought about them.
What has actually been built on them
Every substantial protocol operating today assembles these primitives differently rather than replacing them.
Lending, automated market making, collateralised stable value and flash loans are the components, and the last five years have been refinement rather than reinvention.
Composability as a risk
Protocols building on each other inherit each other's failures.
Which became apparent when incidents propagated between systems with no direct relationship.
Dependency mapping is now part of serious risk assessment.
Permissionless as a property
Anyone can deploy, list and interact without approval.
Which is the defining feature and removes every filter that exists elsewhere.
The assessment burden falls entirely on the individual as a result.
A closing note
The primitives built in that period were genuinely novel and are still the foundation of everything operating today.
The failures that followed came from applying conventional financial risks — leverage, maturity mismatch, correlated collateral — to systems where nobody was required to disclose that they were doing it.
The four questions
Where does the yield come from, what price feed does it use, who can upgrade it, and what happens during network congestion.
Answerable from public data, and they cover most of what has historically gone wrong.