[CURRENT::MONITOR] /risk_feed └─ online /protocol_signals └─ connected /status_updates └─ streaming > system online

Are you even a real surfer if you aren’t looping your yield yet? 🌊 We’ve partnered with @CurrentSUI to give Slushies exclusive access to a 3,000 $SUI rewards pool. Boost your bags with the loop strategy and secure your piece of the pie. Check your Slush Wallet today!

DeFi lending shouldn't need a UI tutorial. @CurrentSUI is now a skill in Epoch AI 🟢 — lend, borrow, repay and withdraw on their Main Market just by asking: "deposit 5 SUI on Current" "borrow USDC" "show my Current positions" Non-custodial: you sign every tx in your own wallet. One chat, real on-chain lending on @SuiNetwork. epochsui.com/epoch-ai

📢 Thank you for your patience. We have completed the Haedal Vault post-mortem report, covering the affected scope, root cause, loss accounting, and current next steps. The total direct loss is estimated at approximately $915,179 (Haedal will cover the user loss). On June 9, we detected abnormal liquidity decline across several Vault pools. To prevent further abnormal activity, we paused the related contracts while investigating the issue. After a thorough diagnosis, we confirmed that the root cause was a hidden cross-version logic issue related to a Vault upgrade deployed at the end of last year. After the newer Vault package was released, older package entrypoints remained callable instead of being fully deprecated through a forced upgrade. This allowed the attacker to mint more Vault LP shares than expected through an older deposit path, then redeem them against the Vault’s underlying assets. The old package, new package, and upgrade had all gone through audit review, and the issue did not surface when each version was reviewed independently. In hindsight, the update should have been treated as a forced upgrade, as keeping older entrypoints callable allowed the hidden cross-version logic loophole to appear. To clarify, the issue was only limited to Haedal Vault. All other Haedal products, modules, and assets remain fully safe and unaffected. We are now working on a patched version, which will go through re-audit and cross-party review before the upgrade and unpause. We are also coordinating with partners on fund tracking and the investigation against the exploiter. As previously stated, all direct losses regarding this incident will be covered by Haedal, and affected users will be made whole. Please rest assured. A detailed fund recovery plan will be shared later once the short-term barriers are cleared. We sincerely apologize for the inconvenience and concern caused. Thank you again for your continued patience while we complete the next steps carefully. 🫡

📢 We recently detected an unusual liquidity decline across a limited number of pools in Haedal Vault. As a precautionary measure, we have temporarily paused the related contract while the team investigates the root cause and prevents any further impact. The impact is limited to a small number of Haedal Vault pools. All other Haedal products and modules remain secure and fully unaffected. All direct losses related to this Vault matter will be fully covered by Haedal. Please rest assured. We will share a more detailed investigation update once the analysis is complete. Thank you for your patience and understanding. 🙏

Bear markets separate the teams who build from the teams who tweet. We chose building. Heads down, every day, on infrastructure most people won't appreciate until the moment they suddenly need it. That moment is coming faster than the market thinks.