Dynamic Position Sizing Algorithm Development

Faced with the fact that a fixed lot in a trading strategy yields unstable results: risks skyrocket during high volatility, and you miss out on profits when volatility is low. In practice, traders often lose up to 40% of their capital due to improper position sizing. We solve this problem algorithmically—by developing a dynamic calculation of position size that adapts to market conditions and portfolio state. It's based on mathematical methods proven in production across thousands of trades. The risk reduction can save up to 30% compared to a fixed lot size. Contact us for a preliminary assessment of your task.

How the Dynamic Position Sizing Algorithm Solves the Instability Problem

Do not confuse this with manual lot resizing—the algorithm itself calculates the optimal size for each entry. We account for risk per trade (typically 1–2% of capital), current volatility via ATR, portfolio drawdown, and correlation with open positions. The final size is a composition of several filters.

Fixed Fractional (Kelly-inspired)

The base approach: risk a fixed percentage of capital on each trade.

def fixed_fractional_size(capital, risk_pct, entry_price, stop_price):
    risk_amount = capital * risk_pct
    risk_per_unit = abs(entry_price - stop_price)
    qty = risk_amount / risk_per_unit
    return qty

Standard risk_pct: 1–2% per trade. After 20 consecutive losing trades: loss = (0.98)^20 = 33% of capital. Manageable.

Volatility-adjusted sizing

Position size is inversely proportional to volatility: the more volatile the market, the smaller the position.

def volatility_adjusted_size(capital, target_risk_pct, atr, entry_price, atr_multiplier=2.0):
    risk_amount = capital * target_risk_pct
    stop_distance = atr * atr_multiplier  # stop at 2×ATR
    position_value = risk_amount / (stop_distance / entry_price)
    return position_value / entry_price  # in units of asset

When ATR = 3% → stop 6% → position X. When ATR = 1% → stop 2% → position 3X. Result: equal monetary risk across different volatility levels.

Kelly Criterion

The mathematically optimal position size to maximize long-term capital growth, first described by John Kelly in 1956:

Kelly % = W - (1-W)/R
where W = win rate, R = average win/average loss

With W=55%, R=1.5: Kelly = 0.55 - 0.45/1.5 = 0.25 = 25% of capital. This is too aggressive. Usually Half Kelly (12.5%) or Quarter Kelly is used. Full Kelly leads to huge drawdowns despite theoretical optimality.

Drawdown-based scaling

As we approach the maximum drawdown, we reduce position sizes:

def drawdown_scaled_size(base_size, current_equity, peak_equity, 
                          max_drawdown=0.20):
    current_dd = (peak_equity - current_equity) / peak_equity
    
    if current_dd > max_drawdown * 0.75:
        # At 75% of max drawdown — reduce to 50% size
        return base_size * 0.5
    elif current_dd > max_drawdown * 0.5:
        # At 50% of max drawdown — reduce to 75% size
        return base_size * 0.75
    
    return base_size

Correlation adjustment

If the portfolio already holds several correlated positions, adding a new one provides less diversification. The new position size is reduced proportionally to correlation:

def correlation_adjusted_size(base_size, correlation_with_portfolio):
    # If correlation is 0.8 — reduce size to 20% of base
    diversity_factor = 1 - abs(correlation_with_portfolio)
    return base_size * max(diversity_factor, 0.2)  # minimum 20%

Why a Combination of Methods Gives the Best Result

No single method is perfect. Fixed Fractional does not adapt to volatility, Kelly is aggressive, and Volatility-adjusted depends on ATR accuracy. A hybrid approach combines strengths: base risk taken from Fixed Fractional, then adjusted for volatility, drawdown, and correlation. In our tests, the hybrid reduces maximum drawdown by a factor of 2 compared to pure Fixed Fractional while maintaining the same returns.

How We Implement the Algorithm

Our stack: Python (NumPy, Pandas for backtesting) + integration via REST API of your platform (MetaTrader, Binance, Bybit, Custom). Configuration is flexible: you can enable/disable any module. Code undergoes leak testing (static Python analysis).

Example: Hybrid Sizing

