Skip to content

Research

The vocabulary, then the classes.

Educational examples, not client results.

Specification
The property, written so a checker can accept it or return a trace.
Invariant
A statement that should hold at the points you claim, usually after every transition.
Assumption
What the proof borrows and does not establish. Oracles, admin honesty, and bounded loops live here.
Counterexample
A concrete trace that breaks the property. It can be a bug, a bad spec, or a model that was too loose.

Illustrative spec

property solvency:
  forall s in Reachable.
    assets(s) >= liabilities(s)

assumes
  oracle_fresh(s)
  admin_key_uncompromised

Illustrative specification. Not a protocol result.

Audit classes, for the work that is not a proof.

Examples of what a manual review looks for; not findings from a named system.

Educational examples. Not client findings, and not a measure of systems reviewed.

Chain
Severity

8 classes in this set

  • Affected assumption

    The latest round is a current, complete price.

    Impact

    Borrowing or minting can clear against a price the feed no longer stands behind.

    Proof outline

    Freeze or stall the feed past the heartbeat the protocol claims to tolerate. Borrow or mint against a price that no longer exists. The transaction succeeds because the code never asked how old the answer was.

    What we check

    Heartbeat, answeredInRound, min/max bounds, and what the protocol does when the feed is down — pause, or proceed.

    Mitigation

    Treat a missing, stale, or partial round as a halt, not as a price.