Why was the perpetual contract liquidated even though the candlestick did not reach the liquidation price?

Why was a perpetual contract liquidated even though the K-line did not reach the liquidation price?

"The lowest point of this K-line was only 100.50, and I remember the liquidation price was 100. How was it liquidated?"

When users open the last-traded-price K-line, the lowest point they see may indeed be 100.50. To explain this liquidation, you must look at the mark price at the exact same moment, as well as the position and margin status at that time.

6MM perpetual contract risk assessment uses the mark price, combined with account or position equity, maintenance margin, and applicable risk rules. When investigating such issues, first confirm what price the K-line in the screenshot represents, and then check whether the estimated liquidation price in the screenshot corresponds to the position at the time of the event.

1. What is the difference between the last traded price, index price, and mark price?

The last traded price is the price of the most recent actual matched trade in this contract market. The traded price K-line records trading activity within a specific time period. For example, if the lowest point of a one-minute traded price K-line is 100.50, it means the actual lowest trading price in that minute was 100.50.

The index price reflects the reference price of the underlying asset. It provides a benchmark for observing the underlying market. The contract market has its own buy/sell orders and trading records, so the contract trading price and the index price can differ.

The mark price is used for position risk assessment. In the 6MM contract system, margin calculation and liquidation judgment both use the mark price. Using this metric reduces the impact of a single abnormal trade or short-term trading price volatility on risk assessment.

At any given moment, all three prices may appear on the trading page. When viewing the market, users should first confirm which price curve the chart is displaying. When performing page acceptance testing, the platform should also check whether the chart labels match the actual data sources.

2. Understand with a set of numbers: Why might a position be liquidated even if the K-line didn't reach the price?

Assume a user holds a long position in a perpetual contract. After review, it is confirmed that at the time of the event, the estimated liquidation price of this position was approximately 100.00. During the relevant one-minute period:

  • The lowest traded price K-line was 100.50.
  • The mark price dropped to 99.80.

The value 100.50 in the user's screenshot records the lowest actual trading price of the contract during this period. The risk control system uses the mark price when evaluating positions. If the mark price changes and the position also meets the applicable margin and risk conditions, the system may enter the liquidation process.

During an actual investigation, it is also necessary to find the exact time of the event. The one-minute K-line helps the team narrow down the search range. To explain when a position reached the liquidation conditions, it is necessary to combine the mark price, position records, and risk events at that specific time. The numbers above are only used to illustrate that the two prices may differ.

Similarly, seeing the trading price briefly touch a certain price cannot determine whether a position should be liquidated based solely on that single trade. To answer this question, it is still necessary to check the mark price and the risk status at that time.

3. Why might the estimated liquidation price in the screenshot have changed?

The estimated liquidation price corresponds to the position and margin status at the time the page was calculated. After a user increases or decreases positions, adjusts margin, or when account equity and applicable maintenance margin requirements change, the previous estimated value in the screenshot may no longer apply.

Under isolated margin mode, prioritize checking the margin, position size, and adjustment records corresponding to this position. For example, if the user added to the position after taking the screenshot, the previous estimated liquidation price needs to be re-verified against the changed position.

Under cross margin mode, you also need to look at the equity, other positions, and capital occupancy within the same margin account. When the risk status of other positions changes, even if the position the user is watching has not been added to or reduced, you must review it using the cross-margin account data from the time of the incident.

Therefore, even if a user provides two screenshots of the same trading pair, the platform should confirm their respective times, margin modes, and position statuses before determining which one explains the situation at the time of the event.

4. What is the difference between the mark price at the time of triggering and the actual liquidation execution price?

In a liquidation event, two different prices generally need to be checked.

The mark price at the time of triggering helps the team verify when the risk conditions were met. The actual liquidation execution price comes from the trade records and is used to check how much was actually traded and what the execution price was.

For example, the system triggers a position reduction based on the mark price and margin status at that time. The user then sees another execution price in their history details. These two figures come from risk assessment and actual execution, respectively. When verifying the final result, you should continue to check the traded quantity, realized PnL, applicable fees, and account flow, while confirming whether the related position was partially or fully liquidated.

5. In what order should customer support handle tickets reporting "liquidation price not reached"?

  1. Align trading pairs, positions, and time. Confirm the contract product, position direction, event time, and page timezone. Use screenshots to verify whether the user was looking at the traded price K-line, mark price K-line, or another market chart.
  2. Query the mark price at the time of the event. Find the mark price for the corresponding market and time period, and compare it with the traded price curve seen by the user. When precise time points are involved, view the event records retained by the platform.
  3. Check the position and margin status at that time. Confirm the position size, cross or isolated mode, account or position equity, applicable maintenance margin requirements, and check whether there were any operations to increase positions or adjust margin prior to the event.
  4. Review the actual processing results. Determine whether it was a partial reduction or a full liquidation of the relevant position, and then use the trade details and account flow to verify the quantity, price, realized PnL, and applicable fees.

When replying to customers, support can tie the process together in plain language: "Your screenshot shows the traded price K-line. We are checking the mark price and margin records of this position at the time of the incident. Once verified, we will explain the conditions under which the position triggered processing, as well as the actual liquidated quantity and execution price."

If a support ticket currently has only one screenshot, you can first clarify what has been confirmed and what is still under investigation. When providing a conclusion, it should correspond to the specific event and trade records.

6. How should trading platforms display prices to reduce such misunderstandings?

Indicate the current chart type on the market page. Clearly display "Last Price", "Mark Price", or "Index Price" directly on the chart so that users can tell which price type they are viewing when switching markets or taking screenshots.

Explain the definition of the estimated liquidation price on the position page. Use "Estimated Liquidation Price" as the field name, and explain near the field that liquidation judgments use the mark price and depend on applicable margin and risk rules. This makes it easier for users viewing their positions to understand why this figure fluctuates with position and account status.

Enable users and support to look up the same event in history records. The page can display event time, position processing results, and actual trade information. Support back-offices can then link to corresponding risk records and account flows via permissions, making it easy to trace from the user-facing result back to backend details.

6MM provides trading technology infrastructure for partner platforms. When integrating perpetual contracts, product and technical teams can first verify the traded prices, index prices, and mark price K-lines returned by the market API, and then run a joint debugging session using the simulation scenario where "the traded price K-line did not reach the estimated liquidation price, but the mark price and margin status reached the applicable conditions". Letting customer support trace a single position record from start to finish will both uncover page wording issues in advance and confirm that the team has sufficient information to respond to users after launch.

Build, Empower, and Drive Your Digital Asset Business

Choose a time with our product team to discuss integration needs, liquidity options, and deployment timelines.

Book a Demo