Scope note
This page maps common Binance- and Bybit-style client concepts to current DerivaDEX public routes. It is not the canonical source for those exchanges’ current APIs, limits, or field catalogs. Use it to translate client assumptions, not to replace vendor documentation.Account and position model mapping
| Common CEX-side assumption | DerivaDEX-side concept | Owning public route |
|---|---|---|
| exchange account balance | strategy-scoped collateral and strategy state | Margin Requirements |
| exchange-managed sub-balance or position bucket | strategy identifier under one trader wallet | For Traders |
| exchange acknowledges order placement as one primary state event | sequencing acknowledgement plus later lifecycle updates | Request Lifecycle: Sequencing, Execution, and Finality |
Order lifecycle mapping
| Client concern | DerivaDEX-side reading | Owning public route |
|---|---|---|
| submission accepted | request crossed the sequencing boundary | How to Handle Order Sequencing vs Execution |
| order state changes | ORDER_UPDATE plus related strategy or trader updates | Order and Account Event Reference |
| terminal outcome | filled, canceled, rejected, or liquidated state after correlated lifecycle handling | How to Track an Order Through Its Lifecycle |
Pricing and risk mapping
| Common assumption | DerivaDEX-side reading | Owning public route |
|---|---|---|
| last trade price is the main operational anchor | mark price governs margin, liquidation, and key safeguards | Price Feeds and Mark Price Inputs |
| leverage or margin checks are separate from execution guidance | safety, solvency, and execution guards are coupled | Trading Safeties and Guards |
| liquidation is only a late-stage exceptional event | liquidation and ADL are explicit public mechanism paths | Price Formation, Risk Controls, and Solvency |
REST and realtime mapping
| Client concern | DerivaDEX-side reading | Owning public route |
|---|---|---|
| polling-only recovery model | REST bootstrap plus realtime continuation | Realtime Connection Model |
| WebSocket continuity is enough by itself | reconnects require explicit REST truth repair | How to Monitor Trading Activity Reliably |
| subscription acknowledgement equals business success | transport control and business outcomes are separate | Realtime Errors |
Failure and retry mapping
| Client concern | DerivaDEX-side reading | Owning public route |
|---|---|---|
| any retryable rejection should be retried unchanged | replay-window, safety, and service faults need different handling | Error Reference |
| rate pressure is one generic problem | REST quota posture and realtime control posture differ | REST Rate Limits and Realtime Rate Limits |
| invalid request path can be repaired without rebuilding signing context | many request repairs require new replay-window and cryptographic material | Request Signing Reference and Request Encryption Reference |
Migration reading order
- How to Migrate from Binance or Bybit to DerivaDEX
- For Traders or For Builders, depending on who owns the client
- Order and Account Event Reference
- Error Reference