Skip to main content

iExec

iExec RLC (RLC) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

iExec — an AI/Compute | Infra platform and a set of developer tools for confidential computing (TEE) and a “privacy stack” (data protection, confidential iApps, use‑case demos). Token: RLC (ERC‑20 on Ethereum).

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: infrastructure and tools for running applications/computations over data in confidential environments (TEE) while keeping a verifiable execution “trace” on the blockchain.
  • Who it’s for: developers and teams building privacy‑preserving applications (including AI pipelines/agents) who want a reproducible dev workflow.
  • Why onchain/token: the blockchain is used for verifiability/tracing of execution and interactions; the RLC token is the ecosystem’s onchain asset (payment/utility in iExec tools; details depend on the specific flow).
  • What you can actually touch (Tier‑1): a use‑case showcase with a live demo (Web3 Messaging) and example repositories (AI agent / image generation PoC), plus a “Hello World” tutorial and the iApp Generator CLI (create/test/deploy an iApp).

How it works (very briefly)

  1. The user/developer does: creates an iApp (via iApp Generator) and prepares input data (including ProtectedData via DataProtector).
  2. The system does: runs the computation offchain in a TEE (per the iExec docs), recording execution/results as an onchain trace (“execution/results traced on-chain” in the Tier‑1 description of Confidential AI).
  3. The user gets: the result of the computation/application run with privacy for data/secrets.
  4. Where the blockchain is: execution accounting/trace, addresses/contracts, token economics and verifiable onchain facts (the RLC ERC‑20 contract).
  5. Token role: RLC is the ecosystem’s onchain token; the Roadmap mentions a “Voucher” mechanism that simplifies the use of RLC and “locking RLC in the ecosystem”.

Quick links: AI thesis fit

Project passport

Field Value
Project name iExec
Also known as (aliases) iExec RLC | RLC
Logo (logo) ../assets/41_rlc_logo.svg
Token symbol (ticker) RLC
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2017
Project status (status) active
Token (standard) ERC-20
Token contract 0x607F4C5BB672230e8672085532f7e901544a7375
Token model (token_type) utility (payments)
Max supply 86,999,784.986845492 RLC (max total supply)
Issuance fixed cap + burn (token contract has burn())
Tokenomics (tokenomics, brief) RLC is the ecosystem’s utility token; the Roadmap mentions a “Voucher” mechanism and “locking RLC in the ecosystem”.
Governance company‑led (iExec), details of DAO governance not established
Admins/keys owner control in the ERC‑20 contract (unlock/transferOwnership; the current owner needs to be clarified)
Audit yes
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) confidential computing for AI (TEE)
Use‑case (use_case) run confidential iApps/AI agents
DecAI Fit — AI thesis fit 6/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 3 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

iExec describes its stack as a set of tools for building applications where data privacy and trust in execution matter: data can remain encrypted, computations run in a trusted environment (TEE), and key events/results have a verifiable onchain trace.

At the “what can be done” level, two layers are visible in the official documentation:

  • dev layer: a “Hello World” path + the iApp Generator CLI for creating and testing iApps, plus DataProtector for working with ProtectedData;
  • use‑case layer: a demo showcase and example repositories (Web3 Messaging demo; demo/repo for an AI agent and PoC projects).

Features/modules

  • DataProtector / ProtectedData: access management and processing of encrypted data via the SDK.
  • iApp Generator: a CLI generator for TEE‑compatible applications (init/test/deploy flow).
  • Use Cases Showcase: a demo showcase (including Web3 Messaging) + links to code.
  • Confidential AI framework (described): TEE execution of AI training/inference with onchain tracing of execution/results.

Typical scenarios

  • Scenario 1 (developer): creates an iApp via iApp Generator → tests locally (TEE simulation) → deploys and runs data processing.
  • Scenario 2 (data owner): publishes/controls ProtectedData → authorizes processing by a specific iApp → gets the result without disclosing the source data.
  • Scenario 3 (demo): the user runs the Web3 Messaging live demo → sees an example of “private” interaction (Web3Mail/Web3Telegram) with data control.
  • Scenario 4 (AI): a developer runs an AI agent (ElizaOS) in a TDX TEE following the iExec reference repository (as an example of confidential AI agent execution).

Getting started (wallet/network)

  • What you need: an EVM wallet and a dev environment (the “Hello World” explicitly lists Node.js/Python/Docker as prerequisites).
  • Network/chain: EVM; the “Hello World” documentation offers a choice of network (Arbitrum One is mentioned as an option), while the RLC token verifiably exists as an ERC‑20 on Ethereum.
  • Fees: gas of the chosen EVM network for onchain operations, plus costs/payment for task execution under iExec rules (details depend on the specific flow).

