Hummingbot Connector v6.1.4

Release Date: August 26, 2026 Tags: CONNECTOR, FUNDING, ORDER-TYPES, API-KEYS, MOBILE

Overview

Three fields this connector reported to professional counterparties were statements about the platform rather than about the market, and all three have stopped being. The perpetual funding endpoint served a hardcoded zero rate to every caller that asked. The exchange-info endpoint declared no OCO support, no trailing stops and only two order types.

Every one of those was true when it was written and none of them is true now. Funding is real, one-cancels-other and trailing stops exist, and conditional orders have rested with a trigger monitor all along. A market maker reads these fields and prices against them, so a stale answer here is a wrong quote there.

The other change is for operators publishing a mobile app: creating, rotating or re-scoping a connector key is refused to a native client. A mobile session can still stop, disable and revoke a running bot — which is the control worth having on a phone. Requires Core v6.7.2, and Futures v6.2.0 for funding.

Update Instructions

pnpm updator

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

Changed

The funding-rate endpoint reports the market, not a constant

• Changed perpetual/funding-rate to read the market's configured rate and its next settlement time. It served lastFundingRate: "0" on a hardcoded eight-hour schedule to every counterparty, in a field they price against, because positions never accrued funding at all.
• A market with no funding configured still answers zero. That is now the truth about that market rather than the truth about the platform.

Exchange info describes what this venue actually offers

• Changed ocoAllowed and allowTrailingStop from hardcoded false to true. Both instructions now exist on ecosystem markets.
• Changed the advertised order types to include STOP_LOSS and STOP_LOSS_LIMIT. Conditional orders have rested in the stop table with a trigger monitor since long before this release and nothing told a counterparty.
• Iceberg orders stay declared unsupported, deliberately. The matcher publishes a level's whole resting amount, so an order cannot yet show less size than it holds — declaring it would be the same class of claim the other two just stopped making.

Added

A phone can stop a bot and can never mint a credential

A connector key is a row in the same table as a general platform key, with the same untyped permission array — and that vocabulary includes withdraw and transfer. Nothing in the schema separates the two families, so "mobile may manage bot keys" and "mobile may mint a withdrawal credential" are one decision wearing two names.

• Added a refusal on key creation, rotation and re-scoping for native app clients. The secret is only ever issued in a browser.
• Disabling a key, deleting one and stopping a running bot are all still available from a phone, and always will be. Stopping a bot you are not sitting in front of is the whole reason to have the console on a phone at all.
• Browsers are unaffected.