Opside is a 3-layer scaling platform providing ZK-Rollups as a Service, whose layer 2 is an EVM-compatible and Rollup-friendly chain, and layer 3 is a collection of different zkRollups. Layer 2, or Opside chain, has made many system-level optimizations for zkRollup and introduced the concept of the native rollup.
Layer 2 and 3 of the Opside architecture share a consensus mechanism that integrates PoS and PoW.
PoS (Sequencer): The validator proposes not only layer 2 blocks but also layer 3 blocks(i.e. data batch); that is, the validators are also the sequencers of the native rollups in layer 3. Sequencers can earn the gas fee from the transaction in layer 3 transactions.
PoW (Prover): Anyone can be the prover of a native rollup as long as it has enough computing power for ZKP computation. Provers generate ZK proofs for each native rollup in layer 3. A prover generates ZK proof for each block of layer 3 submitted by sequencer according to the PoW rules.
The decentralized consensus mechanism of layer 3 is described in detail below.
The validator of layer 2 assumes the role of the sequencer.
The sequencer’s revenue is the transaction fee in the block of each native rollup submitted by the sequencer. Therefore, the more rollup transactions the sequencer packs, the more revenue it generates.
When the sequencer packs the rollup block on the chain, the rollup block enters the finalized state. Therefore the time required for the layer 3 blocks to be finalized is the same as for layer 2.
If a rollup block is not verified by the proof submitted by the prover within a specific time, the block will be skipped, and the corresponding sequencer will be slashed.
Unlike a sequencer, who must be the proposer of the current layer 2 blocks, a prover can be anyone who has the ZKP computing power.
Provers who provide valid proof of a rollup block will get the corresponding block reward, and the block reward of all native rollups is paid by the Opside token (IDE). This part of the IDE token is the PoW part of the Opside reward. The system will automatically adjust the PoW reward amount according to the supply and demand balance of ZKP computing power.
When a rollup block and all its parent blocks are verified, the block is verified.
Through the hybrid consensus of PoS & PoW, Opside unifies the set of validators of layer 2 and 3, ensuring the system’s security, decentralization, and permissionlessness. Opside defines a unified system contract, and developers only need to implement these standardized interfaces and register rollup slots as native rollups. In this way, developers can focus more on implementing business logic and do not need to care about how layer 2 and layer 3 interact with each other and do not need to maintain a full node or ZKP computing power of rollup.