Blog
News, release deep-dives, and multi-language guides from the CCXT team — the open-source library connecting 100+ cryptocurrency exchanges.
CCXT vs everything else: we compared it with every exchange SDK we could find
One page per alternative — CCXT against sixteen multi-exchange libraries, bots and engines, and against the official SDK of all 104 exchanges it supports. Including the venues that turn out to have no SDK at all.
Front-running the S-1: trading the Anthropic-vs-OpenAI IPO race with CCXT
A walk through CCXT's prediction-market API using the binary market "Will Anthropic or OpenAI IPO first?" — reading odds across venues, a tweet-based signal, and cross-venue arbitrage.
How far is your exchange? Mapping crypto API latency around the world
We timed the same fetchOrderBook call to ten venues — spot exchanges, a perps DEX and a prediction market — from eight cities on six continents. It ranges from 6 ms to over a second depending on where you run it. Here's the map.
How fast is CCXT in each of its six languages? We measured every layer
A like-for-like benchmark of CCXT across all six languages — JavaScript, Python, PHP, C#, Go, and Java. Why REST latency tells you almost nothing about a language, what a no-CCXT control run reveals about measuring it, how fast each language really parses an order book, and why the two compiled languages end up the slowest.
Backtest before you bet: pull years of free candles from any exchange
Every exchange gives away its price history through the same CCXT call. How to download years of OHLCV data properly — and the backtesting traps that make losing strategies look like winners.
You're only using two order types — a tour of stops, trailing stops, and post-only
Market and limit are just the beginning. Trigger orders, stop-losses, take-profits, trailing stops, and execution modifiers like postOnly and reduceOnly — unified across exchanges through CCXT params.