Announcement: Trading System Upgrade

Modified on Wed, 18 Jun at 10:41 AM

To enhance system performance, reliability, and overall user experience, Bitkub Exchange has been working on upgrading the trading system, starting from digital assets listed under the section “Digital assets with upgraded trading system per this announcement”. This upgrade applies across the website, application, and public API interfaces of Bitkub Exchange.

Changes after the completed upgrade

The upgrade will introduce our customers a new user experience specifically for the trading system of relevant digital assets, which will differ from others that are not included in this announcement, as follows:

Changes on Website and Application

* The core logic of the Stop-Limit order remains unchanged in both systems. The only difference lies in how the order status is displayed after being triggered according to the below table.

Function/Usage

Current system

New system

(for coins listed in the table at the end of this announcement)

Stop-Limit Order Display Behavior in the Open Orders page

When a Stop-Limit order is triggered, the system will automatically convert the order type from Stop-Limit to a Limit order.

When a Stop-Limit order is triggered, the system will retain the order type as Stop-Limit, and the order status will be displayed as “Triggered”. This enhancement provides clearer visibility into the order’s current state.

Sample	Old System	New System
Before being triggered at the stop price
After being triggered at the stop price

Comparison of the old and new displays

Changes to Public API

Function/Usage	Current system	New system (for coins listed in the table at the end of this announcement)
Order ID and Txn ID	Parent & Child Order Model When a single order is partially matched multiple times, the system generates a new child order for each match. Example: 1 original order matched in 3 parts > 3 Order IDs and 3 txn_ids are generated.	Order & Match Model (Global Exchange Concept) When a single order is partially matched multiple times, no new orders (child orders) will be created. All matches will occur under the original order. (Order ID can match multiple times.) Example: 1 original order matched in 3 parts > 1 Order ID and 3 txn_ids will be generated.
Order_id and Txn_id type	The symbol name and side are specified in the ID. Example: BTCBUY12123312323	Changed to UUID type where the symbol name and side are no longer specified in the ID. Example of the new UUID: 67b03a32a713c3f75f707799
Place Order APIs (Endpoint: place-bid, place-ask)	Old id format	The id will be changed to UUID.
Cancel Order API (Endpoint: cancel-order)	Old id format	The id will be changed to UUID.
My Open Orders API (Endpoint: my-open-orders)	Old id format	id, parent_id, and super_id will be changed to UUID and it will remain the same as the previous match if the partial matches are from the same original order.
My Order History API (Endpoint: my-order-history)	Old id format	order_id, parent_order_id, and super_order_id will be changed to UUID and it will remain the same as the previous match if the partial matches are from the same original order. txn_id will be changed to UUID.
Order Info API (Endpoint: my-order-info)	Old id format	id, first, parent, and last will be changed to UUID and it will remain the same as the previous match if the partial matches are from the same original order. txn_id will be changed to UUID.