Péter Szilágyi, an Ethereum software developer, took to Twitter to announce they had found a regression that resulted in a corrupted state. He explained that it might have been a pull request that had merged toward the new storage model or online pruner.
The developer continued to highlight that the problem will likely affect those running the release, and explained that the reason it wasn’t caught during benchmarking is because data loss only happens on shutdown.
Go Ethereum released a hotfix to patch the bug a day later, and the team advised people to roll back their chains and rerun.
This is the first time that the developers find bugs since the Ethereum Merge was planned for mid-September, and it is unlikely that it will affect the date.
If you see something out of place or would like to contribute to this story, check out our Ethics and Policy section.