Data Reference
Supported Chains
Blockchain networks tracked by Philidor with chain IDs and finality depths.
Philidor tracks vaults across 6 EVM-compatible networks.
| Chain | Chain ID | Native Currency | Explorer | Finality Depth |
|---|---|---|---|---|
| Ethereum | 1 | ETH | etherscan.io | 64 blocks (~13 min) |
| Base | 8453 | ETH | basescan.org | 0 (L2, finality via L1) |
| Arbitrum | 42161 | ETH | arbiscan.io | 0 (L2, finality via L1) |
| Polygon | 137 | MATIC | polygonscan.com | 128 blocks (~4 min) |
| Optimism | 10 | ETH | optimistic.etherscan.io | 0 (L2, finality via L1) |
| Avalanche | 43114 | AVAX | snowtrace.io | 1 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.
- L2s (0 blocks): L2 sequencers provide ordering; finality is inherited from L1 batch posting.
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"