Objective
Expose one coherent execution architecture where local orderbook, DEX routing, and CEX adapters can be reasoned about consistently.
CEX/DEX Node Topology
ProductionExecution paths are split by venue type but unified by a common routing and audit model.
Node Roles
Trading Node handles market interfaces, order lifecycle, and terminal UX. Gateway Node handles cross-node API ingress and routing.
Settlement and Clearing nodes can be attached for post-trade netting and cross-entity reconciliation.
CEX Connector Plane
Network mode supports exchange API-key integration with restricted scopes (read + trade, no withdraw).
Connector outputs are normalized into a unified portfolio and execution context for route comparison and best-execution policies.
DEX Execution Plane
DEX routing evaluates pools and routes with explicit slippage and gas constraints before execution confirmation.
Receipts preserve execution intent, selected route, and resulting settlement references.
Interfaces
Trading API
Ticker, orderbook, trades, order placement, cancel/replace
Connector API
Exchange onboarding, permission check, connectivity status
Production Checkpoints
- ✓Venue routing policy is explicit and auditable
- ✓Connector keys are encrypted at rest
- ✓Portfolio view merges CEX + local positions consistently
- ✓All fills and cancellations produce traceable receipts
Continue exploring