0x4e01546f4e01…4e015472
Chainlink Confidential Compute logs 1 million AWS enclave runs
Chainlink says Confidential Compute completed 1 million workflow runs across more than 170 use cases in roughly 30 days, using AWS Nitro Enclaves and threshold cryptography.

Outputs
1 million workflow runs during early access
More than 170 use cases in roughly 30 days
AWS Nitro Enclaves provide the trusted execution environment
Confidential Compute was announced November 4, 2025
General access is planned for later in 2026
Chainlink said an AWS case study reported 1 million Confidential Compute workflow runs across more than 170 use cases during early access, within roughly 30 days.
The service is Chainlink’s privacy layer for onchain finance. It runs sensitive transaction logic inside AWS Nitro Enclaves, isolated computing environments designed to shield their contents from the outside, including whoever operates the machine.
That combination addresses a sticking point for institutions that have circled tokenization without fully committing: privacy.
What does the privacy layer actually do?
At its core, the framework pairs trusted execution environments, or TEEs, with threshold cryptography. A TEE provides the sealed environment; threshold cryptography divides control over access to sensitive information.
Chainlink uses AWS Nitro Enclaves as that sealed room. A Vault DON, a decentralized oracle network, manages secrets such as credentials through threshold encryption.
No single party holds the whole key. Multiple participants have to cooperate before anything can be unlocked.
When a workflow runs, its confidential portion executes inside an attested enclave. Attestation lets the enclave prove which code it is running, rather than asking everyone to take its word for it.
The Workflow DON then receives the non-sensitive outputs and performs consensus as usual. Private parts stay private, while verifiable outputs remain verifiable. The design also aims to minimize data exposure even if a breach occurs.
Early access reached beyond payments
The AWS case study highlighted the technology’s potential for institutional applications. Chainlink identified three broad target uses:
- Private payments
- Trading
- Eligibility verification
Supported features cover private API access, confidential tokens and transactions, and identity checks that preserve user privacy.
An automated liquidation protection workflow illustrates the model. It can act on a position without revealing the logic behind it.
Chainlink also identified proprietary models and compliance checks as candidates for enclave execution. The early-access program generated the reported volume within roughly 30 days.
The road to general availability
Chainlink announced Confidential Compute on November 4, 2025. The original plan called for early access through the Chainlink Runtime Environment, or CRE, in early 2026, with general access later that year.
Chainlink delivers workflows through CRE. Confidential Compute enters that environment as a privacy capability.
The service builds on Chainlink’s earlier privacy initiatives, including DECO and CCIP Private Transactions.
What does this change for institutions?
A bank cannot put client positions, risk models or compliance logic on a ledger anyone can read. Confidential Compute is designed to keep those operations private while retaining onchain verifiability and composability.
The research findings describe the technology as potentially positioning Chainlink as a leading provider of private transaction infrastructure. Its architecture also creates some reliance on AWS hardware and, by extension, Amazon’s enclave security.
Chainlink presents threshold encryption and the Vault DON as ways to reduce that dependence by spreading control of secrets. For institutions, the practical change is that sensitive computations can run without exposing their inputs, while downstream results remain verifiable onchain.
AWS remains the clearest infrastructure dependency. Organizations evaluating production use still need to weigh the enclave model’s privacy gains against their reliance on AWS and the security of its implementation.
Chainlink’s next milestone is general access later in 2026, after early-access deployments test whether the model can meet institutional privacy, security and compliance demands.
via Crypto Briefing (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,456 articles