This is the kind of update I like to see. The issue was identified, contained, and the excess-reward path has now been shut down. The emergency hardfork is about fixing the root of the problem, not pretending it never happened. That’s how a serious network responds under pressure: detect, contain, coordinate, fix, and document. The assets remain safe, and the full post-mortem should give the community the technical details to properly understand what happened. Battle-testing isn't failure; how a network responds to failure is part of proving its resilience. 🔶