04 / Execution algorithms
AvailableWork large crypto orders over time without telling the market
Qubit's algorithms slice a parent order into child orders on a schedule, in line with market volume or against a price, across one venue or many. Every parameter can be changed while the order is working, and every child order traces back to its parent.
- Layer
- Standalone
- Works on its own
- Yes
- Interfaces
- Blotter, REST, WebSocket, FIX
01 / The problem
A block order sent at once moves the price against you
Crypto order books are thinner than they look, and the market notices size. A large buy sent as one order walks the book and pays for every level it takes. Working it by hand means a trader watching a screen for hours, slicing by feel, with no way to show a client afterward that the execution was disciplined.
02 / What it does
The algorithms
- 01
TWAP
Executes evenly across a time window. Use it when you want a predictable pace and the benchmark is the time-weighted average price.
- 02
VWAP
Follows the expected intraday volume curve for the instrument, trading more when the market usually trades more. Use it when the benchmark is the interval VWAP.
- 03
POV (percentage of volume)
Targets a share of the volume printed on the selected venues, speeding up and slowing down with the market.
- 04
Iceberg
Shows a small visible quantity and replenishes it as it fills, keeping the full size off the book.
- 05
Pegged
Keeps a limit order pegged to the best bid, best offer or mid, with an optional offset, and reprices as the market moves.
- 06
Liquidity seeking
Rests passively, then takes displayed liquidity across venues when it appears at or better than a trigger price. Use it for opportunistic fills on large orders.
- 07
Steady pace
Sends a fixed child size at a fixed interval, with randomization so the pattern is harder to detect.
03 / How it works
From parent order to child orders
- 01
Configure
The trader or the client's system chooses an algorithm and sets parameters: quantity, start and end time, limit price, participation rate, venues.
- 02
Check
The parent order passes pre-trade risk as a whole, and each child order is checked again before it is sent.
- 03
Slice
The algorithm decides the size, timing, price and venue of each child order from the schedule, live market data and fills so far.
- 04
Adapt
It speeds up or slows down against its target, reprices passive orders and respects the limit price and venue constraints throughout.
- 05
Report
Progress against schedule, average price, benchmark and slippage are visible live, and the full record flows to TCA.
04 / Specifics
Technical specifics
- Common parameters
Total quantity (base or quote), side, limit price, start time, end time or duration, venues to include or exclude, minimum and maximum child size, randomization of size and timing, and post-only or take behavior.
- Algorithm-specific parameters
Per algorithm:
- TWAP and steady pace: number of slices or slice interval, catch-up behavior if behind schedule.
- VWAP: volume profile source (historical curve per instrument), maximum deviation from the curve.
- POV: target participation rate, minimum and maximum rate, venues counted in the volume denominator.
- Iceberg: display quantity, display variance.
- Pegged: peg reference (bid, offer, mid), offset in ticks or basis points, reprice threshold.
- Liquidity seeking: trigger price, maximum take size per sweep, resting behavior between sweeps.
- In-flight controls
Pause, resume, amend quantity, amend limit price, amend participation rate or end time, cancel with or without canceling working child orders.
- Order entry
Algo parent orders can be sent from the Qubit blotter, over REST and WebSocket, or over FIX using strategy parameter tags agreed per session.
- Live analytics per parent
Percentage complete, schedule deviation, average price, arrival price, slippage to arrival and to interval VWAP.
05 / Controls and audit
What you configure, and what gets written down
Configurable
- Algorithm and its parameters per parent order
- Venues to include or exclude
- Minimum and maximum child size
- Randomization of size and timing
- Post-only or take behavior
- Catch-up behavior when behind schedule
Logged to the audit trail
- parent order received · algorithm and parameters
- pre-trade check on the parent and on each child
- child order sent · size, price, venue, time
- pause, resume and cancel
- parameter amended · old and new values, user
- progress against schedule, average price, slippage
06 / Where it fits
- Works on its own
- Yes, together with the unified exchange API. Your OMS sends a parent order with algo parameters; Qubit works it on your venues.
- Needs the core
- No. Inside the core, algorithms also use the smart order router to place child orders across venues.
- Who uses it
- OTC desks working client blocks, asset managers and hedge funds, prop firms, brokers executing client orders on an agency basis.
FAQ
Questions we get asked
Can algorithms trade across several venues at once?
Yes. With the core platform, child orders go through the smart order router and can fill on any eligible venue. With the standalone module, the algorithm works across the venues you select through the unified exchange API.
What if the market moves through our limit price?
The algorithm stops sending child orders that would breach the limit, keeps any passive orders inside it and resumes when the market comes back. It does not chase.
Can we change parameters mid-order without canceling?
Yes. Quantity, limit price, end time and participation rate can be amended while the order is working. The algorithm recalculates its schedule from that point.
Can our quants add their own algorithms?
Clients with source access can add strategies against the same interface the built-in algorithms use, and those strategies inherit risk checks, routing, audit and TCA.
Execute size with a record you can show your clients
A scoping call with an engineer, then a demo on sample data that mirrors your venues, desks and limits.