Project structure System consist from multiple independent processes that may be run on different node. Communication is implemented on top of various message queues on top of redis. Redis is also used as distributed caching layer - to reflect actual balance across all exchanges. Data in queues usually pickled. Persistence for historical data - postgres. Alerting is implemented on top of Telegram messenger. CLI management is done manually using scripts within this project. NOTE: Web based UI and data scrapping framework from various resources are NOT part of this repo. Terminology - bot - arbitrage process that trade single commodity between exactly two exchanges - order - what bot is placed to markets - trade - what was actually executed at markets, single order may be closed by multiple trades Key services: - telegram notifier - watch message queues and forward messages based on their severity to corresponding Telegram channels - balancemonitoring - update cached values of balances for all currencies for all exchanges in portfolio All trading processes validate time of last update

⚠ No verified equity curve — no track-record source connected.

No score history is stored yet — only the current score is shown.

⚠ No live verification account connected — ask for proof before buying.

Alerts on changes: coming soon

Prop-firm compatibility not provided.

Data-completeness & trust index (not a profitability rating)