Verification Layer
Mission
We aim to accelerate Bitcoin's capabilities and adoption of verifiable computation by enabling efficient, economical verification, and validation proofs on Bitcoin at 10% less of the cost with aggregated proofs.
What Values Does the LayerEdge Verification Layer Bring to the Bitcoin Ecosystem?
The Blocksize War marked a significant chapter in Bitcoin's history, dividing its community between proponents of Large Block Size, advocating for greater transaction capacity per block, and supporters of Small Block Size, prioritizing network security and decentralization. Large Block Size proponents suggested increasing the block size, while Small Block Size supporters argued maintaining the 1 MB size and focusing on second-layer solutions like the Lightning Network for transaction scalability.
In 2017, the debate concluded with the adoption of segregated witness (SegWit), which effectively optimized data storage within the existing 1 MB blocks to accommodate more transactions.
Since then, various Layer 2 solutions (e.g., Lightning Network) and Layer 1 applications (e.g., sidechains like Liquid and RSK) have been developed on Bitcoin, leading to a significant increase in transaction volumes and data demands on the Bitcoin network. This growth has resulted in a backlog of transactions, causing data congestion and subsequently driving up transaction fees.
LayerEdge emerges as a potential solution to address these challenges of data congestion and high transaction fees.
The LayerEdge Verification Layer is a crucial component of the LayerEdge architecture, designed to enhance the efficiency and security of data settlement on the Bitcoin network. This layer functions as an intermediary that aggregates zk proofs (zero-knowledge proofs) from various sources, verifies them, and ensures their seamless integration into the Bitcoin blockchain. Here’s an in-depth look at the LayerEdge Verification Layer:
Core Functions
Aggregation of zk Proofs: The primary role of the verification layer is to collect zk proofs from different protocols and chains. These proofs can come from DA layers, PoS chains, DID protocols, or ZK roll-ups.
Proof Verification: Once zk proofs are aggregated, the verification layer performs thorough checks to ensure their validity. This verification process is crucial for maintaining the integrity and security of the data being settled on the Bitcoin network.
Data Settlement on Bitcoin: After verification, the aggregated proofs are settled on the Bitcoin network. This involves creating a final proof that encapsulates the information from the individual zk proofs, making it ready for inclusion in Bitcoin’s blockchain.
Interaction with Other Components
Direct Interaction with zk Proof Generators: Protocols and chains that already generate zk proofs, such as DID protocols or ZK roll-ups, can directly interact with the verification layer. They submit their zk proofs, which are then aggregated and verified before settlement on Bitcoin.
Interaction with HMDA for Proof Generation: For DA layers and PoS chains that do not generate zk proofs, the HMDA protocol comes into play. HMDA generates the necessary zk proofs, which are then sent to the verification layer. This process ensures that even chains without native zk proof capabilities can benefit from LayerEdge’s verification and settlement services.
Benefits of the LayerEdge Verification Layer
Enhanced Security: By verifying zk proofs before they are settled on the Bitcoin network, the verification layer ensures that only valid and tamper-proof data is included. This enhances the overall security of the data settlement process.
Cost Efficiency: Aggregating zk proofs reduces the number of transactions needed to settle data on Bitcoin. This aggregation significantly lowers transaction costs compared to settling each proof individually, making the process more cost-effective.
Scalability: The verification layer’s ability to handle zk proofs from multiple sources makes it highly scalable. It can support a wide range of protocols and chains, enhancing their ability to securely settle data on Bitcoin.
Flexibility: The verification layer is designed to be flexible, accommodating both direct zk proof submissions and those generated via HMDA. This flexibility ensures that a broad spectrum of decentralized applications can utilize LayerEdge’s services.
Technical Workflow
Proof Submission: zk proofs are submitted to the verification layer either directly by protocols and chains or via HMDA.
Aggregation Process: The verification layer aggregates multiple zk proofs into a single, comprehensive proof. This involves combining the information contained in each proof to create a consolidated dataset.
Verification Process: The aggregated proof undergoes a verification process to ensure its validity and integrity. This step is critical for maintaining the security of the data settlement process.
Settlement on Bitcoin: The verified, aggregated proof is then settled on the Bitcoin network. This final step involves including the proof in Bitcoin’s blockchain, making the data tamper-proof and publicly verifiable.
Use Cases
DID Protocols: Digital Identity (DID) protocols can directly submit their zk proofs to the verification layer, ensuring secure and verifiable identity management on the Bitcoin network.
ZK Roll-ups: ZK roll-ups, which batch multiple transactions into a single proof, can leverage the verification layer to settle their data efficiently and cost-effectively on Bitcoin.
DA Layers and PoS Chains: DA layers and PoS chains that do not generate zk proofs can utilize HMDA to create these proofs. The verification layer then aggregates and verifies these proofs before settling them on Bitcoin.
The LayerEdge Verification Layer plays a pivotal role in the LayerEdge ecosystem, providing a secure, scalable, and cost-effective solution for data settlement on the Bitcoin network. By aggregating and verifying zk proofs from various sources, the verification layer ensures the integrity and efficiency of the data settlement process. This capability makes it a valuable tool for a wide range of decentralized applications, from DID protocols to ZK roll-ups and beyond.
Last updated
