iExec RLC

For the past three years, the industry has repeated the same forecast: institutional capital is coming on-chain. Some of it has arrived. Most of it has not.
$27 billion in tokenized assets are live on public blockchains today. The addressable market is over $100 trillion. The gap between those two numbers is not explained by demand, regulation, or blockchain readiness. It is explained by a structural problem that every institutional team runs into the moment they evaluate on-chain deployment: public blockchains expose everything by default, and institutions cannot operate that way.
Confidentiality has become the missing primitive. But confidentiality alone is not the full answer. For institutional finance to move on-chain at scale, two properties have to hold at the same time. Sensitive data must stay private. Execution must remain verifiable.
The Problem, Named Precisely
Public blockchains expose the entire operational surface of a financial workflow. Investor allocations are readable on any block explorer. Fund flows are timestamped and traceable. Vault positions and rebalancing decisions leak strategy in real time. Settlement flows broadcast counterparty amounts before the trade completes. 
<h2 id="for-institutional-workflows-this-is-a-disqualifying-condition-not-a-tradeoff-br-br">For institutional workflows, this is a disqualifying condition, not a tradeoff. </h2>
RWA issuers cannot tokenize a regulated fund on infrastructure that publishes its investor registry. Tokenized fund managers cannot meet mandate conditions that require position privacy. Professional DeFi allocators cannot deploy strategy on rails where every rebalance is a signal to copy-traders and MEV bots. Compliance teams cannot operate under disclosure frameworks that force them to choose between full opacity and full transparency.
None of these problems get solved by faster chains or cheaper gas. They only get solved by a confidentiality layer that integrates with existing on-chain infrastructure. 
<h2 id="confidentiality-alone-is-not-enough-br-br">Confidentiality Alone Is Not Enough </h2>
Here is the part of the conversation the industry has been slower to grasp. Confidentiality by itself does not meet the requirements of institutional finance.
Institutions do not just need private data. They need to prove to counterparties, auditors, and regulators that the private data was processed correctly, in the right environment, by the right code. A confidential system that cannot be verified is functionally the same as a black box. Institutions cannot deploy capital into a black box.
The requirement is not confidentiality. The requirement is verifiable confidentiality.
Sensitive data must stay protected from the market. The execution that processes that data must produce cryptographic evidence that it ran correctly, in an approved environment, on the declared inputs. Auditors and regulators must be able to receive scoped access when their mandate requires it. And the whole system must remain composable with the DeFi infrastructure that already exists.
This is the model regulated finance has always operated under. The engineering challenge is bringing it on-chain without breaking composability. 
<h2 id="how-nox-delivers-both-br-br">How Nox Delivers Both </h2>
Nox is iExec's confidentiality protocol for onchain finance. The programmable confidentiality layer makes onchain finance work the way real finance does. Confidential by default. Auditable on demand. The confidentiality side of the system encrypts what matters. Balances, transaction amounts, position sizes, and strategy execution data stay encrypted onchain. Sensitive data is never exposed to the public market. Access to encrypted values is controlled through an on-chain Access Control List, which lets the data owner grant scoped read access to specific addresses, regulators, or auditors, and revoke that access when it is no longer needed.
The verifiability side of the system is where Chain of Trust comes in. 
<h2 id="chain-of-trust-from-trust-us-to-verify-it-br-br">Chain of Trust: From Trust Us to Verify It </h2>
Chain of Trust is one of the core protocol qualities behind Nox. Its purpose is straightforward. Institutional trust cannot rest on promises, reputation, or internal policy. It has to rest on evidence.
Chain of Trust turns confidential execution into something you can prove, not something you have to accept on faith. It covers every critical layer of the execution path. The hardware layer is anchored by Intel TDX, which provides hardware-isolated confidential virtual machines and produces attestations confirming the physical environment your workload runs in. The execution platform produces cryptographic evidence that the correct environment was used and that the workload was not modified. The software running inside the Trust Domain is measured and verifiable. And each layer is independently attestable through Remote Attestation, a cryptographic proof mechanism that lets a user verify remotely that a task ran inside the expected environment, running the expected code, on approved hardware. <img src="https://academy-public.coinmarketcap.com/srd-optimized-uploads/d2fa020f99e5408d9bb7041fb3014899.jpg">
 The orchestration and deployment layer that makes this measurable is built on dstack, the open-source infrastructure developed by Phala Network for deploying verifiable confidential workloads on TDX hardware. Nox integrates dstack to boot and manage its confidential virtual machines from a measured, reproducible image, and to gate which workloads may run inside them. The result is that every confidential workload on Nox starts from a verifiable environment, before it is trusted with sensitive data. Phala provides the dstack infrastructure. Nox brings this verifiable execution model to confidential DeFi and RWA workflows. The practical outcome is that confidential execution stops being a claim. It becomes evidence. <img src="https://academy-public.coinmarketcap.com/srd-optimized-uploads/6afcf095e1d445d2ba774d3035a702a2.png">
