SOON said its security incident review found no impact on the protocol or on user assets, and that mainnet RPC services have been restored, marking a return to normal network access following the incident.
The update, communicated through the project’s official channel on the SOON account on X, framed the review’s conclusion in two parts: the protocol itself was not affected, and user assets were not affected.
This is the extent of what the project has stated publicly. The review’s finding of no impact should be read as SOON’s own reported conclusion rather than an independent audit result, and no third party has confirmed the assessment.
For holders and ecosystem participants, the two claims answer the most immediate questions raised by any security incident: whether the network kept operating and whether balances were touched. SOON’s statement addresses both directly.
What “no impact on protocol or user assets” means for users
A finding of no impact on the protocol indicates that SOON does not consider the network’s core operations or its underlying logic to have been compromised by the incident.
A finding of no impact on user assets indicates that, per SOON’s review, funds and balances held by users were not lost, moved, or otherwise affected. The project has not published a detailed technical breakdown supporting either conclusion, so the statement stands on SOON’s own attribution.
Security incidents remain a recurring risk across the sector, and outcomes vary widely. Some are contained with no losses, while others are severe, as when Echo Protocol halted withdrawals after a security breach. SOON’s stated outcome falls at the contained end, based solely on its own review.
Mainnet RPC restoration signals a return to normal access
Alongside the review, SOON said mainnet RPC has been restored. RPC endpoints are the interface that wallets, developers, and applications use to read from and submit transactions to a blockchain network.
Restored RPC access points to service normalization, meaning users and applications should again be able to interact with the network through standard endpoints. This operational recovery is separate from the review’s findings; one concerns service availability, the other concerns whether harm occurred.
What remains unclear after SOON’s update
SOON’s statement provides the conclusion of the review but not the underlying detail. The available information does not include a root-cause explanation, an incident timeline, or a description of remediation steps.
Readers watching for follow-up may look for later disclosures covering the cause of the incident, any preventive measures put in place, and ongoing monitoring. None of these has been provided in the current update, and this article does not speculate on them.
FAQ: What users should know after the SOON incident update
Were user assets affected?
According to SOON, its security incident review found no impact on user assets. The statement is the project’s own conclusion and has not been independently verified.
Is the network accessible again?
SOON said mainnet RPC services have been restored, which points to a return to normal network access for wallets and applications.
What should users watch next?
The current update does not include a root cause, timeline, or remediation detail. Any future SOON disclosure on those points would clarify what happened and how it is being addressed.
Additional source references: source document 1, source document 2.
Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.
