Release 2.30.0 Overview: Stronger Margin Integrity and Consistent Trading Data

Release 2.30.0 strengthens several areas behind reliable everyday trading: margin calculation integrity, operational visibility, project access management, and consistent trading metrics across mobile and desktop.

The release introduces additional matching-engine safeguards against margin remaining from late order fills, improves diagnostic logging, centralizes project access decisions on the backend, and aligns mobile order metrics with their desktop equivalents.

Preventing Orphan Margin from Late Order Fills

Margin calculations must accurately represent positions that actually exist on a trading account.

A specific edge case could previously occur when an order was closed or deleted while a late fill was still being processed. This could leave used margin associated with an order that should no longer contribute to the account's active margin.

Release 2.30.0 adds safeguards to the matching engine to prevent these late fills from creating orphan used margin.

This strengthens the consistency between order state, active positions, and account margin — particularly during execution scenarios where events can arrive asynchronously.

For brokers, this reduces the risk of incorrect margin or balance states. For traders, it helps ensure the risk metrics shown by the platform accurately reflect their current trading activity.

Clearer Operational Logging

When a trading issue occurs, support and engineering teams need to understand what happened without spending unnecessary time interpreting technical logs.

Release 2.30.0 continues the platform logging overhaul with more human-readable events and structured diagnostic information.

Relevant events now provide clearer context for investigations, while unnecessary technical noise is reduced.

This makes it easier to identify execution and infrastructure issues, understand the sequence of events, and determine where further investigation is required.

Centralized Project Access Management

Project access decisions should remain consistent regardless of where an employee enters the platform.

Project selection and access logic has therefore been moved to the backend, establishing a single source of truth for project-based permissions.

Instead of relying on frontend state to determine the active project context, the platform now resolves this centrally.

This reduces the possibility of inconsistent project states and helps ensure employees work with the correct project and corresponding permissions across different entry points.

Consistent Trading Metrics on Mobile and Desktop

Traders increasingly move between desktop and mobile throughout the same trading session. The financial information presented on both interfaces should therefore mean exactly the same thing.

Release 2.30.0 aligns the trading metrics displayed in mobile order details with the desktop implementation.

The same metric logic is now used across both experiences, eliminating discrepancies that could previously make the same order appear different depending on the device being used.

Traders can move between mobile and desktop with a consistent view of their order information and trading metrics.

Reliability Behind Every Trading Operation

Release 2.30.0 focuses on improvements that may happen behind the interface but directly affect the reliability of everyday trading.

Stronger matching-engine safeguards protect margin integrity. Better logs make incidents easier to investigate. Centralized project access keeps permission logic consistent. And aligned mobile metrics ensure traders see the same trading information regardless of device.

Together, these changes strengthen the infrastructure and data consistency behind Wifox Trading.