Block.one activated their second voting proxy on December 1, 2020 and is now voting with all 95.7M of their EOS holdings, which is a significant milestone for the EOS Mainnet. Not only is it very clear that Block.one is paying close attention to the EOS Mainnet, but this vote also significantly increases the security of the network.
As we explained in a popular tweet following the vote, ‘voting weight’ in a Delegated Proof of Stake network like EOS is the equivalent to ‘hash power’ in a Proof of Work network like Bitcoin, as they both contribute to the security of the network. Adding 85M votes to EOS is the equivalent of a massive +27% increase in hash rate! There are now over 400M EOS tokens that are staked and voting for block producers, which is a new all-time high for EOS!
In order to qualify for the new sub2.b1 85.7M EOS proxy, block producing teams must be currently engaged with the new resource model testing program.
It’s important to note that Block.one is not evaluating this engagement as positive or negative. All feedback that is presented, regardless if it’s in favour of the new ressource model or against it, is valuable to Block.one and rewarded with inclusion in the sub2.b1 proxy. We’ve seen many block producer teams respond to the call and actively engage in testing the new resource model and it’s been a pleasure to see such high levels of engagement across various stakeholders such as popular dApps, wallets, and even regular users.
As a reminder, their first voting account, sub1.b1, contains 10M EOS and votes on a rotational basis for a large selection of block producers who meet that proxy’s basic criteria, which includes:
- The location of the node is disclosed publicly in the JSON file.
- The candidate independently operates an API or P2P node that can be queried publicly.
- The API or P2P node runs on EOSIO 2.0 or later.
- The candidate’s GitHub username is disclosed in the JSON file.
Block.one has also re-confirmed their desire to increase the basic criteria requirements over time and are currently “exploring ways to consistently measure the performance of public API offerings” as their next step in the process. As always, feedback is always welcome and you can message Kevin Rose on Telegram or email the PBE at email@example.com.