Bitget's Announcement on Adjusting the Minimum Price Decimal for Spot Trading Pairs
To enhance user trading experience, Bitget will adjust the minimum price decimal (i.e., the smallest unit price fluctuation) for the MOG/USDT spot pair at 10:00, 8 November 2024 (UTC). The adjustment will take approximately 5-10 minutes. Details of the adjustment is shown in the table below: Spot T
To enhance user trading experience, Bitget will adjust the minimum price decimal (i.e., the smallest unit price fluctuation) for the MOG/USDT spot pair at 10:00, 8 November 2024 (UTC). The adjustment will take approximately 5-10 minutes.
Details of the adjustment is shown in the table below:
Spot Trading Pair
Trading Pair |
Before Adjustment |
After Adjustment |
MOG/USDT |
0.00000000000001(14) |
0.0000000001(10) |
Orders placed before the decimal adjustment, including planned orders, stop loss, and trailing orders, will be executed at the user-set prices based on the original price decimals.
During the decimals adjustment, the following issues may occur:
1. Related spot trading pair strategies may not be successfully initiated.
2. Spot grid strategies and spot Martingale strategies may terminate automatically due to abnormalities.
Users may wait for 5-10 minutes, restart the APP, or update the APP version, switch trading pairs, and then attempt trading again.
We apologize for any inconvenience this may cause and appreciate your support and attention to Bitget!
Disclaimer
Cryptocurrencies are subject to high market risk and volatility despite high growth potential. Users are strongly advised to do their research as they invest at their own risk. Thank you for supporting Bitget!
Join Bitget, the World's Leading Crypto Exchange and Web 3 Company
Disclaimer: The content of this article solely reflects the author's opinion and does not represent the platform in any capacity. This article is not intended to serve as a reference for making investment decisions.
You may also like
Uniswap founder: The killer use case for cryptocurrency is transferring value