flare-fcc

Start from the fce-extension-scaffold repo, define matching OPType and OPCommand constants in your Solidity InstructionSender and Go config, implement handlers in internal/extension/extension.go, then deploy on Coston2 using the pre-build, start-services, post-build, and test scripts.

The InstructionSender is your own deployed contract and the only address allowed to submit instructions for your extension. It must know its extension ID, call sendInstructions on TeeExtensionRegistry with valid params, be payable to forward the per-instruction fee, and exist before registration.

Yes, the fce-sign example ships in Go, Python, and TypeScript, selected via the LANGUAGE variable. Python and TypeScript use a Framework class that registers handlers by opType and opCommand pair, though only Go achieves bit-for-bit reproducible builds 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 each run.

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 demo-only for its on-chain secret storage; production systems should deliver secrets through off-chain channels.