Hummingbot Connector v6.1.5

Release Date: August 27, 2026 Tags: CONNECTOR, FUNDING, WEBSOCKET, MARKET-DATA, FUTURES

Overview

A funding release, and a narrow one: the two surfaces this connector offers for the same number disagreed with each other. The REST funding-rate endpoint reported what the platform settles. The live websocket stream reported what somebody typed into the market form, on a clock of its own. A bot's pricing depended on which of the two it happened to read.

Nothing was ever charged incorrectly. The settlement path is untouched and has always applied its ceiling, so no balance, no position and no ledger row needs re-checking — only the figures advertised to connected bots were wrong.

If you run a perpetual market above the ceiling or off the default eight-hour schedule, the rate and the countdown your bots receive change to the correct values on restart. Every other market streams exactly what it streamed before. Requires Core v6.7.2.

Update Instructions

pnpm updator

Restart the backend. There is no database change and no configuration.

Fixed

The funding-rate stream quoted a rate the platform would never charge

Bots subscribed to the funding-rate channel were sent the number typed into the market's funding field, once every sixty seconds, without the ceiling the platform applies when it settles — a market configured at 5% streamed 5%, while the charge that lands has always been capped at 0.75% per interval. The same messages ignored the market's configured funding interval and announced a fixed eight-hour schedule, so a market settling every four hours told its subscribers the next charge was up to four hours further away than it really was, and a tick landing exactly on a settlement boundary reported funding as due now for a window that had just closed. The REST funding-rate endpoint on this same connector reported the settled figures throughout.

• Fixed the streamed rate to the figure settlement will actually charge, read from the settlement calculation itself rather than from the raw market field.
• Fixed the announced next-settlement time to follow the market's own funding interval, an admin field accepting anything from one to twenty-four hours, instead of a hardcoded eight-hour grid.
• Added the funding interval in hours and a server timestamp to every message on that channel, bringing it in line with what the REST endpoint already returned.
• Markets with no funding rate configured, which is the default, are unaffected.