Multi-Provider

The perpetual venues @lifi/perps-sdk supports through one interface

@lifi/perps-sdk trades across multiple perpetual venues through a single, unified interface. Each venue is integrated as a provider with its own setup, signing scheme, and market data; you pick one per call via the provider argument and the SDK handles the venue-specific details transparently. Each provider tracks its setup and trading signer independently.

Currently supported venues:

• Hyperliquid — an order-book perpetuals exchange on its own L1. Trades use an SDK-managed agent wallet approved once by the user.
• Lighter — lighter mainnet and lighter-rh expose the same normalized contract with deployment-specific endpoints, collateral, and credentials. Trades use a Lighter-native key registered on-chain.
• Ondo — a session-backed venue whose trading requests are HMAC-signed client-side with the user’s registered venue key.

​

Capability differences

The SDK normalizes the request and response shapes. The venue behaviour underneath still differs. Read getProviders() for the actions and signers each provider advertises, and check the rows below before you build a provider-agnostic screen.

	Hyperliquid	Lighter	Ondo
Trading signer	SDK-managed agent wallet, approved once by the user	Lighter-native API key, registered on-chain once	Venue API key: each request is HMAC-signed and relayed by the backend, after a SIWE login
Margin modes	CROSS and ISOLATED; no default	CROSS and ISOLATED; isolated-only markets exist	CROSS only
Time in force	GTC, IOC, POST_ONLY	GTC, IOC, POST_ONLY	GTC, IOC, POST_ONLY on limit orders
expiresAt	Ignored	Honoured on GTC and POST_ONLY	Rejected
Bundled takeProfit / stopLoss on placeOrder	Yes	Yes on perps; not on spot	Yes, at market, always closing the whole position
Trigger leg limitPrice	MARKET leg: rejected. LIMIT leg: required	Required on each leg. On a MARKET leg, the slippage-adjusted limit price	MARKET legs only. limitPrice rejected
Modify can change the trigger order type	Yes	No. type is rejected	No modifyOrder action
Deposit flow (getDepositFlow)	lifiSwap into Hyperliquid USDC	lifiSwap for an existing account; venueDepositPipeline when the address has no account	setupRequired until a session and deposit address exist, then lifiSwap to the per-user address
Withdrawal flow (getWithdrawFlow)	Not defined	Not defined	setupRequired until the destination is in the address book, then ready
WebSocket candle channel	Yes	No	Yes
WebSocket spotBalances channel	Yes	No	Empty snapshot only
WebSocket availableToTrade channel	Yes	No	No

See Placing Orders for the per-provider time-in-force details and Streaming for the full channel table.

See each venue’s Providers section for its signing model, setup, trading actions, and streaming protocol.