THELOGICALINDIAN - After a Block Producers BP vote captivated on June 6th an official nogo was appear for the mainnet barrage The accident has been pushed aback by at atomic addition 24 hours
The long-awaited barrage of EOS’ mainnet has been added delayed afterwards a BP vote captivated on June 6th bootless to accord the blooming light. A new vote is appointed to booty abode 24 hours afterwards aegis firms accomplish an audit. At that time, if BPs do not analyze any added vulnerabilities the ablution action should booty place.
The best acceptable aftereffect – at atomic according to David Moss, arch of a blockchain consulting aggregation which focuses alone on EOS – is that the abutting vote on Thursday is additionally acceptable to be a no-go.
EOS tokens were arctic on June 1st in apprehension for the barrage of the official EOS network. The EOS Mainnet Barrage Group (EMLG) has been tasked to agreement a defended and seamless barrage anytime since.
However, canicule afore June 1st, news emerged that analytical vulnerabilities were begin in the project’s network, according to a arch Chinese cybersecurity company. EOS appeared to accept been acquainted of the vulnerabilities at the time and best of the issues had purportedly already been patched, as apparent by EOS’ academic account on the matter:
The aggregation bootless to accommodate added description on what they meant by “most” of the bugs, and which ones were yet to be fixed. It is clear, though, that the issues they are currently adverse are preventing the mainnet from actuality released, ultimately substantiating the Chinese team’s account that the above vulnerabilities could adjournment the network’s release.
Reports announce that the EMLG aggregation has been alive endlessly to boldness the actual vulnerabilities. Each vulnerability has been labeled according to acceptation with a designator alignment from P0 to P4. The P0 designator represents bugs which comprise a blocker, bidding an burning fix, and P4 represents an affair that should alone be acclaimed for a approaching fix.
In an official statement, the EMLG has autonomous not to accord any added accuracy on the actual bugs which are black the arrangement from advancing to light, nor are they ciphering how abundant time it will booty to fix them.
Immediately afterwards claiming that best of the appear vulnerabilities accept been bound by the team, EOS accomplished a Bug Bounty Campaign. One ability catechism why such a affairs is needed, abnormally anon afterwards most of the issues accept been handled, but arguments can be fabricated that the aggregation is actuality added acute back it comes to flaws in its network.
Things took a hardly abrupt turn, however, as ethical hacker Guido Vranken managed to analyze 8 vulnerabilities in aloof one day – a cardinal which ultimately grew to 12 and becoming Vranken a air-conditioned $120,000 in bug bounties.
In added words, there are at atomic 12 vulnerabilities which accept been articular back May 30th and, up until this moment, the accessible has yet to apprentice how abounding of them – if any – are P0 (blocking) issues and how abounding of them present a bottom blackmail to the network.
The alone advice that users currently accept is that the EMLG refuses to accomplish to a close barrage date as it “would be irresponsible” and that a new amend is set to booty abode aural the abutting 24 to 48 hours.
In ablaze of contempo events, one wonders whether this abridgement of accuracy apparel a activity which managed to accession the whopping $4 billion over the advance of a year-long ICO.
What are your thoughts on the adjournment of the EOS mainnet launch? Is any affair so analytical that no ETA can be provided on its fix? Let us apperceive in the comments below.
Images address of Shutterstock
