Polygon has rolled out Bor v2.7.3, a new maintenance release for the execution-layer client used by the Polygon PoS network. The update applies to both the Amoy testnet and mainnet. Announced on May 8, the release focuses on incremental improvements and bug fixes, with particular attention on pre-confirmations and private transaction relaying.
Private transactions now face a 10-minute TTL
The headline change in Bor v2.7.3 is the introduction of a 10-minute time-to-live (TTL) for private transactions. Under the new rule, if a private transaction is not included in a block within 10 minutes, it will be removed from the private pool and pushed to the public network instead. This creates a defined time window for private relay handling rather than allowing transactions to remain pending indefinitely in a private queue.
A clearer path for stuck transactions
The update also improves how users can respond when a private transaction remains unmined. If the original transaction is still pending, users can submit an alternative transaction with a higher gas fee to improve the chances of inclusion. In practice, this gives users a more direct way to manage execution risk and avoid prolonged delays in transaction confirmation.
Maintenance-focused release for network reliability
While Bor v2.7.3 is not framed as a major feature overhaul, it introduces meaningful adjustments to transaction handling on Polygon PoS. By refining private relay behavior and enhancing pre-confirmation-related processes, the release aims to improve predictability and operational efficiency across the network. For developers and users interacting with Polygon PoS, the update could reduce uncertainty around pending private transactions and provide more transparent fallback behavior when inclusion does not happen quickly.
More broadly, the release shows Polygon continuing to tune its execution infrastructure at the client level. With Bor v2.7.3, the network is placing additional emphasis on transaction flow, relay performance, and a smoother user experience for both testnet and mainnet participants.