zkBridge
  • Polyhedra Network
  • zkBridge: Trustless Cross-chain Bridges Made Practical
    • Introducing zkBridge protocol
    • Block header relay network
    • Updater contract
    • Proof systems of zkBridge
    • zkBridge Research Paper
  • zkLightClient Overview
    • Introduction
    • zkLightClient on LayerZero ​
  • LayerZero zkLightClient Configurations
    • LayerZero V1 zkLightClient Oracle Addresses
    • LayerZero V2 zkLightClient DVN Addresses
    • LayerZero UA Configuration
  • Proving Ethereum Full PoS Consensus in ZK
    • Overview
    • Why Proving Ethereum full consensus?
    • System design for proving Ethereum full consensus
    • Efficient proof system for proving Ethereum full consensus
    • Performance evaluation
    • Concluding remarks
  • Application Use Cases
    • NFT transfer
    • Message passing
  • Tutorial
    • Import and transfer NFTs
  • Code Examples
    • Deploying Cross-chain NFTs
      • Cross-chain ERC-721
      • Cross-chain ERC-1155
Powered by GitBook
On this page
  1. zkBridge: Trustless Cross-chain Bridges Made Practical

Introducing zkBridge protocol

PreviousPolyhedra NetworkNextBlock header relay network

Last updated 1 year ago

zkBridge uses zkSNARKs to enable a prover to efficiently convince the receiver chain that a certain state transition happened on the sender chain. zkBridge consists of a block header relay network and an updater contract.

The block header relay network retrieves the block headers from the sender chain, generates proofs of the validity of the block headers, and sends the headers along with the proofs to the updater contract (set up on the receiver chain).

The updater contract maintains a light-client state. It automatically adds block headers of the sender chain once the associated proofs are verified, and updates the current main chain of the sender chain.