Skip to content
RLC Token Animation

RLC Token

The native cryptocurrency that powers the entire iExec decentralized confidential computing ecosystem

RLC (Run on Lots of Computers) powers all privacy apps on iExec. Every confidential computation uses RLC. Every data protection service uses RLC. Every app execution uses RLC. More builders using our tools = more RLC utility in real applications.

🎯 Why RLC Matters

Stack adoption = token usage. Developers build with iExec tools. RLC gets used. More privacy apps deployed = more RLC demand.

For Users

Every confidential computation you run uses RLC. That's how we keep your data private while making it usable.

For Providers

Build apps, provide data, or run workers. All earn RLC when people use your contributions.

For Holders

Clear positioning: More developers using iExec's privacy tools = more RLC utility in real applications. We're building activable privacy, not just protocols.

💰 Transparent Payment Flow

When you pay for a task execution with RLC, your payment is automatically and transparently distributed to all iExec protocol participants:

🔍 How Your RLC Payment is Distributed

1. App Provider - Gets paid for providing the confidential application

2. Protected Data Provider - Gets paid for providing access to protected confidential datasets

3. Worker - Gets paid for running the confidential computation on their decentralized machine

💡 Transparent: Payments are distributed based on pricing and conditions defined by each provider (iApp, Protected Data, Worker) in their marketplace orders.

🔒 RLC Staking: To run a task on the protocol (executing an application with protected data on a decentralized workerpool), you need to lock RLC in the protocol during the task period. In exchange, you receive sRLC (staked RLC). Once the task is completed, you can recover the RLC that wasn't consumed for the task payment.

💰 Tokenomics & Ecosystem Metrics

RLC operates on a utility-driven economic model where demand for confidential computing services drives token value:

Fixed Supply: RLC has a maximum supply of 87 million tokens, ensuring scarcity and value preservation.

Network Effects: As more users and providers join the iExec ecosystem, the demand for RLC increases, driving token value through network effects.

Utility-Driven Growth: Every interaction in the Turnkey Privacy ecosystem requires RLC:

  • iApp executions consume RLC for computation
  • Data protection services use RLC for encryption and access control
  • Cross-chain operations require RLC for bridge fees
  • Staking mechanisms lock RLC, reducing circulating supply

📊 Ecosystem Growth Metrics

Key Growth Indicators:

  • Task Volume: Increasing daily/monthly iApp executions
  • Developer Adoption: Growing number of deployed iApps
  • Data Provider Growth: More protected datasets entering the ecosystem
  • Cross-Chain Expansion: Multi-chain deployment driving broader adoption
  • Enterprise Integration: Real-world adoption in finance, healthcare, and AI sectors

🚀 Strategic Roadmap & Token Utility Expansion

2024-2025 Growth Drivers:

  • Multi-Chain Expansion: Ethereum, Arbitrum, and Polygon integrations
  • Enterprise Partnerships: Fortune 500 confidential computing adoption
  • AI Integration: Privacy-preserving AI model execution at scale
  • DeFi Integration: Confidential financial applications and protocols
  • Web3 Communication: Mass adoption of Web3Mail and Web3Telegram

Long-term Vision (2025+):

  • Global Privacy Infrastructure: Becoming the standard for confidential computing
  • Regulatory Compliance: GDPR, HIPAA, and SOX-compliant data processing
  • Consumer Applications: Privacy-first apps for everyday users
  • IoT & Edge Computing: Confidential processing at the network edge

🔄 Getting RLC

You can acquire RLC tokens through several methods:

Centralized Exchanges

Decentralized Exchanges

Cross-Chain Bridging

  • Bellecour Bridge
  • Stargate Bridge (Arbitrum)

Earn RLC

  • Develop confidential apps
  • Monetize protected datasets
  • Become a compute provider

🚀 Ready to Get Started?

Ready to dive into the iExec ecosystem? Here are the next steps: