Skip to content

Demo 02 · Audit Contests

Find the code no report names.

Every callable function of ten protocols, checked against the public audit reports we hold and their cited file lists. Pick a row.

FIG 2.1 One tick per callable function
  • 0Byte-for-byte match
  • 584In audit scope
  • 72No audit found
  • 0Not checked

All ten: 656 · Tick count is the protocol's number of callable functions.Pinned block 26,392,435 · public/evidence/catalog + cited supplements (scope-bindings.v1.json)

  • Recorded data
  • 10protocols
  • 656callable functions
  • 584in audit scope
  • 72no audit found
  • 0not checked
  • pinned block26,392,435

02Selected protocol

Aave V3 · Pool revision 12

  • Byte-for-byte match0
  • In audit scope73
  • No audit found2
  • Not checked0

Reports we hold

A gap here means no report in our evidence names this file. Another public report may cover it; send it and the count changes.

In audit scope means the report names the file. It does not mean the deployed code is the reviewed commit; no build match was run for these functions.

No audit found2

No report we hold names the file these functions live in.

FileFunctions
@aave/core-v3/contracts/dependencies/openzeppelin/upgradeability/InitializableUpgradeabilityProxy.sol
InitializableImmutableAdminUpgradeabilityProxy
1
lib/aave-helpers/lib/aave-address-book/lib/aave-v3-origin/lib/solidity-utils/lib/openzeppelin-contracts-upgradeable/lib/openzeppelin-contracts/contracts/utils/Multicall.sol
PoolInstance
1

Not checked0

Our evidence cannot say: the report has no extracted file list for this code, or it is a change review that names only some files.

Every function has a report answer.

03Scope sheet

What a gap-based contest would scope.

The no-audit list becomes a scope sheet. Before any contest, the protocol confirms that no other report covers these files.

Aave V3 · Pool revision 12block 26,392,435

FileFunctionsExample function
InitializableUpgradeabilityProxy.sol1initialize(address,bytes)
Multicall.sol1multicall(bytes[])

Prize, dates and participants are not shown: no contest is listed for these protocols.

Download this scope sheet (JSON)