{"id":7396,"date":"2018-06-06T02:08:22","date_gmt":"2018-06-06T02:08:22","guid":{"rendered":"https:\/\/www.legitgambling.com\/news\/?p=7396"},"modified":"2018-06-06T02:08:22","modified_gmt":"2018-06-06T02:08:22","slug":"eos-provides-update-on-mainnet-candidate-testing-process","status":"publish","type":"post","link":"https:\/\/www.legitgambling.com\/news\/eos-provides-update-on-mainnet-candidate-testing-process\/","title":{"rendered":"EOS Provides Update On Mainnet Candidate Testing Process"},"content":{"rendered":"

\"\"Block.one successfully released version 1.0 of open source EOSIO blockchain software on June 2. EOSIO is an operating System on which scalable DACs (Decentralized Autonomous Communities) can easily be built, launched, and governed. According to the announcement made by the EOSIO team, <\/a>the block producers are conducting detailed tests on the mainnet candidate and is yet to be completed.<\/p>\n

In its detailed update, the EOS Mainnet Launch Group (EMLG) initially announced that it would take at least 7 more days to complete the tests. The time frame was withdrawn later as it didn\u2019t make any sense to the EOS team and the community. Notably, a Dutch ethical hacker was able to identify 12 bugs in the chain and has been awarded $120,000 so far.<\/p>\n

What has been achieved so far?<\/h2>\n

EOS mainnet GitHub \u2013 repo has been officially established. A community review of the process management of the repo is expected to happen in the weeks that follow the launch.<\/p>\n

System accounts & contaracts<\/h3>\n

The EOS team has successfully assessed that the system accounts eosio.msig, eosio.bpay, eosio.ramfee, eosio.names, eosio.ram, eosio.saving, eosio.token, eosio.stake, and eosio.vpay have been correctly created. The team has also validated that eosio (system), eosio.msig, and eosio.token contracts have been installed correctly with ricardian contracts.<\/p>\n

Candidate chains<\/h3>\n

Notably, the EOS team has stated that two candidate chains exist and is being tested over the past two days. Only one of them will become the EOS mainnet.<\/p>\n

During testing the EOS<\/a> team has discovered five issues referred using the syntax P0 to P4.
\nIt has been mentioned that P0 and P1 will take additional time to patch and test. In particular, P1 is a \u2018must fix\u2019 error. If time and resources permit, P2 will get fixed. Likewise, P3 might be fixed. P4 issue has been noted and will be taken up in the future.<\/p>\n

To ensure security of the chain, EOS is collaborating with renowned security firms to standardize the security practices at a Block Producer Candidate level. The firms will introduce themselves after the details are finalized.<\/p>\n

Additionally, the EOS team has set up a security-focused test-network for all Block Producer Candidates who are interested in joining the testing process. The EOS team has also compiled a detailed list of software tests which will be completed by dozens of Block Producer Candidate teams. The tests are aimed to make sure that all functionalities of the software are working as expected.<\/p>\n

In other related news, a Netherlands based ethical hacker who uses Guido Vranken as his twitter name has found 12 bugs in EOS codes. At the rate of $10,000 per identified coding error, Block.one will be paying him $120,000.<\/p>\n

<\/p>\n
\n

Thank you. A couple more waiting to be rewarded. I think the final tally was $120K but I lost count. Took me about a week.<\/p>\n

\u2014 Guido Vranken (@GuidoVranken) June 4, 2018<\/a><\/p><\/blockquote>\n