Continue learning @brevis_zk, the fifth article of the White Paper detailed series is here:

How is it proven that "orders" become "trustworthy results on the chain"?

This is a popular science article explaining the Brevis ZK proof process.

In the previous articles, I shared with you the three major products of Brevis:

Pico can break down large tasks and process them in parallel.

Data Coprocessor can accurately calculate and prove the on-chain historical data.

TODA allows "proof of generation" to be traded on the platform.

What processes will a proof go through from the proposal of a requirement to becoming a "trustworthy on-chain result"?

------------------------------------

Step 1: The user or contract publishes a "proof task"

Here are 2 common examples:

"Help me prove what the user's transaction volume on the chain has been for the past 30 days"
Help me prove that the data recorded on the blockchain is real.

When we release the proof task, we only need to tell Brevis three things:

- What do you want to prove?
- How quickly must the proof be returned (e.g., within 3 seconds)?
- How much are you willing to pay?

It can be simply understood as publishing an "outsourcing task" on the chain.

------------------------------------

Step 2: The TODA market will split based on the complexity of the tasks and match them to suitable validators.

Specifically, after the tasks are released in the TODA market of Brevis:

The system will automatically split into multiple small tasks (supported by Pico).

Multiple validators will provide quotes based on their hardware conditions and capabilities.

TODA will automatically select the best validators to complete the corresponding tasks without manual intervention.

------------------------------------

Step 3: The prover starts to perform the computation work and generate the sub-proof.

Each prover uses different hardware that can meet the task requirements to perform computational work and generate corresponding proofs.

Step 4: Let all sub-proofs automatically merge into a "master proof".
This step utilizes the recursive capability of Brevis Pico, where each published task ultimately has only one proof.

Step 5: Submit the proof to the chain for verification
This only requires a few milliseconds and a small amount of Gas to complete the verification, without the need to recalculate any complex logic, and the on-chain confirmation guarantees authenticity.

Step 6: Timely deliverers receive corresponding rewards, while defaulters will be punished.

It can be seen that Brevis has transformed "ZK proof" from a complex mathematical engineering into an automated production and settlement process with innovative technology and products.

The process of Brevis is very clear and intuitive, and it has been automated while eliminating the need to trust third parties, ensuring transparency and decentralization. No wonder it has gained collaboration from many top projects.

Continue to be optimistic about @brevis_zk, keep the interaction going, and wait for the next big move from the official side. #BrevisZK