Investing In iExec RLC (RLC) – Everything You Need to Know

iExec is a confidential-computing protocol that lets applications process private data and sensitive logic outside a public blockchain while using onchain rules for permissions, payments, and verification. Its RLC (RLC ) token is a fixed-supply Ethereum (ETH ) asset used to pay for or coordinate services within the ecosystem.

The project began as a decentralized cloud marketplace, but its current strategy is more focused: privacy for onchain finance, artificial intelligence, data, and communications through trusted execution environments (TEEs). In 2026, iExec introduced Nox as a multichain confidentiality protocol and retired its Bellecour sidechain. Investors should distinguish the products already in production from Nox deployments that remain on testnets.

What Is iExec?

iExec was founded in France by Gilles Fedak and Haiwu He and launched RLC in 2017. The original design created a marketplace where applications could purchase offchain compute, data, and software services. Resource providers executed jobs and received payment under a blockchain-coordinated protocol.

That foundation still matters, but describing iExec merely as an alternative to Amazon Web Services is outdated. The protocol now concentrates on confidential execution: protecting data while it is being processed, not only while it is stored or transmitted. This can support private AI inference, sealed-bid auctions, protected identity data, confidential messages, and financial workflows that cannot safely publish every balance or strategy.

iExec is infrastructure rather than a general-purpose blockchain. Developers integrate its tools into applications on networks such as Ethereum and Arbitrum (ARB ), while offchain workers execute approved workloads.

How Trusted Execution Environments Work

A TEE is a hardware-isolated area designed to keep code and data hidden from the operating system, cloud administrator, and other processes on the machine. Remote attestation produces cryptographic evidence about the hardware, software measurement, and environment running a workload.

iExec uses TEEs so a worker can process private inputs without revealing them to the node operator. A user or application encrypts data for an approved enclave, the enclave executes the program, and only authorized outputs are released. Smart contracts coordinate permissions, task orders, payments, and results.

This differs from zero-knowledge proofs or fully homomorphic encryption. A TEE can run conventional software efficiently and support complex workloads, but its security depends on hardware vendors, firmware, attestation services, configuration, and the absence of side-channel or implementation flaws. Confidential computing reduces trust in the operator; it does not eliminate trust entirely.

PoCo: Proof of Contribution

iExec’s Proof of Contribution, or PoCo, protocol matches requesters with worker pools and coordinates execution. An order defines an application, dataset, worker pool, price, security requirements, and other conditions. When compatible orders match, workers run the task and submit evidence or results.

PoCo can require workers to lock RLC as a security deposit. Correct participation earns payment; invalid or missing contributions can lose stake. Replication and consensus among several workers can be used for ordinary workloads, while TEE attestation can support confidential workloads that cannot be replicated publicly.

This is not a base-layer proof-of-stake consensus mechanism. RLC staking helps secure marketplace jobs rather than producing Ethereum blocks.

Protected Data and Privacy Tools

iExec’s DataProtector tools let an owner encrypt a dataset, register its ownership and permissions, and authorize specific applications to use it inside a TEE. The receiving application can calculate on the data without receiving the raw plaintext.

Web3Mail and Web3Telegram apply the same principle to communications. A project can message a wallet holder without learning the person’s email address or Telegram identifier in clear text. The holder controls permissions and can revoke access.

These tools create useful privacy primitives for decentralized applications, but they still rely on user consent, accurate application code, secure enclave images, and correct key management. Privacy guarantees apply to the protected workflow, not automatically to linked blockchain transfers, browser behavior, or metadata outside the enclave.

Nox and Confidential Onchain Finance

Nox is iExec’s new confidentiality layer for onchain finance. It is designed to let existing EVM applications add encrypted balances, transfer amounts, positions, and strategy data while allowing selective disclosure to an auditor, administrator, or approved counterparty.

The architecture uses confidential virtual machines based on Intel TDX and a measured software stack. Its chain-of-trust system lets an external verifier inspect a signed hardware quote, boot measurements, runtime measurements, and the deployed application configuration. An onchain access-control list determines which addresses can decrypt specific information.

Demonstrations include confidential ERC-20 wrappers, private managed vaults, payroll, and auctions. The token design wraps an existing asset, uses a confidential representation, permits controlled disclosure, and later unwraps it. That can preserve compatibility with established DeFi liquidity instead of forcing assets onto a separate privacy chain.

As of September 2026, iExec described Nox as live on Ethereum and Arbitrum testnets, with multichain mainnet deployments next. The attestation portal and code show meaningful technical progress, but testnet demonstrations are not evidence of production deposits, fee revenue, or institutional adoption.

Bellecour Sunset and the Multichain Shift

Bellecour was iExec’s purpose-built sidechain for marketplace tasks and iApps. The project concluded that asking users and developers to move to a separate network limited adoption, so applications and tooling migrated toward established EVM ecosystems.

