Custom Candlestick Chart Development for Exchanges and DeFi

A trading platform with a million trades per hour—standard TradingView widgets can't handle it: aggregation lags, customization is impossible. In one project for a client with 50,000 pairs and 2 million trades per minute, we built a custom candlestick chart from scratch. The solution uses TimescaleDB for OHLCV, a Go aggregator for real-time, and Lightweight Charts for rendering—processing a candle in 3 ms and displaying data without delays. Let's break down how to avoid common pitfalls and get a chart that doesn't lag even with 100k candles. Our approach reduces infrastructure costs by 2x through efficient aggregation. Contact us to discuss your chart requirements.

Why Choose a Custom Chart?

Off-the-shelf widgets don't give you control over aggregation logic (e.g., volume-weighted prices) or let you add indicators like VWAP with non-standard periods. A custom chart gives you full control over every stage—from data collection to rendering—which is critical for proprietary trading strategies and fast market response.

Problems We Solve

The main difficulties in building custom charts are latency and customization. Ready-made widgets don't allow changing aggregation logic (e.g., using volume-weighted prices) or adding indicators like VWAP with a custom period. The second problem is performance: with thousands of candles and several indicators, rendering can stutter. We solve this with a combination of TimescaleDB on the server and Lightweight Charts on the client.

How We Solve the Latency Problem

Latency consists of three stages: receiving a trade event, aggregating the candle, and sending it to the client. Each stage must be within milliseconds. Step-by-step process:

1. Receiving: WebSocket gateway handles up to 100,000 messages per second per instance.
2. Aggregation: In-memory aggregator in Go updates the current candle in <2 μs, closed candles in 5 μs.
3. Delivery: Debounce updates to 10 times per second, batch send no more than 10 candles per message.

Continuous aggregates in TimescaleDB automatically update materialized views. We configure a policy with a 1-minute interval for 1m candles, providing data freshness of up to 1 minute. For higher timeframes, aggregation is done on the fly from 1m candles. End-to-end latency from trade to chart display is less than 200 ms.

How to Implement Custom Indicators?

Indicators (EMA, VWAP, volume profile) are calculated either on the client or server—the choice depends on recalculation frequency. For indicators with a fixed window (e.g., 12-period EMA), we use server-side aggregation by adding columns to the continuous aggregate. For interactive ones (e.g., dragging points), we use client-side calculation in a Web Worker to avoid blocking the UI.

Example server-side indicator—VWAP with configurable period:

CREATE MATERIALIZED VIEW vwap_1m
WITH (timescaledb.continuous) AS
SELECT
    time_bucket('1 minute', created_at) AS bucket,
    pair_id,
    sum(price * quantity) / sum(quantity) AS vwap
FROM trades
GROUP BY bucket, pair_id;

How to Implement a Custom Candlestick Chart?

Consider a typical case: an exchange wants to display 1-minute candles with Heikin-Ashi and EMA. We also support Renko, Kagi, and Point-and-Figure. The server part aggregates trades via TimescaleDB, and the frontend uses the Lightweight Charts library.

OHLCV Storage and Aggregation

Raw trades are stored in TimescaleDB. For fast aggregation, we create a continuous aggregate:

CREATE MATERIALIZED VIEW candles_1m
WITH (timescaledb.continuous) AS
SELECT
    time_bucket('1 minute', created_at) AS bucket,
    pair_id,
    first(price, created_at) AS open,
    max(price) AS high,
    min(price) AS low,
    last(price, created_at) AS close,
    sum(quantity) AS volume,
    count(*) AS trades_count
FROM trades
GROUP BY bucket, pair_id;

SELECT add_continuous_aggregate_policy('candles_1m',
    start_offset => INTERVAL '3 hours',
    end_offset   => INTERVAL '1 minute',
    schedule_interval => INTERVAL '1 minute');

From 1-minute candles, higher timeframes are built on the fly—same SQL with time_bucket('1 hour', bucket).

Real-time Update in Go

type CandleAggregator struct {
    mu      sync.RWMutex
    current map[PairTimeframe]*Candle
}

