​
Primary Implementation

Verity is designed for compatibility with any blockchain. The general-purpose Verifier within the protocol ensures this, however, the choice between VDPEs is left to the Developer to determine how best to adopt and implement data pipelines that serve the best outcomes for their use case. Verity Primary Implementation Architecture

​
Off Destination

The “Off Destination” implementation is the most common use case for Verity. It involves abstracting as much data processing and orchestration of the verifiable data pipeline off of the destination blockchain as possible. This is ideal for destination blockchains that:
  1. Are expensive to compute on, such as Ethereum.
  2. Are restricted with respect to their transaction size limits, making them limited with respect to the amount of data they can process.
  3. Involve Smart Contract programming in languages that are not suited for data processing requirements, such as Solidity.

​
On Destination

The “On Destination” implementation is a secondary approach for implementing Verity. Here, the Verity Verifier is utilised specifically to ensure cryptographic compatibility with the destination blockchain. However, all subsequent data processing is performed on the destination blockchain. Some Move-based Blockchains such as Rooch Network have proven to be capable of parsing and processing JSON data, for example.

​
Tailored Alternative Implementations

​
Sovereign Blockchain Extension

Verity’s Verifier serves as the coordination and verification layer of the network. While the Verifier will be deployed for general-purpose use, Verity is designed to empower sovereign blockchains with enhanced capabilities for verifying real-world data. Verifier Sidecars are created to extend blockchain nodes, effectively embedding their role into the base layer of a blockchain. Verity MPC TLS Proof Engine for Sovereign Blockchains The first compatible decentralised networks will be based on CometBFT, such as Kwil. However, Usher Labs is prepared to collaborate with any blockchain team to enable this functionality as a first-class feature.

​
Transparency and Observability for Data Analysis

Cryptographically enforcing verification of real-world data directly within Blockchain Nodes and Smart Contracts may introduce additional considerations, such as upgrade requirements, migrations, and operator coordination. To alleviate these risks while adopting the value of transparent data, Verity can be leveraged preliminarily for the purpose of data & trust analysis. The network roles are maintained; however, instead of pushing transparency proofs to a trustless environment for verification, this metadata is forwarded to a centralised aggregator. Here, it is verified and used to analyse how data impacts the blockchain and where trust is established and maintained. This approach offers significant insights to blockchain developers, auditors, and communities, revealing the true source of data powering various protocols. It helps determine whether there is a need for diversification of data sources or if there are synergies with particular data providers that were previously unknown to the core team. Beyond analysing data and trust flow, this same pipeline enables observability over network operator health, uptime, and more. It indicates whether new updates pose risks to operators or if there are code-level optimisations that can be applied.