From 47% to 1% Used Capacity: How I Scaled My Capacity with the New MT5 Order Splitter

First: What is the Darwinex Order Splitter?

The Darwinex Order Splitter is an open-source MetaTrader execution tool that slices large block orders into smaller, time-weighted tranches. This absorbs liquidity systematically, prevents slippage on thin order books, and drastically improves a strategy's Capacity (Cp) to manage institutional capital without degrading its returns.

Today, we step away from theory. I am Kieran, Head of the Darwinex Zero UK growth team and the manager behind the DARWIN XAQP.

Over the last two months, I deployed our new open-source MetaTrader Order Splitter to completely restructure my execution footprint. Here is what happens when you hit your capacity ceiling, how we engineered the solution, and the hard telemetry behind the results.

Lee este artículo en español aquí

⚠️ Alpha Software. Use at your own risk.

This is alpha-stage code and has not been battle-tested across brokers, symbols, or live market conditions. It is your responsibility to review the source, run the library on a demo account, and verify its behaviour end-to-end before deploying it with real funds.

The authors and contributors accept no liability for trading losses, execution errors, partial fills, missed closes, slippage, broker rejections, or any other financial or operational consequence arising from the use of this software. The library is provided "AS IS", without warranties of any kind. See Sections 7 and 8 of the Apache License 2.0 in the repo for the full disclaimer.

The Execution Bottleneck

Attracting investor capital is the objective. However, as your Assets Under Management (AUM) scale, you face a new mechanical enemy. Market impact.

By late March, XAQP had scaled to $1,672,493.24 in investor capital. The capital was there, but the infrastructure was straining. My Used Capacity had spiked to 47.08%.

Capacity (Cp) estimates the maximum capital your strategy can manage before market impact destroys your returns. It is your structural glass ceiling.

The vulnerability was liquidity. Several of my models execute around the Sunday evening open. This period is defined by notoriously thin order books. When my underlying account triggered a trade, the risk engine replicated it across that $1.67M block of investor capital. That aggregate order chewed through the thin liquidity, generating entirely avoidable slippage.

Left unchecked, this slippage would hard-cap my allocations from the INDX master fund. I had to stop sending block orders and start absorbing liquidity like an institutional desk.

Engineering the TWAP Splitter

The mathematical solution was a Time-Weighted Average Price (TWAP) execution. This requires slicing the block order into smaller tranches spaced seconds apart.

I initially built a rough proof-of-concept. Martí, our Quant Developer at Darwinex Labs, then manually rebuilt the state machines, stress-tested the maths, and engineered the robust, open-source library we released last week.

A major friction point for algorithmic operators is integration. My portfolio is highly hybrid. I run models built in StrategyQuant X (SQX), FX Dreema, and raw manual code. The splitter integrated seamlessly across all of them.

I dynamically configure the splitter based on the asset. A highly liquid FX major requires fewer splits and shorter delays. A thin cross-pair on a Sunday open requires a staggered, drawn-out execution to let the order book replenish.

The Telemetry

I pushed the order-splitting code to live production across my portfolio in April. The structural impact was immediate.

Here is the exact telemetry before and after deployment:

• March 26th (Before Splitting): Investor AUM at $1,672,493.24 with Used Capacity at 47.08%.
• May 28th (Post-Splitting): Investor AUM at $1,778,013.66 with Used Capacity at 1.04%.

My managed capital increased by over $100,000, yet my market footprint essentially vanished.

I did not alter my core strategy logic. I simply upgraded the execution architecture. XAQP is now mathematically positioned to absorb significantly more capital without degrading its edge.

The Mandate for Scale

Capacity is not a metric you should ignore, or leave to late to recognise the importance thereof. It provides an institutional scalability analysis.

Large amounts of capital will only flow to assets with the structural headroom to absorb it. By fixing your execution footprint, you expand the allocatable AUM for yourself, but also for the entire ecosystem.

The open-source code, SQX adapters, and test EA are freely available in our GitHub repository here.

If you are running a live DARWIN and have questions about the XAQP implementation, drop them in the Discord.

Build the logic. Respect the data.

Thanks for reading, 
Kieran Duff,  Community Developer (UK)  

*Darwinex Zero and the domain www.darwinexzero.com are trade names used by Tradeslide Technologies, a company registered in the United Kingdom under number 14398381.

The contents of this blog post and video are for educational purposes only and should not be construed as financial and/or investment advice.