finds.dev

rexonelo/barbotine-arbitrage-bot

CCXT-based cross-exchange arbitrage bot operating on CEXs, entirely written in Python. Work without any transfer between exchanges.

View on GitHub

★ 647PythonNOASSERTIONupdated Feb 2026

// the take

Barbotine is a CCXT-based arbitrage bot that trades the same pair simultaneously on multiple exchanges instead of moving funds between them, chasing orderbook-level price gaps. It's built for someone who already has capital split across a few CEXs and wants to automate what they'd otherwise do by hand, not for someone looking for a managed trading product.

Skipping inter-exchange transfers is a sound design choice rather than a shortcut — moving crypto between exchanges takes minutes to confirm, which kills most arbitrage windows, so holding balance on both sides and trading locally is the right call for this strategy. It runs a balance simulation for every detected opportunity before acting rather than reacting to a raw spread number, which accounts for available liquidity instead of assuming it. Building on CCXT means it inherits order book and order placement handling for a large number of exchanges instead of writing bespoke clients for each one, and the built-in Telegram and webhook notifications plus logging make it usable as a monitoring tool even before anyone trusts it with money.

The README states outright that the real-money trading logic is withheld — contact the author for the full version that works with real balances — so what's actually on GitHub is a fake-money demo; the execution code people would need to run this for real isn't public, and the star count reflects curiosity rather than production use. Because there's no transfer between exchanges, balance on each side drifts with every trade, and the bot's fix is a manual or timed rebalance session that itself pays the same fees and slippage the bot exists to capture, quietly eating into any edge over time. Exchange API keys with trading permissions are configured directly in a plain Python file with no secrets management story, and there's no visible kill-switch or risk limit beyond the balance the operator chooses to feed it. The hard pin to Python below 3.12 with no stated reason, combined with no tests or CI visible in the tree, points to a fragile dependency chain and informal maintenance — not something to leave running unattended with real capital.

We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
647
Forks
153
Language
Python
License
NOASSERTION
Last commit
4 Feb 2026

// nearby

If barbotine-arbitrage-bot isn't quite it.

All repos →