flare-fcc

Explain FCC TEE extension lifecycle, registries, and attestation workflows.

19|5|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/flare-foundation/flare-ai-skills --skill flare-fcc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flare-fcc
Source: https://github.com/flare-foundation/flare-ai-skills/tree/main/skills/flare-fcc-skill
Command: npx skills add https://github.com/flare-foundation/flare-ai-skills --skill flare-fcc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flare Confidential Compute (FCC) enables running code inside Trusted Execution Environments (TEEs) and ties that code to on-chain contracts. This Skill provides domain knowledge and guidance for FCC and TEE extensions—how confidential extensions run inside a TEE, the on-chain TeeExtensionRegistry and TeeMachineRegistry, the InstructionSender contract pattern, the OPType/OPCommand routing model, the instruction lifecycle, the extension action handler, the types server, attestation, and reproducible builds. Use when building, deploying, or reasoning about Flare confidential extensions, including the fce-extension-scaffold, the fce-sign signing example, Confidential Space VMs, code-hash attestation, or registering a TEE on Coston/Coston2.

Core Features & Use Cases

  • Understanding FCC architecture: TEEs, registries, and extension patterns.
  • Designing and deploying confidential extensions with InstructionSender, routing, and attestation.
  • Use Case: Build a TEE extension that handles secure off-chain computations and attested results.

Quick Start

Review the FCC extension scaffold and set up a local environment to explore the extension lifecycle.

Frequently Asked Questions about flare-fcc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do TEE attestation and on-chain registries work in Flare Confidential Compute?

Flare Confidential Compute attestation verifies TEE code integrity, while on-chain TeeExtensionRegistry and TeeMachineRegistry securely map confidential extensions to their verified machines on Coston or Coston2.

How do I build and deploy a confidential compute extension using the FCC scaffold?

Build a confidential compute extension by reviewing the fce-extension-scaffold, implementing the InstructionSender pattern, and configuring OPType routing to deploy attested TEE code on Coston or Coston2.

What is the InstructionSender contract pattern and how does it route instructions?

The InstructionSender pattern routes on-chain commands to confidential TEE extensions using the OPType and OPCommand routing model, managing the full instruction lifecycle from contract to execution.

Do I need reproducible builds for TEE attestation on Flare?

Reproducible builds are required for Flare TEE attestation to ensure the deployed Confidential Space VM code hash exactly matches the hash registered and verified in the on-chain TeeExtensionRegistry.

Can I use Confidential Space VMs with the Flare extension lifecycle?

Confidential Space VMs integrate with the Flare extension lifecycle by running confidential computations inside a TEE, generating attested results verified through code-hash attestation and on-chain registries.

What are the limitations of relying on TEE attestation for confidential compute extensions?

TEE attestation limitations include strict reproducible build requirements and dependency on Confidential Space VMs, meaning any code hash mismatch between build and deployment environments fails on-chain verification.