CCXT Integration
Current capabilities and operational boundaries of Sidepit's CCXT adapter.
Sidepit maintains a CCXT-shaped adapter in Public-API/integrations/ccxt. It runs through the repository's optional local REST/WebSocket facade and has not yet been submitted upstream to CCXT.
Capability contract
createOrder: truecreateMarketOrder: truemarket
timeInForce: IOClimit and market orders, cancel, balances, positions, open orders, trades, ticker, depth, bars, and account-scoped order observation
CCXT Pro watches for ticker, order book, trades, one-minute bars, orders, and account trades
Native market orders omit price so protobuf uses NewOrder.price=0. The adapter returns an optimistic open status after submission because the next DLOB one-second deterministic auction determines the outcome. Confirm it with fetchOrder, fetchOpenOrders, watchOrders, and rejections.
Price conversion
Sidepit's native integer price is sats per USD. The adapter exposes unified BTC per USD:
BTC-per-USD = sats-per-USD × 0.00000001
Conversion happens once at the adapter boundary.
Credentials
For delegated trading:
apiKeyis the owner's publicbc1qSidepit ID;secretis the restricted agent's signing secret; andoptions.traderIdis that agent key's derivedbc1qaddress.
Never configure the owner's money key as an automated trading secret. Keep the local facade local: the adapter serializes and signs client-side, and the relay should receive signed bytes rather than custody a key.
Build and smoke test
Follow the current integrations/ccxt/README.md. The smoke test distinguishes closed-session reads from an explicitly funded live cycle and verifies offline that market wire bytes omit the price field.
Last updated
Was this helpful?