UNCX Vesting V2: Security Incident Update Following the security incident affecting our Vesting V2 contracts across several chains earlier today, we want to share an update on the measures taken, the affected tokens, and what comes next. 1. Security measures and containment We have implemented several measures to prevent further exploitation of the affected contracts: > Introduced substantial flat fees exceeding 1,000 ETH per lock. > Removed all clients and contract interactions that previously allowed these fees to be bypassed. > Increased token fees to the maximum permitted by the Vesting V2 contracts (5%), making repeated vesting top-ups economically unviable. These measures are designed to prevent further exploitation through the identified methods. While our investigation and monitoring remain ongoing, we firmly believe we have taken the necessary steps available to us to contain the incident. 2. Scope of the incident As previously communicated, all LP lockers remain unaffected, across every protocol and chain supported by UNCX. The incident is isolated to UNCX Vesting V2. Our legacy vesting contracts are also unaffected and have undergone additional checks and review. The incident currently involves 10 tokens across 4 chains: Ethereum (6): $pepecoin, $EDGEN, $ZC, $X, $LO0P, $PAAL Base (1): $IMO BNB Chain (1): $BTCLE Robinhood Chain (2): $CASHCAT, $RKST 3. Next steps for affected projects and communities We are already in contact with most of the affected teams, communities or individuals impacted. We expect to share further guidance and next steps with affected teams this week. We will also publish a comprehensive incident report covering the technical findings, financials, and the details of our proposed recovery plan. Important: For all impacted tokens, we strongly advise against trading in the affected pools until further guidance is provided by the respective token teams. We will be coordinating directly with those teams over the coming days. 4. Investigation and recovery efforts Our investigation remains active, and we are coordinating with law enforcement and @seal911. To date, no funds have been returned by the attackers (primary and copycats) on any affected chain. We strongly encourage the responsible party to contact us directly to discuss a resolution. We understand the seriousness of this incident for affected projects, holders, and communities. Our immediate priorities remain preventing further exploitation, establishing the full extent of the impact, and working closely with affected teams toward a recovery plan. We will continue to communicate when any meaningful updates become available. Thank you for your patience. The UNCX Team

Ledger is investigating reports of loss of funds from users in South East Asia who purchased products from a reseller named CryptoBillis. As a precaution, and pending the results of our investigation, we have asked CryptoBilis to pause all sales and shipments of Ledger devices. We recommend Ledger users who purchased from this reseller in the last 90 days to not initiate set up if you have not done so yet. If you have set up your Ledger device, consider moving assets to a new Ledger signer (with new seed). We will continue to inform customers of updates as the investigation progresses. Reach out to Ledger customer support through official channels with any questions: support.ledger.com/

📢 79VAULT SYSTEM UPGRADE 🔧 Our technical team is performing system optimizations to enhance stability and performance. ⚠️ Some front-end features and asset-related operations may be temporarily affected. Services will resume after the upgrade. Thank you for your patience! 💛

Blast will be shutting down. We launched Blast with the goal of building a self-sustaining chain for users and developers. Unfortunately, the economics of operating the chain no longer make sense: the ongoing costs of maintaining Blast exceed the revenue generated by the L2, and we do not see a credible path to making the chain economically sustainable. As a result, we've made the difficult decision to wind Blast down. We're sorry to the users and developers who believed in Blast, built on it, and supported the ecosystem. Our priority now is making the shutdown as smooth and safe as possible. We're asking all users to withdraw their assets from Blast to Ethereum mainnet, including any balances held in the Blast PWA. To make this easier, we will be reducing the withdrawal delay to 24 hours. As part of the shutdown process, we'll first begin withdrawing Blast's Lido assets. This process is expected to take approximately one week. During this period, withdrawals will temporarily be unavailable, even after the withdrawal delay is reduced to 24 hours. Once that process is complete, withdrawals will resume with the new 24-hour delay. Users will have until October 26, 2026 to withdraw through the normal Blast interface. After October 26, assets will remain withdrawable, but users will need to interact directly with the Blast bridge contracts on Ethereum L1. We'll publish detailed instructions before then. We strongly encourage everyone to withdraw their assets to Ethereum mainnet before October 26.

Earlier today NEAR Intents services were stopped after a security incident was detected. The incident was caused by a bug in the Omni deposit and withdrawal infrastructure interaction with NEAR Intents smart contract. The preliminary report indicates the total loss of approximately $3.8M. These funds will be compensated in full. The contract-side vulnerability has been patched. The operations of the NEAR Intents and near(.)com are expected to resume within 1h. Deposits and withdrawals on the following networks will remain unavailable for an additional ~12 hours while fixes to the Omni infrastructure are completed: BSC, Polygon, TON, Optimism, Avalanche, Stellar, Monad, LayerX, Adi, Scroll and Plasma. In case users hold any assets from these chains inside NEAR Intents (for example, in HOT wallet or on near(.)com), they will be able to swap them into other assets once NEAR Intents is back up (in ~1h). The incident has been reported to law enforcement, and we are working with security and blockchain analytics partners to trace the funds and pursue recovery. A detailed report will be shared publicly in the following days.