Deep Dive
1. Nox Testnet Launch (19 May 2026)
Overview: iExec launched "Nox" on the Arbitrum testnet, a new layer enabling encrypted smart contract execution. This lets developers build financial applications where sensitive logic runs privately, a requirement for many real-world assets (RWAs) and advanced DeFi.
The update provides three core features: encrypted execution, selective data disclosure, and on-demand auditability. This means applications can keep transactions and calculations private by default, while still allowing verified auditors to check the code when necessary. It's built specifically for systems that cannot operate with full public transparency.
What this means: This is bullish for RLC because it opens the project to entirely new, high-value markets like private credit and institutional finance. By solving a major technical hurdle, it could attract sophisticated builders and increase demand for RLC to pay for private computations.
(iExec RLC)
Overview: The team released the "iApp Generator," a developer tool that automates the complex setup for Confidential Computing. Instead of manually configuring Trusted Execution Environments (TEEs)—a process that could take weeks—developers can now generate a working, privacy-focused application with one terminal command.
The tool provides ready-to-use code templates in Python or JavaScript, handles compliance checks automatically, and ensures the generated app aligns with iExec's framework. It effectively turns advanced privacy technology into a simple, integrated development step.
What this means: This is bullish for RLC because it dramatically lowers the barrier for developers to build on iExec. Easier development leads to more applications being created, which in turn drives more usage of the network and demand for the RLC token to power those apps.
(iExec RLC)
3. Arbitrum Mainnet Integration (8 September 2025)
Overview: iExec completed a major deployment by bringing its privacy framework to the Arbitrum mainnet. This made iExec the first and only provider of TEE-based privacy tools for Arbitrum's ecosystem, which had over $3 billion in value at the time.
The integration allows any developer on Arbitrum to access iExec's privacy stack—including tools to mask sensitive data and run encrypted processes—without managing their own infrastructure. This rollout was the first phase of a planned multi-chain expansion to other EVM networks.
What this means: This is bullish for RLC because it places iExec's utility directly into one of the largest and most active DeFi ecosystems. Every private transaction or computation on Arbitrum that uses iExec's tools consumes RLC, creating a new, scalable demand stream for the token.
(Decrypt)
Conclusion
iExec's development trajectory is sharply focused on productizing privacy, transforming it from a complex niche into an accessible feature for mainstream Web3 developers. With new testnet capabilities for finance and streamlined tooling, is the project poised to become the default privacy layer for EVM applications?