This is a credible review intended to add some positive constructive additional information to the already known information which had been published in the White paper, yellow paper and Blue paper. Starting from here, I will say this that the EOSIO blockchain has various developing team members which have assisted in getting the word out about EOSIO blockchain and EOSIO based project. Many would wonder what a blue paper is... I will tell you all. This isn't a white paper or yellow paper but this blue paper contains information regarding to the APIs on the EOSIO blockchain.
This blue print comprises of components that were initially involved in the White paper then a yellow paper, a request for a proposal and a road map. After reading the blue paper, I can evidently see that there were some services that were actually used to offer APIs on the EOSIO blockchain. The reason for me doing this review is to make sure that the view and perspectives that I have about the EOSIO blockchain and the APIs and the whole EOSIO Ecosystem could be integrated after view by the EOS Network foundation and the greater EOSIO Ecosystem.
Based on the preliminary information that was received and to the best of my knowledge, this was how the blue paper was published. The EOS Network Foundation (ENF) didn't just publish this on their own, they had to invite about three different teams namely, EOS nation, EOS Rio and EOS Grey mass to come together as a team based on the fact that these individual teams were already conversant with the working principles of the EOSIO APIs and had very brilliant history with related solutions. I can boldly tell all that the reason why EOS Network Foundation put this new team together was to review the existing history solutions and recommend a way forward in the sustainability of the EOSIO blockchain and Ecosystem to have the best for the while EOSIO blockchain users.
The team started working by getting acquainted with each other and with the objective of the team formation. They carried out this review and publication of the blue paper by various means of approach but I have clearly recognised the approach of getting information from stakeholders of the EOSIO blockchain Ecosystem both individuals and corporate bodies based on where they felt the EOSIO blockchain Ecosystem were lacking and the needs they wanted. This provided a great foundation for reliance upon which the API+ team could get some positive feedback result that would be beneficial to the whole EOSIO Ecosystem. The team also tried their best to listen to various public conversations across some social media like Discord, Telegram and Twitter spaces to know the challenges in which developers which develop on the EOSIO blockchain encounter and how they can be improved. This information came from various professionals who depend on the EOSIO API services not excluding developers, eosio based applications, exchanges and other valuable service providers.
To me as an individual, I got to knkutrwq of the EOS coin and EOSIO blockchain as of 2019/2020. This was so amazing to discover that there was actually a coin that hit its all time high as at 2018 of $30 and as at 2020, I actually got about 10 EOS at the rate of $10 each. It was so amazing to hodl EOS. It was so wonderful hodling this token, then I started to exploit the blockchain, I found so many things. The first wallet I ever used to hodl EOS was the Token Pocket wallet and then I also later moved on to use the Wombat wallet but the difference between these two is that, I have my private key with Token Pocket but I don't have with the Wombat wallet. Then as fate would have it, I got to know of Challengeeos application which is being built on the EOSIO blockchain. Challengeeos application is an application this is being built on the EOSIO blockchain and is a marketing tool which rewards users for carrying out some specific tasks. This was the platform I first heard about EOS, it has been ever amazing since then, they educate their users a lot about EOSIO projects and try to inform its users about trending events on the EOS Network foundation and the whole EOSIO Ecosystem. It was so much fun getting to know of an application that was built on the EOSIO blockchain making use of the EOSIO API. The founder of this application is Chace Eskam from San Diego in California. I created an account on the challengeeos application with the username "maxwellmilo2" and this is currently the version 8.0 of the application. I have witnessed the release of various versions before now and I have been a user of the application for over 2 years now. So I can boldly say I have experienced usage of the EOSIO API for over two years.
After careful observation and collection of data via the approaches mentioned above, I also had to take my time and go through the whole blue paper to find out the pressing needs of the EOSIO APIs and to also suggest a better solution to improve the blockchain and its whole Ecosystem. The issue of sustainability is very important to consider in relation to the whole EOSIO Ecosystem, there are a lot of uncertainties which is associated with the EOSIO API services and until this is properly managed and curtailed by developing a suitable non depletion sustainable system.
The main challenge as discovered by me is that the EOSIO blockchain has low customization accessibility as relating to software development. Now in developing services on blockchain, there have been recent developments and it has been as a result of an update in technology. The Web 3.0 have been very productive and it holds many potential for developing software. I cannot overemphasize this but to still say that if software and applications developers which are building currently on the EOSIO blockchain with their various specific features and concepts that they would love to implement have the accessibility to reproduce with effective technology have the opportunity to do these on the EOSIO blockchain, then this challenge would be eliminated. This is my constructive feedback for this. This has portrayed as a very bad thing for both the users of the software or application and it has stressed a lot. I have seen some users that made some complains sometime last year.. Thanks for this opportunity to express myself. There are also some reoccureent times of having CPU timeout or CPU billage time and sometimes we all get out of ram but we buy that also, it's affordable but provisions and development should be made to avoid these in the nearest future.
