The Polygon Blockchain behind the popular altcoin MATIC ran into trouble Wednesday after some nodes synced. After this issue, the popular Blockchain Explorer PolygonScan went offline for a while. Here are the details…
Trouble with Polygon network behind altcoin project
The outage in PolygonScan caused confusion. Ultimately, it prompted Polygon’s leader, Sandeep Nailwal, to tweet that there were “problems” with the blockchain explorer. Nailwal’s tweet, however, created the appearance that no action was taken for it. Nailwal stated that several nodes were synchronized during the evening hours. It turned out that this caused some nodes to be unable to verify blocks for a very short period of time. According to the founder of infrastructure company Rivet, DAPP developers rely on affected nodes. “While I’m afraid to call it a disaster, there’s probably more people affected by talking about it,” Greg Lang, founder of Rivet, said of the event.
“There could have been a temporary degradation in network performance,” a Polygon spokesperson said, explaining the results for some nodes. Although it says all nodes are in sync, the project’s Polygon said it’s investigating what’s causing the issue. According to Lang, Polygon’s troubles appear to stem from an “unusually large” block arrangement that occurred two minutes before Polygon’s nodes were synchronized. As we have reported as Kriptokoin.com, Rivet is a node infrastructure provider at Polygon.
The problem with the network was the size of the blocks edited
When a network’s operators issue two blocks at the same time, it creates a “fork” on the chain where accounts of the permanent record of the chain are located. Rebuilding a block provides an insight into how the network resolved the inconsistency. Small block arrangements are common in Polygon and other networks based on the Ethereum Virtual Machine (EVM), according to Lang. Therefore, there is no need to worry. The only thing that differed on Wednesday was the size of the arrangement. The arrangement appeared as 157 blocks.
“The refactoring was definitely out of the norm,” Lang said. According to Rivet, it has surpassed our regulatory mechanisms by at least a few dozen blocks,” he said. Infrastructure providers handle reorganizations differently, Lang said, but Rivet can automatically handle roughly 125 or less. Beyond that, Lang said Rivet needs to manually restore chain history from backups. He said it probably happened on Wednesday.
Generally speaking, Lang said that node operators can be kicked off the network by Blockchain arrangements and even “offer stale data” if they don’t get back to it quickly. Perhaps the most important public consequence of Blockchain’s era of instability was the outage of the popular Block Explorer PolygonScan. A spokesperson for Polygon said that network issues were “causing PolygonScan to get stuck.” Because Block Explorer may be using asynchronous nodes. Polygon’s Nailwal tweeted that PolygonScan is having problems and Oklink Explorer is available as an alternative.
https://twitter.com/sandeepnailwal/status/1628522387401482241
674
