Ethereum

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

Interestingly, procedures did they follow the proper Or and their critics are just uninformed? Are doing everything above board or is theretheysomething sinister going on? Probably not. Are they even decentralized if they can hard-fork just like that? There seems toforcebe a disturbance in the over there. What’s going on at Polygon? But we can present all the information available and let you all get to your own conclusions. Is the Ethereum Layer 2 project alright? Can those even answer all of we questions?

Let’s launch with DeFi Builder.Nathan Worsley’s accusation Or is he just requesting information? Worsley recently tweeted, “Are we all supposed to just shut haven 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 up’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” part is arguablesince everyone is in different timezones and the Polygon in modern times blockchain is everywhere. However, he cleared up why the issue is important, “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 everything else, “Here’s the commit that was hard-forked into production.”

To add credibility to his from another perspective claim, DeFiance Capital’s Zhu Su joined the chorus asking for answers. Indeed, “Was this to patchcriticala glitch? Why andhow did this happen?”

Actually, Polygon Responds And Shows Receipts

Nofunds were lost. “We’re making an effort as it turns out 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. stable network is The.” The criticism got a response from Polygon’s co-founder Mihailo Bjelic. We immediately introduced.a resolve and coordinated the enhance with validators/full node operators

Ok, that sounds reasonable. Bjelic also promised, “A detailed journal publish coming, we are as a matter of fact finalizing additional security analyses.” A query lingered in the air, though. And crypto enthusiast J. Vicente Correa asked it in the most direct way possible, “U can fork the chain by yourself and take all my funds as u wish?”

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

Fair enough. As you may know, However…

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

A Node Operator Has Some Criticism Of His Own

Indeed, It was not mentionedinor pinned down any major channels as it turns out or publications.” Indeed, In the same thread, Polygon node operator Mikko Ohtamaa blasted the way the corporation handled the whole thing and also showed receipts. Right away this looks super unprofessional and confusing for the community. “Proceed time it happens you at least announce a critical refresh to all Polygoncannode operators.

In factfromHe got a response , Polygon’s other co-creator, Sandeep Nailwal. “could was a security refresh, and hence pre-public-announcement This’ve escalated things.”

“It’s really obvious it is a critical security problem if you do unannounced no notice hard fork in the middle of a weekend.” “Some glitch fixes” for a critical patch is not good. Ok, thatmakes sense. Indeed, Ohtamaa, However had more complaints. In fact, If there is a critical correct you co-ordinate with validators.” Plus, he reinforced Nathan Worsley’s original complaint.

He as a matter of fact According to , “there are multiple access sourceOhtamaaprojects out there” that have done similar operations in a more effective manner. Actually Someone asked what could Polygon have, done better.answeredserieswith a of uncomplicated steps.

  1. Indeed as a matter of fact Prepare, the patch privately.
  2. few days before, announce a critical security resolve isAcoming. All node operators need.to be prepared
  3. Distribute. from another perspective the patch at the preset time
  4. In fact, Not downplay the criticality of the patch and make idiot-looking release notes.

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

So, is there something rotten at Polygon? We will have to wait for the “detailed journal share” Bjelic promised to know for sure.

Featured Image by Mae Mu on Unsplash - Charts by TradingView

Leave a Reply

Your email address will not be published. Required fields are marked *

Active Search Results Search Engine