Galactic
  • ⛓️Tusima Galactic
  • Rollup
    • 🏁Preface
    • Section 1: Rollup Introduction
    • Section 2: ZK Rollup & Optimistic Rollup
  • ZkNode
    • 🏁Introduction
    • Section 1: ZkNode Overview
    • Section 2: ZkNode Consensus Mechanism
    • Section 3: ZkNode Individual Components
    • Section 4: JSON RPC Component
  • Zkprover
    • 🏁Introduction
    • Section 1: ZkEVM Overview
    • Section 2: ZkEVM Functions
    • Section 3: ZkProver Overview
    • Section 4: ZkProver Interaction
    • Section 5: ZkProver Components
    • Section 6: ZkProver Hash Function
    • Section 7: ZkProver ZkASM & PIL
  • Validium
    • 🏁Near DAC
    • Section 1: Near DAC Overview
    • Section 2: Near DAC Implementation
  • Bridge
    • 🏁Introduction
    • Section 1: Bridge Overview
    • Section 2: Bridge Feature
  • Branding kit
    • Tusima Branding kit
  • TERMS & PRIVACY
    • 📋Terms Of Service
    • 🔏Privacy Policy
Powered by GitBook
On this page
  1. Zkprover

Section 4: ZkProver Interaction

To clearly explain the control flow between zkProver, nodes and database, we can use a simplified flow diagram. Please note that the actual process may vary depending on the specific application scenario and system complexity. Here is a basic flowchart example:

+----------------+     +----------------+     +----------------+
|    zkProver    |     |     Node       |     |    Database    |
+----------------+     +----------------+     +----------------+
|                |     |                |     |                |
|  Request Data  |---->|  Receive Data  |---->|  Store Data    |
|                |     |                |     |                |
|                |     |  Process Data  |     |                |
|                |     |                |     |                |
|  Prove Data    |<----|  Verify Proof  |---->|  Retrieve Data |
|                |     |                |     |                |
|                |     |  Send Result   |     |                |
|                |     |                |     |                |
+----------------+     +----------------+     +----------------+

This diagram describes the following steps:

  • zkProver sends a request to the node to obtain certain data.

  • After the node receives the request, it retrieves the required data from the database.

  • The node processes this data and sends it to zkProver.

  • zkProver uses this data to generate a proof.

  • zkProver sends the generated proof back to the node.

  • The node verifies the certificate provided by zkProver.

  • If the proof is valid, the node may need to retrieve more data from the database, or perform other operations based on the proof.

  • The node eventually sends the result (which may be the result of a proof-based operation) back to zkProver or other related components.

Please note that this process is a highly simplified example and does not cover all possible scenarios and details. Real systems may have many more steps, conditional branches, and interactions. In addition, zkProver is usually a component responsible for zero-knowledge proof, which may involve complex cryptographic operations that are not shown in detail in the flow chart.

In actual applications, you may need to draw a more detailed and accurate flow chart based on specific business logic and technical implementation.

PreviousSection 3: ZkProver OverviewNextSection 5: ZkProver Components

Last updated 1 year ago