Repository navigation
π‘ RFC: Live Execution Adapters β CCXT vs. Native Async WebSockets (Bybit / Interactive Brokers) #182
NeoNix-Lab
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Context & Objective
Quant Platform has established a deterministic, event-driven foundation with historical replay (
H05), an order state machine (H01), explicit fee and slippage models (H02), and intra-bar conflict resolvers (H03).The next major frontier is Live Broker Execution: translating simulated execution semantics into real-world market connectivity without violating our core temporal and causal invariants.
The Architectural Choice: CCXT vs. Native Async WebSockets
Option A: CCXT / CCXT Pro
Option B: Native Async WebSockets & FIX Protocols (Exchange-Tailored)
Architectural Guardrails per AGENTS.md
PENDING_NEW->NEW->PARTIALLY_FILLED->FILLED/CANCELED) as historical replay.Instant) without relying on system wall-clock jumps.Open Questions for Discussion
Drop your thoughts, latency benchmarks, or architectural proposals below!
All reactions