HPB芯链白皮书.pdf

HPBTM（ High-perance Blockchain） White Paper 1 HPBTM（ High-perance Blockchain） White Paper HPBTM（ High-perance Blockchain） White Paper 2 Table of Contents 1. Project Background ................................................................................................................ 3 2. Design Concept ..................................................................................................................... 4 3. Technology Framework .......................................................................................................... 6 3.1 Technology Features ........................................................................................................ 6 3.2 Consensus Algorithm DPOS - Delegated Proof-of-Stake Consensus ............................10 3.3 Identity and Authorization Management ...........................................................................11 3.4 Status Channel ................................................................................................................12 3.5 Application Services ........................................................................................................13 3.6 Smart Contract System ....................................................................................................14 3.7 General Virtual Machine GVM Mechanism ....................................................................14 3.8 System Management .......................................................................................................16 4. Governance Framework ........................................................................................................16 4.1 HPB Token Introduction GXN ........................................................................................16 4.2 Crowdfunding Details.......................................................................................................17 4.3 Crowdfunding Allocation ..................................................................................................17 5. Implementation the subsequent success of the company can then free up more resources to improve the open source software. 3.1.2 Support Millions of Daily Users Applications like Google, Uber, and BAT require handling of millions of active users per day through block chain technology, so a plat that can handle massive amounts of user data are critical. 3.1.3 Low Latency Confirmation within seconds. Timely feedback is the foundation of a good user experience. If the delay is more than even a few seconds, it will greatly affect the user experience, and it may even be unable to meet business needs, thus seriously reducing the competitiveness of the application. 3.1.4 High Throughput, High Concurrency Because applications such as exchanges can only cute operations serially as opposed to in parallel, HPB must provide powerful serial capability. For other scenarios, we will provide powerful parallel processing capabilities, parallelization of most tasks, and a combination of hardware and software architectures that allows blockchain TPS to be raised by 2 orders of magnitude. HPB uses TOE technology, which aims to accomplish some or all packet processing tasks through a dedicated processor on a dedicated network card. In other words, by using a specialized network card with a TEO chip, it uses four layers of TCP processing to transfer HPBTM（ High-perance Blockchain） White Paper 8 from the host processor to the hardware accelerator. The end result is accelerated response, enhanced network concurrency, reduced server complexity, and improved node processing perance. 3.1.5 Acceleration Engine The traditional node block chain must support numerous functions on the software level, such as trade confirmations, which consist of broadcasting, transaction confirmation, confirming release of ination, etc. The data connections between each node are serially processed, which leads to complex hierarchical network structure, long time delay, and low serial perance, which leads to user experience problems. Therefore, HPB is designed around block chain dedicated hardware acceleration units including hardware and firmware acceleration and software engine matching system driver and software interface API hardware acceleration. Through parallel processing ability of CPU, GPU, FPGA and serial ASIC chip, it achieves high perance and high speed concurrent computation. The hardware acceleration engine can achieve high concurrent connections, while maintaining support for over 10000 TCP sessions, 10000 parallel sessions, and greatly reduces the number of network layers. It will take over traditional serial processing functions, i.e. transaction data broadcast, unverified blocks, whole network broadcast, transaction confirmation broadcasting, etc. The rate of response for each session as well as session maintenance is greater than 100 times the perance of an ordinary PC node. The HPB hardware acceleration engine, system architecture, and processes are described below HPBTM（ High-perance Blockchain） White Paper 9 1. System and hardware initialization , access to whole network configuration table entries, establish session, maintain reliable session 2. User initiates transaction request at any node. By accelerating the hardware, it sends signature ination to the whole network via parallel broadcast, and also begins to monitor network confirmation status 3. Randomly designated nodes through DPOS algorithm elected block generation receives transaction with signature ination, packages to an unconfirmed block, and through accelerated hardware is broadcast network-wide 4. The HPB hardware of each node throughout the network is confirmed and the result is a block confirmation broadcast 5. Node receives the agreed K block acknowledgement message HPBTM（ High-perance Blockchain） White Paper 10 6. Consensus is reached and a complete block is issued. The whole network broadcasts a completed block, and each node updates their ledgers. Because the HPB hardware acceleration engine can maintain a large number of conversations with so many nodes, it does not have to wait until a complete block is released. Through statistical transaction confirmation, it pushes forward user confirmation, thus enhancing the user experience. 3.2 Consensus Algorithm DPOS - Delegated Proof-of-Stake Consensus The HPB architecture uses the blockchain consensus algorithm DPOS, which is the only one capable of combining the previously mentioned perance requirements. According to this algorithm, the whole network of token holders is able to vote through the system to appoint new block producers. Anyone can participate in block production once elected. HPB is expected to produce a new block every 3 seconds. At any point, only one producer is authorized to produce blocks. If a block production fails at any time, then that block is skipped. Under normal circumstances, DPOS blocks to not experience any forking, because block producers work together to produce blocks rather than compete. If a block is split, the consensus will automatically switch to the longest chain. Blockchains with more producers will grow faster than blockchains with fewer producers. In addition, no block producers should simultaneously produce blocks on both forks of a blockchain. If it discovered a block producer has done this, it can be voted out. HPBTM（ High-perance Blockchain） White Paper 11 3.2.1 Transaction Confirmation The block chains maintained by the DPOS algorithm are 100 online. That is to say, after an average of 1.5 seconds, a transaction will be written into the blockchain and all outgoing nodes will be aware of the transaction. This means that in only 1.5 seconds, a transaction can be identified as 99.9 confirmed received onto the blockchain. 3.2.2 Plug-and-Play Consensus Algorithm Module The DPOS consensus algorithm can widely support public chains, alliance chains and private chains. If there is a specific business use scenario or specific business needs, HPB plug-and-play consensus algorithm module can flexibly support integrated handover of different consensus algorithms, as well as support a common interface for POS-type consensus algorithms. 3.3 Identity and Authorization Management Identity authentication and authorization is an important basic module for enterprise applications. The HPB framework service layer design supports authentication and authorization of multi-level participants and related resources. HPB allows using only a 3 to 32 character long account name to refer to accounts, which is chosen by the account creator. All accounts must be filled with a minimum account balance at the time of creation in order to cover the costs of storing account data. HPBTM（ High-perance Blockchain） White Paper 12 3.3.1 Role-Based Privilege Management Privilege management is chiefly concerned with defining whether or not a particular message is properly authorized. The simplest of privilege management is to check if the transaction has the required signature, but this implies that the required signature is known. Usually, authority is tied to individuals or groups of individuals. HPB provides a declarative rights management system that allows for high-level account granularity and control for anyone at any time. It is essential that authentication and authority management is standardized and separated from the business logic of the application. This makes it possible