Architecture of Hyper Chain
Architecture of Hyper Chain
Building on top of Ethereum Layer 1, the primary function of Hyper Chain is to support smart contract by facilitating state transitions caused by Layer 2 transaction executions. Zero-knowledge proof (ZKP) technology is utilized to generate validity proofs that confirm the accuracy of off-chain state change computations. Essentially, Hyper Chain goes beyond the capabilities of the previous attempts to enable more efficient and secure transaction processing for decentralized applications (dApps).
Implementing Proof-of-Efficiency (PoE) as its consensus mechanism, there are four pillars shoring up the functionalities of Hyper Chain;
Consensus contract: The lastest version of HyperchainZkEVM.sol supports multiple Coordinators to create transaction packages on L2 in a permissionless manner. It also ensures decentralization, efficiency, protection from attacks, and a balance between verification effort and network value.
zkNode: Composed of Sequencers & Aggregators, Synchronizer, as well as RPC, zkNode can be considered as a client that enables synchronization of Sequencers and Aggregators via RPC.
zkProver: Utilized by Aggregators, zkProver employs zero-knowledge proof (ZKP) technology to validate batches and provide validity proofs.
LX-to-LY bridge: A smart contract allows users to transfer their assets between two layers, LX and LY. In the context of Hyper Chain, L1-L2 connects Ethereum minnet and rollups for data migrations.
Figure 1 below can briefly explain how different modules work together.
More detailed information regarding each component and technologies mentioned can be found in the following sections.
Last updated