The Ledger
Polygon publishes Bor v2.11.1 with security and stability fixes
Polygon made Bor v2.11.1 public for Polygon PoS mainnet and Amoy, describing it as a security and stability update over v2.11.0. The release notes detail changes to block-import checks and blob-transaction pre-checks, and say no hardfork or database resync is required.

Public release for two networks
Polygon Labs released Bor v2.11.1 for Polygon PoS mainnet and Amoy on Nov. 16, according to a post on the Polygon Community Forum. It is the public release of v2.11.1-priv, which Polygon says includes important security and stability fixes on top of v2.11.0. The post says the source code is now public.
What operators are asked to do
Operators already on v2.11.1-priv are running the same code, the post says, and should switch to the public v2.11.1 at their next maintenance window to return to the standard release channel. Nodes can be switched one at a time, in any order. Operators still on v2.11.0 are asked to upgrade to v2.11.1 at their earliest convenience.
Polygon says the release is not a hard fork and is not consensus-affecting. Moving from v2.11.1-priv to v2.11.1 changes no behaviour, with no activation block, chain-config or genesis change, database schema change or resync, and v2.11.0, v2.11.1-priv and v2.11.1 nodes interoperate normally. No configuration change is required. The public build reports version 2.11.1, where the private build reported 2.11.1-private.
Behaviour changes
According to the post, eth_simulateV1 calls that include blob hashes now return “blob base fee unavailable” unless the call overrides the blob base fee, while eth_call, eth_estimateGas and the tracers are unchanged. The release also includes stateless sync and transaction processing improvements, and is built with the same Go 1.26.10 toolchain as v2.11.0.
The post does not itemize the security fixes; it points to the release notes on GitHub.
Sources
- Original source 0xPolygon/Bor on GitHub forum.polygon.technology