Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
FollowingSOON said that its security incident review found that neither protocols nor user assets had been affected, and the RPC service on the main network had been restored, marking that network access had returned to normal after the incident.
The update was released through the project's official account on the X platform, dividing the review conclusions into two parts: the agreement itself has not been affected, and user assets have not been affected.
This is the entire public release of the project. The review's conclusion of no impact should be regarded as a self-reported conclusion by SOON, not an independent audit, and no third party has confirmed the assessment.
For holders and ecosystem participants, these two statements answer the most direct questions of any security incident: whether the network continues to operate and whether the balance has been passive. SOON's statement directly responds to both points.
What does "no impact on the protocol or user assets" mean for users?
The review of no impact on the protocol means that SOON believes the incident did not endanger the core operation of the network or its underlying logic.
A review result that has no impact on user assets means that based on SOON's review, funds and balances held by users have not been lost, transferred, or otherwise affected. The project has not yet released detailed technical analysis to support both conclusions, so the statement is based solely on SOON's own claims.
Security incidents remain a recurring risk across the industry, with outcomes varying widely. Some incidents are controlled without loss, while others are serious, such as Echo Protocol suspending withdrawals after a security breach. The results released by SOON are controllable, but are based only on its own review.
Mainnetwork RPC recovery marks a return to normal access
While reviewing, SOON stated that mainnetwork RPC has been restored. RPC endpoints are interfaces used by wallets, developers and applications to read blockchain network data and submit transactions. The restoration of RPC access points to service normalization, meaning that users and applications should be able to interact with the network again through standard endpoints. This operational restoration is separate from the review conclusion: one concerns service availability and the other concerns whether damage occurred.
What remains unclear after the update of SOON
SOON's statement provides review conclusions, but does not provide underlying details. The available information does not include root cause explanations, event timelines, or descriptions of remedial actions. Readers following follow-up developments may expect follow-up disclosures covering the cause of the incident, precautions taken, and ongoing monitoring. None of this content is provided in the current update and this article does not speculate on this.
FAQ: What should users know after a SOON event update
Are user assets affected?
According to SOON, its security incident review found that user assets were not affected. The statement is the conclusion of the project itself and has not been independently verified.
Has network access been restored?
SOON said main-network RPC services have been restored, which means network access to wallets and applications has returned to normal.
What should users focus on next?
The current update does not include root cause, timeline or remediation details. Any future disclosure by SOON of these points will clarify the incident and the response.
