[vc_column_text]After completion of ICO, Edenchain’s developers have been focusing our efforts on preparing for testnet launch. To keep up with quick pace of development in cryptocurrencies and to take technical leadership, we focused on ensuring that Edenchain succeeds on both technology and business.
As many of you would have read from our earlier blog articles, Edenchain is likely to establish a Blockchain Research and Development centre in Vietnam with the goal of having more than a hundred blockchain developers. Currently, the R&D centre has been adding more workforces, who have been working hard on preparing for Edenchain testnet launch. It is to our delight to announce that Edenchain technology development had been faster than we originally anticipated, and we will launch our testnet in September 2018, one quarter ahead of our roadmap schedule.
In addition to that, we would like to share some development updates.
Blockchain Migration to Cloud Computing
Blockchain Migration to Cloud Computing
Cloud computing takes important role in EdenChain because it is multi-tenancy blockchain platform for enterprise. It empowers enterprises to have their own full controllability in EdenChain. For example if enterprise wants to control accessibility of private transaction records, they can do that with customised business logic. If the enterprise is keen to operate a dedicated blockchain platform by themselves, that can be done using Edenchain as well. If enterprise needs to use proprietary encryption algorithm to strengthen security, they can choose an algorithm and apply it to their business logic. The degree of customisation possible on Edenchain would appeal greatly to enterprise users.
To meet enterprise’s need, cloud computing is the most compelling technology to be chosen. In legacy setups, enterprises will have dedicated centralised servers to operate their platform, causing issues such as managing IT inventory, maintenance, high fixed capital expenditures, and server stability issues. Cloud computing can solve these issues. With cloud computing, the focus is on writing scripts for desirable IT environment, configuring CPU/ RAM resources needed, compute machine and regions to be deployed. It is like a “command and wait”.
Other enterprise-grade blockchain platforms such as Hyperledger is not designed for the cloud environment. Changes to the design of Hyperledger architecture is needed to ensure suitability with the cloud. This involves massive structural change. The changes involves rethinking about the whole logic flow process, components inside the architecture and its impacts on the current implementation. Such architecture changes are typically not welcomed by most engineers because it involves significant work to overhaul and integrate the changes with new components. After the redesign, intensive testing is needed to ensure that new architecture is functional and stable.
We have been working on reengineering endpoints part to support massive transaction requests from external system. Existing blockchain software design is not capable to handle such voluminous requests reliably. We conducted stress tests on Hyperledger and found that it crashes during peak usage. The inability of Hyperledger to handle large volume of requests and lack of stability makes it untenable for commercial usage. Because endpoints are exposed to APIs, the platform must be stable and capable of handling large volumes of requests.
Edenchain’s approach to this technical issue is to elaborate reengineering messaging system. We designed a queue memory management system so if the platform can cope with API requests and Edenchain will be able to handle huge API requests with efficient memory management.
Performance optimization is the area where tremendous works should be done. It is obvious that performance optimization is directly correlate with transaction per second. To provide workable blockchain platform to enterprise, we estimated that 1000 TPS per namespace would be the performance needed for most commercial use-cases.
Edenchain chose to use a forked version of Hyperledger because of the great flexibility in architecture structure of Hyperledger.
In EdenChain, business logic is running on enterprise user’s computing zone. That means that whenever business logic needs to access Edenchain platform, it uses internet to interact with Edenchain. To fulfil a transaction request, the enterprise’s business logic will communicate over the internet with Edenchain.
The pros of such a design is flexibility and business logic accessibility. However, such a design tend to compromise on performance. A common way of transaction handling in other blockchains is to conduct the business logic within the blockchain platform computing zone without any communication. However, this also means that the enterprise user have limited control and customisation over the business logic design.
To ensure that Edenchain is an attractive platform for enterprise users, we designed the architecture above because enterprise users want to run their business logic within their own computing zone.
To tackle with the technical issue of low performance when communications are conducted over the internet, we are working on non-blocking task management for business logic. Sending multiple requests at once could be a way to improve performance of transaction handling. Less blocking platform is good for business logic as well as platform. Because Edenchain processes API requests in block level not in transaction level, it is more efficient way to utilize computing resources. Of course writing optimized business logic is fundamental thing.