iExec Developer

seeing more hackathons focused specifically on privacy and confidential compute feels like a strong signal performance alone isn’t enough anymore builders now care about: → privacy → real-world use cases → usable infra

@edenbdn Privacy is becoming default infra, not a feature 👀

For a long time, privacy in web3 felt optional. Now it feels… inevitable. Between regulation, AI, and real-world use cases, you can’t build serious apps without thinking about confidentiality and verifiability. Curious how teams are approaching this today.

How to Educate the Next Generation of Web3 Developers? x.com/i/broadcasts/1…

@edenbdn No winners, just the better combo

Web3 privacy used to feel like a competition: ZK vs MPC vs TEE What we’re actually seeing now is hybrid architectures: ZK → proofs TEE → fast confidential compute MPC→ collaborative privacy Builders mixing tools > picking sides

One architecture pattern showing up everywhere lately: compute off‑chain verify on‑chain It unlocks things that are hard to do fully on‑chain: AI inference private data processing complex DeFi logic Feels like a core building block for the next wave of dApps.

It's not a Yes - No question

@edenbdn @ElectricCapital Some follow AI, some follow privacy ;)

Crypto lost a lot of developers. Last year the ecosystem peaked at 44,000 monthly active developers. Today it’s closer to 30,000. That’s a drop of roughly –30%. @ElectricCapital data this week: → 9,346 full-time crypto developers → 635,000 commits across the ecosystem → 30,265 monthly active developers Where builders still concentrate: → EVM stack: 14,693 devs → @ethereum : 11,146 devs → @solana : 4,074 devs → @Bitcoin : 2,962 devs → @base : 2,442 devs The exodus is real. But it’s mostly the short-term builders leaving. → 13,014 established developers still contributing Where did the rest go? Most who left went to AI. The fastest growing developer ecosystem on GitHub right now. Builders follow momentum, right now, momentum is AI.

@DelforgeJules @iExec_RLC Public $50M orders are easy targets, confidential transaction changes the game

CoW Swap did everything right. Warnings shown, transaction executed as signed. But $50M visible in a thin pool is free money with a flash loan, a pump and a dump. No confidential order size or confidential splitting is a free sandwich. That's the gap @iExec_RLC is building for.

@0xPhoenix77 If we are talking TEE, where is @iEx_ec? Building TEE-based confidential computing for Web3 since 2017

