Smart Contract Risk
Smart contract risk measures the structural assurance of the deployed code behind a protocol. Ozone evaluates each contract on the curated list that materially controls a protocol's operation, scores each one against a fixed rubric, and rolls those scores up to a single per-protocol grade. The grade is surfaced alongside market risk and oracle risk on every vault row, and is one of three dimensions in the composite Ozone Score.
Why this dimension exists
Most DeFi loss events have a specific contract behind them: an upgrade authority that proved excessive in retrospect, a privileged role that escalated quietly, a price-feed precondition that an attacker exploited. These are structural questions, not just code-quality questions. Audits ask whether the code is correct. Smart contract risk asks whether the structure can be trusted.
Smart contract risk evaluates three failure modes that the other risk dimensions in the Ozone Score do not surface on their own:
- Privileged-actor abuse: an admin role can move funds, pause execution, or change parameters in ways the protocol's published behavior does not document.
- Hijackable upgrade paths: a contract's deployed logic can change without its address changing, so observed history is not a guarantee about future behavior.
- Oracle manipulation preconditions: a contract structurally permits price feeds that could be manipulated under realistic conditions. Oracle risk grades the live feed today; smart contract risk grades whether the contract is structurally locked into a sound feed or could substitute a manipulable one tomorrow.
Market risk evaluates the position itself: liquidity concentration, redemption depth, stress-test resilience. Oracle risk evaluates the price feeds the protocol relies on. Smart contract risk evaluates the deployed code, contract by contract.
How a protocol grade is built
Ozone scores each curated contract on a 0.0–1.0 scale, then combines those per-contract grades into a per-protocol grade.
Per-contract grade (per scored contract, 0.0–1.0)
↓ weighted by how central the contract is to the protocol
Per-protocol grade (per protocol, shown on the dashboard)
Some structural findings cap a contract's grade regardless of other evidence. A confirmed unrestricted privileged action, a confirmed oracle-manipulation precondition, or unreviewable code context each cap the contract's grade at 0.39, 0.59, or 0.84 respectively (lowest cap wins when more than one applies). The cap applies to the per-contract grade, before that grade enters the per-protocol roll-up.
See Dimensions for the full rubric, the score reductions that apply before capping, and the aggregation rule.
What stays stable, what changes
In practice, smart contract grades do not fluctuate between meaningful events. The contracts behind a mature protocol change rarely, so their grades stay put. A grade moves when a contract change is detected on chain, when the curated list of contracts Ozone scores for a protocol is revised, or when the rubric itself is updated in a published, dated methodology revision.
A flat grade is the affirmative output of a check that ran and found nothing material. Stability matters because smart contract risk does not stand alone: it sits next to market risk and oracle risk, both of which move on faster cadences. See Monitoring for what triggers a re-evaluation and what does not.
How it sits next to the other risk dimensions
Smart contract risk is one of three pillars in the composite Ozone Score, reported alongside market risk and oracle risk on every vault row. Each dimension answers a distinct question about a different surface:
| Dimension | Question it answers |
|---|---|
| Market risk | How fragile is this vault under current conditions? |
| Oracle risk | How reliable are the price feeds this vault depends on? |
| Smart contract risk | How robust is the deployed code, contract by contract? |
Read next
- Dimensions: the evidence families, the score reductions, the capping conditions, and how per-contract grades roll up to per-protocol grades.
- Worked Example: Maple v2 walked through three contracts (MapleGlobals, GovernorTimelock, PoolManagerFactory) ending in a single protocol grade.
- Monitoring: what triggers a re-evaluation, what does not, and what a flat grade means.
- How Ozone Scores Work: how the three risk categories combine into the composite Ozone Score.