Updated October 14, 2026. The June 29, 2020 notice described INSIDE 2.5 updates for MT4, MT5, FIX API and New Hope Feed. It is a historical change list, not an instruction to install 2.5 today or a specification for current NH PRO.

Which components the release changed

For MT4/MT5, the announcement listed communication-protocol changes, licence identification and spread displays for certain indices. The 2Leg items covered logging and overflow protection; the MT5 section mentioned revised FOK/IOC handling. FIX API changes included selection of limit or market orders and server-error handling. Feed licensing and component interaction were updated separately.

These items cannot be combined into a promise that every variant provided every feature in the same way. Identify the exact build and connection type first. The notice also described MT5 callback testing: that is a historical development stage, not a statement of current status.

FOK and IOC: an example to check

The MQL5 order reference distinguishes volume-filling policies. FOK requires the full quantity or no execution; IOC permits the available quantity to execute and cancels the remainder. Allowed policies depend on the instrument and execution mode. This is separate from selecting a market or limit order.

Suppose an order requests 1.0 lot and 0.6 lots are available under acceptable conditions. In a simplified IOC scenario, 0.6 may execute while 0.4 is cancelled. If the full quantity cannot be obtained, FOK does not execute the request. This illustrates the rules, not actual liquidity or an expected execution price.

If the strategy expected 1.0 lot, its records must make the actual 0.6-lot result visible. Submitted volume cannot simply be treated as an open position. The limit and market order guide explains the separate order-type distinction.

A short update acceptance scenario

1. Record the version, instrument, account type and supported filling policy.

2. Check successful authentication separately from trading permissions.

3. Preserve the request, response and final transaction history in a test environment.

4. Check handling of a valid server rejection and the absence of uncontrolled retries.

5. Reconcile the sum of individual fills with the resulting position volume.

Testing need not create a risky situation on a live account. If a scenario cannot be reproduced safely, record that limitation. The demo/live protocol covers environment comparisons, while the execution audit explains how to read confirmations.

What a licensing change does and does not establish

A historical change to licence identification does not define licence duration, device allowances, a free upgrade or transfer rights. Confirm those terms separately for the selected product. For a current configuration, consult the NH PRO setup guide. For an old installer or activation issue, send the team the version and error message, keeping secret keys and passwords out of the enquiry.