Question 1

What is RLC?

Accepted Answer

RLC is the native utility token of the iExec decentralized confidential computing ecosystem and does not represent equity in the iExec company. iExec places confidential application execution, protected data usage, and decentralized computing tasks within the same task-settlement system: when these services are used, RLC is the payment asset used by the protocol.

Question 2

What are the main uses of RLC?

Accepted Answer

RLC is primarily used to pay for task execution on iExec. When users run confidential computing, execute privacy applications, or consume protected data, tasks must be settled in RLC; participants who provide applications, protected data, or computing worker nodes are paid RLC for their contributions. In other words, the token's utility arises from the use of applications, data, and computing power by specific tasks, rather than task revenue being generated automatically merely by holding RLC.

Question 3

Who receives the funds after payment with RLC?

Accepted Answer

Task payments are not distributed equally without conditions. Application providers, protected data providers, and worker nodes performing confidential computing receive their respective payments according to the prices and conditions they set in marketplace orders. The components used by a task determine which participants take part in settlement: for example, if a task does not use protected data, remuneration for a data provider should not be regarded as an inevitably present component of that task. Orders first define the services and conditions, and paid RLC is then allocated under those conditions after task execution.

Question 4

Why must RLC be locked when using a task?

Accepted Answer

When a user executes an iApp task using protected data in a decentralized worker pool, RLC needs to be locked in the protocol during the task, and the user receives sRLC, a representation of locked RLC. Locking enables the protocol to process task payment during execution, rather than treating all funds as finally spent before the task has been completed. After the task is completed, RLC not actually used for that task's payment can be reclaimed; the portion consumed under the order conditions is used to settle participant remuneration.

Question 5

What is RLC's supply mechanism?

Accepted Answer

RLC has a maximum supply of 87 million tokens. iExec documentation states that the entire circulating supply has already been minted, with no tokens pending unlock or private-sale allocation; this describes token creation and pending-unlock arrangements, rather than guaranteeing the quantity tradable at a particular point in time. Task locking limits the availability of the relevant RLC while a task is underway, and unconsumed portions can still be reclaimed after completion. Therefore, “fixed maximum supply,” “minted,” and “available balance at a given time” are concepts that need to be understood separately.

Question 6

What is the relationship between iExec usage and demand for RLC?

Accepted Answer

Greater use of iExec services may increase demand for RLC as a task-payment asset: developers deploying privacy applications, users executing tasks, or users consuming protected data all need to use RLC in the relevant tasks. This relationship depends on whether such service use actually occurs, the order conditions of the tasks, and whether participants choose iExec; it does not mean that the number of applications or technology releases automatically translates into token purchases or price increases.

iExec (RLC) Price

Price of iExec (RLC) Today in USD

iExec (RLC) Price History

Fear & Greed Index

Why Did iExec (RLC) Fall in the Last 24 Hours?

About iExec (RLC)

Use Cases and Features

Supply and Issuance Mechanism

How to Buy and Use iExec (RLC)

How to Buy

Related Markets

Simple Earn

iExec (RLC) Basics & Market Insights

Fundamentals

Market Analysis

Frequently Asked Questions About iExec (RLC)