iExec RLC

On July 2, 2026, iExec will shut down the RLC bridge between Ethereum and the Bellecour sidechain. This is more than a technical deprecation. It is the formal closing of a chapter in iExec's history, and the opening of the one that follows.
Bellecour: Where iExec Made History
Bellecour was built with ambition. It was iExec's purpose-built sidechain, fast, low cost, and designed to power decentralized compute at scale. For years, it was the backbone of iExec's marketplace, the chain on which thousands of tasks were computed, on which iApps were deployed, and on which iExec's vision of a decentralized cloud took its first real shape.
We are proud of what was built there. Bellecour represented a bet that if iExec built the right infrastructure, builders would come. And many did.
But the landscape of Web3 evolved. Liquidity, developer activity, and institutional attention consolidated on a smaller set of EVM networks. The cost of asking projects and institutions to come to Bellecour, rather than meeting them where they already operate, became a friction point that limited the protocol's reach. The ecosystem signaled where it wanted iExec to be. iExec listened.
That is what good infrastructure decisions require: acknowledging what is no longer the right path, learning from it, and adapting.
What Comes Next
The Bellecour sunset is the first step in a broader renewal of iExec's technical stack, and that renewal is already underway.
iExec is now live on Arbitrum, one of Ethereum's most developer-active L2 ecosystems, bringing iExec's confidential computing capabilities to the environment where builders already operate. The Nox protocol, iExec's confidentiality layer for on-chain finance, is now live on Arbitrum and Ethereum testnets. Mainnet deployments across multiple EVM networks are next. iExec is positioning itself to be the confidential computing layer of the multichain ecosystem, not a destination network builders have to migrate to.
The iApp migration is already complete. iExec tooling has fully moved on. The bridge shutdown is the final symbolic closure of the Bellecour era.
What This Means for RLC Holders
No RLC will be lost in this transition.
If you hold RLC on Bellecour today: You have until June 30, 2026 to bridge your tokens back to Ethereum yourself, using the official bridge at bridge-bellecour.iex.ec.
If you still hold RLC on Bellecour after the bridge shuts down on July 2: No action is required. Any wallet holding at least 0.1 RLC on Bellecour at the time of shutdown will be automatically credited the equivalent amount on Ethereum. The process may take a few business days to complete after July 2.
The majority of funds have already been withdrawn. The automatic credit mechanism is a safety net to ensure no holder is left behind.
Timeline
Now: Ethereum → Bellecour transfers are already disabled.June 30, 2026: Last day to self-bridge RLC from Bellecour to Ethereum.July 2, 2026: Bridge officially shuts down.July 2 onwards: Automatic Ethereum credit for remaining Bellecour balances (≥ 0.1 RLC) within a few business days.Following weeks: Bellecour chain fully sunset; protectedData on Bellecour archived.
Thank You, Bellecour
To everyone who built on Bellecour, deployed iApps, ran workers, and helped shape what decentralized computing could look like: thank you. Bellecour is where iExec grew up. What comes next is built on everything we learned there.
The best chapters of iExec's story are still being written.
$RLC

The New Standard for Privacy in Managed Asset Vaults
The world of Decentralized Finance (DeFi) has traditionally operated on a principle of absolute transparency. While this openness is a core pillar of blockchain, it also creates a major hurdle for professional investors and fund managers who require privacy to operate effectively.
In DeFi, a vault is a smart contract that manages assets for multiple users. Passive vaults function like simple savings accounts, where assets are deposited and yield is generated automatically. Active strategy vaults are different. They rely on professional managers to make decisions, allocate capital, rebalance portfolios, and execute strategies.
For managed asset vaults, full transparency becomes a real problem. Every rebalancing move, every allocation decision, every large position, and every execution strategy can be read in real time. Competitors can copy the strategy. Bots can front-run execution. Large investors can have their position sizes exposed to the market.
This is not just a privacy issue. It is a performance issue. When every movement is publicly readable, the alpha of a strategy, the unique insight that creates value, can be copied the moment it is executed. For institutional players, this becomes a structural barrier to entry. Institutional capital stays out because full public exposure does not fit how Institutional Finance operates.
Current DeFi structures often force users to choose between the transparency and security of blockchain, and the privacy standards of TradFi. This lack of a middle ground has limited the growth of the managed vault market. For DeFi to truly scale and attract institutional liquidity, privacy needs to become part of the infrastructure itself.
iExec is changing that with Confidential Vault, a new use case bringing programmable confidentiality to on-chain vaults. 

