0x62640f646264…62640f61
Chainlink Reports 1 Million Confidential Compute Runs
Chainlink says its AWS-backed confidential computing processed 1 million workflow runs across more than 170 use cases in about 30 days ahead of a planned rollout.

Outputs
Chainlink reports 1 million workflow runs across more than 170 use cases during roughly 30 days of early-access operation.
An AWS case study highlighted the early-access figures.
Chainlink unveiled Confidential Compute on November 4, 2025.
AWS Nitro Enclaves provide isolated execution, while Vault DON distributes control of secrets through threshold encryption.
Early access through CRE was slated for early 2026, followed by broader availability later in the year.
Chainlink says its Confidential Compute processed 1 million workflow runs across more than 170 distinct use cases during roughly 30 days of early-access operation, according to an AWS case study highlighting the figures.
The offering, unveiled on November 4, 2025, is designed to run sensitive onchain workflows “without exposing their confidential data or logic publicly.”
From early access to a scheduled rollout
The AWS case study emphasized the technology’s potential for institutions handling confidential workflow data. Its reported volume covered approximately 30 days of operation.
Under the rollout schedule, early access was slated to begin in early 2026 through the Chainlink Runtime Environment, or CRE, with broader availability later in 2026. CRE provides the underlying framework through which Chainlink runs workflows, while Confidential Compute operates as an embedded privacy feature.
The offering extends Chainlink’s earlier privacy work, including DECO and CCIP Private Transactions.
How execution and key control work
Chainlink Confidential Compute combines AWS Nitro Enclaves with threshold cryptography to keep sensitive operations private while preserving onchain verifiability. Confidential workflow segments execute inside an isolated computing environment rather than becoming publicly visible on a ledger.
AWS Nitro Enclaves provide a trusted execution environment, or TEE. The sealed environment is designed to shield its contents from outside access, including access by the party operating the machine.
The enclave also supports attestation, which provides proof of the code running inside it. After confidential processing finishes, non-sensitive outputs return to the Workflow DON for consensus. Sensitive inputs and logic remain in the enclave; the distributed oracle network handles the verifiable results.
Chainlink manages credentials and other secrets through Vault DON, a decentralized oracle network that uses threshold encryption. Control is distributed among participants, so no single party holds the complete key and multiple participants must cooperate to unlock a secret.
Together, enclave isolation and distributed secret control are intended to reduce reliance on Amazon’s enclave security. The design also seeks to limit data exposure after a breach by keeping confidential execution inside the enclave and passing only non-sensitive results to the Workflow DON.
Where the product is aimed
Chainlink identifies several institutional workloads for the early-access service:
- Private payments and trading, supported by confidential API access, private tokens and private transactions.
- Eligibility verification and automated liquidation protection.
- Compliance checks intended to execute without publishing sensitive decision logic.
- Identity verification that safeguards user privacy.
- Proprietary models, which the company presents as candidates for execution inside an enclave.
In the liquidation-protection example, a workflow acts on a position without exposing the logic behind that action. This allows an automated response to remain confidential while the resulting non-sensitive information can pass through the verifiable workflow.
What does this change for institutional workflows?
For institutions tokenizing assets, privacy has been an obstacle because client positions, risk models and compliance logic cannot be placed on a ledger open to everyone. Chainlink frames the commercial objective as keeping those operations confidential “without giving up onchain verifiability and composability.”
Under the design, selected private operations can run inside the enclave while their non-sensitive outputs reach the Workflow DON for consensus. That gives institutional teams a route to protect confidential workflow components without abandoning verification of the results they choose to publish.
The architecture also leaves two distinct control surfaces for practitioners to assess: AWS provides the hardware-isolated execution environment, while Vault DON participants collectively govern access to secrets. The next concrete checkpoint is the planned early-2026 opening through CRE, followed by broader availability later in 2026. Those dates will show whether confidential execution becomes routine institutional infrastructure rather than remaining an early-access service.
via en.cryptonomist.ch (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles