Search
Close this search box.

Polygon’s blockchain hard fork did not warn of closed-source Genesis. why?

Picture of Justice News Flash Report

Justice News Flash Report

Polygon’s blockchain hard fork did not warn of closed-source Genesis. why?

Facebook
Twitter
LinkedIn

[ad_1]

What happened to the polygon? The forces over there seem to be a bit chaotic. Is the Ethereum layer 2 project good? Is everything they do fair and honest, or is there something sinister happening? If they can hard fork like that, are they even decentralized? Or did they follow proper procedures without their critics just unaware? Can we even answer all these questions? maybe not. But we can provide all available information so that everyone can draw their own conclusions.

Let’s start with the accusation of DeFi Builder Nathan Worsley. Or is he just asking for information?Worsley Recently tweeted, “Should we all shut up and forget the fact that Polygon hard-forked their blockchain in the middle of the night more than a week ago, and did not warn of the origin of the completely closed source code and still did not verify the code? Or an explanation happened? what?”

Related Reading | Polygon: Friends of Ethereum are seeking to make strides

The “midnight” part is controversial because everyone is in a different time zone and the Polygon blockchain is everywhere. However, He clarified the reason This question is very important, “Before verifying the code, the billions of dollars in assets currently protected by the chain are not guaranteed to be safe.” All other evidence was posted on Twitter, “This is a hard fork to production submission.”

In order to increase the credibility of his statement, Zhu Su of DeFiance Capital joined the chorus to seek answers. “Is this to fix a serious bug? Why and how did this happen?”

Polygon response and display receipt

The criticism was echoed by Mihailo Bjelic, the co-founder of Polygon. “We are working hard to improve the safety practices of all Polygon projects,” Bjelic tweeted. “As part of this work, we are collaborating with multiple security research groups, white hat hackers, etc.. One of the partners discovered a vulnerability in a recently verified contract. We immediately introduced a fix and communicated with the verifier /All node operators coordinate the upgrade. There is no capital loss. The network is stable.”

Well, this sounds very reasonable. Bjelic also promised, “A detailed blog post will be published soon, and we are completing additional security analysis.” However, one issue remains unresolved. Crypto enthusiast J. Vicente Correa asked it in the most direct way, “Can you fork the chain yourself and take all my funds as you like?”

Mihailo Bjelic of Polygon gave the answer in the most political way. “Absolutely not. The network is run by validators and full-node operators. We cannot control any of these groups. We just tried our best to communicate and explain the importance of this upgrade, but in the end it is up to them to decide whether they are Will do it.”

fair enough. However…

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

Node operators have some criticisms of their own

In the same post, Polygon node operator Mikko Ohtamaa blasted the company’s way of handling the whole thing and showed the receipt. “Next time this happens, you can at least announce an important update to all Polygon node operators. Now this looks very unprofessional and confusing to the community. It is not mentioned in any major channels or publications or fixed.”

He got a response from Sandeep Nailwal, another co-founder of Polygon. “This is a security update, so the announcement before the release may escalate things.”

Well, this makes sense. However, Ohtamaa has more complaints. “Some bug fixes” for critical patches are not good. If there is a critical fix, you will coordinate with the verifier. In addition, he reinforced Nathan Worsley’s initial complaint. “It is clear that if you do an unannounced hard fork in the middle of the weekend, this is a serious security hole. “

According to Ohtamaa, “there are multiple open source projects” that accomplish similar operations in a more efficient manner. Someone asked what Polygon could do better.he Answer in series Simple steps.

  1. Prepare patches privately.
  2. A few days ago, it was announced that a critical security fix was coming. All node operators need to be prepared.
  3. Distribute patches at preset times.
  4. Don’t downplay the importance of patches and make release notes that look idiot.

Related Reading | How Polygon reached a $400 million deal to take the lead in the Ethereum ZK Rollup competition

So, is there anything bad about Polygon? We will have to wait for the “detailed blog post” that Bjelic promised to confirm.

Featured Image by Mae Mu on Unsplash - Charts by TradingView



[ad_2]

Source link

More to explorer

Keep in touch