> For the complete documentation index, see [llms.txt](https://docs.accountable.capital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.accountable.capital/accountable-documentation/data-verification-network-dvn.md). # Data Verification Network (DVN) ### Introduction Data Verification Network is a neutral infrastructure layer that enables institutions to share real-time financial reporting of assets and liabilities across wallets, exchanges, custodians and banks without revealing sensitive information like API keys, wallet addresses or trading strategies. Reports can be shared privately (peer-to-peer), semipublicly, or fully onchain through oracle feeds, with cryptographic proofs embedded by default. Data Verification Network is the trust foundation powering all Accountable products: Proof of Solvency, Accountable NAV, Accountable Ledger, Vault-as-a-Service and YieldApp. ### **Privacy-Preserving Data Verification** Accountable resolves the transparency-versus-privacy trade-off through confidential computing: * **On-premise processing:** Sensitive data stays inside your environment. API keys and wallet addresses are stored locally and never shared with Accountable; retrieved data is kept encrypted on infrastructure you own. * **Verifiable computation:** Data acquisition and report generation attach cryptographic proofs that source data is accurate and that the aggregation can be trusted without revealing the underlying data. * **Selective disclosure:** Choose exactly what to share and with whom, and prove it. Sharing works peer-to-peer, through permissioned access to derived reports, or via public dashboards. * **Trusted execution:** Optional secure enclaves for maximum assurance, with SGX, Nitro, SEV-SNP and TDX supported.
### Key Benefits * **Lower collateral requirements:** Demonstrate creditworthiness through live, verified data instead of static disclosures. * **Privacy without disclosure:** Prove financial health to counterparties without exposing positions, strategies or credentials. * **Verifiable trust:** Provide cryptographic proof of solvency and integrity that partners, lenders and auditors can independently check. ### How Data Verification Network Works Data Verification Network balances transparency and privacy through confidential computing and cryptographic proofs applied to both data acquisition and data transformation. Every participant runs a local node, self-hosted by the institution or operated by a trusted node operator, that can join peer-to-peer data sharing, forming a private network that is trustless and permissioned at the same time. The network supports both live, verifiable monitoring and snapshot exchanges. Verification runs end-to-end across three layers, each closing a distinct trust gap: * **Retrieval - Source authenticity:** zkTLS and secure enclaves establish a direct, attested connection to the primary source, answering "is this data actually from the claimed source?" without exposing credentials. * **Processing - Integrity and non-repudiation:** Source signatures are preserved, computation is timestamped and aggregation is deterministic, answering "was the data modified after retrieval?" * **Disclosure - Private verifiability:** Zero-knowledge proofs and selective disclosure let counterparties verify aggregations without any raw financial data being exposed.
### Core Components * **Data Verification Network (DVN):** The enterprise layer for privacy-preserving data reporting. It enables organizations to verify and share financial data in real time while maintaining complete control over privacy and ownership, with each participant running their own node for security and peer-to-peer sharing. * **Data Verification Platform (DVP):** A secure, on-premise backend that exposes the DVN through a private dApp. * **Secure on-premise backend:** Privately managed, securely configured and firewalled; accessible only to authorized users via wallets or email magic links. * **Private decentralized application (dApp):** A publicly accessible frontend that stores no user data on centralized or remote servers. It connects to a local node and never exfiltrates data; everything stays local. #### **Data Integration and Processing** * **Diverse data sources:** Interface with blockchains, centralized exchanges, custodians, banks, pricing sources, and more. * **Data verification:** Each asset and liability is retrieved through a process with an assigned verifiability level, reflecting source and process trust. * **Local storage:** Results are verifiable, cryptographically signed and stored securely on-prem. * **Data advertising:** Reports and proofs can be exchanged within the network, exposed via public or authenticated APIs, shown in public or gated dashboards, or published onchain. ### What Accountable Proves Accountable builds a complete picture of assets and liabilities, onchain and offchain, and ensures the data cannot be tampered with during acquisition, then builds verifiable aggregations that can be shared selectively and verified with cryptography. Accountable builds its verifiable reports by tracking: * **Assets:** Support onchain and offchain assets like fiat, spot, perpetuals, futures, options, DeFi protocols, stocks, treasuries and TradFi derivatives. Proving them means the node itself is part of the data retrieval: connections run inside the on-prem node over HTTPS with API keys, wallets for onchain assets, bank processes (SFTP, SWIFT MT, custom reconciliations) or signed document attestations. This guarantees data coming from the source itself, with immutability proofs attached to every value entering the calculation (see [Verifiability](#verifiability-trust-levels-and-data-integrity)). Reporting frequency is bound only by the sources themselves and their rate limits. Beyond balance proofs, the node can be customized to track any trading activity and attest that the entity running it is operating as intended. * **Accounts ownership:** Wallet ownership is proven via signatures. Venue accounts are verified by matching entity names through APIs where possible, relying on venue KYC, or using additional documentation. Where needed, third parties attest ownership, or test transfers can confirm control of the wallets. * **Attestations:** Accountable partners with audit firms that perform both full audits and light audits, making sure that all the connections are properly plugged in, accounts are verified, and any liabilities that cannot be tracked by technology alone are added manually. The ideal setup is a full audit once a year, periodic light audits confirming every account is properly connected to the node, and live provable attestations generated in real time. Self-reported PDFs, the current standard in the space, can continue and be matched against the live reporting. * **Liabilities**: Accountable can pull data from loan management systems, onchain lending protocols or other Accountable instances to build a picture of existing loans. The Data Verification Network can also reveal [hidden liabilities](https://accountable-capital.notion.site/Accountable-Unveiling-Liabilities-and-Hidden-Accounts-in-Crypto-Lending-9fbe9eab374e4c39819d1b369c544df9), checking in a zero-knowledge fashion that all liabilities known to its member nodes are properly reflected in the reports being exchanged. Together, these build a comprehensive picture of the financial health of entities running the node, allowing them to prove solvency, or that they operate as intended, peer-to-peer or to the outside world. ### Verifiability: Trust Levels and Data Integrity Verifiability is a spectrum, non-binary. Each data source is assigned a level based on its retrieval method, and that level becomes a risk dimension lenders can track. The goal is to raise verifiability gradually toward the highest achievable level of trust.
**Trust Level Hierarchy** 1. **Manual data entries:** Basic claims by the account holder. 2. **Documentation-enhanced data**: Attached documentation increases trust. 3. **API connectors:** Automated retrieval through [connectors](https://docs.accountable.capital/accountable-documentation/data-verification-network-dvn/connectors), maintained and verified by Accountable. 4. **Compute lineage**: API connectors running in verified containers with timestamped, signed, and hashed results. 5. **Trusted execution environments (TEEs):** Secure enclaves prevent code tampering, with SGX, Nitro, SEV and TDX supported. 6. **Zero-knowledge proofs:** Verifiable reporting with cryptographic guarantees. 7. **zkTLS**: Secure verification of HTTPS connections through [zkTLS](https://accountable-capital.notion.site/Accountable-zkTLS-and-beyond-9f3084ca7510445a8fc7366b41212ee1) providers. 8. **Signed APIs:** Inherit trust from the source using ZK proofs built on data hashes and signatures, making zkTLS or enclaves unnecessary. Signatures from source are also a solution to the technical part of the non-repudiation problem. Supports Accountable's own ZK-friendly method, RFC 9421 (HTTP Message Signatures) and the future ISO 22144 (C2PA Content Credentials). 9. **Consensus:** Where read-only API keys or wallet addresses can be shared, consensus across multiple Accountable instances run by different parties adds reliability. However, this is an optional step; Accountable is built to work as a trusted single-source oracle. 10. **Audits:** Auditors verify figures or attest that all connections are properly plugged in.

Cryptography methods used in DVN

### Reporting and Analytics Once data is verified, reporting and alerting can be configured to user preferences. * **Aggregated reporting:** Exposure, custodian breakdowns, stablecoin percentages, and more. * **Customizable reports:** Historical performance, cash flow analysis, and benchmark comparisons, from simple exposures to GARCH VaR models. * **Extensible measures:** Third-party metrics integrate through WebAssembly, R or Docker plugins. * **Real-time dashboard:** A daily performance and risk management view. * **Advanced alerting:** Proactive monitoring of verifiability levels, gross amounts and concentration risks, with customizable triggers for borrowers and lenders.
### **Controlled and Secure Data Sharing** * **Selective report sharing:** Share full reports or specific data proofs with a counterparty, or publish to public and semi-public dashboards with proofs attached. * **Multi-borrower reporting:** Multiple borrowers can report to one lender confidentially, with the lender viewing both individual and aggregated positions. * **Snapshot or live reporting:** One-time snapshots or continuous reporting at custom frequencies, down to minutes. * **Oracle publishing:** Reserves data can stream to third-party oracle providers or directly onchain for use in smart contracts. * **Robust security:** All data is encrypted at rest and in transit, with plain HTTP connections automatically upgraded with an additional AES layer. ### **Secure Third-Party Credit Ratings** (Optional) * **Strict data privacy**: By default, no positions data is shared with external parties. * **Selective replication**: Option for secure replication of aggregated measures and detailed reports. * **Advanced encryption**: Fully Homomorphic Encryption (FHE) using the CKKS encryption scheme preserves borrower data privacy while maintaining credit agency algorithm confidentiality
### Proof of Solvency Proof of Solvency gives institutions verifiable balance sheets, onchain and offchain. Instead of slow audits or one-off Proof of Reserves checks, it delivers a continuous, cryptographically verified view of both assets and liabilities across wallets, custodians, banks, and internal accounts, without ever exposing sensitive keys or data. Institutions can share live solvency attestations with regulators, counterparties, or users, backed by zero-knowledge proofs and auditor or fund admin collaboration when required. The result is a tamper-proof record of solvency that updates continuously and can be independently verified at any time. Built on the DVN, it produces comprehensive, verifiable solvency reporting: * **Proof of Reserves**: Merkle-Sum Trees built from positions data, with ZK proofs for Merkle inclusion * **Provable assets and liabilities**: A complete picture annotated with verifiability levels. * **Live reporting**: Automatic report generation and reconciliation. * **Liabilities unveiling**: Detects liability misrepresentation in zero-knowledge. * **Auditor integration**: Addresses the hidden-accounts problem through auditor verification.
### Venue Deploys While the primary use case is on-premise deployment, the DVN is built to embed at source venues once critical mass is reached. Borrowers generate authorization tokens specifying which aggregated reports to share, simplifying onboarding without security compromises and letting lenders verify that liabilities are properly reflected without revealing the details.
### **Integration with the Accountable Products** The Data Verification Network (DVN) serves as the foundation powering all Accountable products: * [Proof of Solvency](#proof-of-solvency) - Verifiable balance sheets, onchain and offchain * [Accountable Ledger](https://docs.accountable.capital/accountable-documentation/accountable-ledger) - A complete, audit-ready record for digital asset funds * [Accountable NAV](https://docs.accountable.capital/accountable-documentation/accountable-nav) - Net asset value backed by cryptographic proofs * [Vault-as-a-Service](https://docs.accountable.capital/accountable-documentation/vault-as-a-service) - Build financial products onchain, with proof at the core * [YieldApp](https://docs.accountable.capital/accountable-documentation/yieldapp) - A premium marketplace for yield you don’t have to guess on Across the network, the DVN already spans 100+ data sources, 20+ custodians and 125+ blockchains.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.accountable.capital/accountable-documentation/data-verification-network-dvn.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.