Reference
What it does
The enclave module records and verifies attestations from trusted execution environments. A provider offering confidential compute can prove on-chain that a workload runs inside a genuine hardware enclave with a specific measured configuration, and a tenant can require that proof before their workload — or its data — is delivered.
Attestation evidence is validated against the state machine's expectations, turning "trust me, it's confidential" into a verifiable claim any counterparty can check.
Why it exists: Some workloads cannot leave their trust boundary on faith alone — regulated data, proprietary models, private keys. Confidential computing solves the technical problem; the enclave module solves the marketplace problem of proving it, so confidential capacity can be advertised, verified, and priced like any other attribute.
State
Primary objects
| Concept | Definition |
|---|---|
TEE | Trusted execution environment — hardware-isolated compute whose state the host cannot inspect. |
Attestation | Cryptographic evidence, signed by hardware, of exactly what code runs inside an enclave. |
Measurement | The digest of an enclave's code and configuration that attestation commits to. |
Messages
Messages & queries
Message and query surfaces are documented at implementation level in the module docs ↗ and the source ↗. The objects above are the state those messages create and transition.
Connections
Module interactions
-
x/encryptionWorkload secrets are encrypted for delivery only after attestation verifies. -
x/providerConfidential-compute capability is a provider attribute tenants filter on. -
x/marketOrders can require attested enclave execution as a placement constraint.
Flows
Core flow
- Offer — Providers advertise capability. Confidential-compute capability becomes a filterable provider attribute tenants can discover.
- Require — Tenants constrain orders. Attested enclave execution enters placement constraints for workloads that need it.
- Verify — Attestation is validated. Hardware-signed evidence is checked against the state machine's expectations.
- Deliver — Secrets flow, workload runs. Encrypted payloads deliver post-verification; usage settles through the normal pipeline.
Questions
Asked about x/enclave
What is a TEE?
A trusted execution environment — hardware-isolated compute whose state even the host operator cannot inspect. The enclave module proves workloads actually run inside one.
What is a measurement?
The digest of an enclave's code and configuration that attestation commits to — the precise fingerprint tenants accept or reject in placement constraints.
How is confidential capacity priced?
Like any other attribute: confidential capability is priced by open bidding, with its premium set by supply and demand rather than a vendor price list.
Related