5 hours ago
3
What MultiversX confirmed
- The problem involved transaction atomicity.
- Invalid changes were recorded onchain.
- Mainnet operations were suspended.
- A patch entered shadow-fork testing.
- Targeted recovery was being evaluated.
What remains unknown
- Whether users permanently lost funds.
- Which accounts or contracts were affected.
- How the attacker triggered the failure.
- Which recovery method will be adopted.
- When every service will reopen.
The halt froze the problem; it did not undo it
In its incident update, MultiversX said an attacker attempted to exploit an atomicity problem in the mainnet virtual-machine layer. Developers suspended network operations while they traced the resulting state changes and prepared a patch. No confirmed loss figure had been disclosed.
Stopping block production prevents new transactions from building on records that may already be incorrect. It also blocks another attempt using the same method while engineers determine which balance...
English (US)