This is the Bor v2.2.11 maintenance release for Polygon Mainnet. It focuses on improvements and bug fixes related to milestone processing and fork validation.

Important Note: This release is for Polygon Mainnet only and should not be deployed on Amoy, as it does not include the Rio hard fork changes.

This update brings several key enhancements for node stability and correctness:

Enhanced Fork and Milestone Validation
This release significantly strengthens how nodes handle chain validation.
- A new safety check has been added to validate the correctness of imported chains that do not yet have a whitelisted entry. The node will now trace the chain's history backwards to validate it against the last known whitelisted entry, preventing the node from syncing to an incorrect fork.
- A fix has been implemented to handle an edge case where a new milestone arrives while the node is importing a chain on a wrong fork. The node will now periodically check the canonical chain against the latest milestone to ensure it's on the correct path.
- A bug was fixed where a milestone-to-block hash mismatch error was not being returned correctly. Now, if a mismatch occurs, the milestone will be properly kept for future re-evaluation instead of being discarded.

New CLI Command and Resilience Improvements
To help operators manage corrupted local data, a new CLI subcommand has been introduced: bor purge-whitelisted-entries. This command allows for the purging of all local whitelisted entries for checkpoints and milestones. Additionally, the node can now bypass validation against an incorrect milestone and skip loading corrupted local entries, improving overall resilience.

TxPool Bug Fix
A bug in the legacy transaction pool has been fixed that could cause a node to panic. The fix prevents the use of a negative value when initializing an array during the transaction discard process, improving txpool stability.