iExec RLC

<h2 id="transparency-built-defi-now-it-s-the-ceiling-br-br">Transparency Built DeFi. Now It's the Ceiling. </h2>
DeFi was built on the principle that everything should be verifiable, by anyone, in real time. That property is what gave the system its credibility, its composability, and its first $172B in total value locked. It is also what is now keeping the next $100T off chain.
Public by default works for verification. It does not work for the workflows the next phase of on chain finance depends on. Tokenized funds cannot publish investor allocations to a block explorer. Treasury managers cannot broadcast every rebalancing decision to copy traders. OTC desks cannot expose counterparty amounts mid settlement. Regulated funds cannot operate under disclosure rules that force them to choose between full publicity and full opacity.
The path forward is not less transparency. It is better defined transparency. The shift is from "everything visible to everyone" to "auditable on demand by the right parties."
That is what auditable finance means. It is also what confidentiality as infrastructure delivers.
<h3 id="what-auditable-finance-actually-means-br-br">What Auditable Finance Actually Means </h3>
Three properties, defined precisely.
<ul>
 <li>Confidential by default. Sensitive financial data, investor allocations, position sizes, transaction amounts, strategy execution, is not readable to the public market. Encryption happens at the protocol layer, not as an opt in feature on top of a transparent base.</li>
 <li>Selective disclosure. Scoped, permissioned access is granted to the parties that need it: regulators, auditors, counterparties, internal compliance teams, specific smart contracts. Access is configurable in granularity, time bound where appropriate, and revocable. Disclosure is the answer to a specific question from a specific party, not a public broadcast.</li>
 <li>Auditability without forced transparency. Verification is still possible. Every confidential operation produces cryptographic evidence that the declared logic executed correctly on the committed inputs. The chain confirms the rules were followed without exposing the underlying data. Counterparties verify behavior without observing it.</li>
</ul>
This is the disclosure model regulated finance has always operated under. The architectural question is how to bring it on chain without breaking composability.
<h3 id="why-institutions-care-three-concrete-workflows-br-br">Why Institutions Care: Three Concrete Workflows </h3>
<ol>
 <li>Tokenized funds and RWAs. Investor allocations, subscription amounts, and redemption flows are confidential by mandate, not by preference. A regulated fund cannot tokenize on infrastructure that publishes its investor registry to a public ledger. With selective disclosure, the fund operates on chain while regulators retain scoped access to the data their oversight requires.</li>
 <li>OTC and settlement rails. Counterparty amounts, fill prices, and settlement flows leak information that moves markets. Today, $30B+ per month settles through OTC desks operating off chain through Telegram, not because the participants want it that way, but because public chains cannot offer confidentiality at execution. Confidential settlement keeps the auditability of onchain finality without broadcasting the trade.</li>
 <li>Treasury and strategy execution. Every rebalancing move, every position change, every allocation decision is a signal. Without confidentiality, strategy performance is taxed by copy traders, MEV extraction, and information leakage at execution. With confidential execution, the same strategy runs onchain without the leakage that degrades it.</li>
</ol>
In each case, the requirement is the same: confidentiality where the market shouldn't see, auditability where the regulator must.
<h3 id="what-this-is-not-a-privacy-coin-br-br">What This Is Not, A Privacy Coin </h3>
It's worth saying directly. Confidentiality as infrastructure is not anonymity tooling. It is not designed to obscure participants from oversight, evade regulation, or signal opacity as a value.
The closest analogy is TLS for the internet. TLS does not make the internet anonymous. It makes data exchange confidential between authorized parties while leaving the structure of the system fully observable. Auditable finance applies the same model to onchain capital: data confidentiality between authorized parties, structural transparency for the system, scoped disclosure for the parties that need it.
This is the architectural distinction that matters when institutional compliance teams evaluate confidential infrastructure. The framing is not "private from everyone." It is "controlled visibility."
<h3 id="multichain-matters-meet-liquidity-where-it-already-lives-br-br">Multichain Matters: Meet Liquidity Where It Already Lives </h3>
Builders do not migrate to a new chain for a single feature. The capital, the integrations, and the developer attention are already converging on a small set of EVM environments. Confidentiality has to land there, not behind a migration cost.
This is why multichain availability is a structural requirement, not a marketing line. The same confidentiality layer, deployed across the EVM environments builders already operate in, lets confidential workflows compose with the existing stack. Liquidity, tooling, custody, and user wallets do not change. The confidentiality is added.
iExec's Nox is now live on Ethereum and Arbitrum testnets. Same protocol, same primitives, same onchain ACL, available on both networks today.
<h3 id="a-reality-check-operational-risk-is-real-br-br">A Reality Check: Operational Risk Is Real </h3>
Confidentiality infrastructure operates in an environment where some assets, including the most widely used stablecoins, carry issuer level controls. Centralized asset issuers can enforce blacklists, freeze flows, or block specific addresses. These controls predate any confidential infrastructure and apply across the ecosystem regardless of how the underlying value moves.
What this means in practice: confidential infrastructure does not exempt integrations from issuer policy. A confidential token built on top of a centralized stablecoin still sits within the operational rules of that stablecoin.
This is why the framing matters. Confidentiality as infrastructure aligns with the operational realities of regulated finance, including issuer controls, regulatory access, and compliance enforcement. It is built to work inside the financial system, not around it. The value proposition is selective disclosure and auditability, not exemption from oversight.
This is the difference between privacy as token hype and confidentiality as infrastructure. Institutional teams evaluating the category understand the difference. The architecture has to reflect it.
<h3 id="what-builders-should-do-now-br-br">What Builders Should Do Now </h3>
The onramp is open.
Try it on Ethereum or Arbitrum testnet. Wrap an ERC-20 into its confidential ERC-7984 equivalent. Run a confidential transfer. Grant scoped read access through the onchain ACL. The full toolkit, the Solidity library, the TypeScript SDK, confidential smart contracts, ships with the testnet.
If you're building RWA, vault, settlement, or credit rails, the architecture is ready for serious technical conversations. The right time to evaluate confidentiality infrastructure is before the integration deadline, not after.
Start here: https://docs.iex.ec/

Confidentiality as Infrastructure

Table of Contents

iExec RLC

Other articles published on Jun 17, 2026

Join our free newsletter for daily crypto updates!