func (ca *CandleAggregator) OnTrade(trade Trade) {
    ca.mu.Lock()
    defer ca.mu.Unlock()
    for _, tf := range TIMEFRAMES {
        key := PairTimeframe{trade.PairID, tf}
        bucket := truncateToTimeframe(trade.Time, tf)
        candle, exists := ca.current[key]
        if !exists || candle.Bucket != bucket {
            if exists {
                ca.publishClosedCandle(candle)
            }
            ca.current[key] = &Candle{
                Bucket: bucket, Open: trade.Price, High: trade.Price,
                Low: trade.Price, Close: trade.Price, Volume: trade.Quantity,
            }
        } else {
            if trade.Price > candle.High { candle.High = trade.Price }
            if trade.Price < candle.Low  { candle.Low  = trade.Price }
            candle.Close = trade.Price
            candle.Volume = candle.Volume.Add(trade.Quantity)
        }
        ca.publishLiveCandle(ca.current[key])
    }
}

Frontend: TradingView Lightweight Charts

import { createChart, CandlestickSeries } from 'lightweight-charts';

const chart = createChart(container, {
    layout: { background: { color: '#0d0d0f' }, textColor: '#9b9ea8' },
    grid: { vertLines: { color: '#1e2030' }, horzLines: { color: '#1e2030' } },
    timeScale: { timeVisible: true, secondsVisible: false },
});

const candleSeries = chart.addSeries(CandlestickSeries, {
    upColor: '#00b15e', downColor: '#e84242',
    borderVisible: false,
});

// Load historical + stream via WebSocket
candleSeries.setData(historicalData);
ws.onmessage = (event) => candleSeries.update(JSON.parse(event.data));

Indicators (EMA, VWAP) are added as LineSeries on top. For Heikin-Ashi, convert data on the client:

function toHeikinAshi(candles: OHLCV[]): OHLCV[] {
    return candles.map((c, i) => {
        const prev = i > 0 ? candles[i-1] : c;
        const haClose = (c.open + c.high + c.low + c.close) / 4;
        const haOpen = i === 0 ? (c.open + c.close)/2 : (prev.open + prev.close)/2;
        return {
            time: c.time,
            open: haOpen,
            high: Math.max(c.high, haOpen, haClose),
            low: Math.min(c.low, haOpen, haClose),
            close: haClose,
        };
    });
}

Performance Comparison: Lightweight Charts vs Other Libraries

Lightweight Charts is 3–4 times faster than D3.js when rendering 10,000 candles and uses 3 times less memory.

What Data Do We Need to Start?

To begin, we need access to trade events (raw trades) via API or files. We set up aggregation ourselves. If no data is available, we help connect to exchange sources via WebSocket or REST. The minimum configuration does not require specific schemas—TimescaleDB adapts to any structure.

Stages of Work

What's Included in the Work

The result includes a full package: documentation (DB schemas, API specification, deployment instructions), access to source code in a Git repository, training for your team (2-day workshop), 2 weeks of free support after launch, and an SLA with a response time of up to 4 hours. We ensure a smooth transition and independent operation.

Tech Stack

Timeframes and Cost

Timeframes are indicative and calculated individually:

• Basic chart (live updates, 2–3 indicators): 4–6 weeks.
• Full-featured charting (all timeframes, 10+ indicators, drawing, Heikin-Ashi/Renko): 2–3 months.
• Server part (TimescaleDB + aggregator + WebSocket): 3–5 weeks in parallel.

Cost is calculated based on your data volume and requirements. We guarantee transparency: preliminary assessment is free, budget is fixed after approval of the technical specification. Our clients save up to 40% of development time thanks to ready-made components and proven solutions.

Our Experience and Guarantees

We are a blockchain development team with 5+ years of experience in Web3. We have implemented 30+ projects for crypto exchanges, DeFi platforms, and trading terminals. We use proven tools and provide an official warranty on the code.

Order custom candlestick chart development—we implement turnkey, from architecture to deployment. Get a consultation—let's discuss your project and propose the optimal solution.

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.