Crypto News

Polygon ’s Blockchain Hard-Forked Without Warning To Closed-Source Genesis. Why?

What’s happening at Polygon? There appears to be a disturbance within the drive over there. Is the Ethereum Layer 2 undertaking alright? Are they doing every little thing above board or is there one thing sinister happening? Are they even decentralized if they will hard-fork similar to that? Or did they comply with the correct procedures and their critics are simply uninformed? Can we even reply all of these questions? Probably not. But we will current all the knowledge accessible and allow you to all get to your personal conclusions.

Let’s begin with DeFi Builder Nathan Worsley’s accusation. Or is he simply requesting data? Worsley recently tweeted, “Are we all supposed to just shut up and forget about the fact that over a week ago Polygon hard-forked their blockchain in the middle of the night with no warning to a completely closed-source genesis and still haven’t verified the code or explained what is going on?” 

Related Reading | Polygon: Ethereum’s Friend Is Looking To Make Big Strides

The “middle of the night” half is debatable since everyone seems to be in numerous timezones and the Polygon blockchain is all over the place. However, he cleared up why the difficulty is essential, “Until the code is verified there are no security guarantees about the billions of dollars in assets the chain currently secures.” And tweeted proof of every little thing else, “Here’s the commit that was hard-forked into production.”

To add credibility to his declare, DeFiance Capital’s Zhu Su joined the refrain asking for solutions. “Was this to patch a critical bug? Why and how did this happen?”

Polygon Responds And Shows Receipts

The criticism bought a response from Polygon’s co-founder Mihailo Bjelic. “We’re making an effort to improve security practices across all Polygon projects,” Bjelic tweeted. “As a part of this effort, we are working with multiple security researcher groups, whitehat hackers etc. One of these partners discovered a vulnerability in one of the recently verified contracts. We immediately introduced a fix and coordinated the upgrade with validators/full node operators. No funds were lost. The network is stable.”

Ok, that sounds cheap. Bjelic additionally promised, “A detailed blog post coming, we are finalizing additional security analyses.” A query lingered within the air, although. And crypto fanatic J. Vicente Correa requested it in essentially the most direct means potential, “U can fork the chain by yourself and take all my funds as u wish?”

And Polygon’s Mihailo Bjelic solutions in essentially the most political means potential. “Absolutely not. The network is run by validators and full node operators, and we have no control over any of these groups. We just did our best to communicate and explain the importance of this upgrade, but ultimately it was up to them to decide whether they will do it or not.”

Fair sufficient. However…

MATICUSD price chart - TradingView

MATIC price chart on Poloniex | Source: MATIC/USD on

A Node Operator Has Some Criticism Of His Own

In the identical thread, Polygon node operator Mikko Ohtamaa blasted the best way the corporate dealt with the entire thing and in addition confirmed receipts. “Next time it happens can you at least announce a critical update to all Polygon node operators. Now this looks super unprofessional and confusing for the community. It was not mentioned or pinned down in any major channels or publications.”

He bought a response from Polygon’s different co-creator, Sandeep Nailwal. “This was a security update, and hence pre-public-announcement could’ve escalated things.”

Ok, that is sensible. However, Ohtamaa had extra complaints. “Some bug fixes” for a crucial patch shouldn’t be good. If there’s a crucial repair you co-ordinate with validators.” Plus, he strengthened Nathan Worsley’s unique grievance. “It’s really obvious it is a critical security bug if you do unannounced no notice hard fork in the middle of a weekend.”

According to Ohtamaa, “there are multiple open source projects out there” which have performed comparable operations in a simpler method. Someone requested what might Polygon have performed higher. He answered with a series of straightforward steps. 

  1. Prepare the patch privately.
  2. Just a few days earlier than, announce a crucial safety repair is coming. All node operators must be ready.
  3. Distribute the patch on the preset time.
  4. Not downplay the criticality of the patch and make idiot-looking launch notes.

Related Reading | How Polygon Sealed A $400M Deal To Get Ahead In The Ethereum ZK Rollup Race

So, is there one thing rotten at Polygon? We must await the “detailed blog post” Bjelic promised to know for positive.

Featured Image by Mae Mu on Unsplash - Charts by TradingView

Related posts

Mandates Ban Unvaccinated From Visiting Banks in Multiple Countries, Australian Premier Says ‘There’s Going to Be a Vaccinated Economy’ – Featured Bitcoin News

Crypto Advisor

Skate Punks Club NFT Sales

Crypto Advisor

What Are The CryptoPunks V1? And, How Can They Disrupt The Market?

Crypto Advisor

Leave a Comment