Data Reference

Supported Protocols

11 protocol modules with versions, strategy defaults, audit context, and incident history.

Philidor tracks vaults across 11 protocol modules registered publicly, plus Kamino staged below in the indexer.

Protocol Modules

Protocol ModuleStrategy CoverageVersionsLaunch DateAuditsBug Bounty
Aavelendingv2, v3, v3-lido, v3-etherfi2020-01-088Immunefi
Aave V4lendingv4 hub-spoke2026-03-305Immunefi
Yearnyield_aggregationv2, v32020-07-178Immunefi
Beefyyield_aggregationv22020-10-086Immunefi
Morphoisolated_lendingv1, v22024-01-108Morpho
Sparksavings and lendingv1, v22023-05-098Spark Security
Compoundlendingv3 Comet2022-08-263Immunefi
Uniswap V2liquidity_provisionv22020-05-189Uniswap Security
Uniswap V3liquidity_provisionv32021-05-059Uniswap Security
Uniswap V4liquidity_provisionv42025-01-319Uniswap Security
Nestmulti_market and savingsv12025-01-011Nest Security

The strategy column describes module coverage. Individual vault rows carry the canonical strategy_type used for scoring.

Kamino (Solana) — rolling out

Kamino is Philidor's first non-EVM protocol module, covering both Kamino programs: K-Lend (isolated lending markets whose reserves become vault rows, and whose markets are served first-class by /v1/markets) and Kamino Earn kVaults (curated vaults allocating across K-Lend reserves, with allocation snapshots and curator attribution).

What is different from the EVM modules, by construction:

  • Identity: addresses are base58 and case-sensitive; the chain id is the synthetic 1399811149. The standards-based CAIP-2 key is served by /v1/chains once Solana's first vault rows are public (the endpoint lists active-vault chains).
  • Verification: every published figure is reconciled against finalized on-chain account state decoded with pinned program IDLs — vendor API values that disagree with chain state are withheld, not served.
  • Control scoring: program upgrade authority and emergency powers, not contract admins — see Control and Governance.
  • Oracles: reserve price sources resolve through Kamino's Scope aggregator with worst-of attribution — see Oracle Providers.

Rollout status: the chain, scoring, reconciliation and event ingestion are live internally; Kamino vault rows appear in the public API when the staged rollout gate flips the chain to supported. Until then ?chain=solana validly returns an empty list.

Aave V4 markets and hubs

Aave V4 is hub-and-spoke: a hub pools liquidity per asset and owns the rate accounting, while spokes are the user-facing markets that draw on it, each with its own collateral set and risk policy. Several spokes can share one hub — bespoke risk without fragmenting liquidity.

Each spoke reserve is a vault row in /v1/vaults. The spokes themselves are served as first-class markets by /v1/markets, with supplied/borrowed rollups and hub_address so markets sharing liquidity stay identifiable.

Instances beyond the Aave DAO deployments

Some Aave V4 instances are operated by third parties rather than the Aave DAO. They clear Aave governance (TEMP CHECK / ARFC / AIP) but are absent from the official Aave API and changelog, so Philidor indexes them directly from chain against a reviewed allowlist of hub addresses:

InstanceChainDiscoveryNotes
Aave DAO deploymentsEthereum, AvalancheAave APIMain, Bluechip, Forex, Gold, Lido, Etherfi, …
EtherFi CashOptimismOn-chainether.fi-operated; powers the ether.fi Cash card backend

Numbers for on-chain-discovered instances come from the same on-chain reads as every other Aave V4 row. Two limits are worth knowing: supply caps are not read on-chain, so deposit_capacity_usd is null rather than unlimited; and borrow availability is reported unknown rather than inferred — on EtherFi Cash, borrowing is permissioned to KYC'd cardholders while supply is open.

Key Auditors

Across all protocols, primary audit firms include OpenZeppelin, Trail of Bits, ChainSecurity, Spearbit, Cantina, Certora, Zellic, ABDK, and PeckShield.

Contest platforms such as Code4rena and Sherlock receive additional credit in audit density scoring.

Notable Incidents

ProtocolDateIncidentLoss EvidenceSeverity
Yearn2021-02-05yDAI V1 Flash LoanMaterialMajor v1
Yearn2023-03-13Euler exposureMaterialMajor v2
Yearn2023-04-13yUSDT Legacy iearnMaterialMajor v1
Aave2022-06-24Harmony Bridge HackPeripheralMinor
Aave2024-08-28ParaSwap Adapter exploitPeripheralMinor
Spark2020-03-12MakerDAO Black ThursdayDependencyMajor
Beefy2024-05-14Sonne Finance exposureNone recordedMinor

Incidents affect the Platform vector through severity-aware incident caps.

Using Protocol Filters

curl "https://api.philidor.io/v1/vaults?protocol=morpho"
curl "https://api.philidor.io/v1/protocols/morpho"

On this page

Raw