Skip to main content
TermDefinition
VerityA data security infrastructure solution that enables developers to verify data authenticity, integrity, and transformation, creating verifiable data pipelines between traditional systems and blockchains.
Verity Prover OrchestratorThe process created by the Developer to orchestrate the data pipeline, using the Verity Client to interface with the Verity Prover.
Verity Prover ProxyA proxy node for generating MPC-TLS proofs.
Verity ClientA client interface used to interact with the Verity Prover and manage data pipeline orchestration.
Verity NotaryA node that verifies TLS proofs generated by the Prover, ensuring the integrity and authenticity of the data.
Verity NetworkA network of nodes, including Provers and Notaries, that collectively collaborate over a protocol to verify data authenticity, integrity, and transformation.
Verity CLIA command-line interface for operating Verity Network Nodes and verifying TLS proofs.
Verity Data Processor (VDP)A framework that provides libraries and tools to process multiple TLS attestations into a verifiable output via a zkVM, ensuring scalability and efficiency.
zkTLSA protocol that combines Zero-Knowledge (ZK) and Multi-Party Computation (MPC) cryptographic primitives to cryptographically prove data authenticity for TLS-enabled sources.
Data Flow Proofs (DFPs)Cryptographically verifiable proofs of data flow, ensuring that data is sourced and processed according to predefined logic. Used interchangeably with zkTLS proofs.
Verifiable Data Processing Environment (VDPE)An environment, such as a zkVM or a decentralised replicated compute platform, where data processing logic is executed and verified.
Oracle IntegrationsCollaborations with Decentralised Oracle Networks (DONs) and Data Delivery Networks (DDNs) to integrate zkTLS proofs into blockchain systems, simplifying the delivery of private data on-chain.
zkRollupA method of consolidating numerous TLS attestations into a single verifiable proof via ZK VDPE.
TLS ProofA cryptographic proof generated by the Verity Prover to verify the authenticity and integrity of data sourced from TLS-enabled endpoints. Used interchangeably with MPC-TLS proofs.
MPC-TLSAn implementation of TLS that uses Multi-Party Computation to ensure data authenticity and integrity.
VerifierThe coordination and verification layer of the Verity network, ensuring non-collusion and authorised notary selection.
Proof PrecomputationThe process of extracting and processing public elements from TLS proofs to optimise ZK computations and minimise proving times.
Proof Verification & ConversionThe process of verifying TLS proofs and facilitating conversions to cryptographic formats like tECDSA for reduced ZK computational load and wider compatibility with destination systems.
SourceA TLS-enabled HTTP endpoint, either third-party or first-party data owned by the Prover, from which data is sourced. May also be first-party data provided directly.
DestinationTypically a blockchain for trustless final verification, but may also include centralised systems for data analysis, trust management, and cybersecurity applications.
zkVMA virtual machine that uses Zero-Knowledge proofs to verify computations, ensuring data privacy and integrity.
Decentralised Oracle Networks (DONs)Networks that decentralise trust in data sourcing, enabling the delivery of real-world data to blockchains.
Data Delivery Networks (DDNs)Networks that facilitate the delivery of data feeds to multiple parties, often used in conjunction with Oracle technologies.
IC (Internet Computer)A decentralised and replicated compute platform that enables the processing of data in a verifiable manner. It uses Chain-key cryptography to facilitate secure and efficient computation, allowing for the integration of real-world data into blockchain systems.
Chain-key CryptographyA cryptographic primitive specific to the Internet Computer (IC) that combines several advanced cryptographic techniques, including MPC, TSS, and DKG, to produce portable cryptographic outputs.