We have extensive experience running multi-region, high available, disaster recovering applications that are used by tens of millions of users. These are real technical challenges that BPs will face when the EOS main net goes live. Therefore the second goal of EOS Asia is to dedicate our technical strength to maintain a highly available and robust network for the EOS community.
The Stakes Are High
EOS is right now the center of attention for the blockchain world. The stake is quite high. There will be malicious actors launching technical attacks such as DDOS to the system for their benefits. If BPs failed to address and recover from these attacks, people will lose confidence in the technology. No dApp developers will not want to build on a platform that constantly fails because of some technical incompetent BPs are doing their job.
The Most Fundamental Part of a BP
We collectively as BPCs actually have a huge responsibility to maintain a highly available network for the EOS ecosystem. And yet, right now, we felt like a lot of the BPCs are not paying enough attention to the technical challenges of running BPs. They are doing PRs, marketing and trying to get people to vote for them, but they are not prioritizing the most fundamental thing: which is, whether they have the right technical people to run the BP node. This problem is particularly problematic in Asia in my opinion. Some of them got listed on EOS Go, but never really participated in testnet. Some participated but never really maintain it or stay updated.
We are only 1 month and less than 10 days away from the mainnet launch. Therefore, we don’t really have a lot of time. We still haven’t performed a successful BIOS boot simulation.
However, it is not all bad news. We have also seen some technically savvy BPCs releasing technical details and trying to help each other to navigate the technical difficulties. This gives me a lot of hope moving forward.