⛓️zkSHIELD Chain

Over the years, numerous Layer 2 solutions have been created to increase the BNB's scalability, particularly transaction throughput. The decrease in petrol expenses while retaining decentralization and security is the ultimate and intended advantage for BNB Chain consumers.

The Layer 2 Rollup solution zkSHIELD combines data accessibility and execution verification in Layer 1 of the BNB Chain to guarantee the security and dependability of L2 state transitions.

This section will provide an overview of the components utilized in the creation of the zkSHIELD Protocol while also describing the infrastructure that zkSHIELD created and put into place.

USER TRANSACTION:

The zkSHIELD Chain's three primary parts are as follows:

Secure sequencer:

Receives L2 transactions, and the Secure Sequencer organizes them, creates batches, and submits them to the Consensus Contract. For quick finality and lower network costs, it broadcasts batches of transactions to L2 network nodes.

Secure Aggregator:

Utilising the batches produced by the Secure Sequencer, the Secure Aggregator determines the L2 State. It generates Zero-Knowledge proofs that verify the batches' computational integrity, and the Consensus Contract validates these proofs. A validated proof demonstrates how a particular batch sequence leads to a particular L2 State.

Consensus Contract (zkSHIELD.sol, deployed on L1)

The Trusted Sequencer and the Trusted Aggregator both employ the Consensus Contract, zkSHIELD.sol, a smart contract installed on L1, in their communications with L1. Its goal is to verify that the zkSHIELD inherits the L1 security and to validate the Zero-Knowledge proofs created by the Trusted Aggregator.

Execution Modes for zkSHIELD Nodes

A software package called zkSHIELD node includes every part required to run the zkSHIELD network. It may be used as a Sequencer, Aggregator, or RPC in any of these three operating modes.