iExec RLC
@iEx_ec

Programmable Privacy for Web3.

iex.ec/
Joined September 2016
2,129 Photos and videos
Pinned Tweet
iExec RLC
@iEx_ec
Jul 29
Article

Six Months Building the Missing DeFi Layer

At the start of this year, we made a quiet bet based on intensive market research: That the next phase of onchain finance wouldn't be unlocked by faster chains, bigger throughput, or cheaper gas. That

9
12
86
25,448
Removing a name doesn't automatically protect the financial data attached to an address. An unnamed treasury making recurring payments still exposes balance movements, payment timing, and transaction patterns. Observers see patterns. Patterns aren't proof of identity, but they're often enough.
2
2
20
2,253
Your wallet has no name. What can its activity still reveal?
3
18
2,402
Imagine your competitors could see every payment your company made to suppliers. Amounts. Timing. Frequency. They'd know your purchasing volume. Your pricing leverage. Your relationships. That's what corporate payments on transparent public rails look like today. The fix isn't private chains. It's confidentiality on shared ones.
1
5
26
3,284
What actually changes when a token becomes confidential? The transfer still happens on chain. The sender and receiver are still visible. What changes ➡️ the amount is encrypted, and only authorized parties can see it.
2
4
24
3,363
The AI conversation shifted this year, and most people missed why. The concern isn't smarter chatbots. It's chatbots that stopped being chatbots, AI systems that access files, run code, and execute transactions on your behalf. That changes the risk profile entirely 👇
2
6
31
3,548
more replies
Three separate AI risks worth thinking about, not equally established: Well-documented: deliberate misuse (fraud, phishing, cyber attacks). Well-documented: mistakes with real-world consequences. More contested: loss of human control over advanced systems.
1
1
10
310
The middle category is the one that changed the most in 2026. An agent making a wrong choice used to mean a bad chat. Now it can mean a bad transaction, a leaked file, or an unrecoverable action. Serious reading on all three, from the International AI Safety Report 👇 internationalaisafetyreport.…

International AI Safety Report

internationalaisafetyreport.org
6
219
Summer 2026 will be remembered as when confidentiality stopped being contrarian and started being consensus.
2
5
27
2,697
Hardware. Environment. Code. Check them all.
7
28
3,167
what is the hardest requirement for bringing serious financial workflows on-chain without breaking DeFi composability?
7
6
29
2,922
Private execution is cute. Verifiable execution is serious. Encryption is table stakes. Proof of what code ran, on what hardware, in what environment, that's what institutional finance actually needs.
7
30
3,785
The public market doesn't need to see everything. Different parties need different levels of visibility. — @RicardoKanaan_ , Head of Growth at @iEx_ec That's the entire idea behind selective disclosure. Regulators see what they need. Auditors see what they need. Markets see what's public.
2
6
33
3,434
iExec RLC retweeted
iExecuTEEr🛢️
@Fryderyk3388
Sep 18
Article

Tokenization Is Winning. Privacy and Selective Disclosure Are What Make It Scale.

Tokenization is the winner of crypto summer 2026. BTC thopped. Tokenized RWAs kept climbing. RWA.xyz now puts distributed on-chain RWA value at $38.25B. Represented value is about

3
7
14
2,691
Proof of Cloud isn't replacing TDX attestation. It complements it. TDX proves the execution environment. Proof of Cloud proves the hosting context. Both, together, close the provenance chain. docs.iex.ec/
6
29
2,836
Protect the data while it’s actually being used.
3
22
2,848
A TDX quote is structured evidence. It's produced by the Intel TDX Quoting Enclave, signed with an Intel-provisioned attestation key, and verifiable back to Intel's root of trust. Nox relies on three fields inside it 👇
2
6
20
4,002
more replies
RTMR3 (runtime measurement register): Holds application-specific measurements, app-id, os_image_hash, compose_hash, instance-id, key-provider. Cryptographic fingerprint of exactly what code is running.
1
7
236
Event logs make RTMR3 interpretable. A verifier replays the event log and matches it against the signed RTMR3. If they match, the OS image and docker-compose hashes can be trusted as representative of what actually ran. Three fields. One chain of evidence 👇 trust.noxprotocol.io
4
182
Load more