femtos

HyperCore · Bridge & wallet

Wallet stream

Every event of the three layers touching one address.

WebSocket channel wallet on wss://api.femtos.xyz/v1/ws

Parameters

ParamInExample or values
addressfilter<address>
channelfilter(optional)

Subscribe

{"op":"subscribe","channel":"wallet","filter":{"address":"<address>"}}

Key: Authorization: Bearer $FEMTOS_KEY or X-API-KEY. Get a free key, or with no browser through agent onboarding.

Response fields

FieldTypeMeaning
snapshot: trueobject[]last 50 events
data{channel, data}one event: hc.trades, hc.orders, hc.ledger, bridge.transfers…
channelfilterkinds to keep, comma list

Related: Bridge & wallet

  • Bridge transfers GET /v1/bridges
    Matched HyperCore ↔ HyperEVM transfers with 24 h stats.
  • Bridge coverage GET /v1/bridges/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.
  • 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.
  • Ledger stream WS hc.ledger
    Deposits, withdrawals, transfers and other non-trade balance moves.

More