How decentralized confidential computing works
A decentralized network of Intel SGX nodes executes your code inside hardware-secured enclaves. Every task produces a cryptographic proof written to the blockchain.
Three enclaves. One proof. Zero trust required.
Every task runs through a triple-enclave pipeline secured by Intel SGX. The network proves correct execution on-chain — no trust in any single party needed.
Validates code & data checksums against owner signatures. Attested via Intel SGX DCAP. Never executes client code.
Runs your code inside an isolated enclave. Even the node operator cannot read memory. Encrypted I/O via IPFS.
Independently validates the on-chain Proof of eXecution and unlocks payment to the operator. A forged proof is invalidated and can be slashed.
Proof of eXecution written to blockchain. Anyone can verify.
The triple-enclave pipeline
TrustedZone (Gatekeeper)
The first enclave receives your encrypted code and data. It validates checksums against owner signatures to ensure nothing was tampered with. TrustedZone is attested via Intel SGX DCAP on mainnet (self-signed on testnet). It never executes client code — it validates, brokers keys, and signs the Proof of eXecution.
SecureLock (Executor)
Your code runs here. SecureLock decrypts the payload using keys brokered by TrustedZone and executes your function inside an isolated SGX enclave. Even the node operator cannot read the enclave's memory. Input and output are encrypted via IPFS. A malicious payload cannot forge a Proof of eXecution because it never touches TrustedZone.
Validator
A separate enclave that independently validates the on-chain Proof of eXecution: it re-derives the enclave identity and confirms the result was signed by the genuine execution enclave. On a valid proof it validates the order and unlocks payment to the operator; a forged or mismatched proof is invalidated and can be slashed (on networks with a ValidatorSlasher contract). Because validation is separated from execution, a node cannot approve its own payment for a tampered result.
On-Chain Proof of eXecution
TrustedZone generates a signed transaction containing the result hash and status code. This Proof of eXecution is written to Polygon or Bloxberg via the _addResultToOrder smart contract method. Anyone can verify on-chain that the computation ran correctly on attested hardware.
How data moves through the system
You encrypt input data with the enclave's public key. Encrypted code, input, and challenge are uploaded to IPFS.
A task request is submitted via the addDORequest smart contract method, containing IPFS hashes and checksums.
The smart contract matches your request to a suitable node based on resource requirements (CPU, RAM, storage, bandwidth).
The matched node downloads encrypted materials from IPFS, acquires enclave Docker images, and establishes SGX enclaves with attestation.
TrustedZone validates, re-encrypts for SecureLock's key. SecureLock runs your code. Enclaves communicate only through shared object storage (SwiftStream/MinIO) — no direct calls.
TrustedZone signs the Proof of eXecution. Result is encrypted, stored on IPFS. Proof is written on-chain. You retrieve and decrypt.
Why this is secure
Hardware isolation — Intel SGX creates encrypted memory regions (enclaves) that even the operating system and hypervisor cannot access.
Separation of concerns — Client code runs only in SecureLock. TrustedZone never executes client code. A malicious payload cannot forge proofs.
Enclave-to-enclave isolation — The three enclaves communicate only through shared object storage. No direct function calls. Each decrypts only data encrypted for its specific key.
Attestation — Mainnet uses real SGX DCAP quotes verified through CAS (Configuration and Attestation Service). Testnet uses self-signed certificates for development.
On-chain verifiability — Every execution proof is public. Anyone can audit.
Supported networks
| Network | Chain | Token | Status |
|---|---|---|---|
| Polygon Mainnet | Polygon | ECLD | Production |
| Bloxberg Mainnet | Bloxberg | ETNY | Production |
| Bloxberg Testnet | Bloxberg | tETNY | Testnet |
| Polygon Testnet | Polygon | tECLD | Testnet |
| IoTeX Testnet | IoTeX | — | Testnet |
| Ethereum Sepolia | Ethereum | — | Testnet |
| LitVM LiteForge | LitVM | — | Testnet |
This site uses cookies to deliver our services. By using our site, you acknowledge that you have read and understood our Cookies Policy and our Privacy Policy Your use of Ethernity's Website is subject to these policies and terms.
I have read and accepted the Cookies Policy