The Polygon proof-of-stake (PoS) network has been the subject of extensive research to enhance its public and decentralized protocol. Addressing previous challenges like long block reorganizations that impacted user experience and chain stability, Polygon Labs researchers have identified the root causes and proposed solutions to the community.
Following the footsteps of Ethereum’s EIP framework, Polygon introduced the Polygon Improvement Proposal (PIP) framework. Acting as a coordination layer for all Polygon PoS upgrades, this framework facilitates consensus among ecosystem participants through forums and Polygon Protocol Governance Calls.
The Inborg Upgrade, consisting of two proposals named Indore [PIP-12] and Aalborg [PIP-11], is currently underway thanks to the PIP framework. The Indore proposal focuses on upgrading the State Sync mechanism to improve network stability and eliminate potential BADBLOCK errors. Meanwhile, Aalborg aims to introduce “Milestones” for faster finality on the Polygon PoS network. The two-step Inborg Upgrade intends to enhance network stability and reduce finality time, with the Aalborg proposal scheduled for on-chain consensus next month.
This article will delve into the Indore Upgrade, explaining how it is designed to bolster the network’s stability. Here’s a breakdown of the Indore Upgrade’s expected benefits if implemented:
- Enhanced network stability: The Indore State Sync Upgrade aims to provide a more stable network environment, ensuring smoother operations and improved user experiences.
- Elimination of the BADBLOCK error: One of the key issues addressed by the upgrade is the occurrence of the BADBLOCK error. This error sometimes arises during reorganizations (network partitions) longer than 16 blocks. The Indore Upgrade modifies the State Sync mechanism from a block-based design to a time-based one, effectively resolving this error.
- Impact-free upgrade: The proposed changes will not have any adverse effects on users or developers. It is a seamless upgrade that maintains continuity in the network’s operations.
To understand the significance of the Indore Upgrade, let’s revisit the State Sync mechanism and its relevance within the Polygon PoS network. The network’s dual-consensus architecture comprises the validator layer, Heimdall, and the block producer layer, Bor.
Heimdall initiates the State Sync mechanism, which involves reading data (events) from Ethereum. This data is then passed on to Bor, where key operations like transactions and block production occur. The State Sync process entails Bor fetching State Sync events from Heimdall at the beginning of each sprint, which represents a series of contiguous produced blocks by a single validator on Bor.
During this process, Bor utilizes two arguments: “fromID,” a unique and incremental identity of the state, and “to,” a timestamp representing a specific period. In simpler terms, Bor requests all State Sync events from Heimdall that occurred between two different points defined by the “fromID” and “to” values.
To determine the “to” value, Bor calculates it using the “current block” at the start of the sprint and subtracting the most recent sprint length (16 blocks after the Delhi hard fork). This calculation ensures that the State Sync events include all the data from Ethereum in Heimdall during that period.
However, an error can occur in cases of network partitions or reorganizations where two forks run in parallel for more than a sprint length. When attempting to merge these forks, a discrepancy arises in determining the “to” time value. Each fork has different prior blocks, leading to conflicting timelines and the BADBLOCK error.
While most forks quickly converge to the “canonical” version and restore the main timeline, longer forks can struggle to determine the precise “to” value. This delay can cause the BADBLOCK error to persist for many blocks, affecting network stability.
Inborg Upgrade Boosts Stability and State Sync for Polygon PoS Network
The Polygon proof-of-stake (PoS) network has been the subject of extensive research to enhance its public and decentralized protocol. Addressing previous challenges like long block reorganizations that impacted user experience and chain stability, Polygon Labs researchers have identified the root causes and proposed solutions to the community.
Following the footsteps of Ethereum’s EIP framework, Polygon introduced the Polygon Improvement Proposal (PIP) framework. Acting as a coordination layer for all Polygon PoS upgrades, this framework facilitates consensus among ecosystem participants through forums and Polygon Protocol Governance Calls.
The Inborg Upgrade, consisting of two proposals named Indore [PIP-12] and Aalborg [PIP-11], is currently underway thanks to the PIP framework. The Indore proposal focuses on upgrading the State Sync mechanism to improve network stability and eliminate potential BADBLOCK errors. Meanwhile, Aalborg aims to introduce “Milestones” for faster finality on the Polygon PoS network. The two-step Inborg Upgrade intends to enhance network stability and reduce finality time, with the Aalborg proposal scheduled for on-chain consensus next month.
This article will delve into the Indore Upgrade, explaining how it is designed to bolster the network’s stability. Here’s a breakdown of the Indore Upgrade’s expected benefits if implemented:
- Enhanced network stability: The Indore State Sync Upgrade aims to provide a more stable network environment, ensuring smoother operations and improved user experiences.
- Elimination of the BADBLOCK error: One of the key issues addressed by the upgrade is the occurrence of the BADBLOCK error. This error sometimes arises during reorganizations (network partitions) longer than 16 blocks. The Indore Upgrade modifies the State Sync mechanism from a block-based design to a time-based one, effectively resolving this error.
- Impact-free upgrade: The proposed changes will not have any adverse effects on users or developers. It is a seamless upgrade that maintains continuity in the network’s operations.
To understand the significance of the Indore Upgrade, let’s revisit the State Sync mechanism and its relevance within the Polygon PoS network. The network’s dual-consensus architecture comprises the validator layer, Heimdall, and the block producer layer, Bor.
Heimdall initiates the State Sync mechanism, which involves reading data (events) from Ethereum. This data is then passed on to Bor, where key operations like transactions and block production occur. The State Sync process entails Bor fetching State Sync events from Heimdall at the beginning of each sprint, which represents a series of contiguous produced blocks by a single validator on Bor.
During this process, Bor utilizes two arguments: “fromID,” a unique and incremental identity of the state, and “to,” a timestamp representing a specific period. In simpler terms, Bor requests all State Sync events from Heimdall that occurred between two different points defined by the “fromID” and “to” values.
To determine the “to” value, Bor calculates it using the “current block” at the start of the sprint and subtracting the most recent sprint length (16 blocks after the Delhi hard fork). This calculation ensures that the State Sync events include all the data from Ethereum in Heimdall during that period.
However, an error can occur in cases of network partitions or reorganizations where two forks run in parallel for more than a sprint length. When attempting to merge these forks, a discrepancy arises in determining the “to” time value. Each fork has different prior blocks, leading to conflicting timelines and the BADBLOCK error.
While most forks quickly converge to the “canonical” version and restore the main timeline, longer forks can struggle to determine the precise “to” value. This delay can cause the BADBLOCK error to persist for many blocks, affecting network stability.
