Data Reference

Supported Chains

10 chains — Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Monad, Plume, Stable, Plasma — with chain IDs and finality confirmation depths.

Philidor tracks vaults across 10 EVM-compatible networks.

ChainChain IDNative CurrencyExplorerFinality Depth
Ethereum1ETHetherscan.io64 blocks (~13 min)
Base8453ETHbasescan.org0 (L2, finality via L1)
Arbitrum42161ETHarbiscan.io0 (L2, finality via L1)
Polygon137MATICpolygonscan.com128 blocks (~4 min)
Optimism10ETHoptimistic.etherscan.io0 (L2, finality via L1)
Avalanche43114AVAXsnowtrace.io1 block (sub-second)
Monad143MONmonadvision.com1 block (sub-second)
Plume98866PLUMEexplorer.plume.org0 (L2, finality via L1)
Stable988USDT0stablescan.xyz0 (inclusion-based)
Plasma9745XPLplasmascan.to1 block (sub-second)

Finality Depths

Philidor only reads finalized blocks to prevent data corruption from chain reorganizations:

  • Ethereum (64 blocks): 2 epochs post-Merge. Provides economic finality.
  • Polygon (128 blocks): Heimdall checkpoint-based finality.
  • Avalanche (1 block): Avalanche consensus provides sub-second finality.
  • Monad (1 block): High-throughput L1 with sub-second block finality.
  • Plasma (1 block): Tether-backed stablecoin L1 (PlasmaBFT), sub-second finality.
  • Stable (0 blocks): Immediate inclusion finality in the chain registry.
  • L2s (0 blocks): L2 sequencers provide ordering; finality is inherited from L1 batch posting (Base, Arbitrum, Optimism, Plume).

See Data Integrity for how finality is enforced.

Using Chain Filters

Filter vaults by chain using the chain parameter:

curl "https://api.philidor.io/v1/vaults?chain=ethereum"
curl "https://api.philidor.io/v1/vaults?chain=ethereum,base"

On this page

Raw