API reference · Bridges & wallets

Ledger stream

Deposits, withdrawals, transfers and other non-trade balance moves.

Not on Elysium or HyperEVM: HyperCore’s ledger (deposits, withdrawals, transfers): an EVM wallet’s moves are its ERC-20 transfers and the wallet stream

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

Parameters

Param	In	Example or values	Meaning
`kind`	filter	(optional)	Update kind: spotTransfer, send, deposit, withdraw…
`token`	filter	(optional)	Token
`min_amount`	filter	(optional)	Minimum amount

{"op":"subscribe","channel":"hc.ledger","filter":{}}

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

Field	Type	Meaning
`data`	HcLedgerUpdate	deposits, withdrawals, transfers and other non-trade balance moves: {kind, user, token, amount, usdc_value, destination, hash, block, time, users, fee, fee_token, …}
`data.kind`	string	spotTransfer, send, deposit, withdraw, borrowLend…

Cross-layer wallet GET /v1/wallet/{address} Elysium, HyperCore, HyperEVM
One address (or a named wallet's handle) on HyperCore, HyperEVM and Elysium, plus its latest events.
Wallet stream WS wallet Elysium, HyperCore, HyperEVM
Every event of the three layers touching one address.
Swaps by wallet GET /v1/trades Elysium, HyperEVM
Every swap a wallet sent (or a pool’s, a token’s), newest first, filterable by token, side, size and time.
Transfers by wallet GET /v1/transfers Elysium, HyperEVM
ERC-20 transfers sent and received by a wallet, newest first, filterable by token, direction, size and time.
Bridge movements GET /v1/bridges Elysium, HyperCore, HyperEVM
Matched HyperCore ↔ HyperEVM transfers with 24 h stats.
Bridge stream WS elysium.bridge · bridge.transfers Elysium, HyperCore, HyperEVM
Each HyperCore ↔ HyperEVM transfer, initiated then completed.
Bridge coverage GET /v1/bridges/coverage HyperCore, HyperEVM
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.