femtos

HyperCore · 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

ParamInExample or values
windowqueryall, 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

FieldTypeMeaning
directions.evm_to_core · core_to_evmobject{legs, matched, coverage, unmatched: {reason: n}, notALeg, latencyMs: {p50, p90, p99, p999, max}, tokens[]}
coveragenumbermatched / (legs − not legs − in flight): 1 = every settled leg has its other leg
unmatchedobjectin_flight · missing_peer · amount_mismatch · late_peer · unknown_token
core_to_evm.matchedByobject{nonce: exact (coreReceiveWithData), order: same key in order}
unpairedCreditsobject | nullcredits on the receiving side no leg took
source · settledUntilstring · msmaterialized tables (and how far they are settled) or the views

Related: Bridge & wallet

  • Bridge transfers GET /v1/bridges
    Matched HyperCore ↔ HyperEVM transfers 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.
  • Wallet stream WS wallet
    Every event of the three layers touching one address.
  • Ledger stream WS hc.ledger
    Deposits, withdrawals, transfers and other non-trade balance moves.

More