There was fear that after a vulnerability 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

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. 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 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

This seems to be what caused people to remain concerned. If they’re searching for bugs, does that mean there are bugs? Some have taken to Twitter to air their doubts, including some big names in the crypto community.

Raises $4B, offers to pay only $10k for catastrophic bugs 2 days before mainnet launch. Strange. 🤔 And quite a few other concerning issues with EOS. See: https://t.co/C4HypNFet5
This will also be one of the biggest ERC20 token to blockchain launch. Should be an exciting day! https://t.co/Ey7mF10Dry
— Charlie Lee [LTC⚡] (@SatoshiLite) May 30, 2018

The EOS team is likely just being cautious. If there are problems, they’ll likely be able to fix them pretty quickly, seeing how quick they dealt with the Qihoo 360-discovered bug.

As of now, the EOS mainnet launch is still happening when it’s meant to happen. Until we hear otherwise (and hear from EOS itself), that’s what we’ll have to believe.

What do you think about it all?