Updated October 14, 2026. The February 2, 2021 publication announced INSIDE 3.1. It listed MT4, MT5 and FIX API variants, including the cryptocurrency versions offered at that time. This is a release archive; an old variant name does not establish the features of present-day NH Crypto.

What the 3.1 release described

The notice covered Diff and quote-history displays, compatibility with certain broker connections, reconnection after server restarts and configuration saving. It also mentioned changes to inactive-chart rendering and the restoration of an earlier signal-detection method. A possible Bid–Ask calculation for 3.2 was a plan, not a feature demonstrated by this release.

The original fivefold resource-load claim did not include a measurement method or dataset. It cannot be used as a current resource-saving guarantee. The practical lesson is to check display behaviour, session recovery and preserved state separately.

What remains unknown after a connection returns

A green status indicator does not establish that every subscription has recovered, quotes are fresh or order state is reconciled. Data and trading messages may use separate channels. For example, the cTrader FIX communication model separates market-data exchange from trading messages. Consult the actual connection's documentation for its recovery procedure.

If an order was submitted just before the interruption, a missing response does not prove that the server rejected it. Check its identifier and the current position before resubmitting. This matters particularly when recovery delivers multiple messages concerning one transaction.

Four states for an acceptance test

1. Before interruption: preserve versions, settings, positions and working orders.

2. During interruption: establish which data remains available and which actions the application permits.

3. After reconnection: check quote times, subscriptions and order history.

4. After reconciliation: resume automated activity using the documented procedure.

Check this scenario in a controlled test environment first; there is no need to deliberately interrupt a live connection for an experiment. The feed-recovery checklist and execution audit provide further detail.

A blank chart is not necessarily missing data

Disabled rendering, a different history interval and a lack of incoming messages are different conditions. Compare the chart window with receipt logs and the latest tick time. If one view displays 10 minutes and another displays 20, align the observation periods before concluding that half the events have disappeared.

After restarting, check saved parameter values, units, selected instruments and the connection profile. A settings file existing on disk is insufficient: the application must load the intended file. Do not treat the old notice's set.program path as a universal settings path for a current product.

For current NH PRO, start with the up-to-date manual and environment preparation guide. You can send the team an unclear recovery scenario with event times and logs, excluding secret data.