Architecture/tech (non‑AI)

  • Components: iApp (container/code), DataProtector SDK, iApp Generator CLI, TEE execution environment, onchain contracts/accounting (and the RLC ERC‑20 token).
  • Participant roles: iApp developers, data owners (ProtectedData), users/task requesters, execution providers (TEE/workerpools).
  • Where logic runs: computations and data processing — offchain in a TEE; key events/execution trace and token facts — onchain (Tier‑1 wording: “Execution and results are traced on-chain”).
  • Dependencies: TEE (SGX/TDX as technology classes in the description), Docker and dev tools, EVM infrastructure (RPC/explorers).

Token/economics (expanded, no forecasts)

  • Token utility: RLC is described as the ecosystem token; the official Roadmap highlights a focus on the “utility of the RLC token” and the iExec Voucher mechanism, which “simplifies developers’ use of the RLC token” and leads to “more RLC locked in the ecosystem”.
  • Protocol necessity drivers: the Roadmap (Tier‑1) links utility to dev flows (Voucher/locking); onchain facts on supply/contract — on Etherscan.
  • Who pays fees: users/developers performing onchain operations and running iExec flows (gas + protocol payments).
  • Where fees go: — (not established from the Tier‑1 pages extracted within this card; depends on the flow/execution participants).
  • Issuance/burn: max total supply is fixed (Etherscan); the token contract contains burn() (Etherscan contract view).
  • Security/incentive mechanisms: Tier‑1 describes locking of RLC for the duration of task execution (staking/locking → sRLC) and RLC rewards to participants (workers/providers) for correct task execution.
  • Distribution/vesting: — (not established from the Tier‑1 extracted within this card).
  • Treasury: — (not established).

Governance

  • Who makes decisions: — (not established within the extracted Tier‑1; no public DAO process is recorded).
  • How protocol parameters change: via releases/updates and documentation (see the GitHub/Changelog links).
  • Where decisions are discussed/made: —.
  • Keys/multisig: — (an owner pattern is visible in the token contract; the parameters of protocol multisigs were not extracted).

Security and incidents

  • Audits: the security-audit repository in the iExec GitHub organization contains folders of audits by component (Tier‑1 navigation).
  • Bug bounty: — (no confirmed program in links_*).
  • Incidents: — (not established per Tier‑1 within this card).
  • Threat model: risks of trust in TEE providers/configuration, correctness of onchain tracing, centralization of admin rights in the token contract (owner pattern), as well as the need to separately confirm AI claims with measurable artifacts and metrics.

Project status and timeline

  • Current status: active; the RLC token exists on Ethereum mainnet (Etherscan), documentation and dev tools are public.
  • Key milestones: ICO start in April 2017 (Etherscan token page); current initiatives are described in the 2025 Roadmap.
  • Roadmap: the 2025 Roadmap (Tier‑1) includes the directions “AI: The Trust Layer for AI”, expansion of workerpools/TEE and new dev tools.

Ecosystem/integrations

  • Integrations: dev tools (DataProtector, iApp Generator), demo project repositories, EVM infrastructure.
  • Partners: the Roadmap mentions partnership directions (Intel/NVIDIA/CCC and others), but specific integrations/contracts were not extracted within this card.
  • Where it’s actually used: the use‑case showcase and demo repositories (Web3 Messaging demo; AI agent/PoC projects).

AI component of the project

  • What is real AI here? iExec positions itself as “confidential computing infra for AI” and publishes reference use cases/repositories (AI agent, image generation/validation PoC). This is infrastructure for AI pipelines, not a claim to “its own” model with quality metrics.
  • What is truly onchain? onchain facts: the RLC ERC‑20 token (contract, supply). The Tier‑1 description of Confidential AI separately states that execution and results are “traced on-chain”.
  • Why is a token needed? RLC is described as the ecosystem’s utility token; the 2025 Roadmap emphasizes mechanics for increasing utility and “locking RLC” via the Voucher.
  • Red flags (based on the information found): no public quality metrics for the AI components (AI_3=0); part of the product logic is inevitably offchain (TEE), so it is important to look at real demos/code and trust boundaries.

DecAI Fit component summary

  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
  • DecAI Fit: 6/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity high 3
