Chainlink Confidential Compute logs 1 million workflow runs using AWS enclaves
Chainlink’s Confidential Compute service processed 1 million workflow runs across more than 170 use cases during early access on Amazon Web Services.
Blockchain networks are designed to prove events but struggle to keep data private. Chainlink’s Confidential Compute service addresses this by processing sensitive logic on-chain without broadcasting it to the public ledger.
The system relies on AWS Nitro Enclaves, Amazon’s isolated computing environments, to handle the parts of a transaction that must remain confidential. Secrets are managed through a Vault Decentralized Oracle Network using threshold encryption.
This approach ensures no single party holds the entire key, requiring multiple participants to cooperate before any data is unlocked. A workflow runs its confidential portion inside an attested enclave, which can prove which code it is executing without revealing the underlying logic.
The non-sensitive outputs are then returned to the Workflow DON, where consensus is reached as usual. The private parts remain shielded, while the verifiable parts stay verifiable on the blockchain.
1 million runs in 30 days
The service processed 1 million workflow runs across more than 170 distinct use cases during early access. The figures were highlighted in an AWS case study, which pointed to the technology’s potential for institutional applications.
Supported features include private payments, trading, eligibility verification, private API access, confidential tokens, and identity checks that preserve user privacy. One example cited is automated liquidation protection, where a workflow can act on a position without revealing the logic behind it.
Proprietary models and compliance checks are also named as candidates for enclave execution. The design aims to keep data exposure minimal even if a breach occurs.
Developers clearly want a way to run sensitive logic onchain without broadcasting it to everyone.
Institutional potential
Chainlink announced Confidential Compute on November 4, 2025. The plan called for early access through the Chainlink Runtime Environment, or CRE, in early 2026, with general access to follow later that year.
CRE is the environment through which Chainlink delivers these workflows, with Confidential Compute arriving as a privacy capability inside it. The service builds on earlier Chainlink privacy initiatives, including DECO and CCIP Private Transactions.
A bank cannot put client positions, risk models, or compliance logic on a ledger anyone can read. Confidential Compute is pitched as a way to keep those operations private without giving up on-chain verifiability and composability.
There are trade-offs to watch. Building on AWS hardware introduces some reliance on Amazon’s enclave security. Threshold encryption and the Vault DON are meant to reduce that dependence by spreading control of secrets.