mainnet

Raydium core contributor InfraRAY posted on platform X, stating that the team has confirmed that the old version of the AMM V3 program, which was previously discontinued in 2021, has been attacked. The attacker unauthorizedly removed part of the liquidity, but this incident does not affect current Raydium users, and the related liquidity pools have been unable to interact through the official Raydium UI since being disabled. The Raydium SDK and DApp also do not support operations on the mainnet old version AMM V3 liquidity pools.The five affected liquidity pools include: Sollet USDT-RAY, Sollet ETH-RAY, SRM-RAY, USDC-RAY, and RAY-SOL. Preliminary statistics show that the stolen assets include approximately 150,177 RAY, 5,603 SOL, and 893,700 USDC, with a total value of about $1.34 million. The related losses will be fully compensated by the treasury.Investigations reveal that the vulnerability originated from insufficient verification of the LP token minting address. The attacker created new LP tokens and impersonated legitimate LP tokens, bypassing the protocol's ratio verification mechanism to extract funds. However, this incident is classified as an independent logical vulnerability and is not due to private key leakage or permission intrusion, and there is no risk of spread. Currently, all existing Raydium mainnet programs have not been affected.

StarkWare announced on the X platform that the Starknet v0.14.3 version will go live on the mainnet this month, with the testnet launch scheduled for June 9 and the mainnet launch scheduled for June 22. The new version will support dynamic L2 Gas base fee adjustments based on STRK, improve block generation speed, reduce the target L2 Gas consumption per block while keeping the maximum block size unchanged, and deprecate RPC 0.8.Due to the significant changes included in this update, the official recommends that all developers carefully read the pre-release notes to prepare for compatibility and upgrades.

According to The Block, the Sui Foundation released an incident analysis report on the recent three interruptions of the mainnet, attributing the three network outages that occurred last Thursday and Friday to two independent vulnerabilities introduced by the v1.72 version upgrade. The first interruption lasted about six and a half hours, while the second and third occurred on Friday morning and afternoon, respectively.The first two interruptions were caused by the "address balance" feature introduced in v1.72, which exposed flaws in the transaction fee deduction method. When a transaction was canceled due to insufficient funds, the network would still spend those funds, resulting in a negative balance that caused the validation node reconciliation process to crash. The foundation acknowledged that the temporary fix pushed urgently on Thursday carried known interruption risks, and the team accepted this risk to quickly restore on-chain services, which led to another network interruption on Friday morning.The third interruption was triggered by another undisclosed random state vulnerability, occurring when the validation nodes restarted to install the fix patch. Sui stated that user funds were never at risk, that both vulnerabilities have been fixed, and that a mechanism to forcibly terminate stalled epochs has been established. The foundation also mentioned that AI agents with access to its production systems significantly accelerated the diagnostic process.

According to developer donnoh, due to a vulnerability that occurred during a recent upgrade, the status updates of the Base network have been stagnant for over 30 hours. However, since the withdrawal from Base to the Ethereum mainnet requires about a 7-day challenge period, most ordinary users have not yet noticeably perceived this anomaly.Subsequently, the official Base status page released an announcement confirming that the issue originated from a fault related to the TEE (Trusted Execution Environment) enclave, which caused the network proposal process to be interrupted, thereby affecting the status update process.The official statement indicated that the withdrawal function of the Base mainnet is currently experiencing delays, and the team is working on repairs. Aside from the withdrawal process, other core network components have not been directly affected.

Circle released the "Post-Quantum Security White Paper," proposing a phased post-quantum resilience roadmap focused on the long-term security of the Arc blockchain ecosystem.The roadmap covers multiple technical directions, including quantum secure signatures, private execution environments, validator hardening, infrastructure migration, and account recovery, applicable to core components such as the Arc network, USDC, smart contracts, and validators.Circle stated that it plans to provide post-quantum signature support when the Arc mainnet launches (in 2026) to enhance the ecosystem's ability to respond to future quantum computing threats.

Sui stated on platform X that the mainnet has been restored and transactions are proceeding normally. During the deployment of the long-term repair plan yesterday, the end of the epoch was triggered, causing a pause. When the validating nodes restarted to deploy the new binary files, the random number initializer that runs at the beginning of each epoch could not complete because its quorum threshold was higher than the Sui consensus mechanism. After the validating nodes restarted, there was a potential vulnerability in the fault state preservation mechanism, which prevented the network from completing the transition to the next epoch. Currently, the validating nodes have implemented a fix that addresses the underlying vulnerability and the affected epoch, and network activity has resumed.

Sui stated on platform X that due to issues during the epoch change, the Sui mainnet has stopped accepting user transactions. The validator nodes are still running and creating system transactions, but currently cannot accept user transactions. The Sui core team is investigating this issue and will release updates immediately.

According to the official announcement from Sui Network, the Sui mainnet has resumed normal operation, and transaction processing and network activity have both returned to normal. The official disclosure states that the two network outages that occurred yesterday and the day before were related to an interaction issue between the "Address Balances" feature introduced in version 1.72 and the Gas billing logic. The Sui core team indicated that the fix deployed yesterday was only a temporary measure aimed at quickly restoring network operation, but this solution carried a known and low-probability risk of outage. Today, the network triggered a variant of the known issue, causing the mainnet to pause again. Currently, the validators have completed the deployment of a long-term fix, and the official claims that the known issues caused by the original vulnerability have been thoroughly resolved, with the network now operating normally. The Sui team stated that they will release a more detailed incident review report in the future, explaining the cause of the failure and the repair process.

