💞 #Gate Square Qixi Celebration# 💞
Couples showcase love / Singles celebrate self-love — gifts for everyone this Qixi!
📅 Event Period
August 26 — August 31, 2025
✨ How to Participate
Romantic Teams 💑
Form a “Heartbeat Squad” with one friend and submit the registration form 👉 https://www.gate.com/questionnaire/7012
Post original content on Gate Square (images, videos, hand-drawn art, digital creations, or copywriting) featuring Qixi romance + Gate elements. Include the hashtag #GateSquareQixiCelebration#
The top 5 squads with the highest total posts will win a Valentine's Day Gift Box + $1
#BTC# Futures Trading
#SOL# Futures Trading
Dear cryptocurrency friends, please let me know if Gate.io should take responsibility for this incident. Thank you!
Gate Account UID: 1602622
The margin details show that on 2025-08-26, the initial margin was around 10300U. Due to the market dropping in the evening, I was worried about my position being liquidated, so on 2025-08-26 at 05:31 in the morning, I added around 5100U (I transferred 19800aleo from my wallet and sold it for U to add to the margin to prevent liquidation). As a result, my account's margin balance reached around 16000U (there was a slight discrepancy due to opening and closing positions). Throughout the day on the 26th, the market was in an upward trend. At 17:52, Gate.io automatically transferred 6530U from my opening margin to the Yubibao. Subsequently, my position was forcibly liquidated by the system at 19:34 on 2025-08-26. After the issue occurred, Gate.io did not show any attitude towards addressing the problem and kept looking for reasons with the customers. I feel very powerless and helpless about such incidents.
Summary: The system automatically transferred the additional margin I added for the futures trading to the Yubi Treasure. Subsequently, my futures position was liquidated. Before the system transfer, my futures position was in a floating loss, and I cannot understand why the system operated in such an illogical manner. Is it to profit from the liquidation? That shouldn't be the case.
Request: Since it has already happened, please actively address the losses caused and do not simply push the responsibility onto the users for losses that should not have been theirs.