Verifiable Offchain Data
Proven Onchain
DIA ZK lets an issuer verify its reserves, balances, and NAV onchain, cryptographically bound to the source, without exposing the book. Curators, lending markets, and auditors check the proof instead of trusting a report.
The Problem
The backing is offchain
Stablecoin reserves, vault collateral, and fund NAV increasingly live offchain: at custodians, on exchanges, in loan books. The onchain token is a claim on performance the holder cannot see.
Reports, not proofs
Issuers show that backing through a dashboard they control, a monthly attestation, or a single verification provider. Each is a report about the offchain state, not a proof of it.
Single points of failure
When one provider's feed can be switched off, the proof becomes a dependency the whole market inherits. If it stops, the assets built on it freeze.
Regulation wants proof
MiCA already requires continuous reserve proof in the EU, and the US GENIUS Act takes effect in January 2027. A point-in-time attestation no longer meets a continuous obligation.
Three questions every integrator asks
Behind the demand for proof sit three separate questions. Most setups answer only the first. DIA ZK answers all three.
Did the value come from the source it claims?
Was it changed before it reached the chain?
Can the issuer prove the fact that matters without revealing the figure behind it?
From Source to Chain.
Verified at Every Step.
DIA sources data directly from the original venues rather than a third-party aggregator, and publishes how each feed is computed. DIA ZK adds a proof layer on top that works two ways: it proves origin and integrity, so a consumer contract can check a value came from the stated source unaltered, and it enables selective disclosure, proving a condition such as reserves exceed supply without revealing the figure. The proofs are verified onchain alongside each data point.
Sources
HTTPS APIsAuthenticated HTTPS APIs from custodians, fund admins, and data providers.
zkTLS Layer
Proof GenerationZK proofs generated during the TLS session, binding each response to its source.
Pods
Smart ContractsData points with proofs submitted to pod contracts for independent verification.
Aggregator
Smart ContractVerified inputs aggregated onchain into a single canonical value.
Delivery
Smart Contract FeedPublished to an onchain feed contract, readable by any protocol.
Consumer
Chains / dAppsProtocols query the feed for collateral checks, NAV pricing, and settlement.
Sources
HTTPS APIsAuthenticated HTTPS APIs from custodians, fund admins, and data providers.
zkTLS Layer
Proof GenerationZK proofs generated during the TLS session, binding each response to its source.
Pods
Smart ContractsData points with proofs submitted to pod contracts for independent verification.
Aggregator
Smart ContractVerified inputs aggregated onchain into a single canonical value.
Delivery
Smart Contract FeedPublished to an onchain feed contract, readable by any protocol.
Consumer
Chains / dAppsProtocols query the feed for collateral checks, NAV pricing, and settlement.
Built for Institutional DeFi
Stablecoins and synthetic dollars
Prove reserves cover supply, from custodian and issuer data, without publishing the exact holdings or where they sit.
Vaults and lending
Prove the offchain collateral behind a vault token and that its risk parameters hold, against authenticated values.
NAV reporting for tokenized funds
Pull NAV from the fund administrator's API with a proof tied to the source, and settle issuance and redemption at verified NAV.
Proof of reserves and balance checks
Query a custodian or prime-broker balance with a zkTLS session proving the figure came from the authenticated endpoint.
Bitcoin DeFi backing
Prove that a wrapped or synthetic Bitcoin product is fully backed, with source-authenticated reserve and threshold proofs.
Perps and derivatives inputs
Authenticated price and reference-index feeds, each bound to its source, for settlement, funding, and liquidation.
What Every zkTLS-Verified Feed Proves
Source Authenticity
The value came from the stated endpoint, not an intermediary relay or cache.
Data Integrity
The reported value was not altered between the source and the onchain contract.
Session Binding
The proof is tied to the specific TLS session, which prevents replay or substitution.
Selective Disclosure
Prove a condition such as reserves exceeding supply, without revealing the underlying figures.
DIA ZK, answered
DIA ZK is a proof layer for offchain data. It sits on top of DIA's oracle stack and lets a protocol verify that a reported value came from the stated source, was not altered on the way onchain, and meets a required condition, without exposing more of the underlying data than necessary. It works two ways: source authenticity and selective disclosure.
zkTLS proves that data was genuinely returned by a specific website or API over HTTPS, and that it was not changed before it reached the chain. A zero-knowledge proof is generated inside the encrypted session with the source and bound to the reported value, so a smart contract can check the data's origin and integrity without exposing the session.
Through selective disclosure. Instead of publishing an exact figure, DIA ZK generates a zero-knowledge proof that a condition holds, for example that reserves exceed supply or a collateral ratio clears its minimum. The proof is verifiable onchain by anyone, while the underlying value stays private. The market gets its answer and the issuer keeps its book.
A proof binds a value to its source. It does not make the source honest. If a source reports a figure it does not hold, the proof will faithfully carry a wrong number. What DIA ZK guarantees is that the value came from the stated source unaltered and is checkable onchain, which a controlled dashboard or a monthly PDF is not. For fully offchain reserves, trust in the source remains, and DIA is explicit about where that boundary sits.
DIA ZK does not replace the oracle stack, it strengthens it. DIA already sources data directly from the original venues rather than a third-party aggregator and publishes how each feed is computed. ZK adds cryptographic proofs of provenance and integrity, plus privacy through selective disclosure, on top of that foundation, delivered across 60+ chains on DIA's own onchain oracle layer.
DIA ZK is in early access. If your protocol holds stablecoin reserves, tokenized fund NAVs, vault collateral, or other offchain assets, talk to us about verified data delivery.
Integrate verified offchain data
If your protocol holds stablecoin reserves, tokenized fund NAVs, vault collateral, or offchain assets, talk to us about verified data delivery. DIA ZK is in early access.