Suppose a trader uses Fixed Fractional with 1.5% risk and Kelly on backtest suggests 20%. We combine: base risk = 1.5% * 0.5 (Half Kelly) = 0.75%, then adjust for volatility: if ATR = 2%, stop 4% → position = 0.75% / (4%/current price). The output is a single module with a unified API: calculate_size(capital, volatility, correlation, drawdown). Get a consultation on implementing such a hybrid for your strategy.

Typical Mistakes When Choosing a Method

Process Overview

1. Analytics — we study your strategy, trade history, risk parameters.
2. Design — select method combination, write specification.
3. Implementation — develop module in Python or Solidity/Rust.
4. Testing — backtest on history + forward test, adjust parameters.
5. Deployment — integrate with your platform, documentation, training.

What's Included

• Source code of the sizing module (Python or Solidity).
• Configuration file with parameters.
• Documentation for integration and configuration.
• Access to a private Git repository.
• 2 weeks of support after handover.

Timeline and Estimation

Development time: from 2 to 4 weeks, depending on the complexity of the method combination. To get an estimate for your project, contact us for a free analysis of your strategy and proposed approach.

Why exchange development requires deep domain expertise

We develop exchanges — not 'chart sites,' but matching engines that process thousands of orders per second without delay, route liquidity between pools, and guarantee that no user gains access to others' funds. Teams that start with the UI and postpone the engine 'for later' end up rewriting everything in six months in 90% of cases.

Order Book vs AMM: where most projects break

Centralized exchanges (CEX) are built around an order book + matching engine. Decentralized exchanges (DEX) either also use an order book (dYdX on StarkEx, Serum/OpenBook on Solana) or an AMM with concentrated liquidity (Uniswap v3/v4, Curve, Balancer). A classic mistake when developing a CEX is implementing the matching engine on top of a relational database with transactions for each match. PostgreSQL handles ~500 RPS without special effort, but at peak loads of 5,000–10,000 orders per second, it turns into a deadlock nightmare. The correct architecture: in-memory order book (Redis Sorted Sets or custom C++/Rust structure), asynchronous writing of matches to PostgreSQL via a queue (Kafka/RabbitMQ), and a separate settlement service that finally updates balances.

For DEX, the most painful problem is sandwich attacks and MEV. A pool with a plain xy=k AMM without slippage protection becomes a target for MEV bots within hours of launch. Uniswap v2 lost hundreds of millions of dollars in user liquidity. Solutions: integration with Flashbots Protect, a commit-reveal scheme for orders, or switching to TWAMM (Time-Weighted AMM) for large trades.

Concentrated liquidity and impermanent loss

Uniswap v3 introduced concentrated liquidity – LPs choose a price range in which to provide liquidity. Capital efficiency increased 4,000x compared to v2 for stable pairs. But implementing this mechanism correctly is non-trivial. The Uniswap v3 liquidity contract uses tick-based accounting: the price space is divided into discrete ticks (tick = log₁.0001(price)), each tick stores accumulated fee growth and liquidity delta. When creating a position, the lower and upper ticks are computed, and the contract recalculates all active positions at each swap. Storage layout is critical here – incorrect variable packing in slots easily adds 40–60% to swap gas cost.

We implemented a Uniswap v3 fork for a client on Polygon with a custom fee tier system. The initial version consumed 180k gas for a swap across 2 ticks. After slot packing of variables in Tick.Info and inlining several internal calls, it dropped to 112k gas. This reduced gas costs by 38% and saved the client substantial costs on fees monthly. The techniques applied are described in the Uniswap v3 Whitepaper and confirmed by our audit experience.

How a matching engine delivers performance

A production-ready matching engine is built according to the following scheme:

• Order ingestion layer – WebSocket gateway (Go or Rust), accepts orders, validates signature, checks balance via Redis, queues them. Latency at this level must be <1ms.
• Matching core – single-threaded event loop (eliminates race conditions without mutexes). In memory, we hold two Sorted Sets for each trading instrument: bids and asks. FIFO matching for limit orders, immediate-or-cancel for market orders. Throughput with a proper Rust implementation – 500k–1M matches per second on a single core.
• Settlement service – reads matches from Kafka, atomically updates balances in PostgreSQL (UPDATE accounts SET balance = balance - $1 WHERE id = $2 AND balance >= $1). Optimistic locking via row versioning.
• Withdrawal pipeline – separate service with cold/hot wallet architecture. The hot wallet holds 5–10% of total deposits, the rest is cold storage with multi-sig (Gnosis Safe or custom HSM). Automatic withdrawals only from hot wallet, large amounts require manual authorization.

