> ## Documentation Index
> Fetch the complete documentation index at: https://www.diadata.org/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# DIA ZK

> DIA ZK is a zero-knowledge assurance layer for verifying the source, integrity, and thresholds of DIA feeds, without revealing the underlying value.

DIA ZK is a zero-knowledge assurance layer for verifying the source, integrity, and thresholds of DIA feeds, without revealing the underlying value.

**Price any asset. Verify every feed. Prove only what matters.**

## Overview

DIA ZK is a zero-knowledge assurance layer built on top of DIA's oracle stack. Alongside a data feed, it lets consumers verify that the data came from the expected source, moved through the expected delivery path, and satisfies a required condition, without revealing more of the underlying value than necessary. Instead of trusting a final number, consumers can verify the statement behind it.

DIA ZK does not replace its [oracle stack](https://www.diadata.org/docs/dia-stack/architecture/core-components/overview) but it strengthens it by adding cryptographic proofs of authenticity, integrity, and privacy around the feeds DIA already delivers.

## Features

<CardGroup cols={2}>
  <Card title="Source Authenticity" icon="shield-check" iconType="solid">
    Proof that a data point came from the expected source and wasn't tampered with, verified with zkTLS.
  </Card>

  <Card title="Selective Disclosure" icon="eye-slash" iconType="solid">
    Prove a value meets a condition, e.g., `Reserve > $100M` , without revealing the value itself.
  </Card>
</CardGroup>

## How it works

DIA sources data directly from its origin and processes it with [transparent methodologies](https://www.diadata.org/docs/guides/methodologies-overview). DIA ZK adds a proof layer on top of that pipeline:

* **zkTLS** proves that a piece of data was genuinely returned by a source over HTTPS, without exposing all of the underlying response.
* **Threshold proofs** verify that a value meets a condition while keeping the value private: the threshold is a public input, the actual value stays a private input.
* Proofs can be **verified on-chain or off-chain**, so both smart contracts and off-chain systems can check them.

The result is a feed a protocol can act on, together with a proof of where it came from and what it satisfies.

## Use cases

<CardGroup cols={2}>
  <Card title="Stablecoins" icon="coins" iconType="solid">
    Prove reserve sufficiency, validate collateral values, and verify issuer or custodian data while limiting unnecessary disclosure.
  </Card>

  <Card title="Vaults & Lending" icon="vault" iconType="solid">
    Use authenticated values and private threshold proofs to verify collateral safety, liquidation readiness, and risk parameters.
  </Card>

  <Card title="Tokenized RWAs" icon="building-columns" iconType="solid">
    Verify off-chain market data, NAV inputs, proof-of-backing, and asset administrator data.
  </Card>

  <Card title="Bitcoin DeFi" icon="bitcoin" iconType="brands">
    Prove backing of wrapped  Bitcoin products, using source authenticity and reserve threshold proofs.
  </Card>
</CardGroup>

## Get started

Bring verifiable, privacy-preserving data to your protocol. Reach out to get started.

<Card title="Contact us" icon="telegram" iconType="brands" horizontal href="https://t.me/DIAOracles_Support_Bot" />