Sabitlenmiş Tweet
iExec Developer
229 posts
iExec Developer
@iExecDev
The home of iExec builders | Join us for dev updates, tutorials, and experiments around Confidential Web3 | Built by builders, for builders 💪
TEE Katılım Ekim 2025
567 Takip Edilen399 Takipçiler
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-…
English
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!
English
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.
iExec RLC@iEx_ec
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/build-c…
English
@iexec_nox/handle v0.1.0-beta.13 is live.
Ethereum Sepolia support added. All previous versions are now deprecated.
Your dependencies need updating.
@iexec-nox/handle/v/0.1.0-beta.13" target="_blank" rel="nofollow noopener">npmjs.com/package/@iexec…
English
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.
English
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.
English
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.
English
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
English
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.
English
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.
English
There's a new token standard on the block.
ERC-7984.
And it changes what a token is allowed to hide.
🧵
English
The only way in or out is the Handle Gateway.
It runs inside Intel TDX.
It checks on-chain ACLs before releasing anything.
It coordinates with the KMS for key material.
Battle-tested storage. Hardware-enforced access. End-to-end encrypted.
This is what serious infrastructure looks like.
English
Here's the thing though.
Nothing stored in S3 is readable.
Every handle is ECIES-encrypted before it ever hits a bucket — keyed to the protocol's public key.
What lands in S3 is ciphertext. Pure ciphertext.
Amazon can't read it. We can't read it. Nobody can.
English
Nox stores its handles in S3.
Let's talk about what that actually means.
🧵
English