Algo Trading Bots v6.0.5

Release Date: August 19, 2026 Tags: BOTS, ORDERS, PERFORMANCE, ECOSYSTEM

Overview

A single change, on the read a running bot makes most often. Checking whether a working order has filled looked that order up by its id alone, which the database can only answer by scanning the owning account's entire order history, across every market it has ever traded, to return one row. A bot asks that question once per working order on every tick, so the cost grew with everything the bot had ever placed and was paid on the same database session every manual placement on those markets is queued behind.

The lookup now names the market as well as the account, so it covers one market's orders instead of all of them. No figure changes. Fills, sizes, fees, balances and the bot's own history rows are computed from exactly the same values by exactly the same arithmetic — this is which table the question is asked of, and nothing else.

Requires Core v6.6.9 and the Ecosystem add-on updated in the same pass.

Update Instructions

pnpm updator

Restart the backend afterwards. No database change, no script, and nothing in your existing bots or their records to review.

The cheaper read applies only where the matching Ecosystem build is installed; on an install where it is not, bots keep working exactly as they do today on the previous read. There is no failure mode in between.

Changed

Fill checks no longer scan an account's whole trading history

• Changed a bot's fill check to look its order up by market and account rather than by account alone. It reads one market's orders instead of every market the account has traded, and no longer forces a filtered scan.