Solution of EPOCH highly fault-tolerant commercial Blockchain
The team members of EPOCH have large-scale data processing experience and technical practice. The core developers all worked in large multinational companies before and held the important positions in technology research and development, so now they all have a unique accumulation of technology and operational capacity to set up and optimize the framework of massive data processing system, and to handle the ledger storage and distributed computing.From the EPOCH official disclosure of the White Paper we can find the following key technical points:
In enterprise-level blockchain solutions, the concurrent processing capability of a single blockchain is mainly subject to consensus algorithms. In the actual blockchain application, the network status between nodes is good in most of the time, and the probability of node failure or byzantine node is small, so that only the data consistency of multiple nodes needs to be solved and complete the transaction efficiently in most of the time. As long as there is a node failure or fraud, it can automatically switch to the algorithm with byzantine fault tolerance to ensure the smooth operation of the business. The adaptive blockchain consensus algorithm provided by the EPOCH blockchain is efficient when the network is in good condition, and there is no node failure or fraud, and can accurately detect node failures or node frauds. When a node failure or fraud is detected, the system automatically enables the byzantine fault tolerance algorithm. In a network with 3f+1 total nodes (where f is the number of byzantine error nodes), the system normally provides services to the outside when the fault-tolerant node does not exceed f; when all node failures are repaired or byzantine fault-tolerant node is solved and all node data are the same, it automatically switches back to the efficient algorithm. Adaptive algorithm can ensure efficient concurrent processing of consortium blockchain in most of the time and accurately handle the problem of node error.
The contract part of EPOCH blockchain includes standard contracts and customized service contracts. Standard contracts include asset consistency check, automatic transaction matching, jointly confirmed transfer, automated clearing on maturity, and other contracts of relatively simple logics. The contracts are built in EPOCH blockchain and can be used by directly linking to the blockchain. User customized smart contracts include modifying configuration and adding additional business logic through contract templates, as well as supporting more complex user-programmed contracts that run in a standalone environment.
To ensure that users can access the EPOCH blockchain conveniently at low cost, EPOCH Ledger provides a flexible programming API to the application layer. The API supports both synchronous and asynchronous modes. After parsing, authenticating and verifying the service request, the interface adaptation layer records the service request to the ledger storage through a consensus algorithm. As the client of consensus management module, interface adapter module also participates in consensus management. The interface adaptation module is mainly responsible for the summary and consistency judgment of the results returned by each consensus node. In addition, when the “improved bft-pos” consensus algorithm with independent intellectual property rights is used, the interface adaptation module receives and collects the election switchover request from the service side. When the switching conditions are met, it notifies the consensus management module for reelection.
Multi-node quasi-real-time data verification: When the private key of a node is stolen and the malicious user has the possibility to modify all the data in the ledger chain, the EPOCH blockchain provides quasi-real-time data comparison mechanism among multiple nodes, which can find out whether the ledger data of a node has been tampered in time.