femtosHyperEVM · Bridge & wallet
Bridge coverage
Every HyperCore ↔ HyperEVM leg since our data starts, paired with its other leg: matched share per direction and token, why the others are not, latency.
GET https://api.femtos.xyz/v1/bridges/coverage
Parameters
| Param | In | Example or values |
|---|---|---|
window | query | all, 30d, 7d, 24h |
Example
curl -H "Authorization: Bearer $FEMTOS_KEY" "https://api.femtos.xyz/v1/bridges/coverage?window=all"Key: Authorization: Bearer $FEMTOS_KEY or X-API-KEY. Get a free key, or with no browser through agent onboarding.
Response fields
| Field | Type | Meaning |
|---|---|---|
directions.evm_to_core · core_to_evm | object | {legs, matched, coverage, unmatched: {reason: n}, notALeg, latencyMs: {p50, p90, p99, p999, max}, tokens[]} |
coverage | number | matched / (legs − not legs − in flight): 1 = every settled leg has its other leg |
unmatched | object | in_flight · missing_peer · amount_mismatch · late_peer · unknown_token |
core_to_evm.matchedBy | object | {nonce: exact (coreReceiveWithData), order: same key in order} |
unpairedCredits | object | null | credits on the receiving side no leg took |
source · settledUntil | string · ms | materialized tables (and how far they are settled) or the views |
Related: Bridge & wallet
- Bridge transfers GET /v1/bridges
HyperCore ↔ HyperEVM transfers (core_evm) or HyperEVM ↔ Elysium movements (evm_elysium), with 24 h stats. - Bridge stream WS bridge.transfers
Each HyperCore ↔ HyperEVM transfer, initiated then completed. - Cross-layer wallet GET /v1/wallet/{address}
One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events.