Tree News

Orochi Network · 2026-11-19 09:26 UTC

ON #8: Privacy Built for Institutions Going On-Chain The problem, and how the market is solving it today Privacy is one of the main barriers to bringing institutional finance on-chain, because funds and banks will not move trading, lending and settlement to a public blockchain where their balances, positions and counterparties are visible to everyone. To solve this, the market already offers several privacy solutions. Some networks, such as Canton Network, keep data inside a closed group of members and give a regulator access only to the contracts it needs to see. Newer privacy chains, such as Midnight and Aztec, let users keep their data on their own side and send only a Zero-Knowledge Proof (ZKP) to the chain, so a contract can check a fact without seeing the data. There are also encrypted computation, which lets a system work on data it cannot read, and hardware enclaves, which process data inside a sealed part of the chip that the host cannot see. Each of these solutions keeps data private, but most of the data an institution has to stand behind, such as reserves, fund accounting, collateral and KYC registers, sits in its own systems and changes every day. The lenders, auditors and regulators who rely on that data need to confirm specific facts about it, such as whether the collateral still covers a loan, whether a client has passed KYC, or whether the reserves still back the tokens in circulation, and today they usually have to receive the data itself, or wait for the next report, to do that. How today's privacy approaches handle it The main approaches on the market today each hide different data, prove different things and rely on a different party or assumption. Permissioned networks. Data is shown only to the parties that need it, and an outside checker can compare data it receives with a hash on the shared ledger, so checking still means receiving the data. Privacy chains with client-side proofs. A contract checks a fact without seeing the data, but the proof is about state on that network, so contracts on other chains need a bridge to use it. Shielded pools and private transfers. ZKPs prove that each private transfer is valid, but they say nothing about data that lives outside the pool. Confidential rollups and private smart contracts. Logic runs on private state, protected by validity proofs in some designs and by enclaves in others, but data that lives off-chain, such as bank statements, custody positions and fund accounting, still has to enter the system from somewhere. Encrypted computation. Fully Homomorphic Encryption (FHE) and Multi-Party Computation (MPC) let parties compute on data without seeing it, and hardware enclaves process it inside sealed hardware, but an outside party who wants to rely on the result needs an added proof, or has to trust the committee or the hardware that ran it. Encrypted databases and searchable encryption. Stored data stays encrypted while the server still answers queries. Classic schemes assume an honest-but-curious server, and catching a server that drops or alters results needs a verifiable variant built on authenticated data structures. A proof that a private transaction is valid does not, by itself, show how a collateral figure in an off-chain report was computed, or which version of the data it came from. Closing that gap is the idea behind Verifiable Data: data that comes with a proof others can check without seeing the data. How zkDatabase onboards institutions on-chain zkDatabase is a verifiable database powered by Zero-Knowledge Proofs, developed by Orochi Network. An institution stores sensitive data such as reserves, collateral or a KYC register in zkDatabase, the data stays off-chain, and every insert, update and query produces a Zero-Knowledge Proof that it was done correctly. This solves two problems that keep institutions from moving on-chain: Proving a fact without exposing the data. A lending protocol checks from a proof that a client is on the KYC-cleared list, or that a collateral entry exists in the committed data, so the institution never puts its positions or client data on a public chain. Checks between reports. Each update comes with its own proof, so auditors can follow how the data changed between two reporting dates instead of waiting for the next report. With these proofs, an institution can bring trading, lending and settlement on-chain while its balances, positions and counterparties stay private, and the parties that need to check its data do so from a proof instead of a copy of the data. For teams building tokenized assets, KYC systems or stablecoin reserves, zkDatabase is designed to be the data layer that lets privacy and on-chain verification work together.

Loading the story on Tree News…