Confidential Vault creates a better model: keep public what builds trust, and protect what drives strategy. Balances and LP positions can be encrypted at the protocol level, while vault operators can grant selective access to the right parties when needed. Vault activity stays verifiable. Sensitive strategy intelligence does not become public by default.
DeFi cannot become a mature financial market if every valuable strategy is forced into public view. 
To solve this, a confidential DeFi protocol adds a layer of privacy to smart contracts. It uses hardware secured environments, specifically Intel TDX, to run financial calculations on encrypted data. This ensures that while the inputs remain private, the results stay verifiable on the blockchain. The Confidential Vault uses this technology to encrypt balances and positions at the protocol level. It separates what needs to remain public to maintain trust from the specific execution strategies that must stay hidden.
To achieve this level of privacy, the system is based on the ERC-7984 standard, a confidential token wrapper, utilizing a wrap and unwrap process. Liquidity providers wrap their tokens into confidential versions (cTokens) to enter the vault and unwrap them upon withdrawal. This mechanism ensures that while the assets are within the vault's strategy, the specific details of how they are being moved and managed remain fully encrypted. By using production-grade infrastructure, Nox ensures that the strategy execution is not only private but also cryptographically proven and accurate without requiring developers to be experts in complex cryptography.
This gives vault creators, liquidity providers, and auditors a more professional framework:
Vault creators can define the vault, set parameters, and decide who can access what.Liquidity providers can deposit with encrypted positions instead of exposing their full position to the market.Auditors and regulators can receive scoped access to the information they need, without making the full vault activity public.
Confidential Vault
Selective Disclosure and Institutional Compliance
One of the most significant features of the Confidential Vault is selective disclosure. In a fully private system, data is often locked away from everyone, which makes auditing and regulation impossible. With the Confidential Vault, the vault operator can grant specific read access to authorized parties. This means a fund manager can keep their strategy hidden from the general market while giving a regulator or auditor full, scoped access to the data they require for oversight.
This architecture introduces three distinct roles that satisfy both market and legal needs. The Vault Creator sets the parameters; the Liquidity Provider enjoys an encrypted position visible only to themselves; and the Auditor receives the specific access required for compliance. This approach removes the final hurdle for Real-World Asset (RWA) issuers who are legally required to report to authorities but must also keep their market moves private to stay competitive.
Confidential Vault shows where DeFi is heading: privacy where it matters, transparency where the market needs it. 
The lack of confidentiality has long been the missing piece in the evolution of onchain finance. By launching the Confidential Vault on Nox, we are providing the foundational infrastructure needed to move toward a more mature, professional financial ecosystem. By encrypting positions and enabling selective disclosure, we are allowing managers to protect their strategies and institutions to trade securely. This technology has unlocked the primitive for confidential strategy execution, bridging the gap between the efficiency of Web3 and the privacy requirements of global finance.
As the managed vault market continues to grow, the protocols that prioritize privacy will become the standard infrastructure for the next generation of finance. The Confidential Vault ensures that trust is maintained through confidential computing and hardware, rather than through total exposure. We are inviting builders and fund managers to join a more secure, sovereign future for Confidential DeFi where strategy remains private and results remain verifiable.
With Confidential Vault, iExec is turning privacy from a limitation into core infrastructure for the next DeFi market. 
Ready to Protect Your Execution Strategy?
Don’t let transparency limit your performance. Whether you are an institutional allocator or a vault builder, the future of DeFi is confidential.
➡️ Explore the documentation: https://docs.iex.ec/nox-protocol/getting-started/welcome
➡️ Try Confidential Vaults on Arbitrum testnet: https://cvault.demo.noxprotocol.io

