52.20 $
+1.97% +1.01 $
52.20 $
+1.97% +1.01 $
Corrected chronology of the 2026 MWEB incidents, the invalid-chain reorganization and current upgrade references.
The earlier article conflated two incidents and described a rollback of the valid chain. The developer postmortem gives a different account; this correction replaces that wording and withdraws the unsupported fixed dollar-loss headline.
According to David Burkett's postmortem of 28 April 2026, a March validation flaw enabled an inflated peg-out of 85,034.47285734 LTC at block 3,073,882. Recovery and rebalancing followed. On 25 April, another attempt triggered a failure affecting upgraded mining nodes. Unupgraded miners extended an invalid branch; the valid chain subsequently displaced 13 invalid blocks. The report did not give a finalized total for all third-party losses.
| Earlier wording | Correction |
|---|---|
| Valid history was rolled back | The postmortem describes removal of an invalid branch. |
| A single first incident | The March exploit and April disruption must be distinguished. |
| A definitive $600,000 total | A fixed aggregate dollar loss was not established by the cited report. |
A release that addressed a historical incident is not automatically today's recommended installation. Consult official Core releases, verify signatures and read subsequent release notes. See our Core 0.21.5.8 analysis for the September release.
Wallet operators and merchants should maintain a tested backup and upgrade process. A price chart, hash-rate estimate or list of confirmations cannot establish that a specific integration handles every consensus edge case correctly. Review node behavior and payment reconciliation together.
