Welcome to the next crypto level
← Nexorena

technology

Polygon moves Bor 2.11.1 for PoS nodes to public distribution

A November 16 announcement on Polygon’s forum detailed the move to the public release channel for Bor 2.11.1. Operators already running the private release have the same code.

Nexorena Editorial Team

Polygon moves Bor 2.11.1 for PoS nodes to public distribution

The fix reaches the public channel

The maintainers of Bor, the software that executes Polygon PoS blocks, announced public availability of version 2.11.1 on November 16 for mainnet and the Amoy testnet. The release uses the same code as 2.11.1-priv, which operators had been able to install earlier. According to the release notes, most validators were already running the private release. The public repository now supplies packages, checksums and signatures for standard distribution.

Instructions vary by installed version. Operators still running Bor 2.11.0 are asked to upgrade their nodes. Those already using the private release can move to the public version at their next maintenance window. Because the code is identical, that second change restores the usual distribution channel without changing node behavior. A team running several machines can set its upgrade order according to the version actually installed.

Import checks blocks before execution

The fix strengthens stateless import checks. Bor checks each block header and verifies that its body matches the header before execution. The checks apply to both sequential and parallel import. On the parallel path, the software waits for the entire batch’s header checks before starting execution.

That order distinguishes checking the structure of a block from processing the transactions it contains. A failed header or body-to-header check is therefore detected before execution on the affected import path. The change is among the security and stability fixes in Bor. The release notes call for no database schema change or resynchronization to apply it.

Operators can stagger the upgrade

Bor also clarifies transaction prechecks for blob transactions when no blob schedule is configured. In that case, the software reports that a blob base fee is unavailable. The eth_simulateV1 method also returns that error if a call includes blob hashes and provides no replacement blob base fee. The notes say the change leaves eth_call, eth_estimateGas and tracing tools unchanged.

Bor 2.11.1 has no activation block. The maintainers say nodes on 2.11.0, 2.11.1-priv and 2.11.1 remain compatible during the transition. Teams can upgrade one node at a time in any order. The instructions cover software deployment on Polygon PoS and Amoy, with no change to the chain configuration or genesis block.

Article sources

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena