Learn · Confidential Computing
Our FCC readiness
Seraphim Lab is preparing Seraphim FTSO for confidential computing now, so that when FCC ships we can adopt it quickly and credibly — rather than scrambling afterwards.
What "getting ready" means for an oracle operator
The skills FCC will demand are learnable today on existing confidential-compute hardware. Our readiness track is a hands-on proof-of-concept:
- Stand up a confidential VM (AMD SEV-SNP to start, evaluating Intel TDX) and confirm it boots in confidential mode.
- Verify attestation — fetch the enclave's signed quote and validate the signature chain off-chain, proving "this code ran in a genuine enclave."
- Compute in the enclave — fetch a price inside the TEE and bind it to the attestation.
- Post to testnet — submit the attested datum to a contract on Coston2 and verify it on-chain.
- Publish a how-to — share a public, redacted write-up so other operators can follow.
This is forward-looking R&D, kept deliberately separate from our production oracle. We'll link the proof-of-concept write-up here as milestones land. Background: TEEs explained · Flare Confidential Computing.
Nothing here describes production keys or infrastructure; it's an account of how we're building readiness.
Last reviewed June 2026