BLUB NFTs are more than collectibles.
🐟 Blubbers
Created by the community.
Burn this NFT to receive 50,000,000 $BLUB
https://t.co/iAx2HCL8dS
🐟 BLUB Originals
Created by the team.
Recently revived and back in the ecosystem.
Stored on Walrus for decentralized data storage.
Built with no single point of failure.
Two collections.
One community.
Whether you're here for the burn utility, the history, or what may come next, BLUB NFTs continue to be part of the ecosystem.
Still swimming. 🌊🐟
@blubsui@SuiNetwork
Most crypto users still rely on a single wallet.
That means a single point of failure.
If your seed phrase is stolen...
If your wallet is compromised...
If an attacker gains access...
Your funds can be moved immediately.
SuiSafe by BLUB was built to solve this problem.
Instead of relying on a single wallet, SuiSafe uses Sui's native multisig technology.
For example:
Wallet A
+
Wallet B
Both approvals are required before any funds can move.
If Wallet A is compromised, the attacker still cannot move funds without approval from Wallet B.
This removes the biggest weakness of traditional wallets: relying on a single key.
SuiSafe is also built directly on Sui's native multisig system.
✅ No smart contracts
✅ No third-party custody
✅ No contract upgrade risk
Just multiple approvals protecting your assets.
Security isn't only for institutions, DAOs, or large holders.
Everyone deserves better protection.
That's why the BLUB team built SuiSafe.
Not just a memecoin.
Building real infrastructure on Sui.
BLUB × SuiSafe × Sui
SuiSafe by BLUB https://t.co/E6ZIZLSjhS
@blubsui@SuiNetwork
Many people still think BLUB is just another meme coin.
It's not.
BLUB is building:
• NFT ecosystem
• DEEP reward staking
• SuiSafe security tools
• Developer SDK
All on SUI.
Still swimming. 🐟
@blubsui@SuiNetwork
📢 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. 🫡