The Bellecour-to-Ethereum RLC bridge closed on July 2, 2026. Holders had until June 30 to bridge manually; accounts with at least 0.1 RLC remaining were scheduled to receive an automatic Ethereum credit. Bellecour and its protected-data records were then sunset or archived.

RLC buyers should now treat Ethereum as the primary token network unless an exchange explicitly supports another current deployment. Legacy Bellecour tokens or instructions should not be used. As with any migration, investors should verify balances, contract addresses, and official notices rather than trusting unsolicited recovery messages.

What Is RLC?

RLC means “Run on Lots of Computers.” It is an ERC-20 utility token with a fixed supply of approximately 87 million and no protocol inflation or future unlock schedule. The token was distributed through the 2017 sale and ecosystem allocations.

Its roles include:

• Service payment: requesters can pay for compute, applications, and data.
• Worker security: PoCo participants can stake RLC against correct job execution.
• Developer access: vouchers provide preloaded RLC and predictable usage budgets.
• Incentives: grants, builder rewards, privacy programs, and liquidity campaigns distribute existing RLC.
• Planned Nox value capture: iExec has proposed using a share of confidential-protocol revenue for market purchases of RLC.

Fixed supply prevents inflation, but it does not guarantee scarcity-driven appreciation. Ecosystem reserves and incentive programs can increase circulating supply, while service users may be abstracted from direct token handling. The planned Nox buyback model should be treated as roadmap until parameters, contracts, launch dates, and executed purchases are verifiable.

Why Investors Consider RLC

• Long operating history: iExec has built confidential-computing infrastructure since 2017.
• Specialized privacy: TEEs can execute complex existing software more directly than some cryptographic alternatives.
• Verifiable execution: Nox exposes boot and runtime attestation rather than asking users to accept a generic hardware claim.
• Multichain design: the project is meeting applications on established EVM networks after retiring Bellecour.
• Fixed token supply: RLC has no protocol inflation.
• Working developer tools: protected data, private messaging, worker pools, and SDKs predate the current institutional-finance narrative.

Risks of Investing in RLC

• Mainnet execution: Nox’s most important financial products remained on testnets in September 2026.
• Hardware trust: Intel TDX, firmware, microcode, attestation roots, and side-channel defenses are critical dependencies.
• Operator and key risk: secure hardware cannot compensate for compromised application code, access lists, keys, or deployment processes.
• Product pivot: Bellecour and the original destination marketplace were retired after failing to achieve sufficient adoption.
• Competition: zero-knowledge systems, FHE networks, MPC protocols, cloud confidential computing, and other TEE projects target similar demand.
• Token abstraction: institutions may pay in fiat or stablecoins while middleware handles RLC, weakening direct user demand.
• Incentive quality: grants, vouchers, and rewards can create activity that is not recurring customer usage.
• Regulatory exposure: confidential finance must balance privacy with sanctions, disclosure, data protection, and financial-market obligations.
• Liquidity: a fixed supply does not prevent price volatility or shallow markets.

What Investors Should Monitor

Track Nox mainnet launches, independent audits, live confidential value, paid tasks, repeat applications, worker-pool diversity, TDX operator concentration, attestation availability, latency, failure rates, and fees. Separate testnet demonstrations and grant recipients from production customers.

For RLC, monitor service spending, worker stake, voucher usage, reserve balances, incentive distributions, decentralized-exchange liquidity, Bellecour credit completion, and any onchain buyback program. Confirm whether revenue is actually converted into RLC rather than relying on intended tokenomics.

How to Buy iExec RLC (RLC)

RLC is available on the following exchanges:

Coinbase – A publicly traded exchange listed on the NASDAQ. Coinbase accepts residents from 100+ countries, including Australia, Canada, France, Germany, Netherlands, Singapore, the United Kingdom, and the United States (excluding Hawaii).

Kraken – Founded in 2011, Kraken offers trading access in many supported jurisdictions, subject to local availability.

Kraken Disclaimer: Not investment advice. Crypto trading involves risk of loss. Payward European Solutions Limited t/a Kraken is authorised by the Central Bank of Ireland.

KuCoin – This exchange offers access to a broad selection of crypto assets. Restrictions may apply depending on location.

Final Thoughts

iExec should now be evaluated as confidential-computing infrastructure rather than a generic decentralized cloud. Protected Data, PoCo, and private messaging provide a working base, while Nox extends that expertise toward auditable financial privacy on established chains.

The 2026 Bellecour shutdown demonstrates a willingness to abandon infrastructure that did not fit the market, but it also shows execution risk. RLC’s strongest case requires Nox to reach production, attract recurring paid workloads, and implement transparent value capture. Until then, mainnet usage matters more than the size of the institutional privacy opportunity.