Bump to version 1.18.0 - #300
Conversation
|
|
||
| ### Confidential Workflows | ||
|
|
||
| A Confidential Workflow is a CRE workflow that designates part of its logic to run inside a secure [enclave](https://docs.chain.link/cre/key-terms#enclave)—a running instance of a [Trusted Execution Environment (TEE)](https://docs.chain.link/cre/key-terms#tee-trusted-execution-environment), a hardware-isolated environment designed to keep the computation and data it processes confidential from the machine's own operator during execution—instead of on Workflow DON nodes. |
There was a problem hiding this comment.
Confidentiality of computation is a future roadmap item. This is disclosed separately in the confidentiality boundary section. Since the SDK, doesn't have this section, could you please update this section to remove any references to confidentiality of computation ("designed to keep the computation", "any computation you mark as confidential"). Proposal below
"A Confidential Workflow is a CRE workflow that designates part of its logic to run inside a secure enclave—a running instance of a Trusted Execution Environment (TEE), a hardware-isolated environment designed to keep the indicated data it processes confidential from the machine's own operator during execution and node operators."
Secrets fetched inside the enclave such as Vault DON secrets, HTTP response payloads, and intermediate computation data remain confidential throughout workflow execution. They also provide DON consensus-based verification of enclave attestations, helping ensure the integrity of confidential workflow execution. You decide what stays inside the enclave and what crosses back out to the Workflow DON for consensus-verified execution, such as generating a report to submit onchain."
2 participants
No description provided.