We are experienced programmers and we know that it is impossible to build any complex software project without errors. EOS is a big system written in C, any experienced software engineer understands: for a system of such level of complexity the existence of errors is normal. Let's be calm about the error messages, carefully study and understand each case. The existence of errors does not change the fact that a system is working, and panic from such messages about “new scary bugs in EOS” is mostly suggested by those who never ran large C projects.
We must tune the eos network on each big or small problem. This will teach the EOS network to negotiate software updates, learn how to cooperate and organize collective defense against bugs and targeted attacks. It will definitely take a significant time, but this is an absolutely necessary stage for the formation of a stable and reliable network.
We don't believe that everything will go smoothly. We know for sure that this does not happen in real engineering tasks, so we call on the community to focus on tasks that allow EOS networks to easily upgrade, distribute changes and configure the network, fix the consequences of errors, learn how to make forks and test, test the network more and more. We also call security specialists and penetration testers to pay attention to the EOS software, your tests are extremely important now, it is better to fix all easy-detected bugs now than after launch the EOS mainnet.