Hard-Forked Polygon Blockchain Without Warning at Closed Source Genesis. Why?

0


[ad_1]

What is happening at Polygon? There appears to be a disturbance in the strength there. Is the Ethereum Layer 2 project going well? Are they doing everything over the edge or is there something sinister going on? Are they even decentralized if they can hard-fork just like that? Or did they follow the proper procedures and their detractors just aren’t informed? Can we even answer all of these questions? Probably not. But we can present all the information that is available and let you all draw your own conclusions.

Let’s start with the accusation of DeFi builder Nathan Worsley. Or is he just asking for information? Worsley recently tweeted, “Are we all supposed to shut up and forget the fact that over a week ago Polygon forged its blockchain in the middle of the night without warning at a completely closed genesis and still has not verified the code or explained what’s going on?

Related reading | Polygon: Ethereum’s friend seeks to make great progress

The “middle of the night” part is questionable as everyone is in different time zones and the Polygon blockchain is everywhere. However, he explained why the problem is significant: “Until the code is verified, there is no guarantee of security for the billions of dollars in assets the chain is currently securing. And tweeted proof of everything else, “Here’s the commit that was tough on production.” “

To add credibility to his claim, Zhu Su of DeFiance Capital joined the chorus to ask for answers. “Is it to correct a critical bug?” Why and how did it happen?

Polygon responds and displays receipts

The review received a response from Polygon co-founder Mihailo Bjelic. “We strive to improve security practices in all Polygon projects,” Bjelic tweeted. “As part of this effort, we are working with several groups of security researchers, hackers, and so on. One of these partners discovered a vulnerability in one of the recently audited contracts. We immediately introduced a fix and coordinated the upgrade with the full node validators / operators. No funds were lost. The network is stable.

Okay, that sounds reasonable. Bjelic also promised: “A detailed blog post to come, we are finalizing additional security scans.” One question remained in the air, however. And crypto enthusiast J. Vicente Correa asked him in the most direct way possible: “You can forge the chain on your own and take all my funds however you want?”

And Polygon’s Mihailo Bjelic is responding in the most political way possible. “Absolutely not. The network is managed by validators and full node operators, and we have no control over any of those groups. We have just done our best to communicate and explain the importance of this upgrade. , but in the end it was up to them to decide whether or not they would.

Fair enough. However…

MATIC price chart on Poloniex | Source: MATIC/USD on TradingView.com

A node operator has his own critiques

In the same thread, Polygon node operator Mikko Ohtamaa criticized the way the company handled everything and also showed receipts. “The next time that happens, can you at least announce a critical update to all Polygon node operators. Now that looks super unprofessional and confusing to the community. It hasn’t been mentioned or pinned in any major channel or post. “

He got a response from Polygon’s other co-creator, Sandeep Nailwal. “This was a security update, so a pre-public announcement could have made matters worse.”

Okay, that makes sense. However, Ohtamaa had more complaints. “Some bugfixes” for a critical fix is ​​not good. If there is a critical fix, you coordinate with the validators. Additionally, he reinforced Nathan Worsley’s initial complaint. “It’s really obvious that this is a critical security bug if you hard fork without warning in the middle of a weekend. “

According to Ohtamaa, “there are several open source projects” that have done similar operations more efficiently. Someone asked what Polygon could have done better. He responded with a series simple steps.

  1. Prepare the patch in private.
  2. A few days before, announce the arrival of a critical security patch. All node operators must be prepared.
  3. Distribute the patch at the preset time.
  4. Don’t minimize the criticality of the fix and make silly release notes.

Related reading | How Polygon Reached $ 400 Million Deal To Get Ahead In Ethereum ZK Rollup Race

So, is there something rotten about Polygon? We’ll have to wait for the “detailed blog post” that Bjelic promised to know for sure.

Featured Image by Mae Mu on Unsplash - Charts by TradingView


[ad_2]

Share.

Comments are closed.