Proof feature 08 of 10 · smart contract audit function coverage

Check Smart Contract Audit Function Coverage

Determine whether deposit, withdraw, borrow, stake, swap, claim, and bridge functions were inside the reviewed audit scope.

Plain-English definition

What function scope means

Function-scope evidence maps a user action to the exact code path and identifies which auditors, review tiers, findings, and residual risks apply to it.

Questions this page answers

What to verify

  • Was this exact entrypoint reviewed?
  • Did review include every downstream contract and dependency?
  • Which findings and confidence statements apply to this action?

Evidence checklist

Evidence that makes this useful

Each item must be tied to an inspectable source or remain clearly labeled as pending, unavailable, or unidentified.

01

Action mapping

User intent to selector, entrypoint, implementation, and downstream calls.

02

Reviewer coverage

Auditor identity, role, tier, reviewed files, and confidence.

03

Residual risk

Excluded surfaces, assumptions, unresolved findings, and follow-up work.

Decision use

How to use this proof

Use function coverage to avoid treating a contract-wide badge as proof for an unreviewed action path.

Proof of Audits shows evidence and gaps. It does not guarantee protocol or transaction safety.

Specific answers

Frequently asked questions

Why is contract-level scope not always enough?

A function may call other contracts, implementations, libraries, or external systems that were not included in the same review.

Can multiple auditors cover one function path?

Yes. Different reviewers may cover function logic, cross-contract behavior, system assumptions, or fix validation.