Polygon revealed that it is experiencing delays in transactive sinality. The chain is currently confronted with a delay of 10-15 minutes when completing blocks due to a technical problem that is going on.
Summary
- Polygoon chain bounces for a delay in transactive tanality with 10-15 minutes.
- It is said that the problem is caused by nodes that cause delays in the process.
On September 10 at 10.30 am UTC was the last transaction block on the Polygon (Matic) chain validated About five hours ago. The comment above the site says that “Block data is currently data. We are working on it to solve this.” This indicates that the problem is still underway and that the protocol still has to come up with a solution to tackle the transaction delay.
In the recent afterThe Protocol insured traders that the chain will continue to run and that blocks are still being produced. However, there is a delay of 10-15 minutes in the finality that happened on the chain. The team said the problem was caused by a ‘milestone problem’.
“We have identified a solution and this is being rolled out for all validators and service providers,” the team said in his recent position.
Once the problem has been solved, the Polygon Foundation shares an update about its social media accounts. In the meantime, users can Status provides about whether the delay is still persistent.
“We are now actively working with RPC providers to speed up the resolution and to restore user-oriented services,” wrote the protocol.
The most recent update, posted on September 10 at 8:52 AM, the team said the problem is still being investigated. The problem depends on various nodes that cause delays in block finality, making it difficult for transactions to be processed.
According to the web page there are currently 103/108 Active nodes. With a total of more than 76.2 million blocks that have been processed by the polygon chain, the 76.28 million blocks are.
So far, Checkpoint Finality is running again as expected within the first 15 minutes.
What does the Polygon -Bug influence?
According to the site updateThe problem stems from a bug in the milestone treatment of the network, which influences the consensus layer. This is the part that is responsible for confirming transactions Finality. Although this bug does not stop the production of blocks, it slows down the process that makes transactions irreversible.
The platform reported that the restarting of nodes resolved the problem for many validators and RPC providers. Although this is still a temporary solution.
“While a few providers had to return to the last completed block of 76273070 and are currently synchronized. We keep an eye on the problem and continue to post updates here,” the team wrote in the previous update.
The Polygon team emphasized that the bug was isolated and did not endanger the core protection or led to possible exploits that could endanger user funds. However, it also emphasized the importance of continuous network audits and improvement protocols in the rapidly evolving blockchain landscape.
