Coverage Matrix
Per-chain coverage status across all supported networks.
As of 2026-05-04 · Schema v1
Stage taxonomy
General Availability — full historical depth within stated window. Compliance-grade.
Active migration / soak window. Coverage windows may temporarily vary; reports reflect data available at scan time.
Pre-v1 — reports may have incomplete depth or gaps. Not for compliance-grade decisions yet.
Known operational incident. See incident link for status.
Per-chain status
| Chain | Stage | Window | Data path | GA target / notes |
|---|---|---|---|---|
| arbitrum | Rollout | 30d | Self-hosted index | Earliest planning anchor ~2026-05-13 (depends on phase a v1 + 7-day clean soak; not contractual) |
| avalanche | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| base | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| cardano | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| celo | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| cosmos | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| cronos | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| eth | Rollout | n/a (passthrough) | Public RPC | Phase e v1 — earliest target post-phase-d, lean approachRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| fantom | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| linea | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| ltc | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| moonbeam | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| multichain | Rollout | n/a (passthrough) | Aggregate per chain | Per-chain coverage breakdown is a follow-up tied to hybrid read model v1 fields (served from / fallback used / historical completeness) |
| optimism | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| polygon | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| polygon_zkevm | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| scroll | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| sol | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| ton | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| xrp | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| zksync | Rollout | n/a (passthrough) | Third-party API | Post-v1 multichain hardeningRisk scoring for this network currently uses the upstream provider's data path. OnChainRisk's local node-backed indexing for this network is in active rollout. |
| bsc | Preview | n/a (passthrough) | Tbd phase b v1 | Phase b v1 — earliest target window 2026-05-13 to 2026-05-22 (planning, not commit)Risk scoring for this network uses third-party API data. |
| btc | Preview | n/a (passthrough) | Tbd phase c v1 | Phase c v1 — earliest target post-phase-b + bitcoin core ibd (3-5 days planning)Risk scoring for this network uses third-party API data. |
| tron | Preview | n/a (passthrough) | Tbd phase d v1 | Phase d v1 — earliest ≥7 days after tron readiness gates close (gates blocked on fullnode sync; no firm date)Risk scoring for this network uses third-party API data. |
What “rollout” means in practice
OnChainRisk's multi-chain coverage is in active rollout. We're upgrading our infrastructure across supported networks; during this rollout, coverage windows and historical depth may temporarily vary by chain. Reports reflect data available at the time of the scan against the current production data path for each network.
Full historical completeness is not yet guaranteed across all supported networks during the rollout phase. The matrix above is updated when chain stages change — typically when a chain's phase v1 ships and clears a 7-day clean post-launch soak.
For compliance-grade decisions on a chain not yet at General Availability, contact us — we can surface the current GA target and any active incidents.
Integrating with the API
Every report response from the OnChainRisk API includes a coverage block with the current stage, window, and disclosure text for the chain being scanned. Clients integrating OnChainRisk are required to surface the coverage.disclosure field to end users when stage != ga. For preview and degraded stages, the response also includes a warning field that clients MUST surface prominently.
See the API reference for the full Coverage schema, or fetch the canonical machine-readable matrix at data/coverage/matrix.json.
Update cadence
This matrix changes when a chain's stage transitions (typically preview → rollout on phase kickoff, or rollout → ga after 7-day clean soak post-launch). Operational incidents flip a chain to degraded until resolved. All transitions land via PR to GitHub and propagate to the API + UI in the same deploy cycle.