Technologie & IA
Polygon releases Bor 2.11.2 to improve connection management for PoS nodes
The stable Bor release published on November 19 changes how Polygon PoS nodes free up connections when capacity is under pressure. It also gives operators more visibility into peer activity and fixes a block production issue.

Connection rotation starts when capacity becomes scarce
Polygon released stable version 2.11.2 of Bor, the execution software for Polygon PoS, on November 19, 2026, at 17:15 UTC. The notes say the release carries forward code tested in the third beta of the same series. It introduces a connection rotation policy for cases when slots on a node become scarce. Nodes communicate with peers to receive or share data they need to operate.
The notes distinguish peers that remain silent from certain incoming peers that request data without contributing any. The second category becomes eligible for rotation when the node has refused new incoming connections for lack of capacity. The policy takes recent useful contributions into account. It protects peers the operator has configured as static or trusted. The mechanism as described is meant to free up slots under defined conditions, with settings that apply to the individual node.
Scores become visible in monitoring tools
The release adds information about peer activity and scores to the node’s administration data. It also exposes aggregate metrics and logs changes between score categories. Detailed per-peer metrics remain off by default. These measures give operators points of comparison between a peer’s observed behavior and the overall state of the node’s connections.
Polygon says the score serves as an observation tool in this release. Connection rotation uses a separate activity policy. The features serve different purposes. A log entry about a score change tells the operator about observed activity. Freeing a connection depends on the rotation policy’s criteria. The notes do not describe these scores as a new penalty applied across the network.
A fix for block producers
Bor 2.11.2 also changes how a node handles a block it has already produced. The fix prevents the producer from rebuilding its own block when the entry has been accepted but the read path has not processed that information yet. Polygon links the change to the sequence store used by producers. A separate change covers how future protocol versions are identified while preserving compatibility with versions already known to released binaries.
According to the notes, operators using the third beta can move to the stable release without changing their settings. Rotation is on by default and its settings can be changed. The November 19 release covers Bor, the execution layer for Polygon PoS. Heimdall’s Purley upgrade concerns the consensus software and follows its own timeline.
