📢 MEXC Will Support the Stacks (STX) Network Upgrade To support the Stacks (STX) network upgrade, deposits and withdrawals will be temporarily suspended. Network Upgrade: Jul 29, 2026, 03:00 (UTC) Deposit & Withdrawal Suspension: Jul 29, 2026, 00:00 (UTC) Please note: ✅ STX trading will remain available. ✅ No hard fork is expected. ✅ Deposits & withdrawals will resume once the network is stable. Please complete your deposits in advance if needed. #MEXC# #STX# #Stacks# #NetworkUpgrade#

🔔 SCR Network Upgrade Incoming MEXC will support the upcoming Scroll (SCR) network upgrade. ⏰ Upgrade: Sep 22, 02:00 UTC ⏸ Deposits & withdrawals suspended from 00:00 UTC ✅ SCR trading remains unaffected 🚫 Please DO NOT make deposits during the suspension period. Plan ahead, $SCR holders 👀💙 #MEXC# #Scroll# #SCR# #CryptoUpdate#

In a future network upgrade, HIP-3 will support optinal deployer configuration for permissioned markets. This would, for example, allow U.S. investors to access certain markets, or institutional investors that have strict rules.

📢 Important Notice for ADA Network Users Following the Cardano (ADA) network upgrade, MEXC will update deposit addresses for: 🪙 ADA, FLDT, SNEK, MIN & NIGHT Please remember: 🔹 Deposits will be suspended from Aug 1, 12:00 (UTC). 🔹 Deposits resume on Aug 3, 12:00 (UTC). 🔹 Generate a new deposit address before making any deposits after services resume. 🔹 Do NOT use your old deposit address—it will become permanently invalid and may result in asset loss. Stay safe and thank you for your support! 💙 #MEXC# #Cardano# #ADA# #Crypto# Please refer our announcement:

Zcash rolled out its Ironwood network upgrade Tuesday, permanently sealing the chain’s previous primary private transaction pool, called Orchard, so that it can no longer accept deposits or internal transfers, and opening a private pool named Ironwood. More here 👇

Testnet Scheduled Maintenance Announcement Please be advised that the testnet will undergo a scheduled protocol and network upgrade today. • Maintenance Window: 17:00 – 21:00 UTC+8 (4 hours total) • Service Impact: All testnet services—including testnet RPC nodes, block explorers, cross-chain bridges, and the testnet faucet—will experience full downtime during this window. • User Action: Please pause active deployments, automated transactions, and AI agent testing prior to 17:00. Unsubmitted or pending transactions may fail to execute while nodes are brought offline for updating. All services will automatically resume once full network synchronization is completed following the upgrade.

What is Stellar’s “Adapter” Upgrade? Stellar’s (@StellarOrg) next network upgrade, Protocol 28, is called Adapter. Stellar describes it as a builder-focused upgrade, with most of its changes aimed at making Soroban smart contracts easier to build, upgrade and maintain. But Adapter also includes a deeper change to Stellar’s consensus process that could help the network handle growing activity more efficiently. Here’s what is changing: (1) Faster consensus under heavy network load CAP-83 changes how Stellar validators handle transaction data during consensus. Today, validators need to receive a full transaction set before they can make progress. Adapter allows validators to begin voting before the entire transaction set has arrived. If the transaction data is late or invalid, validators can explicitly drop it instead of waiting indefinitely. That means consensus can keep moving even when transaction data is slow to propagate. The performance gains will roll out gradually as parallel transaction set downloading is enabled after mainnet. For users, this is mostly a behind-the-scenes improvement. For Stellar, it could become important as the network scales and needs to maintain fast, low-cost transactions under heavier demand. (2) Smart contract fleets can be upgraded together CAP-85 introduces externally managed executables for Soroban contracts. This targets protocols that operate large fleets of contracts using the same underlying code. Today, upgrading those contracts individually can leave some instances running old code while others use the new version. That creates both operational complexity and a potential security risk. With Adapter, contracts can point to a shared executable reference controlled by another contract. Developers can update that shared reference once, allowing every connected contract to switch to the new code atomically. (3) Smart contract data becomes easier to migrate CAP-86 tackles another problem developers face as contracts evolve. Smart contract data structures can change over time as developers add fields, remove old ones or modify interfaces. Existing host functions can reject data when its structure does not exactly match what a contract expects. Adapter introduces new sparse host functions that can handle missing or additional fields more gracefully. That makes it easier for developers to migrate contract data between different versions without breaking existing applications. For builders, this could make long-lived Soroban applications easier to maintain. (4) Adapter is mainly about developers The important point is that Protocol 28 is not primarily a user-facing feature upgrade. Two of its three major changes, CAP-85 and CAP-86, are focused directly on smart contract development. They aim to make contracts easier to upgrade, safer to maintain and more flexible as applications evolve. CAP-83 works at a deeper infrastructure level by improving how Stellar reaches consensus when transaction data is delayed. Together, the changes are aimed at making Stellar more capable as its smart contract ecosystem grows. So when does Adapter actually arrive? Stellar has scheduled the Protocol 28 testnet upgrade vote for August 27 at 17:00 UTC. The mainnet upgrade vote is scheduled for September 16 at 17:00 UTC. The mainnet vote is the key governance decision. A successful vote would move Protocol 28 closer to deployment, but the vote itself does not mean Adapter is already live. Stellar also expects its Core stable release to become available on August 13, followed by additional infrastructure and SDK releases between August 13 and 21. Developers, validators and infrastructure operators will need to prepare for the upgrade before the relevant votes. If Protocol 28 passes its mainnet vote, Stellar will take another step toward becoming a more mature platform for large, long-lived smart contract applications.

🔓 Hyperliquid Is Unlocking Idle Liquidity .@HyperliquidX is upgrading HLP so unused USDC will automatically earn native lending yield instead of sitting idle. After the next network upgrade, HLP will deploy USDC that isn't being used for market-making into HyperCore’s native lending pool. The numbers show why this matters: → HLP TVL: ~$188.7M → Idle $USDC: ~$148.7M, nearly 79% of HLP capital → Allocated to strategies: ~$40M → Native lending supply APY: ~2.87% at the time of the snapshot At the current supply rate, deploying the idle capital could potentially generate several million dollars in annual interest, although actual returns will vary with utilization and lending rates. HLP was originally built around market making and liquidation backstop functions, requiring large cash reserves. But as Hyperliquid's order books mature and external liquidity grows, keeping most of that capital idle becomes increasingly inefficient. This is a strong sign of Hyperliquid's infrastructure maturing. Instead of choosing between liquidity and yield, HLP is becoming a multi-strategy capital engine: Market making + liquidation backstop + native lending yield. The bigger picture is that Hyperliquid is increasingly optimizing every layer of its ecosystem for capital efficiency.