The home of iExec builders | Join us for dev updates, tutorials, and experiments around Confidential Web3 | Built by builders, for builders 💪
TEE
Joined October 2025
- Tweets231
- Following553
- Followers384
- Likes379
Huge announcement for the WTF Hackathon!
We're thrilled to welcome @DeVinciBC as our Community Partner for the WTF Summer Edition! 🎓
DeVinci Blockchain isn't just an association, they're a talent pipeline. Students shipping real products and alumni building the future of Web3.
If you're serious about builders who understand privacy & confidential computing, this is where they come from.
Let's go build together 🤝
dorahacks.io/hackathon/2283
WTF Hackathon Summer Edition is LIVE!
Write The Future with Nox
This time: We're looking for builders who can take a real, impactful open-source protocol and add privacy or build something truly innovative with Nox by @iEx_ec
1500 USD pool
25 days left
Join us: dorahacks.io/hackathon/wtf-h…
It’s official, the Bellecour Bridge has officially taken its final bow.
We are happy to share that the reimbursement operation is now fully complete.
All users who held a minimum of 0.1 RLC on Bellecour have been successfully credited on Ethereum.
Thank you all for your patience, let’s keep pushing forward and building!
This is the friction killer. Devs shouldn't have to learn a new stack to build private. One plugin, existing workflow, actual confidentiality. That's how privacy gets adopted.
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…
@iexec_nox/handle v0.1.0-beta.13 is live.
Ethereum Sepolia support added. All previous versions are now deprecated.
Your dependencies need updating.
npmjs.com/package/@iexec-nox…
5/ You control it. Fully private or selectively shared. You decide where each piece of data sits.
Not the protocol.
Not the regulator.
Not the market.
You.
4/ Here's the honest part: once added, a viewer can't be removed. Not a bug. A logical reality. If they could already decrypt and store the value, revoking access wouldn't undo that.
The system doesn't pretend otherwise. For sensitive audits, you create a new handle with a fresh ACL. Access isolation at the application layer.
3/ The Viewer role is the regulatory primitive.
addViewer(handle, regulatorAddress)
One line. The regulator can now decrypt that specific handle. Not your whole portfolio. Not your strategy. Not your other positions. Just what you granted. To whoever you chose.
2/ Every encrypted value in Nox has an access list. Two roles. Hard lines between them.
Viewer can decrypt. That's it.
Admin has full control: add viewers, manage admins.
1/ In TradFi, when a regulator knocks, you don't publish your books to the whole market. You show them exactly what they asked for.
Nothing more.
That's selective disclosure.
Nox brings it on-chain.
Tomorrow at 5 PM GMT+2!
Our super ambassador @Altcoin_daddy is hosting an incredible developer workshop on How Nox Fits Into Developer Workflows!
Learn how to build privacy-first on-chain apps, explore confidential tokens & DeFi and get your questions answered.
Perfect for Solidity devs, Web3 builders & anyone curious about privacy
luma.com/3lga6ml3
ERC-20 compatible. Standard Solidity. No new wallet.
You write confidentialTransfer() the same way you'd write transfer().
The enclave handles the rest.
This is what a privacy primitive looks like when it's built to actually ship.
Here's the detail that makes it serious.
Transfers in ERC-7984 never revert on insufficient balance.
They silently cap instead.
Why? Because a revert is information.
If your transfer fails, I now know your balance was too low.
In a confidential system, even failure must reveal nothing.
Allowances are gone too.
ERC-20 allowances are a known mess — front-runnable, hard to revoke cleanly, unlimited by default if you're not careful.
ERC-7984 replaces them with time-bound operators.
Access granted until a timestamp. Then it expires. Automatically.
No amount limit. No manual revoke needed.
ERC-7984 closes the blinds.
Balances: encrypted. euint256, not uint256.
Transfer amounts: encrypted. Gone from public view.
Arithmetic: executed off-chain, inside a TEE enclave. Nothing computed in the open.
The token still exists on-chain.
The values don't.
Think about who actually moves money at scale.
Citadel. BlackRock. Brevan Howard. Point72.
Real asset managers with real AUM and real strategies.
They don't publish their positions.
They don't let competitors watch their trades in real time.
They don't operate in glass boxes.
ERC-20 is a glass box.
With ERC-20, everything is public.
Your balance. My balance.
Every transfer amount. Every address. Every timestamp.
It's all there. On-chain. Forever. Readable by anyone with an RPC node and five minutes.
That's not a bug. That's how ERC-20 was designed.
It just wasn't designed for everyone.
There's a new token standard on the block.
ERC-7984.
And it changes what a token is allowed to hide.
🧵