flare-fcc

Start with the fce-extension-scaffold, a runnable Hello World extension in Go with contracts, deploy tooling, and a types server. You modify the config constants, request/response types, action handlers, and the InstructionSender contract, then follow the pre-build, start-services, post-build, and test deployment phases.

OPType selects an operation group and OPCommand sub-routes within it, and both must match exactly as bytes32 identifiers across the Solidity contract, Go config, and Go router. A mismatched OPType returns unsupported op type; a mismatched OPCommand returns unsupported op command.

Yes, the fce-sign example ships in Go, Python, and TypeScript, selected via the LANGUAGE variable in .env. Python and TypeScript use a Framework class that registers handlers by opType/opCommand pair, though only the Go build is bit-for-bit reproducible across machines.

This error means the attestation challenge expired before registration completed. Re-run post-build.sh and ensure register-tee uses the -command rRap flag, which issues a fresh attestation challenge on re-runs.

MODE=0 is the production attestation backend whose results FTDC accepts on testnet and mainnet, while MODE=1 produces simulated attestation that FTDC rejects. For Coston2 deployment the image must bake MODE=0 with SIMULATED_TEE=false and LOCAL_MODE=false.

No, storing encrypted secrets on-chain is not safe for production because on-chain data is public and encryption weakens over time. The fce-sign example is explicitly demo-only for its on-chain secret storage; use off-chain channels for secret delivery instead.