DVC (Data Verification and Computation)

Introduction

DVC (Data Verification and Computation) mode is a workflow where:

1. one uses zkTLS to verify the correctness and authenticity of HTTPS requests and responses by proving the encrypted TLS transcript directly, without executing any business logic itself.
2. one uses zkVM to consume and compute the verified private data for business logic execution.

The advantages of the DVC pattern are clear: user data privacy is strongly protected, while the value or insights derived from the data can be extracted and consumed through an external zkVM program. This separation keeps the workflow clean, modular, and easy to maintain. Moreover, the output of the zkVM programm, a.k.a., a zkSNARK proof, can be publicly verified through zk verifier contract on-chain.

The Reference Implementation

Developers can refer to the reference implementation repository for a complete implementation guide.

Comparison with Native zkTLS Operations

The zkTLS Operations is another approah to process with private data, which also provide a certain type of computation in the zkTLS algorithm layer. However, The method of using zkTLS operations provides less public verifiability, since the output of a zkVM circuit, namely a SNARK proof, can be publicly verified on-chain.