Sui posted, "The Sui mainnet is currently experiencing network stagnation, and current network activity may have been paused. The Sui Core team is actively investigating the issue. Updates and event reviews will be shared as soon as they are available."Earlier, Sui's official update this morning stated that Sui mainnet activity has returned to normal. The network had previously gone down due to a crash bug caused by the Gas billing logic introduced in version 1.72.

Base Azul has launched its mainnet, and this upgrade makes the Base network faster and more secure.

Sui official announced this morning that the Sui mainnet activities have returned to normal. Previously, the network experienced downtime due to a crash bug introduced by the Gas billing logic in version 1.72. The official stated that a complete incident review report will be released in the coming days.

Sui official announcement, the mainnet is currently experiencing network stagnation, and the core development team is actively working to resolve it. Please note that transactions may be suspended at this time, and the latest updates will be released as soon as possible.

According to official news from Optimism, the OP mainnet has adjusted its transaction sorting rules for the first time starting today. For many years, the sorter only used the "highest priority Gas fee first" mechanism, and now a new priority sorting option based on staking has been added.This experiment will last for four weeks (until June 23) and was approved by the Optimism governance body earlier this month, allowing users to participate voluntarily. The participation condition is to stake no less than 100,000 OP to the PolicyEngine Staking contract.The experiment will be conducted in two phases: the first phase (Week 1) will use FIFO (first in, first out) sorting, and exceeding the minimum staking amount will not affect priority; the second phase (Weeks 2-4) will change to a priority Gas multiplier mechanism weighted by staking duration, where the longer the staking time, the higher the priority.The transaction sorting rules for users who do not participate in the experiment will remain unchanged, and the PGA mechanism will continue to operate as usual.

According to Token Terminal data, Ethereum's monthly transaction count has reached a historic high, exceeding 70 million transactions, while the median transaction fee is approximately $0.00554, marking a historic low.

Lighter officially stated on X that it has completed the escape mechanism verification conducted by the third party L2BEAT, which means that even if the sequencer at the L2 level fails, users can withdraw funds from Lighter's L2 back to Ethereum in a permissionless manner. It is the first L2 Perp DEX in the industry to achieve this functionality.

The Solana development company Anza announced that it has officially recommended the mainnet validators upgrade to Agave 4. This upgrade introduces XDP for Turbine, QUIC-only TPU data access, a faster replay stage, and several SIMD features that will be activated during this cycle.Anza stated that production environment tests on large mainnet validators showed that XDP has reduced the Turbine retransmission delay from about 600 ms to approximately 0.8 ms, providing critical performance headroom for Solana's push towards 100 million CU blocks. Additionally, Agave 4 has completely removed UDP transaction access, making QUIC the only transaction submission method; PoH entry verification and Ed25519 signature verification have also been removed from the critical path and processed asynchronously to enhance replay stage performance.This round of upgrades will also gradually enable several SIMD features, including p-token (an SPL Token alternative that can free up about 13% of block capacity), Stake Program v5, SBPFv3 support, pre-funded account creation, and BLS12-381 syscall, among others.

According to official news, the BNBAgent SDK has officially launched on the BSC mainnet, providing core infrastructure for the large-scale implementation of AI agents on the blockchain.This SDK is centered around four modular components:Identity and trust based on ERC-8004;Business and custody based on ERC-8183 (APEX);Autonomous payments integrating MPP and x402;Memory and storage based on BNB Greenfield, comprehensively addressing key challenges for AI agents in authentication, business collaboration, automatic settlement, and continuity of memory across operational environments.Developers can leverage this standardized framework to efficiently build, deploy, and realize commercial monetization of AI agents on the BNB Chain.The first batch of partners is strong, including industry leaders such as Google, AWS, Virtuals, Binance Pay, Trust Wallet, Binance Wallet, and $U, jointly injecting strong momentum into the implementation and development of the BNBAgent SDK.

According to CoinDesk, the Solana validator client Firedancer developed by the crypto division of high-frequency trading firm Jump Trading has been launched on the Solana mainnet and has begun producing blocks.Firedancer's founding engineer Ritchie Patel stated that the client has processed tens of millions of transactions in a production environment, but the team will still take a gradual approach to promotion and does not want validators to switch en masse before the security audit is fully completed.In addition, Patel mentioned that the architecture of Firedancer heavily draws from traditional financial high-frequency trading systems, and the team recently completed a public security audit competition that included a $1 million bug bounty pool.

Kelp announced on platform X that the rsETH protocol has fully resumed normal operation, and the related functions have been re-launched on the mainnet and all Layer 2 networks, with the overall system status restored to normal levels. The rsETH exchange rate has been updated, accounting for all staking reward earnings accumulated during the suspension period. Meanwhile, EIGEN rewards are now open for distribution to rsETH holders, covering the entire suspension period.In addition, the deposit and withdrawal functions have been restored on the mainnet and Layer 2 networks, and the rsETH asset support status has been fully restored to 100% backing. The official emphasized that the current rsETH has achieved complete and sufficient support on the mainnet and L2 networks, and all operational processes have returned to normal.