Seraphim Learn · Confidential Computing
Flare Confidential Computing
Flare Confidential Computing (FCC) brings TEEs into the protocol itself — letting Flare run and verify secure off-chain computation, and sign on other chains, with hardware-backed proofs.
Status: FCC is in its final development stages and not yet live on mainnet. This page explains the design as Flare has described it; treat capabilities as planned, not shipped.
What FCC is designed to enable
- Secure off-chain compute. Run heavier logic — data validation, modelling, AI inference — inside TEEs and bring back an attested result, without exposing inputs or trusting the operator.
- Protocol Managed Wallets (PMW). Flare smart contracts can instruct TEE-held wallets to sign and broadcast transactions on external chains (BTC, XRP, ETH) only when on-chain conditions are met — cross-chain action without a custodian holding user funds.
- Fast data attestation. Instead of posting raw data on-chain, a TEE can attest that consensus was reached off-chain and emit a single signature — cheaper and faster.
How it fits the rest of Flare
FCC complements the data protocols you've met: it can harden how FTSOvalues are produced, accelerate FDC attestations, and give FAssets a path to confidential, custody-free cross-chain signing.
What we're watching (not yet confirmed)
- A firm mainnet launch date.
- Which TEE backend(s) Flare standardises on (e.g. cloud confidential-compute platforms vs bare metal).
- Whether operating FCC infrastructure becomes a reward-relevant requirement for entities.
See how we're preparing: our FCC readiness →. Official docs: https://dev.flare.network/fcc.
Last reviewed June 2026