Chart Engine
The in-house charting surface Bicrypto draws prices on — candles, 144 indicators, 73 drawing tools, price alerts, replay and a bot cockpit, painted from your own site palette instead of an embedded third-party widget.
Chart Engine is the platform's own charting library. It draws candlestick, line, area, bar and Heikin-Ashi charts on a canvas it controls, rather than embedding a third-party widget in an iframe. That distinction is the whole point of the product: because the chart is yours, it can draw things a hosted widget cannot — a binary order's expiry countdown, a spot order's take-profit line, a running bot's grid ladder — and it can paint from the palette you configured in Appearance & Design → Site Design instead of a private colour scheme that disagrees with every other screen.
What it requires
Requires BicryptoChart Engine is an addon. It needs a working Bicrypto install and nothing else. It has no database tables, no cron jobs, no API routes and no seeders of its own — it is a frontend package that mounts inside screens core already ships.
What it pairs with changes what it can draw:
| If you also run | Chart Engine gains |
|---|---|
| Ecosystem | Candles for your own native markets, from /api/ecosystem/chart |
| Futures | Candles and position overlays for perpetual markets |
| Forex Multi-Asset Trading | Candles for session-limited FX instruments |
| Algo Trading Bots | The algorithmic mode — a bot's ladder, fills and control dock drawn on the price axis |
None of those are required. On a core-only install the chart works against the CEX market data core already fetches.
Where it appears
Chart Engine never replaces a screen. It replaces the chart inside a screen, and it does so on four surfaces:
The full binary presentation: order markers, barriers and strike lines, expiry lines, the countdown, and profit-and-loss shading between entry and the live price.
Order markers with take-profit and stop-loss lines, fill ticks, and no expiry furniture. This is the presentation the Trading Pro workspace uses as well.
The same spot/futures presentation, mounted inside the multi-panel Pro layout.
The algorithmic mode shipped with Algo Trading Bots — grid rungs, band edges, average entry, stop, trailing stop, every fill, and a floating cockpit with Start, Pause, Resume, Stop and Close position.
Two settings decide the first three — one for binary, one for everything else. The bot terminal has no setting and always asks for Chart Engine. Every surface falls back to TradingView when the addon is absent. See Administering Chart Engine.
What is in the box
- Five chart types — candlestick, line, area, bar (OHLC) and Heikin-Ashi.
- Nine timeframes — 1m, 3m, 5m, 15m, 30m, 1h, 4h, 1d, 1w — with automatic timeframe switching when you zoom past the readable candle count.
- 144 indicators in seven categories, each with editable parameters, a price source, colours and line widths, drawn as an overlay or in its own panel. See Indicators.
- 73 drawing tools in eight categories, including the complete Fibonacci, Gann and pitchfork families, position tools, measurement tools and freehand annotation. See Drawing tools.
- Analysis panels — price alerts, aggregated trading signals, candlestick and harmonic pattern detection, divergence detection, multi-timeframe mini-charts, a volume heatmap, chart replay and saved templates. See Chart panels.
- Theme-aware painting — grounds, candles, grid, axes, crosshair, order markers and every overlay panel read the live design tokens. See Theming.
How it gets its data
The chart fetches historical candles over HTTP and then keeps itself current
over a WebSocket. Which endpoint and which socket it uses is decided entirely by
the marketType the host screen passes — spot, eco, futures or forex —
and getting that wrong is the single most common cause of a chart that loads
without error and shows nothing.
The full contract, including the query parameters, the array-of-arrays candle shape, the subscription frame and the server-side cache, is in Data sources.
What it is not
Chart Engine has no backend. It does not fetch, store or reconcile candles itself; it consumes the same endpoints the rest of the platform already exposes. If candles are missing, wrong or stale, the fault is upstream — in the exchange provider, in ScyllaDB, or in the market's own configuration — and no chart setting will fix it.
It also does not place orders on its own. In binary mode a click can arm a one-click trade, and a price alert can carry a limit order, but both call back into the host screen. In algorithmic mode manual order entry is switched off entirely, deliberately: a hand-placed order inside a bot's chart would be attributed to the bot's profit and loss and corrupt the numbers the view exists to report.
Start here
Where the files go, why the frontend must be rebuilt, and the settings that decide which screens use it.
Adding, configuring and persisting indicators — and why they follow the user, not the market.
The eight categories, magnet and lock, and how drawings are stored per symbol.
How the canvas reads your palette, and the one case where it needs a nudge.
Every endpoint and socket the chart touches, per market type.
Empty charts, wrong-market charts, blank canvases and stale colours.