For institutional counterparties, this is the difference between operational risk they can quantify and operational risk they cannot. A confidential system with verifiable execution can be audited, insured, and integrated into existing compliance workflows. A confidential system without verifiable execution cannot.
👉<a href="https://trust.noxprotocol.io/" rel="noopener noreferrer nofollow">https://trust.noxprotocol.io/</a> 
<h2 id="where-this-extends-q3-and-q4-direction-br-br">Where This Extends: Q3 and Q4 Direction </h2>
Chain of Trust is not a static feature. It is a system that iExec is continuing to build out, and two extensions are on the roadmap for the second half of the year.
The first is on-chain governance for protocol measurements. Today, the reference measurements that Remote Attestation checks against are managed through operational processes. Bringing these measurements on-chain means the approved set of hardware, execution platforms, and software artifacts becomes part of the protocol's verifiable state. Any change to what counts as a trusted configuration becomes an on-chain action that participants can inspect and verify. This makes the trust layer itself governable in the same way protocols already govern parameters, upgrades, and access control.
The second is source code binding. This extends the Chain of Trust one more link back, from the executed artifact to the source code it was compiled from. Institutional counterparties evaluating a confidential system today have to trust that the software running inside the Trust Domain corresponds to the source code that was audited. Source code binding closes that gap by producing verifiable evidence that the running artifact and the audited source are the same.
Both of these are upcoming milestones, framed as roadmap direction rather than shipped features. Their purpose is the same as the rest of Chain of Trust. Institutional finance requires evidence. The system should provide it at every layer, and the trust surface should get more complete over time, not less. 
<h2 id="what-this-means-for-institutional-deployment-br-br">What This Means for Institutional Deployment </h2>
The strongest single argument for why confidentiality has to be verifiable is a practical one. Every institutional counterparty who evaluates on-chain infrastructure eventually asks the same question. How do I know the system did what it said it did?
If the answer depends on trusting the operator, the deal does not happen. If the answer is a cryptographic proof that anyone can verify, the deal can happen.
Nox is being built so that the answer is always the second one. Encrypted balances. Confidential vault positions. Selective disclosure to regulators. Attested execution on approved hardware. All of it composable with the DeFi that already exists.
This is what institutional-grade on-chain finance actually requires. Not confidentiality alone. Verifiable confidentiality.
The market has spent three years learning that transparency-by-default is not compatible with institutional finance. The next three years are about learning that confidentiality-by-default is only half the answer.
Institutions need both properties at once. Sensitive data has to stay private. Execution has to remain verifiable. Public blockchains offered the second property in extreme form and none of the first. Confidential DeFi is now catching up on the first property. Verifiable confidentiality is where the two finally meet.
That is what Nox is being built to deliver. Confidential by default. Auditable on demand. Verifiable at every layer.
👉 <a href="https://trust.noxprotocol.io/" rel="noopener noreferrer nofollow">https://trust.noxprotocol.io/</a>
The market is not waiting for another chain. It is waiting for the confidentiality layer that makes finance work the way finance is supposed to work.
We are building it.

Why OnChain Finance Needs Verifiable Confidentiality

Table of Contents

iExec RLC

Other articles published on Jul 9, 2026

Join our free newsletter for daily crypto updates!