Why VeighNa Maintains Separate CTP Production and Test Interfaces

Summary

A short VeighNa community exchange explains why the project continues to maintain vnpy_ctptest alongside vnpy_ctp. The response says that some futures companies still use an older version of the CTP testing environment, so the test interface remains supported for those users. It also describes a planned transition: once those firms move to the unified testing and production interface version 6.7.11, the older test-specific component is expected to be removed.

The exchange is useful as a practical note about broker connectivity and version compatibility for developers or traders setting up CTP access. It does not compare the interfaces’ technical behavior, installation steps, or trading capabilities, and it gives no schedule for the transition. Its explanation is limited to the maintenance rationale and the stated condition for eventual removal, so users should confirm the current status and broker requirements before choosing an interface.

Key ideas

• The test-specific interface remains maintained because some futures firms still use an older CTP test environment.
• The response anticipates retiring that component after firms adopt the unified test and production interface at version 6.7.11.
• The exchange gives a maintenance rationale but no technical comparison or migration instructions.
• Broker requirements and current interface status may need separate confirmation.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.