Smart Contract Risk

Definition

Smart contract risk covers vulnerabilities, upgrade keys, oracle assumptions, and economic exploits. Audits reduce but do not eliminate it, and admin powers can matter as much as obscure bug classes.

Read who can upgrade, pause, or seize. A protocol can be “audited” and still custodial in practice through powerful admin keys. Document the control surface beside the TVL headline. Bridged representations can depeg when trust assumptions crack.

Economic exploits — oracle manipulation, unhealthy liquidations, reflexive collateral — often matter as much as classic reentrancy. Composability means risk arrives from dependencies you did not deploy. Searcher-validator splits change who benefits from ordering power.

Newer codebases and rapid feature shipping raise uncertainty. Time-in-market without incident is not proof, but brand-new critical contracts deserve smaller size and clearer kill criteria. Systemic stable exposure turns one peg break into many liquidations.

Why researchers care

• TVL without security diligence is incomplete research.
• Admin keys can be as important as bugs.
• Newer codebases carry higher uncertainty.
• Oracle and composability risks hide outside a single repo audit.

How to use it in research

• Upgradeability controlled by a 2-of-3 multisig of anonymous keys — raise governance custody risk.
• Lending market accepting low-liquidity collateral — model oracle manipulation paths.
• Bridge contracts holding the bulk of an L2’s TVL — prioritize bridge diligence.

Common mistakes

• Treating an audit badge as a guarantee.
• Ignoring admin and upgrade powers.
• Assuming battle-tested dependencies cannot fail in new combinations.