There was fear that after a vulnerability[1] was discovered in the EOS code, the EOS mainnet launch might get delayed. But have no fear because that’s not happening! Block.one confirms that all systems are a go and the EOS mainnet launch should still be coming out according to plan.
EOS Eliminates Panic
The EOS team tweeted out their reassurances that the EOS mainnet launch was still on schedule.
Media has incorrectly reported a potential delay in the release of EOSIO V1 due to software vulnerabilities. Our team has already fixed most and is hard at work with the remaining ones. EOSIO V1 is on schedule; please stay tuned to our EOSIO channels for official information.
— EOS (@EOS_io) May 30, 2018[2]
Much of the panic was due to the vulnerability that was discovered by Qihoo 360, a Chinese internet security firm. The vulnerability was in fact fixed, but nervousness still lingered among some people.
After being notified of the major flaw in their code, EOS promptly set to fixing the problem, which was shown to be resolved on Github[3]. This vulnerability scare, however, did prompt EOS to take affirmative action to search for any more flaws in the system. Dan Larimer asked the community for help in their endeavors.
Help us find critical bugs in #EOSIO[4] before our 1.0 release. $10K for every unique bug that can cause a crash, privilege escalation, or non-deterministic behavior in smart contracts. Offer subject to change, ID required, validity decided at the sole discretion of Block One.
— Daniel Larimer (@bytemaster7) May 28, 2018[5]
This seems to be what caused people to remain concerned. If they’re
