Update

KiloEx updates on the hacker incident: a case has been filed in Hong Kong, and a compensation plan is being developed while funds are being raised

ChainCatcher news, according to official information, KiloEx announced on April 15 regarding the progress of the hacking incident that it has reported to the Hong Kong police and filed a case, and is cooperating with the Criminal Investigation and Cybersecurity departments for investigation. Some information related to the hackers has been obtained. Meanwhile, KiloEx has collaborated with the security company SlowMist to submit a detailed incident report, which will be publicly released when the time is right.The security vulnerability has been fixed, and there is currently no risk of position liquidation. All positions will be settled at the snapshot price before the incident. KiloEx is formulating a compensation plan and raising funds, and the Vault function will gradually resume after the plan is implemented, ensuring the safety of user funds.The hackers have not yet moved the stolen funds. KiloEx has repeatedly sent messages on-chain requesting the return of 90%, but has not received a response so far. The related addresses have been jointly blocked in coordination with multiple DeFi protocols and CEX.In response to rumors about internal involvement, KiloEx solemnly clarifies: the police and SlowMist have fully intervened in the investigation and obtained all internal data. If there are internal issues, the case will not be filed.

Hyperliquid co-founder responds to concerns about agreement security: Leveraging system and HLP liquidation mechanism have been updated

ChainCatcher message, Hyperliquid co-founder @chameleon_jeff responded on X to concerns that "the Hyperliquid protocol may suffer significant losses due to market manipulation":Hyperliquid's margin design strictly ensures the platform's solvency through mathematical mechanisms, with HLP's losses always limited to its own treasury, and the protocol's operation never relying on HLP------this feature existed prior to the JELLYJELLY incident. The newly added protective mechanisms after the incident only optimize HLP's loss resistance in backup liquidation, and the underlying architecture of the protocol has not changed. In the recent JELLYJELLY incident, an attacker attempted to manipulate HLP (liquidity provider pool) by establishing a massive long and short position on themselves. Although the unliquidated contract limit at that time allowed for the establishment of a position worth 4 million USDC, the logical flaw was that HLP used its entire fund balance as collateral for this liquidation. It should be clarified that the platform itself does not face solvency risks, but HLP did face excessive risk exposure due to market manipulation.Currently, HLP's liquidation component treasury has set a collateral limit, restricting potential losses through the backup liquidation mechanism. Hyperliquid still maintains its original operating mechanism, processing under-collateralized positions in the following order: 1) market liquidation 2) backup liquidation 3) automatic deleveraging (ADL). The current backup liquidation of HLP has added protective mechanisms by setting loss limits, making the cost of manipulating the mark price far exceed the limited gains that can be obtained from HLP.
ChainCatcher Building the Web3 world with innovators