Turnkey Development of Trading Bots Based on Indicators

Lookahead bias: why demo shows 30% ROI, but live drains deposit

Backtesting shows 30% ROI per year — on demo. On a live account, the strategy drains the deposit in a month due to slippage and lookahead bias. Lookahead bias occurs when code uses data that would only be available after the candle closes. For example, reading the current unclosed candle as closed gives an illusion of profit. In reality, slippage on liquid pairs takes 0.5-1% on entry and exit. And for DeFi bots, gas limit can make a transaction unexecutable during peak hours. Gas losses on the Ethereum network can reach 0.5 ETH per month with active trading.

Developing a trading bot based on indicators is not just pandas code, but an engineering task: eliminating lookahead bias errors, ensuring atomic execution, and staying within gas limits (for DeFi) or latency (for CEX). We create turnkey bots: from strategy formalization to deployment on VPS and integration with your Telegram/Slack for alerts. Over 5 years, we have developed 100+ algorithms for clients — from scalpers to hedge funds. More about lookahead bias on Wikipedia.

What's included in development?

How to implement an RSI strategy without lookahead bias?

import pandas_ta as ta
import pandas as pd

class RSIStrategy:
    def __init__(self, rsi_period=14, oversold=30, overbought=70):
        self.rsi_period = rsi_period
        self.oversold = oversold
        self.overbought = overbought

    def generate_signal(self, df: pd.DataFrame) -> str:
        # IMPORTANT: shift(1) — use only closed candles
        rsi = ta.rsi(df['close'], length=self.rsi_period).shift(1)
        prev_rsi = rsi.shift(1)

        current_rsi = rsi.iloc[-1]
        previous_rsi = prev_rsi.iloc[-1]

        # Entry from oversold zone (crossing upwards)
        if previous_rsi < self.oversold and current_rsi >= self.oversold:
            return 'BUY'

        # Entry from overbought zone (crossing downwards)
        if previous_rsi > self.overbought and current_rsi <= self.overbought:
            return 'SELL'

        return 'HOLD'

Why does combining indicators produce fewer false signals?

One indicator — much noise. For example, RSI near 70 can give a false entry in a strong trend. A combination of RSI + moving averages + volume filters out up to 70% of false signals. Our multi-indicator strategy implementation uses three levels of confirmation:

class MultiIndicatorStrategy:
    def generate_signal(self, df: pd.DataFrame) -> str:
        rsi = ta.rsi(df['close'], 14).shift(1)
        ema_20 = ta.ema(df['close'], 20).shift(1)
        ema_50 = ta.ema(df['close'], 50).shift(1)
        volume_ma = df['volume'].rolling(20).mean().shift(1)

        current_close = df['close'].iloc[-1]

        # BUY conditions: all three factors align
        trend_up = ema_20.iloc[-1] > ema_50.iloc[-1]
        rsi_ok = 40 < rsi.iloc[-1] < 65  # not overbought but above neutral
        volume_confirm = df['volume'].iloc[-1] > volume_ma.iloc[-1] * 1.3
        price_above_ema = current_close > ema_20.iloc[-1]

        if trend_up and rsi_ok and volume_confirm and price_above_ema:
            return 'BUY'

        # SELL conditions: trend broken
        if ema_20.iloc[-1] < ema_50.iloc[-1] and rsi.iloc[-1] > 60:
            return 'SELL'

        return 'HOLD'

Such a strategy on historical data shows 2.5 times fewer losing trades than a standalone RSI. And the profit/risk ratio (profit factor) improves from 1.2 to 2.0.

How to process data in real time?

In live trading, you cannot recalculate indicators on the entire history at every tick. We use incremental updates:

class IncrementalCandleManager:
    def __init__(self, symbol: str, interval: str, history_length: int = 200):
        self.symbol = symbol
        self.interval = interval
        self.history_length = history_length
        self.df: pd.DataFrame = None

    async def initialize(self):
        """Load history on startup"""
        candles = await self.exchange.get_klines(
            self.symbol, self.interval, limit=self.history_length
        )
        self.df = self.to_dataframe(candles)

    def update(self, new_candle: dict):
        """Add new candle, remove old one"""
        new_row = self.candle_to_row(new_candle)

        if new_candle['time'] == self.df.index[-1]:
            # Update current unclosed candle
            self.df.iloc[-1] = new_row
        else:
            # Add new closed candle
            self.df = pd.concat([self.df, pd.DataFrame([new_row])])
            # Keep fixed history length
            if len(self.df) > self.history_length:
                self.df = self.df.iloc[-self.history_length:]

This saves up to 90% processing time compared to full recalculation.

How to set stop-loss and take-profit?

We use OCO orders for atomic setting:

class PositionManager:
    async def open_with_sl_tp(
        self,
        symbol: str,
        side: str,
        amount: float,
        entry_price: float,
        sl_percent: float,
        tp_percent: float
    ):
        # Main order
        order = await self.exchange.place_order(symbol, side, amount)

        if side == 'buy':
            sl_price = entry_price * (1 - sl_percent / 100)
            tp_price = entry_price * (1 + tp_percent / 100)
        else:
            sl_price = entry_price * (1 + sl_percent / 100)
            tp_price = entry_price * (1 - tp_percent / 100)

        # OCO order for simultaneous SL and TP
        await self.exchange.place_oco_order(
            symbol=symbol,
            side='sell' if side == 'buy' else 'buy',
            quantity=amount,
            price=tp_price,            # limit (take profit)
            stop_price=sl_price,       # stop trigger
            stop_limit_price=sl_price * (0.995 if side == 'buy' else 1.005)
        )

Proper Stop Loss calculation is key to capital preservation. Our clients on average save 0.3 to 0.5 ETH per month by optimizing gas fees. If the strategy runs on DEX, we integrate liquidity aggregators to reduce slippage.

Testing: from backtest to live

Before going live, backtesting on historical data (5+ years) and forward testing on a demo account are mandatory. Backtesting rules: execute on the open of the next candle, include commissions (minimum 0.1% per trade), account for slippage. Metrics: Sharpe ratio, maximum drawdown, win rate. The strategy must show positive results on out-of-sample data.

Skipping the paper stage is the most common trader mistake. We insist on mandatory testing on a demo account for 2 weeks.

Typical mistakes in bot development

Our advantages

• Over 5 years in trading algorithm development, 100+ projects for private and institutional clients.
• Warranty on code: we fix bugs free of charge within 30 days after deployment.
• We use best practices: formal verification for DeFi contracts, reentrancy guards, gas optimization.
• Potential profit from a properly configured strategy can range from $5,000 to $10,000 per month depending on capital and market conditions.

Contact us to discuss your project. We'll estimate within 1 day. Get a consultation on your strategy — we'll help turn your idea into a working algorithm.

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.