On July 2, 2026, iExec will shut down the RLC bridge between Ethereum and the Bellecour sidechain. This is more than a technical deprecation. It is the formal closing of a chapter in iExec's history, and the opening of the one that follows.
Bellecour: Where iExec Made History
Bellecour was built with ambition. It was iExec's purpose-built sidechain, fast, low cost, and designed to power decentralized compute at scale. For years, it was the backbone of iExec's marketplace, the chain on which thousands of tasks were computed, on which iApps were deployed, and on which iExec's vision of a decentralized cloud took its first real shape.
We are proud of what was built there. Bellecour represented a bet that if iExec built the right infrastructure, builders would come. And many did.
But the landscape of Web3 evolved. Liquidity, developer activity, and institutional attention consolidated on a smaller set of EVM networks. The cost of asking projects and institutions to come to Bellecour, rather than meeting them where they already operate, became a friction point that limited the protocol's reach. The ecosystem signaled where it wanted iExec to be. iExec listened.
That is what good infrastructure decisions require: acknowledging what is no longer the right path, learning from it, and adapting.
What Comes Next
The Bellecour sunset is the first step in a broader renewal of iExec's technical stack, and that renewal is already underway.
iExec is now live on Arbitrum, one of Ethereum's most developer-active L2 ecosystems, bringing iExec's confidential computing capabilities to the environment where builders already operate. The Nox protocol, iExec's confidentiality layer for on-chain finance, is now live on Arbitrum and Ethereum testnets. Mainnet deployments across multiple EVM networks are next. iExec is positioning itself to be the confidential computing layer of the multichain ecosystem, not a destination network builders have to migrate to.
The iApp migration is already complete. iExec tooling has fully moved on. The bridge shutdown is the final symbolic closure of the Bellecour era.
What This Means for RLC Holders
No RLC will be lost in this transition.
If you hold RLC on Bellecour today: You have until June 30, 2026 to bridge your tokens back to Ethereum yourself, using the official bridge at bridge-bellecour.iex.ec.
If you still hold RLC on Bellecour after the bridge shuts down on July 2: No action is required. Any wallet holding at least 0.1 RLC on Bellecour at the time of shutdown will be automatically credited the equivalent amount on Ethereum. The process may take a few business days to complete after July 2.
The majority of funds have already been withdrawn. The automatic credit mechanism is a safety net to ensure no holder is left behind.
Timeline
Now: Ethereum → Bellecour transfers are already disabled.June 30, 2026: Last day to self-bridge RLC from Bellecour to Ethereum.July 2, 2026: Bridge officially shuts down.July 2 onwards: Automatic Ethereum credit for remaining Bellecour balances (≥ 0.1 RLC) within a few business days.Following weeks: Bellecour chain fully sunset; protectedData on Bellecour archived.
Thank You, Bellecour
To everyone who built on Bellecour, deployed iApps, ran workers, and helped shape what decentralized computing could look like: thank you. Bellecour is where iExec grew up. What comes next is built on everything we learned there.
The best chapters of iExec's story are still being written.
$RLC

Transparency Built DeFi. Now It's the Ceiling.
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.
What Auditable Finance Actually Means
Three properties, defined precisely.
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.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.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.
This is the disclosure model regulated finance has always operated under. The architectural question is how to bring it on chain without breaking composability.
Why Institutions Care: Three Concrete Workflows
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.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.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.
In each case, the requirement is the same: confidentiality where the market shouldn't see, auditability where the regulator must.
What This Is Not, A Privacy Coin
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."
Multichain Matters: Meet Liquidity Where It Already Lives
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.
A Reality Check: Operational Risk Is Real
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.
What Builders Should Do Now
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/ 

Nox is now live on Ethereum testnet.

Programmable Privacy coming to the home of EVM.

RWA issuers & DeFi builders can now integrate confidentiality at an institutional level.

➡️ Start here: docs.iex.ec

$RLC