Polygon fixes security flaw via two hard forks after private deployment

The private-then-public deployment sequence is the notable detail here, signaling that Polygon prioritized minimizing exploit risk over transparency in real time. This affects validators and node operators who must upgrade in sync, as hard forks carry coordination friction. The open question is whether this quiet patching approach becomes a template for future critical fixes across the network, and how the community reacts to being informed only post-deployment.