Backtesting with Fees and Slippage: Accurate Cost Modeling

Realistic crypto strategy backtesting is impossible without accounting for all costs: commissions, slippage, and funding rates. Ignoring these factors leads to inflated expectations — a strategy showing 30% annualized on historical data can easily turn negative in reality. For example, a strategy executing 100 trades per month with a 0.1% taker fee eats 10% of capital annually. Add market impact and funding, and you see the true return.

We develop systems that honestly account for all trading costs, including exchange fees, slippage, and funding rates. This approach reveals true performance and avoids illusions. One client shared a strategy showing 40% annualized on historical data without costs. After adding real fees and slippage, the return dropped to 12%, and with funding rate to 5%. This is a typical scenario where illusions turn into disappointment. We know how to avoid that. Order a cost model and get truthful analysis.

Why Backtesting Without Fees Is Useless

Even tiny costs accumulate: a 0.1% taker fee per trade with 100 trades per month consumes 10% of capital annually. Add slippage, and a strategy that seemed profitable turns negative. A realistic backtest must include:

• Exchange fees: maker/taker, VIP discounts, rebates
• Slippage: market impact, bid-ask spread, gap slippage
• Funding rate for futures: payments every 8 hours
• Indirect costs: latency, network fees

One client brought a strategy with 25% annualized on historical data without fees. After including the real fee schedule and slippage, the result dropped to 9%, and with funding rate to 4%. Only then did they realize that trading low-volume futures was consuming all profits. Our hybrid approach to slippage modeling helps avoid such surprises: it is at least twice as accurate as a fixed value on real data.

How to Correctly Account for Slippage

There is no single model. For low-volume strategies, a fixed percentage suffices. For large orders, a market impact model is needed — slippage grows with position size relative to candle volume. We use a hybrid approach: a combination of fixed spread and volume impact. Here is an example implementation of fixed slippage:

class FixedSlippage(SlippageModel):
    def __init__(self, slippage_pct: float = 0.0005):
        self.slippage_pct = slippage_pct

    def get_fill_price(self, order_price: float, bar, side: str) -> float:
        if side == 'BUY':
            return order_price * (1 + self.slippage_pct)
        else:
            return order_price * (1 - self.slippage_pct)

And for volume-dependent slippage:

class VolumeImpactSlippage(SlippageModel):
    def __init__(self, impact_factor: float = 0.1):
        self.impact_factor = impact_factor

    def get_fill_price(self, order_price: float, bar, side: str, order_size_usd: float = 0) -> float:
        bar_volume_usd = bar.volume * bar.close
        market_impact = self.impact_factor * order_size_usd / bar_volume_usd if bar_volume_usd > 0 else 0
        if side == 'BUY':
            return order_price * (1 + market_impact)
        else:
            return order_price * (1 - market_impact)

Fee Structure: Realistic Schedules

Many strategies are designed for a specific exchange, so it is essential to incorporate its fee schedule. Here is an example for Binance Spot with VIP tiers:

@dataclass
class FeeSchedule:
    maker_fee: float
    taker_fee: float
    vip_tiers: list[tuple[float, float, float]] = None

    def get_fee(self, order_type: OrderType, volume_30d: float = 0) -> float:
        if self.vip_tiers and volume_30d > 0:
            for min_vol, maker, taker in sorted(self.vip_tiers, reverse=True):
                if volume_30d >= min_vol:
                    return maker if order_type != OrderType.MARKET else taker
        if order_type == OrderType.MARKET:
            return self.taker_fee
        else:
            return self.maker_fee

BINANCE_SPOT = FeeSchedule(maker_fee=0.001, taker_fee=0.001,
    vip_tiers=[(1_000_000, 0.0009, 0.001), (5_000_000, 0.0008, 0.0009), (20_000_000, 0.0007, 0.0008)])

Funding Rate for Futures

For perpetual strategies, funding is a significant cost. We incorporate historical rates and calculate the total payment over a period:

class FundingRateModel:
    def __init__(self, funding_interval_hours: int = 8):
        self.interval = funding_interval_hours
        self.funding_history: dict[str, pd.Series] = {}

    def calculate_funding_cost(self, symbol, position_value, from_ts, to_ts, position_side) -> float:
        if symbol not in self.funding_history:
            return 0.0
        rates = self.funding_history[symbol]
        mask = (rates.index >= from_ts) & (rates.index < to_ts)
        period_rates = rates[mask]
        total_funding = 0.0
        for rate in period_rates:
            if position_side == 'LONG':
                funding_payment = -position_value * rate
            else:
                funding_payment = position_value * rate
            total_funding += funding_payment
        return total_funding

What Cost Accounting Delivers: A Comparison

We test strategies in two modes: ideal (no costs) and realistic. The difference is striking:

According to Binance, the average taker fee is 0.1%.

More about slippage can be read on Wikipedia.

How We Do It: Our Process

1. Analysis — study the strategy, its trading frequency, volumes, target exchange.
2. Design — select fee and slippage models, tune parameters.
3. Implementation — write the backtesting engine with data integration (historical candles, funding).
4. Testing — run on synthetic and real data, verify via Tenderly.
5. Deployment — deliver documentation, code, and a monitoring dashboard.

What's Included (Deliverables)

• Cost model documentation
• Source code of the engine (Python, integrated with your stack)
• Integration with historical exchange data
• Analysis of divergence between ideal and realistic backtest
• 14 days of support after delivery

Common Pitfalls in Cost Accounting

• Using only fixed slippage without volume dependency
• Ignoring funding rate for long-term futures strategies
• Overlooking VIP discounts for volumes >$1M
• Treating bid-ask spread as constant without considering volatility

Timeline and Pricing

Development time: 5 to 15 business days depending on strategy complexity and number of exchanges. Pricing is individual — contact us for a same-day estimate. Our team has 5+ years of backtesting experience and has completed over 30 cost-modeling projects. Typical client savings reach up to $5,000 per year by uncovering hidden costs.

We guarantee model realism within 5% of actual trading results. Get in touch to request a consultation and order development. Receive a system that does not hide costs but reveals the real picture.

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.