Sabitlenmiş Tweet
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
English
iExec RLC
9.3K posts
Before a confidential workload can be trusted, one question comes first:
How do you know the right code is running on genuine confidential hardware?
Our new technical article breaks down the first layer of Nox's Chain of Trust👇
iExec RLC@iEx_ec
English
WTF!! for Write The Future
The challenge is simple: pick an open source protocol, add privacy with Nox, ship something a company could deploy.
$1,500 pool.
23 days on the clock.
What are you building? 👇
dorahacks.io/hackathon/wtf-…
English
GM to those using the Arbitrum Platform
Robinhood@RobinhoodApp
GM to those using Robinhood Chain
English
We integrated dstack into Nox’s Chain of Trust.
Nox can now better measure executions before receiving any sensitive data.
Privacy builders strong together 🤝
Phala@PhalaNetwork
Congrats @iEx_ec on bringing dstack into Nox’s Chain of Trust. Nox is iExec’s confidential DeFi/RWA protocol. dstack adds measured CVM execution before sensitive workloads receive secrets or produce results.
English
iExec integrates @PhalaNetwork dstack into Nox to bring this verifiable execution model to confidential DeFi and RWA systems.
Institutions need to know that sensitive computation ran in the expected environment before they trust the result.
That's what dstack helps verify.
Nox uses it to make confidential execution measurable, attested, and provable.
English
How do you make sure a confidential workload runs in exactly the environment it's supposed to?
That's why we used dstack, an open source orchestration layer built by @PhalaNetwork that operates Confidential Virtual Machines on Intel TDX.
Instead of managing Trust Domains manually, dstack provides:
🔸 A supervisor that boots CVMs from a measured, reproducible OS image
🔸 A KMS that only lets workloads boot if their measurements match a trusted whitelist
🔸 A Gateway that terminates TLS and routes traffic to each CVM over an encrypted overlay
English
This is the right framing.
Institutions need to protect treasury, settlement, and customer flows while still settling onchain.
Configurable confidentiality.
Nox brings this to DeFi as a building block, confidential primitives + onchain ACL for selective access.
Arbitrum@arbitrum
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.
English
Privacy is such an easy bull case to make.
It already exists by default in web2 finance and it should be the same in web3.
@mert and @blknoiz06 talking facts on @MarketBubble
English
When we partnered with REAL, the point wasn't another RWA announcement.
It was a signal.
Institutional RWAs won't scale as long as investor allocations, subscriptions, and settlement flows are public by default.
The next layer is confidentiality. Private where it matters. Auditable where required.
Real@RealFinOfficial
English
Before a confidential workload can be trusted, users should be able to verify the environment behind it.
The Nox Attestation Portal gives builders and partners a clearer way to inspect verification signals across Nox components.
Explore it here ➡️ trust.noxprotocol.io
iExec RLC@iEx_ec
How do you know a confidential workflow is running in the right environment, with the right code, before it touches sensitive data? You measure it. You attest it. You verify it at every layer. That is Chain of Trust: Nox’s way of making confidential execution measurable, attested, and verifiable from the hardware layer up to the running workload. ➡️ trust.noxprotocol.io
English
Congrats! @iEx_ec is bringing dstack into Nox’s Chain of Trust for confidential DeFi and RWA workloads 💪
iExec RLC@iEx_ec
English