Futures Trading v6.1.7

Release Date: August 12, 2026 Tags: FEES, INSURANCE-FUND, ORDERS, TREASURY, RELIABILITY, BUG-FIXES

Overview

An insurance-fund accounting release. When an order is placed, its whole fee is credited to the treasury and a slice of it is immediately moved into the insurance fund. So between placement and cancellation the treasury holds less than the fee — and the refund path was booking the reversal before putting that slice back.

A reversal is capped at what the treasury actually holds, so on a treasury that had little in it the cap bit by exactly the withheld slice, the slice was then returned, and nothing ever took it out again. The trader was refunded in full either way, so the platform came out ahead on money it had given back. A second path — an expired or unfilled immediate order — never returned the slice at all, so the insurance fund reported cover it had not earned.

Nothing a trader sees changes. Requires Core v6.6.4.

Update Instructions

pnpm updator

Restart the backend afterwards. No database migration and no setting changes. Balances already recorded are not recalculated.

Fixed

A cancelled order left the platform holding fee money it had refunded

The two halves of a fee reversal — returning the withheld insurance slice and booking the refund against the treasury — were run in the wrong order. Booking the refund first, against a treasury that was short by exactly the withheld slice, meant the reversal was capped and the slice stayed put. Measured on a fee of 0.60 with a 10% withholding on a treasury holding nothing else: the platform ended a fully refunded cancellation holding 0.06 with the insurance fund empty.

It is most likely on the accounts it is hardest to notice: a fresh install, or a currency the platform has just started trading in, where the fee being reversed is the only thing in the treasury.

• Fixed the withheld insurance share being returned after the refund was booked rather than before, which left the platform holding part of a fee it had already given back.

An expired order never returned its withheld insurance share

Three paths refund a futures order's fee. Two returned the slice that had been withheld into the insurance fund; the third — the one that retires an expired or unfilled immediate-or-cancel order — did not. The trader got their fee back, and the slice stayed in the insurance fund permanently, against a fee that no longer existed.

• Fixed an expired or unfilled immediate order refunding the trader's fee while leaving the insurance fund holding a share of it, so the fund reported cover it had not earned.

The market feed reported a keepalive as a parse failure

The periodic are you still there every browser sends to a live screen was being read by the futures market feed as a malformed subscription, which raised an error inside the handler. It surfaced as a generic parse failure naming neither the route nor the cause — once per connected terminal, every thirty seconds. The platform now answers keepalives itself before any screen sees them, and a frame the feed genuinely cannot act on is logged once a minute at most, naming who sent it.

• Fixed a connection keepalive being reported as a parse failure on the futures market feed.