Key Concepts

Understand vaults, risk scores, Prime/Core/Edge tiers, and the four scoring vectors.

Vaults

A vault is a tokenized or account-based yield position. On EVM chains most rows are ERC-4626 vaults or lending-market reserves; on Solana they are Kamino kVaults and K-Lend reserves. Users deposit assets such as USDC and earn yield through lending, liquidity provision, staking, or more complex strategies; each row is scored with the same four-vector methodology regardless of chain.

Philidor tracks 800+ vaults across 11 protocol modules and 10 chains.

Risk Scores

Every vault receives a composite risk score from 0 to 10, where higher indicates stronger relative resilience under the current methodology and evidence state.

The model is deterministic for a given input state and methodology version.

Score = 0.30 × Asset
  + 0.30 × Platform and Strategy
  + 0.20 × Control and Governance
  + 0.20 × History

Scores are recomputed on hourly sync cycles, with incident-triggered rescoring within minutes. See the full Risk Framework for scoring details.

Risk Tiers

Vaults are classified into three tiers based on their composite score.

TierScore RangeInterpretation
Prime8.0 - 10.0Strong relative resilience
Core5.0 - 7.9Moderate resilience with constraints
Edge0.0 - 4.9Elevated or unresolved modeled risk pressure

The framework also emits a suitability label using review status, confidence, flags, and score criteria.

The API publishes published_risk_tier with boundary stability. Promotions dwell for 6 hours, demotions dwell for 24 hours, and hard floors publish material deterioration immediately. See Published-Tier Stability.

Tiers are relative risk classifications, not recommendations. Prime means strongest observable security characteristics, not safety.

Risk Vectors

Four vectors measure distinct dimensions of risk.

Asset Composition (30%)

Quality of underlying assets using category-specific dimensions. Asset scoring is cap-driven, and review status, hard-fail flags, overrides, staleness, and unresolved address safeguards can bind.

Platform and Strategy (30%)

Probability that the protocol code or strategy causes loss. The vector averages Lindy score, audit score, and strategy score, then applies dependency factors and severity-aware incident caps.

Control and Governance (20%)

Depositor exit window and governance control surface. Immutable contracts score 10. AMM no-pause control scores 9. Timelocks score on the live ladder from 9 at seven days to 1 when no timelock exists.

History (20%)

Recent operational instability and confirmed loss history — realized adverse events only (incidents, bad debt, emergency pauses, detected proxy mutations; methodology v4). Events are time-decayed, Warnings have diminishing returns, and confirmed lifetime Critical loss events carry a non-decaying penalty. Governance and cap-management activity is priced by the Control vector instead.

Protocols

11 protocol modules are registered publicly in the indexer, plus Kamino (Solana) staged for rollout. See Supported Protocols for versions, audits, and incident history.

Protocol ModuleDefault Strategy
Aavelending
Aave V4lending
Yearnyield_aggregation
Beefyyield_aggregation
Morphoisolated_lending
Sparklending
Compoundlending
Uniswap V2liquidity_provision
Uniswap V3liquidity_provision
Uniswap V4liquidity_provision
Nestyield_aggregation

Curators

Curators manage vault allocations and parameters. Examples include Gauntlet, Steakhouse, Re7, and MEV Capital. Curators are tracked with their vault portfolios, actions, and track records.

Chains

Active networks are listed below (the authoritative list, with vault counts, slugs and CAIP-2 identifiers, is served live by GET /v1/chains). Coverage is not EVM-only: chain identity is namespace-aware — see Supported Chains for identifier semantics and per-namespace address formats, including Solana.

ChainChain IDFinality
Ethereum164 blocks
Optimism10L2 via L1
Polygon137128 blocks
Base8453L2 via L1
Arbitrum42161L2 via L1
Avalanche431141 block
Stable9880 blocks
Monad1431 block
Plume98866L2 via L1
Plasma97451 block

Events Severity

Events use three public severities.

SeverityMeaning
CriticalLoss, active exploit, material security failure, or outage
WarningMaterial risk signal, degraded state, or parameter change
InfoInformational update, recovery, or routine state change

Severity affects alerts and display floors for every event. The History vector additionally requires the event to be vault-scoped AND inside the incident-class allowlist (realized adverse events; an all-false pause action counts as recovery and is excluded) — see the History vector methodology page.

Holders

Holder endpoints measure ownership concentration for vault share tokens. Public responses separate protocol-managed addresses from external holders, include entity labels where available, and mark coverage as complete or indexing.

APR

APR is stored as a decimal. 0.05 means 5%.

  • apr_net is total APR including base yield and incentive rewards
  • base_apr is native protocol yield only
  • Rewards include token emissions, points, trading fees, and sub-strategies
apr_net = base_apr + SUM(reward APRs)

Next Steps

On this page

Raw