iExec RLC

Programmable Privacy for Web3.

[iExec RLC @iEx_ec]

https://t.co/FlTu3gRwmM

[iExec RLC @iEx_ec]

How does a confidential app get paid for work on data it never sees?

PoCo matches signed orders into an onchain deal, runs the task in an Intel TDX Trust Domain and verifies the proof. 🔐

[iExec RLC @iEx_ec]

Standard encryption protects data at rest and in transit.

Confidential computing protects data in use.🔐

[iExec RLC @iEx_ec]

@binance Prioritize privacy & security always. 🔐

[iExec RLC @iEx_ec]

@EliBenSasson It's on.

[iExec RLC @iEx_ec]

Building a confidential app used to mean complex TEE configuration, manual compliance checks and debugging after deployment.

The iApp Generator removes that setup.

🔸 Ready-to-use templates in Python or JavaScript
🔸 Automated TEE setup
🔸 Built-in checks against the iExec iApp framework before you deploy

An iApp is the part of your application that handles protected data, running inside a TEE.

[iExec RLC @iEx_ec]

Consent you can’t revoke isn’t really consent.
Real consent comes with an off switch that actually works.

[iExec RLC @iEx_ec]

Run code on someone else’s machine, and three things can go wrong:

You lose control of the data.
The operator can read it while it runs.
You get an output, but no proof of how it was produced.

iExec PoCo removes the operator from the trust equation.

[iExec RLC @iEx_ec]

Building AI on sensitive data?
What would you protect first? 🔐

[iExec RLC @iEx_ec]

@web3privacy @0xmikemcc @0xbowio @0xprivacypools Privacy is for everyone. Confidentiality and selective disclosure is how we protect the information behind it. 🔐

[iExec RLC @iEx_ec]

On-chain is where you prove things.
Off-chain is where you compute them.

[iExec RLC @iEx_ec]

@StaniKulechov Keep building! 🧱⛓️

[iExec RLC @iEx_ec]

@RWAFoundation_ Good morning!

[iExec RLC @iEx_ec]

Every access to protected data needs explicit authorization.

With DataProtector, you choose the authorizedUser who can submit it, and how many times.

You stay the owner. The data remains protected.

[iExec RLC @iEx_ec]

@bondoncredit Congrats for the new looks! 🤝

[iExec RLC @iEx_ec]

Data isn't the only thing worth protecting. Your logic is, too.

Model parameters, scoring thresholds, API keys.

On iExec, an iApp's secrets are delivered only inside the TEE at runtime, never exposed to the machine running it.

[iExec RLC @iEx_ec]

A TEE isn't a file safe. It's an isolated computer.

Software runs inside. Data lives inside. The host, hypervisor, OS, even the cloud operator, can't read what's happening in there.

Intel TDX calls this a Trust Domain. Different TEE, same principle: protect computation, not just files.

[iExec RLC @iEx_ec]

Privacy design fails at disclosure, not at encryption.

The question isn't how do we encrypt it? It's who gets to see it, and when?

[iExec RLC @iEx_ec]

Public infrastructure should expose the rules and the proof.

Not the positions, the amounts, or the strategy.

[iExec RLC @iEx_ec]

A protected computation does not automatically return an encrypted result.

[iExec RLC @iEx_ec]

What happens when you protect data with DataProtector?

1. Client-side encryption before anything leaves your machine
2. Encrypted payload uploads to supported storage (IPFS, Arweave)
3. Ownership registered on-chain

Three functions, three layers. On-chain ≠ publicly readable.
👉 https://t.co/CQNgctLv7U