Developing the BMCHAIN platform

The closed beta test of the BMCHAIN platform have been launched two months earlier that it was planned. The first testers have already submitted their first feedbacks, the dev team continues their work considering the comments received, so we decided to say a little about the platform in this article.

For the beginning we must to say that the BMCHAIN platform was created on the basis of existing platform named steemit. However, while the development process and with the operating results of the other platform named platform.molodost.bz it became clear that the code must be rewritten to implement all the features planned. In particular, the changes were made in the blockchain's core. For example, content downloading speed were increased, and compatibility for new design and functionality were added. But the client application had to be completely rewritten. The new client application was determined by several factors, both because the steemit client is quite complicated and with a lack of documentation for its working process, and because the team wanted not only to expand the capabilities of the BMCHAIN platform compared to original steemit, but to create a new unique design. The Angular 2.0 framework from Google were choose for client application development. Later it was gradually moved to the updated Angular version 4.0, and recently started the transition on the fifth version, which update was released on November,1 this year. On assurances of developers, all of this helped to create a more flexible client, that becomes easy respond to users requests and wishes. The increasingly popular technology of SPA (Single Page Application) was also implemented, which will help to reduce the load of servers and simplify user's working with the page because of the most of the necessary code is loading along with the page when first loaded, thereby reducing subsequent requests to the server, and expanding the capabilities of the page viewing in the browser.

Further work with the platform assumes a series of load tests on its functionality. The original purpose of the audit is to find the boundaries, the maximum value for the number of simultaneous connections per time, to guarantee a stable work of the platform for users. Due to results of the tests a new changes in the configuration of the generation rate or the size of the blocks in the blockchain might be done, with the aim of improving the reliability or the downloading speed of the platform.