In Ou Yizhong, the investigation and analysis of the contract grid strategy will automatically stop shortly after the manual creation (contact customer service, program bug)
1. In Ouyizhong, the contract grid policy will automatically stop shortly after the manual creation. Delegation time 2024/11/25 22:27:48. Stop time 2024/11/25 22:42:13. as shown in Figure 1
2. On the income details page, there is a start button. as shown in Figure 2
3. Click the Start button, prompt: The policy is being opened. The policy does not exist or has stopped. as shown in Figure 3
4. Decide to create the same strategy again. Before creating, check the USDT in the asset, which can be $3,046.32. as shown in Figure 4
5. Create the same strategy again, and soon it will automatically stop. The consequence of this automatic stopping is that the cumulative input and cumulative increase of the margin are occupied. View the USDT in the assets, available at $13.97. as shown in Figure 5
6. The consequence of this is that the two stopped ENSUSDT perpetual waiting signals in the contract grid, occupying a total of $6000 available USDT. as shown in Figure 6
7. Then try to manually stop an ENSUSDT perpetual contract grid, compare the previous two, and confirm that there is a big difference. as shown in Figure 7
8. Now try to restore the occupation of $6000 USDT. for the creation of other contract grids. Copy the parameters, create a grid policy, prompt: available funds have been exceeded. as shown in Figure 8
9. However, to view the USDT in the asset, $6,251.01 can be used. Therefore, it is initially speculated that the reason for the inability to recover is that the total amount limit of the EnsusDT perpetual contract is caused by the limit. as shown in Figure 9
10. When the total amount of the EnsusDT perpetual contract is reduced to $10000. As shown in Figure 10
11. Copy the parameters and create a grid policy, which can be 2,354.77 USDT, and the amount has been greater than the accumulated input of 2,000 USDT in the historical policy. as shown in Figure 11
12. Try to restore the history strategy again, click the Start button, prompt: The policy is being opened. The policy does not exist or has stopped.
13. Therefore, the USDT in the seemingly assets can be 9146.68. as shown in Figure 12
14. However, when withdrawing the currency, the USDT balance of the withdrawable currency is 37.83, which feels like it is close to 9000 USDT is occupied. as shown in Figure 13
15. In the end, there is no way to log in to the PC After the website, then contact the manual customer service, and finally got a preliminary answer (for the question about the cessation of the contract grid that you reported to stop, please also Don’t worry, your assets will not be lost. For you, the assets occupied by your two strategies have been already in 2024-11-27 16:53 Release 3000USDT twice, total: 6000 USDT to your trading account, you can check the balance of your USDT assets in the lower right corner of the asset-bill-trading account. We have positioned the problem and expect a new version to be released in the future This fixes this problem, please pay attention to the subsequent APP version optimization, the page display shall prevail, sorry for the inconvenience caused during the period, you may need to re-upgrade my account. It feels like a program bug. Figure 14
16. In the reply to the work order, it means that the assets occupied by the two strategies have been released twice at 3000USDT at 2024-11-27 16:53. After checking, it was indeed released. as shown in Figure 15
17. After a few days, a prompt will pop up: update the app and experience the latest version. as shown in Figure 16
18. However, after the update is found, after a period of time, it is found that the USDT balance that can be withdrawn is 4,543 when the coin is withdrawn, which feels like it is close to 6000 USDT is occupied. Consult customer service again, and reply that this is a normal situation (if you are the spot and contract margin model, it is the situation you said. But you are now a cross-currency margin model, so it is normal). as shown in Figure 17
















