Around June 9, 2026, the crypto market was put on high alert in a very short time by two alarming events: the DeFi protocol Haedal on the Sui ecosystem noticed an abnormal liquidity drop in some of its Vault pools, while on the other end, the SAHARA token of the AI concept project Sahara AI plummeted about 60% in the secondary market within 24 hours. Faced with the sudden thinness of Vault funds, Haedal chose to immediately hit the pause button on the relevant contracts, investigating the root cause of the anomaly while making the only clear commitment so far—that all direct losses related to this liquidity anomaly would be fully borne by the project party, trying to hedge the uncontrollable decline of user sentiment with quantifiable compensation. Meanwhile, Sahara AI, which was experiencing a cliff-like plunge in its price curve, took a radically different approach: the official categorized this sharp drop as “abnormal market volatility of the token,” emphasizing that there were no security issues with the SAHARA token contract and products, and announced the initiation of an internal investigation, but did not provide a clear explanation for the trigger factors or compensation expectations. At this same time frame, what was magnified was the same kind of structural fragility—when liquidity in the pools suddenly withdraws and the prices on the order book collapse instantly, how the project team can re-establish enough persuasive power to withstand ongoing trust pressures among technical explanations, funding commitments, and public attitudes.
Haedal on the Sui Ecosystem: Liquidity Plummets, Pause Button Pressed
On another chain, Haedal chose a completely different stance to save itself. As a DeFi protocol deployed on the Sui ecosystem, Haedal is more often viewed as “infrastructure” rather than a speculative target—users lock their assets into its Vault pools to exchange for profits generated by automated strategies, and these Vault pools are the core of the entire protocol and the part where users perceive risk most directly. Around June 9, 2026, Haedal officially detected abnormal liquidity declines in some Vault pools, where the funds in the pools were withdrawn to a degree that warranted pressing the “pause button,” and the team immediately announced the suspension of the operation of the relevant Vault pool contracts on the grounds of precautionary measures, simultaneously stating that they had initiated an investigation into the root cause of the anomaly.
The trouble is that until now, no one has been able to provide a sufficiently specific answer based on the publicly available information: whether this liquidity drop was due to technical flaws, strategic failures, or more external shocks; whether it is limited to “some Vault pools” or might spread to a larger area. On one hand, Haedal promised that all direct losses related to this incident would be fully borne by the project party, attempting to hedge uncertainty with a financial stance, while on the other hand, they had to admit they were still “in the process of identifying the cause.” For users, what they see is not just a number of losses but a complete set of how the DeFi infrastructure reacts in extreme conditions: when liquidity at the protocol level can evaporate overnight on a monitoring panel, any announcement of “pausing contracts” will be interpreted as a pressure test on the long-term credibility of this infrastructure.
From Full Compensation to Trust Stabilization: Haedal's Self-Rescue
Haedal’s statement that “all related direct losses will be fully borne by the project party” is not just a simple assurance; it delineates the boundary of responsibility early in the incident: any loss identified as a direct result of this anomaly will be covered by the team. This response shifts the users' concerns from “Will I lose everything?” to “How are direct losses calculated, and when will compensation be paid?”, psychologically providing a barrier against the most extreme panic. Compared to many past cases in the DeFi sector where losses arose from contract flaws or oracle issues, the common approach taken by project parties is to first emphasize “investigating” and “extreme market conditions,” sometimes even shifting the responsibility to third-party components, with discussions on compensation happening only after public opinion has fermented. Haedal, on the other hand, clearly locked in the “we will bear full responsibility” approach before announcing the suspension of relevant Vault contracts and without providing technical details, thus setting a distinguishing speed of response.
The combination of suspending contracts and compensation commitments constitutes a typical “stop the bleeding before diagnosis” plan: technically stopping potential risks from spreading further, while providing a baseline guarantee financially, thereby alleviating the pressures of concentrated redemptions and secondary market sell-offs in the short term. However, with the official language still at the stage of “precautionary measures” and “investigation ongoing,” the gap in transparency remains—users do not know the specific paths that triggered the anomaly and have no idea if there are systemic risks present, leaving them to temporarily place their trust in the quality of Haedal's future disclosures. Ultimately, whether this crisis can be seen as “trust restoration” rather than “the beginning of a black box incident suppressed by money” will depend on the completeness of subsequent investigation reports, update frequency, and whether they are willing to publicly share this lesson as a risk management case that can be scrutinized from the outside.
The Mystery of Sahara AI's 60% Plunge in 24 Hours
Almost at the same moment that Haedal announced it had entered the “investigation period,” the market curve for Sahara AI also began to distort: within the past 24 hours, the SAHARA token was reported to have dropped about 60%, with some media citing OKX market data reflecting its price approaching $0.01549 at one point. For many investors who had just bought in due to the “AI concept,” the speed of refreshing the order book far surpassed any official explanation, and the price plummeted straight down without any accompanying public negative information to match this decrease; this dislocation itself amplified the panic.
Faced with the unexpected crash, Sahara AI quickly issued a statement: the official characterized this market activity as “abnormal market volatility of the token,” emphasizing that the team was monitoring the situation in real-time, while specifically stating that the token contract and products “do not have security issues,” and announced the initiation of an internal investigation. From the wording, the project party deliberately positioned the risk boundary at the “secondary market trading level” rather than the contract or product itself. However, as of now, they have not disclosed specific events triggering the crash, characteristics of participating addresses, or any chain links that can provide insights for external review. In this information vacuum, investors can only guess based on experience: some choose to believe this is a singular sell-off magnified by thin liquidity, while others view this 60% drop as a discount for “unknown risks,” directly reflecting their lack of trust in the project through the sell button—when the price collapses before a conclusion, the market often penalizes not the fluctuation itself but the project’s ability to provide sufficiently transparent and verifiable narratives when uncertainty arises.
One Pauses, the Other Claims Safety: Contrasting Crisis Management
At the same stage of “reason yet to be clarified,” Haedal and Sahara AI chose two completely different paths. After Haedal detected an abnormal liquidity drop in some Vault pools, its first reaction was to “press the pause button” on the system: relevant contracts were halted, risks artificially locked down, while delivering the strongest commitment—full responsibility for all related direct losses would rest with the project party. For a DeFi protocol that provides yield pools to users on Sui, this stance amounts to admitting it is infrastructure: once algorithms and contracts malfunction, responsibility primarily lies with the protocol rather than attributing fluctuations to “market behavior.” The Haedal incident was first reflected in the abnormal liquidity internally within the protocol, and the project chose to intervene directly in the system itself, sending a signal to participants through the halt and backing: the risks are still present, but have been confined within a visible boundary.
Sahara AI's handling logic, on the other hand, resembles that of a narrative-driven AI concept token project: when SAHARA dropped approximately 60% within 24 hours, the crash was starkly visible in the secondary market price, yet the first statement from the official emphasized that “the token contract and products do not have security issues,” while noting that the team was monitoring market conditions in real-time and had launched an internal investigation. The implied positioning here is: the technical aspects are clean, with volatility attributed more to “abnormal market behavior,” shifting the responsibility back to a vague external environment rather than the protocol itself, which is why no compensation arrangements have emerged yet. In this rhetoric, Haedal regards itself as “infrastructure” responsible for asset safety, while Sahara AI acts more as if to remind users: the token you purchased is a highly volatile narrative token, so the price risks are supposed to be borne by yourself. Both sides say “investigating,” yet the former uses contract suspension and compensation commitments to shape a perception of “risk being controlled,” while the latter confines “safety” at the contract level, making the crash appear both severe and yet without anyone truly accountable for the outcome. Thus, the market can only express its stance through lower prices and worse liquidity as an immediate vote on the two different crisis response strategies.
The Era of Liquidity Fragility: How Users and Projects Can Coexist
As Haedal and Sahara AI faced issues around June 9, 2026, they laid bare the two most vulnerable points of this market: liquidity can dry up in a matter of hours, and trust can plummet sharply after an announcement or a trade. The former detected an abnormal liquidity decline in some Vault pools, chose to promptly suspend the relevant contracts, initiate an investigation, and committed to fully compensate for direct losses; the latter, after the token's approximately 60% drop, acknowledged "abnormal market fluctuations," emphasized that there were "no issues" at the contract and product level, and also announced an investigation, yet did not provide more specific technical causes or loss descriptions. Both incidents are still stuck at the “reason yet to be clarified” stage, with inherent information asymmetry existing; at this time, the project party's ability to timely contain losses, clarify the narrative, and assume responsibilities often has a greater impact on subsequent reputation and valuation than the fluctuation itself. For users, in this time window, it is more important to see the disclosed risk warnings, commitment boundaries, and action rhythms rather than just relying on any party's self-justification; before the conclusion is reached, reserving a buffer for their positions is crucial. Similar liquidity anomalies and price crashes are not uncommon in this industry, and whether Haedal and Sahara AI can continue to disclose investigation progress and maintain or even restore market trust after more details are revealed will directly determine whether users are still willing to allocate funds and time to these two names.
Join our community, and let’s discuss and become stronger together!
AiCoin exclusive Hyperliquid benefits: https://app.hyperliquid.xyz/join/AICOIN88
AiCoin exclusive Aster benefits: https://www.asterdex.com/zh-CN/referral/9C50e2
On-chain Telegram community: https://t.me/AiCoinWhaleData
On-chain community: https://www.aicoin.com/link/chat?cid=N6OVMor5g
AiCoin on-chain Twitter: https://x.com/aicoinwhaledata
免责声明：本文章仅代表作者个人观点，不代表本平台的立场和观点。本文章仅供信息分享，不构成对任何人的任何投资建议。用户与作者之间的任何争议，与本平台无关。如网页中刊载的文章或图片涉及侵权，请提供相关的权利证明和身份证明发送邮件到support@aicoin.com，本平台相关工作人员将会进行核查。