Token necessity medium 2
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI relevance is confirmed not only by intent (roadmap) but by the existence of use‑case demos/repositories and dev tools for confidential AI.
  • Evidence: Tier‑1 — https://www.iex.ec/news/iexec-2025-roadmap-and-rlc-ecosystem
  • Why sufficient / why not (one line): AI_0 records intent only; here there are Tier‑1 “how to run/what to do” artifacts, so the intent flag is not needed.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): iExec provides infrastructure for AI pipelines/agents with confidential execution (TEE) and onchain tracing of execution/results.
  • Evidence: Tier‑1 — https://www.iex.ec/confidential-ai
  • Why sufficient / why not (one line): Tier‑1 directly describes the Confidential AI pipeline and AI use cases, which is sufficient for “AI is present”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the Tier‑1 use‑case showcase has a live demo (Web3 Messaging) and a set of example repositories (AI agent / image generation / PoC).
  • Evidence: Tier‑1 — https://www.iex.ec/confidential-ai, https://demo.iex.ec/web3messaging
  • Why sufficient / why not (one line): there are reproducible demo/code artifacts and public dev instructions.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.iex.ec/confidential-ai
  • Why sufficient / why not (one line): there are demos/repositories, but no published quantitative quality metrics for the AI components in Tier‑1.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 1
  • Claim (one line): Tier‑1 describes an end‑to‑end confidential AI pipeline (TEE, encryption, onchain trace) and publishes technical use‑case repositories.
  • Evidence: Tier‑1 — https://www.iex.ec/confidential-ai, https://docs.iex.ec/guides/build-iapp/build-&-test
  • Why sufficient / why not (one line): there is an architecture‑level technical description + a dev workflow, which is sufficient for AI_4=1.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 RLC: 0x607F4C5BB672230e8672085532f7e901544a7375
  • Evidence: Tier‑1 — https://etherscan.io/token/0x607F4C5BB672230e8672085532f7e901544a7375
  • Why sufficient / why not (one line): the token address and onchain parameters (supply/contract) are publicly verifiable.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 1
  • What useful logic is onchain: the Tier‑1 description of Confidential AI states that execution and results have an onchain trace (“traced on-chain”) for verifiability/accountability.
  • Evidence: Tier‑1 — https://www.iex.ec/confidential-ai
  • Why sufficient / why not (one line): Tier‑1 directly links the product value (traceability) to the onchain part.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain, the verifiable public trace of execution/results and the trustless properties (accountability) for which iExec describes the “confidential AI” flow are lost.
  • Evidence: Tier‑1 — https://www.iex.ec/confidential-ai
  • Why sufficient / why not (one line): Tier‑1 describes the onchain trace as part of the guarantee; without it, this becomes an ordinary centralized execution service.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, RLC (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x607F4C5BB672230e8672085532f7e901544a7375
  • Why sufficient / why not (one line): the onchain fact of the token and its contract is verifiable.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): the 2025 Roadmap links RLC to utility in dev flows (Voucher) and “locking RLC in the ecosystem”.
  • Evidence: Tier‑1 — https://www.iex.ec/news/iexec-2025-roadmap-and-rlc-ecosystem
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the use of the token as part of the product mechanism (not just a “trading ticker”).
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): Tier‑1 describes locking of RLC (staking/locking → sRLC) for the duration of task execution and RLC rewards to participants (workers) for correctly executed tasks.
  • Evidence: Tier‑1 — https://docs.iex.ec/get-started/overview/rlc ; https://docs.iex.ec/get-started/overview/workerpool ; https://iex.ec/academy/how-to-become-a-worker-and-start-to-generate-revenue-by-providing-computing-power
  • Why sufficient / why not (one line): this is a direct Tier‑1 description of incentives (rewards) and of the mechanics of locking the token in the protocol during execution.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): no confirmation that RLC is used for onchain governance was found in the extracted Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.iex.ec/
  • Why sufficient / why not (one line): without a Tier‑1 description of governance mechanics we set 0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token (USDC/subscription) is not established per Tier‑1; we do not draw strong conclusions.
  • Evidence: Tier‑1 — https://www.iex.ec/news/iexec-2025-roadmap-and-rlc-ecosystem
  • Why sufficient / why not (one line): without an explicit Tier‑1 comparison/argument we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.iex.ec/confidential-ai Confidential AI pipeline (TEE + encryption) + “execution/results traced on-chain” + a use‑case showcase and links to repositories/demos.
Tier‑1 https://demo.iex.ec/web3messaging Live demo (Web3 Messaging) as a reproducible example of “what you can touch”.
Tier‑1 https://docs.iex.ec/get-started/helloWorld Step‑by‑step dev guide (Hello World) for running the iExec privacy stack flow.
Tier‑1 https://docs.iex.ec/guides/build-iapp/build-&-test iApp Generator: init/test flow and a description of iApps as confidential computing apps.
Tier‑1 https://etherscan.io/token/0x607F4C5BB672230e8672085532f7e901544a7375 Onchain facts on RLC: the ERC‑20 contract and max total supply.
Tier‑1 https://www.iex.ec/news/iexec-2025-roadmap-and-rlc-ecosystem Roadmap: “AI trust layer” and utility/locking of RLC via the Voucher mechanics.
Tier‑1 https://docs.iex.ec/get-started/overview/rlc Transparent payment flow + RLC staking/locking (sRLC) for the duration of task execution.
Tier‑1 https://docs.iex.ec/get-started/overview/workerpool Workers receive RLC rewards for successfully executed tasks in a workerpool.
Tier‑1 https://iex.ec/academy/how-to-become-a-worker-and-start-to-generate-revenue-by-providing-computing-power Tier‑1: “worker will be rewarded with RLCs” + an RLC deposit is required as stake for incoming tasks.
Tier‑1 https://github.com/iExecBlockchainComputing/security-audit Public navigation of audit materials/folders in the official organization.
Tier‑2 https://www.coingecko.com/en/coins/iexec-rlc Context/profile (not proof).
Tier‑3 — —

No comments to display

Back to top