After a Block Producer’s (BP) vote held on June 6th, an official ‘no-go’ was introduced for the mainnet launch. The occasion has been pushed again by at the least one other 24 hours.
The long-awaited launch of EOS’ mainnet has been additional delayed after a BP vote held on June 6th failed to present the inexperienced mild. A brand new vote is scheduled to happen 24 hours after safety corporations carry out an audit. At the moment, if BPs don’t establish any additional vulnerabilities the launching course of ought to happen.
The probably final result – at the least in line with David Moss, head of a blockchain consulting firm which focuses solely on EOS – is that the subsequent vote on Thursday can be prone to be a no-go.
The Present State of the Launch
EOS tokens had been frozen on June 1st in anticipation for the launch of the official EOS community. The EOS Mainnet Launch Group (EMLG) has been tasked to ensure a safe and seamless launch ever since.
Nevertheless, days earlier than June 1st, information emerged that essential vulnerabilities had been discovered within the venture’s community, in line with a number one Chinese language cybersecurity firm. EOS appeared to have been conscious of the vulnerabilities on the time and a lot of the points had purportedly already been patched, as evidenced by EOS’ formal assertion on the matter:
Media has incorrectly reported a possible delay within the launch of EOSIO V1 as a consequence of software program vulnerabilities. Our crew has already mounted most and is difficult at work with the remaining ones. EOSIO V1 is on schedule; please keep tuned to our EOSIO channels for official info.
— EOS (@EOS_io) Might 30, 2018
The crew failed to supply additional clarification on what they meant by “most” of the bugs, and which of them had been but to be mounted. It’s clear, although, that the problems they’re at the moment going through are stopping the mainnet from being launched, finally substantiating the Chinese language crew’s assertion that the aforementioned vulnerabilities may delay the community’s launch.
Stories point out that the EMLG crew has been working tirelessly to resolve the remaining vulnerabilities. Every vulnerability has been labeled in line with significance with a designator starting from P0 to P4. The P0 designator represents bugs which comprise a blocker, prompting an pressing repair, and P4 represents a problem that ought to merely be famous for a future repair.
In an official assertion, the EMLG has opted to not give any additional readability on the remaining bugs that are deterring the community from coming to mild, nor are they estimating how a lot time it can take to repair them.
Partial Readability on the Matter
Instantly after claiming that a lot of the reported vulnerabilities have been resolved by the crew, EOS initiated a Bug Bounty Marketing campaign. One may query why such a program is wanted, particularly instantly after most of the problems have been dealt with, however arguments might be made that the crew is being further vigilant in the case of flaws in its community.