Crypto privacy now spans an entire stack. Privacy coins → ZK → FHE → confidential compute → private AI → DID → encrypted payments. ❯ I mapped 8 key sectors and their flagship projects. ⮯ 1. Privacy Coins/Private Transactions (Foundational financial privacy - the original flagship sector) @monero - $XMR: Mandatory privacy using ring signatures and stealth addresses; reclaimed the top privacy position in 2026. @Zcash - $ZEC: zk-SNARK–based privacy with optional shielded transactions; one of the strongest performers in the sector. @Dashpay - $DASH: PrivateSend mixing mechanism; remains a long-standing privacy payment network. @PirateChain $ARRR: Mandatory zk-SNARK privacy for all transactions. @firoorg $FIRO: Lelantus protocol with large anonymity sets. 2. Zero-Knowledge (ZK) Privacy & Programmable Privacy (ZK emerging as a major privacy moat in 2026) @Zcash - $ZEC: Early implementation of zk-SNARK cryptography. @0xMiden: ZK-STARK–based chain focused on privacy and scalability. @penumbrazone: Privacy-focused DeFi ecosystem on Cosmos with shielded assets. @namada: Multi-chain shielded liquidity pools; funding exceeds $60M. 3. Fully Homomorphic Encryption (FHE) & Confidential Compute (Encrypted computation as a long-term privacy primitive) @zama - $ZAMA: Creator of fhEVM; valued around $1B, focusing on confidential smart contracts. @fhenix: EVM-compatible FHE infrastructure layer. @inconetwork: Confidential computing layer integrated with Base and Ethereum. @mindnetwork_xyz: Encrypted Web3 infrastructure with AI privacy features. @Arcium: Confidential computing architecture on Solana. TGE & airdrop coming 4. Trusted Execution Environments (TEE) & Programmable Privacy Layers (TEE-based architectures enable confidential computation in secure hardware environments, often combined with ZK or FHE models.) @OasisProtoco $ROSE: TEE-based privacy architecture for DeFi and data privacy. @SecretNetwork - $SCRT: Encrypted smart contracts within the Cosmos ecosystem. @PhalaNetwork $PHA: Confidential computing infrastructure supporting privacy-focused AI workloads. @RAILGUN_Project $RAIL: Privacy middleware with shielded transaction pools. 5. Privacy in RWA & Institutional Tokenization (Compliant privacy for tokenized financial assets) Privacy combined with regulatory compliance is emerging as an important component of institutional tokenization. @OndoFinance $ONDO: Tokenized treasury infrastructure with privacy-oriented features. @centrifuge - $CFG: RWA lending platform with confidential data handling. @maplefinance: Institutional credit pools with selective privacy structures. @Securitize: Tokenized securities platform designed for regulatory compliance. @SeismicSys: Encrypted EVM infrastructure targeting fintech and tokenized assets (pre-token stage). 6. Privacy AI/Private AI Systems Privacy-preserving AI systems focus on protecting user queries, training data, and inference processes. @AskVenice - $VVV: Privacy-first AI infrastructure with local storage and uncensored inference; led by Erik Voorhees. @PhalaNetwork - $PHA: Confidential compute applied to AI workloads. @mindnetwork_xyz: Privacy infrastructure supporting encrypted AI agents. @OasisProtocol - $ROSE: Privacy-preserving compute for AI data. @bittensor - $TAO ecosystem variants: Decentralized machine learning networks incorporating privacy components. 7. Decentralized Identity (DID) & Selective Disclosure (Privacy-preserving identity verification) @worldcoin - $WLD: Identity infrastructure combining biometric verification and decentralized identity. @spruceid: Ethereum-native decentralized identity toolkit. @0xPolygon: ID – ZK-based identity proofs enabling verification without revealing underlying data. 8. Encrypted Payments & Privacy Stablecoins (Privacy infrastructure for everyday financial rails) @namada: Shielded stablecoin infrastructure integrated with multi-chain ecosystems. @Penumbra: Shielded stablecoin variants within private DeFi pools. @Zcash ecosystem: Shielded payments using zk-SNARK cryptography. @PayPal - $PUSD: Payment infrastructure exploring privacy-related improvements. This map offers a starting point for exploring the crypto privacy ecosystem. And more @a16zcrypto said "privacy as moat." @Grayscale said "preference for privacy." ➜ Privacy in 2026 become infrastructure necessity for institutional and VC Which sector do you think will drive the next wave of adoption?

Congrats to @bondoncredit on the RHC Innovation Award 🏆 Love the story, deciding to team up at @EthCC Cannes the same day @RobinhoodApp announced Robinhood Chain powered by @arbitrum Orbit. Excited to see what you build next.

@arbitrum can't wait to see!

Yesterday: founders locked in building onchain. Today: the final day of NYC Founder House. Teams will present what they built over the past few days before we close with a ceremony and dinner. The next generation of onchain businesses is being built on the Arbitrum platform.

Tips: Keep secrets local. Nothing is shared during testing. For advanced setups, explore the "advanced" mode in iapp init. Check docs.iex.ec for more examples. This gets you from zero to a running confidential app in minutes.

6/ Run Your iApp Execute the deployed app on the network. Run: iapp run --chain arbitrum-sepolia-testnet This creates a deal and task in the TEE. Results are stored in runs.json with dealid, taskid, etc. Use the iExec Explorer to monitor tasks. If using protected data or args, add flags like: --protectedData your-data-address --args your-args

How to Create an iApp on iExec Building an iApp (iExec Application) allows you to create decentralized, confidential apps that run in Trusted Execution Environments (TEEs) for secure data processing. This is perfect for Web3 developers working on privacy focused projects like DeFi, RWAs or AI. Below is a step by step guide based on the official iExec documentation. Make sure you have Node.js and Docker installed as prerequisites.

🎙️Building Confidential Prediction Markets: LIVE w/ iPred x.com/i/broadcasts/1…