- The Block.one is a private open-source publisher company responsible for creating platforms like EOS.IO.
- EOS Nation has decided to test the new versions in production on the EOS Mainnet.
- Block.one’s contribution includes their ability and agility to solve problems faced by EOS mainnet group, as fast as possible.
The Block.one is a private open-source publisher company responsible for creating platforms like EOS.IO, a blockchain platform enabled by the EOS cryptocurrency. This platform aims at facilitating a huge number of financial transactions within a small span of time through its smart contract process, which allows the platform to crunch off high transaction fees charged by various institutions.
EOS.IO is the result of a white paper published in 2017 and Block .one’s ability to transcribe the idea into reality and release the same as open-source software on June 1 of 2018.
As a marketing strategy, Block.one distributed around one billion tokens as ERC-20 tokens during its launch. Subsequently, block.one raised around four billion US dollars to back up the blockchain platform during its ICO period.
This article focuses on the contributions of Block .one and key block producers of EOS Mainnet on the blockchain platform, including their collaborations to achieve the ends of the objectives set out by the platform.
Block.one’s contribution includes their ability and agility to solve problems faced by EOS mainnet group, as fast as possible. This includes addressing the microforks and handling the missing block challenges.
The product of their contributions includes various new features, which includes the Drop-Late Box, which ensures that the blocks moving late from the prior block producers to next block producers are dropped, unlike the previous blocks.
This continuously interrupted the production process, the CPU-effort –percent to calculate and estimate the quantity of CPU used for the blocks, which ultimately increases the speed of smaller blocks and the read-only feature which aims at increasing the efficiency of the block-exchange process.
These features were noted in the release notes for 1.8.11 and 2.02 versions of the platform. Apart from the above, the platform has also gone through significant infrastructural changes to increase overall productivity.
This includes upgrading the CPU performance, node architectural improvements, configuration tuning, and so on. The result of each of these changes can only be observed from the overall output received from the conglomeration of all the single changes put together to achieve the end product.
However, it is also to be noted that, this process might also face several challenges during its working stage. The cause of these challenges the platform cannot handle new and old configurations at the same time.
The 2.0 Version
The platform effectuates the EOSIO 2.0’s upgrade process through public API and P2P nodes. In addition to that, the infrastructure developers are looking forward to launching the 2.0.2 version of the platform to improve the overall performance. The other areas of the platform will be improvised eventually by the producers at appropriate durations.
EOS Nation has decided to test the new versions in production on the EOS Mainnet. It is hoped that other block producers participate in the event subsequently. The result of which has made Matthew Darwin, Chief Infrastructure Officer, to be n continuous contact with Block .one to clarify and solve various issues associated with the platform.
One a conclusive note, it can be ascertained that Block .one and the block producers are enduring hand in hand through various ups and downs to achieve the end result from their unique collaboration aimed to achieve the objectives set out by the platform.