How our exchange development process ensures reliability

Smart contracts and gas optimization

For EVM-based DEX (Ethereum, Arbitrum, Optimism, Polygon), the entire critical path lives in Solidity. Main contracts: Pool, Factory, Router, PositionManager (for v3-like), and Quoter for off-chain calculations. Typical mistakes we see in audits:

Reentrancy via callback. Uniswap v3 uses flash swap with a callback (uniswapV3SwapCallback). If your router lacks a nonReentrant guard and you don't check msg.sender == pool, the contract gets drained via a nested call. This is not hypothetical – several v3 forks lost funds this way.

Oracle manipulation in AMM. If your contract uses the spot price from the pool for collateral calculation, it is front-runnable. Correct: TWAP over 30+ minutes (Uniswap v3 OracleLib) or an external oracle (Chainlink).

Unbounded loops in liquidity range. If a swap crosses many ticks in a row (price impact 80%+), gas may exceed the block limit. Need MAX_TICKS_CROSSED with partial fill and returning the remainder.

For Solana DEX (Anchor framework, Rust), the architecture is fundamentally different: account-based model, Program Derived Addresses (PDA) instead of storage, Cross-Program Invocations instead of internal calls. Solana's throughput (~3,000–4,000 TPS vs 15–30 on Ethereum mainnet) allows building on-chain order books – exactly what Phoenix DEX does.

Liquidity bootstrapping and aggregator integration

Launching a pool is not enough – you need to ensure liquidity at launch. Practical mechanisms:

• Liquidity Bootstrapping Pool (LBP) – initial price is high, asset weights dynamically shift, creating selling pressure and even token distribution. Implemented in Balancer v2.
• Initial Liquidity Offering via Uniswap v3 – adding liquidity in a narrow range around the initial price, then gradually expanding as volume grows. Requires active liquidity management or integration with Arrakis/Gamma.
• Integration with 1inch, Paraswap, Li.Fi – aggregators bring traffic but require standard compliance: the pool must have correct getAmountsOut, support ERC-20 approval/permit, and not have custom transfer hooks that break the aggregator's routing.

Development process and deliverables

Analytics and design begin with choosing the architectural model: CEX with custodial storage, non-custodial DEX, or hybrid (off-chain order book + on-chain settlement, like dYdX v3). This decision determines everything – regulatory load, tech stack, team.

Development proceeds in layers: first smart contracts with full Foundry coverage (fuzzing, invariant testing), then backend services, then integration layer, and finally frontend. Testing includes fork testing on mainnet via Foundry – we reproduce real liquidity conditions, not synthetic ones.

Audit is mandatory before mainnet deployment. For DEX contracts, minimally one firm with manual review (Trail of Bits, Spearbit, Code4rena contest). For CEX custody, audit of key storage processes. We guarantee all contracts undergo formal verification and fuzzing testing (Echidna, Foundry invariant).

Estimated timelines

Cost is calculated individually after a technical briefing: chain selection, throughput requirements, custodial model. Our certified engineers with 10+ years of experience will help you choose the optimal architecture and avoid common pitfalls. Contact our team for a detailed proposal.

Pitfalls to avoid at launch

• Forgetting the price oracle in AMM. Spot price can be manipulated with a flash loan in one transaction. If your lending protocol uses the spot price from its own pool, that's a bug.
• Hot wallet without limits. A CEX without daily limits on automatic withdrawals is an invitation for attackers. Compromising one key should lose at most 10% of total funds.
• Absence of circuit breaker. A 40% price drop in 5 minutes should halt automatic liquidations or withdrawals until manual review. Without this, a cascading liquidation spiral destroys all TVL.
• Incorrect decimal handling. USDC uses 6 decimals, WBTC – 8, most tokens – 18. Mixing without normalization leads to either precision loss or overflow. Solidity has no float; we work with fixed-point using FullMath (mulDiv with overflow protection).

Want to avoid these problems? Get a consultation — we will select the architecture for your project and provide exact timelines. Order exchange development with quality guarantee and ongoing support.