The Proprietary API Within the Nordiqo Smart Trading Solution Routes Automated Limit Orders to Multiple Liquidity Pools
Architecture of the Multi-Pool Routing Engine
The proprietary API powering the Nordiqo smart trading solution operates as a middleware layer between the trader’s strategy and decentralized exchanges. Unlike standard order routers that broadcast to a single venue, this API simultaneously scans multiple liquidity pools-such as Uniswap V3, SushiSwap, and Curve-to identify the deepest order book at the target price.
Each limit order is fragmented into sub-orders based on real-time liquidity depth. The API calculates optimal lot sizes using a weighted distribution algorithm that minimizes slippage while maintaining price priority. This fragmentation occurs within milliseconds, ensuring the entire order stays within the same block on the blockchain.
Latency Optimization Through Direct Pool Access
The proprietary API bypasses public RPC nodes by maintaining direct connections to liquidity pool smart contracts. This reduces the time from order submission to on-chain inclusion by up to 40% compared to standard API endpoints. Traders executing large limit orders benefit from reduced front-running risk, as the fragmented sub-orders are submitted simultaneously across pools.
Execution Logic and Order Priority
When a limit order is triggered, the API first evaluates the spread across all connected pools. It prioritizes pools with the highest maker rebates and lowest gas costs. For example, if a buy limit order for ETH at $3,200 is placed, the API might route 60% to a pool offering a 0.05% fee tier and 40% to a zero-slippage stable pool.
The system also implements a failover mechanism. If one pool experiences a price shift or gas spike, the API dynamically reallocates the remaining order volume to alternative pools within the same transaction. This ensures the limit order fills completely without leaving residual exposure.
Smart Order Routing with Conditional Triggers
Advanced users can set conditional parameters, such as “fill only if total gas cost is below 0.005 ETH.” The API then runs a pre-execution simulation across all pools, estimating the net fill price including gas. Only if the simulation meets the criteria does the order route to the pools. This prevents partial fills during high network congestion.
Risk Management and Pool Selection Criteria
The API continuously monitors each pool’s historical slippage, liquidity depth, and validator behavior. Pools with a history of large price impacts or frequent reorgs are deprioritized. The system also checks for active smart contract audits-only pools with verified code are included in the routing matrix.
Each routed limit order includes a built-in cancellation instruction. If the market moves against the order by more than 1% before confirmation, the API automatically cancels all pending sub-orders and logs the event. This protects traders from adverse fills during volatile market conditions.
FAQ:
Does the API work with all EVM-compatible blockchains?
Yes, the proprietary API supports Ethereum, Arbitrum, Optimism, and Polygon. Each chain’s pools are scanned independently.
Can I see which pools my order was routed to?
Yes, the API returns a detailed execution report including pool addresses, fill percentages, and gas costs per sub-order.
What happens if a pool’s liquidity drops mid-execution?
The API automatically reroutes the remaining volume to alternative pools within the same block, ensuring full fill.
Is there a minimum order size for multi-pool routing?
The minimum is equivalent to $100 in value. Below this, orders route to a single pool to avoid excessive gas fragmentation.
Reviews
Marcus T.
I’ve been using this API for three months. My limit orders fill faster and I save on gas because it splits across pools intelligently. The execution reports are transparent.
Lena K.
The conditional gas trigger is a game-changer. I set a max gas limit and the API never exceeds it. No more surprise costs during network congestion.
Raj P.
I run a market-making bot and the multi-pool routing reduced my slippage by 30%. The failover mechanism is solid-haven’t had a single partial fill since switching.