←
iExec RLC9,656 posts
iExec RLC avatar✓

iExec RLC ✓

@iEx_ec

Programmable Privacy for Web3.

◷ Joined September 2016▧ 2,149 Photos and videos
iExec RLC avatar
iExec RLC@iEx_ec·22h

When software is updated, your data permissions should remain intact.

iExec RLC avatar
iExec RLC@iEx_ec·Nov 16

With DataProtector, access to a protectedData is granted explicitly and can be revoked the same way. revokeOneAccess removes one authorization. revokeAllAccess removes all of them, or only those for a given app or user. Control stays with the data owner at every step. 🔐

0:07
iExec RLC avatar
iExec RLC@iEx_ec·Nov 16

Onchain, everything is visible by default. Selective disclosure brings back a basic financial norm: Share what’s required, with whoever requires it.

iExec RLC avatar
iExec RLC@iEx_ec·Nov 14

What matters most before you give an AI agent access to your wallet?

iExec RLC avatar
iExec RLC@iEx_ec·Nov 13

An agent compromised at the infrastructure level exposes everything it can access. Isolating its runtime limits that exposure. 🔐

iExec RLC avatar
iExec RLC@iEx_ec·Nov 12

Model owners won't expose their weights. Data owners won't expose their data. Confidential computing lets them compute together inside a hardware-isolated enclave, so neither side ever sees the other's plaintext.

Post attachment
iExec RLC avatar
iExec RLC@iEx_ec·Nov 11

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. 🔐

Post attachment
iExec RLC avatar
iExec RLC@iEx_ec·Nov 10

Standard encryption protects data at rest and in transit. Confidential computing protects data in use.🔐

Post attachment
iExec RLC avatar
iExec RLC@iEx_ec·Nov 9

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.

Post attachment
iExec RLC avatar
iExec RLC@iEx_ec·Nov 8

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

iExec RLC avatar
iExec RLC@iEx_ec·Nov 7

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.

Post attachment
iExec RLC avatar
iExec RLC@iEx_ec·Nov 6

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

iExec RLC avatar
iExec RLC@iEx_ec·Nov 5

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

Post attachment
iExec RLC avatar
iExec RLC@iEx_ec·Nov 4

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.

0:07
iExec RLC avatar
iExec RLC@iEx_ec·Nov 3

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.

Post attachment