Hummingbot Connector v6.2.2

Release Date: October 1, 2026 Tags: MARKET MAKING, PERFORMANCE, ORDER STREAMS, KIT

Overview

A market-making bot bought its whole sell side every time it started. Hummingbot's position rebalance counts its executors' positions, never the wallet, so at every start it market-bought the base asset for the sell side — on a book the bot makes itself that buy meets only its own orders, and on a thin book it can sweep the asks. Generated configs now skip it, and the bot quotes from the base the account already holds. Fund the account with the base asset before you start a bot.

The connector's private order streams also stop reading a busy account's orders over and over: on one live install the backend spent 38.7% of its CPU on those reads for an account with about 460,000 orders.

No new dependency: requires Core v6.7.8, as before. Ecosystem 6.5.6, released with it, carries the cheaper order-row decoding behind that figure.

Update Instructions

pnpm updator

No schema change, no setting. KIT_VERSION was not changed, although the kit's market-making controller was — see Upgrade Notes.

Upgrade Notes

Market-making bots no longer buy their sell side

• Bots started from the admin panel pick this up the next time they start; a running bot keeps its old config until then.
• A config you downloaded for your own Hummingbot does not change: download it again, or add the line skip_rebalance: true to it.
• To make the new default apply to configs without that line, including the kit's sample presets, re-run the kit installer (python install_connectors.py /path/to/hummingbot). The kit's version string was not changed, so a matching version does not mean the controller is current.

Changed

Generated market-making configs skip the start-up buy

• Changed the market-making configs the platform generates to include skip_rebalance: true, and the bundled market-making controller to default to it. A preset can ask for the old start-up buy with acquireBaseAtStart: true in its config; the admin form has no field for it.

Fixed

Order streams and order lookups loaded the backend

• Fixed the private order and trade streams each reading the account's orders on their own timer, and starting a new read while the last was still running, which loaded the backend heavily for busy bot accounts. The two streams now share one read per account, and a tick is skipped while the previous one is still in progress.
• Fixed slow order-status lookups: looking up one order scanned up to 5,000 of the account's orders on that pair. An order placed through the connector is now read directly, with the previous lookup kept as the fallback.