BNB Chain has introduced the combination of zero-knowledge (zk) fault proofs for its opBNB protocol. This growth goals to reinforce the efficiency and robustness of the blockchain, in line with the BNB Chain Weblog.
Background on zk-Fault Proof
Up to now 12 months, Optimism initiated a Basis Mission Request to develop the Op Stack Zero Data Proof (ZKP) for verifying the correctness of its fault proof program. The ZKP goals to scale back the problem interval from 7 days to 12 hours, avoiding difficult interactive problem procedures. Optimism funded three proposals from Risc Zero, O(1) Labs, and the ETH Storage workforce, all of which proposed compiling the fault proof program right into a generic instruction set like RISCV, WASM, or MIPS.
The compiled directions are verified utilizing zkVMs corresponding to zkRISCV, zkWASM, or zkMIPS. This technique, often known as the generic VM strategy, contrasts with a customized circuit strategy, which BNB Chain believes affords higher efficiency.
Improvement and Implementation
Polygon Zero just lately developed a extremely performant type1 zkEVM, aligning with BNB Chain’s expectations for making a customized circuit for opBNB’s fault proof program. Consequently, BNB Chain developed a proof of idea (PoC) based mostly on Polygon Zero’s type1 zkEVM to show efficiency benefits over the generic VM strategy. The PoC is particular to Optimism and may generate ZKP for its blocks.
The prevailing fault proof design for Optimism includes off-chain and on-chain parts, characterised by a excessive fuel value and susceptibility to censorship assaults. The zk-fault proof goals to handle these points by enabling challengers to submit only one on-chain transaction, thereby lowering fuel prices and shortening the problem interval.
Structure of ZK Fault Proof
The zk-fault proof design contains a number of parts:
- Optimism Block Execution Circuit: Processes L2 blocks in line with the Optimism state transition protocol.
- Optimism Block Derivation Circuit: Derives L2 blocks from L1 information, verifying the correctness of the derived L2 block.
- Fault Proof Circuit: Validates the execution and derivation proofs, making certain consistency.
- zkFaultProofVerifier Contract: Resides on the L1 chain to confirm the correctness of the ZK fault proof.
Challengers can generate a zk-fault proof for disputed L1 blocks and submit it to the zkFaultProofVerifier contract. If verified, the challenger wins, lowering susceptibility to censorship assaults and enhancing consumer expertise.
Efficiency Testing
BNB Chain performed efficiency exams evaluating the opBNB customized circuit with Zeth developed by Risc Zero. The customized circuit proved extra environment friendly, producing 10 occasions fewer ZK cycles and proving 5-6 occasions quicker than Zeth, making the opBNB strategy 5-6 occasions cheaper.
Future Work
The type1 zkEVM remains to be in growth, with options like continuations geared toward making proof technology extra parallel-friendly. BNB Chain plans to contribute to those enhancements, anticipating important efficiency boosts for the opBNB customized circuit strategy.
To finish the ZK fault proof for Optimism or opBNB, extra parts just like the block derivation circuit, fault proof circuit, and on-chain zkFaultProofVerifier contract have to be applied. These duties are slated for the following part of the PoC.
Upon completion, the opBNB workforce will contribute their work to the Optimism ecosystem to reinforce the safety and efficiency of the multi-proof system.
Picture supply: Shutterstock