#multiversx计划协调硬分叉恢复
MultiversX has confirmed that someone exploited the “atomicity” vulnerability in a virtual machine and wrote invalid states onto the blockchain. The team’s response isn’t a patch-and-restart; instead, they’re preparing for a “coordinated hard fork”—restarting the chain from a verified clean checkpoint, which effectively means rolling the ledger back.
There are two things here: fixing the code and rolling back the ledger. The patch is about how the system should run going forward; the rollback is about the portion that has already been recorded. The former is an engineering issue, while the latter is more like setting rules for a chain that shouldn’t need to be rewritten.
So I’d like to ask one question: when it comes to this kind of “rewind” done to recover losses, would you rather treat it as an emergency measure—or as a precedent that shouldn’t be set?
One detail worth paying attention to: after this block-production pause, the 26 protocols in the MultiversX ecosystem have a combined total fund size of less than $10 million. The ledger can be rolled back, but once trust has been rolled back once, can it be rolled back again?