Programmable Privacy for Web3.
- Tweets 9,202
- Following 961
- Followers 87,525
- Likes 4,632
Nox is now live on @ethereum testnet.
Programmable Privacy coming to the home of EVM.
RWA issuers & DeFi builders can now integrate confidentiality at an institutional level.
➡️ Start here: docs.iex.ec
8
15
68
9,888
For everyone asking how to test confidential contracts without rebuilding their workflow:
@HardhatHQ 3 plugin x NOX. Native. Runs the confidential stack during tests, plugs in helpers for encryption + decryption, works with Viem or Ethers.js.
👉 docs.noxprotocol.io/guides/b…
1
6
32
3,298
iExec RLC retweeted
Can AI actually stay private without slowing everything down?
Depends on where you are willing to place the trust.
🔹 FHE and MPC keep data encrypted throughout computation, but need more processing.
🔸 TEEs run close to native speed, but rely on secure hardware, manufacturers and data centres.
@loosty from @Arcium and @fotshudi, CTO at @iEx_ec, break down the trade-off 👇
9
11
69
7,968
What if you could back a creator without anyone seeing how much you gave?
That's FUNDME.
Built on Nox. Encrypted contributions onchain, TEE computed leaderboards, permanent ranking history pinned to IPFS.
Crowdfunding without the privacy compromise.
👉 Dorahacks::dorahacks.io/buidl/43574
👉 GitHub: github.com/Zifeng-Ma/FUNDME
4
5
30
2,804
The transparency paradox: blockchains build trust by exposing everything, while institutions need confidentiality to operate.
BlackRock's BUIDL fund holds $2B+ on-chain. That's a fraction of the $30T tokenized asset opportunity.
The gap is because of privacy frameworks institutions actually require.
Worth reading on @chainlink 👇
chain.link/article/instituti…
2
7
25
2,387
The path forward is not less transparency. It is better defined transparency.
Auditable finance means confidentiality by default, selective disclosure, and verification without forced transparency.
Sensitive financial data such as investor allocations, position sizes, transaction amounts, and strategy execution should not be readable by the public market.
The right parties, regulators, auditors, counterparties, compliance teams, or specific smart contracts, can receive scoped and revocable access when needed.
The chain can still verify that the declared logic executed correctly on committed inputs, without exposing the underlying data.
This is how regulated finance already works: confidential by default, auditable on demand.
Start here 👉 docs.iex.ec/
Businesses won't choose between transparency and privacy.
They'll expect both.
Arbitrum's confidentiality features let organizations protect sensitive activity while selectively disclosing information to customers, partners, auditors and regulators when appropriate.
3
3
28
2,325
What this changes for builders:
Before, testing confidential smart contracts meant dealing with encrypted inputs, handles, SDK setup, and local Nox infrastructure.
Now, Nox + @HardhatHQ handles that in the background.
You write Solidity tests the way you already do.
The confidential layer plugs in underneath.
➡️ docs.noxprotocol.io/guides/b…
Building confidential smart contracts on iExec just got easier.
Nox now has a native @HardhatHQ 3 plugin for confidential smart contracts.
In simple words: Solidity devs can test encrypted inputs and decrypted results from their usual Hardhat setup.
Build confidential smart contracts in the framework you already know.
✅ One package.
✅ One config block.
✅ Your existing test command.
No new toolchain. No new workflow. No manual infra setup.
Just confidentiality plugged into the dev environment most of DeFi already uses.
➡️ docs.noxprotocol.io/guides/b…
3
3
24
2,368
Building confidential smart contracts on iExec just got easier.
Nox now has a native @HardhatHQ 3 plugin for confidential smart contracts.
In simple words: Solidity devs can test encrypted inputs and decrypted results from their usual Hardhat setup.
Build confidential smart contracts in the framework you already know.
✅ One package.
✅ One config block.
✅ Your existing test command.
No new toolchain. No new workflow. No manual infra setup.
Just confidentiality plugged into the dev environment most of DeFi already uses.
➡️ docs.noxprotocol.io/guides/b…
2
8
43
4,833
Today is the last day to self bridge RLC from Bellecour to @ethereum.
The bridge officially shuts down on July 2.
Holders with ≥ 0.1 RLC on Bellecour will be auto credited on Ethereum.
Bridge here 👇
bridge-bellecour.iex.ec
2
20
3,034
"Confidentiality and Compliance"
Two main requirements. Both non-negotiable. — @RickK9_Algo
This is where RWAs need protocols like iExec & @COTInetwork.
1
1
16
511
This is the part builders should pay attention to.
@Chain_GPT released a @claudeai Code skill that helps turn confidential app ideas into working flows with iExec Nox.
Start here 👇
github.com/ChainGPT-org/chai…
8
8
51
4,658
This is how Programmable Privacy gets into more real apps.
The Premonition Vault: a sealed-prediction engine on Nox by @iEx_ec, powered by ChainGPT.
Crypto Twitter is full of "I called it" posts nobody can verify. Tweets get deleted. Screenshots get faked.
We built a demo to fix it. Predictions are encrypted client-side via Nox by iExec, then judged by a ChainGPT-powered AI Oracle once a time-lock expires.
Only the right ones become public.
Two modes:
→ Personal: seal your own. Right ones go public with proof, wrong ones stay sealed forever.
→ KOL: seal an influencer's call. If they're wrong, it becomes a public receipt.
No deleted tweets. No "trust me bro."
The whole thing was lab-coded with the ChainGPT Claude Code skill.
One prompt scaffolded the frontend, Nox encryption, Sepolia commits, smart contracts, oracle wiring, and UI.
What used to take devs weeks now takes a prompt and an afternoon.
Install: /plugin install ChainGPT-org/chaingpt-claude-skill
Anyone can build with ChainGPT and iExec!
Demo below.
1
14
649