Why Flare Confidential Compute is the foundation of private DeFi on Flare, and why Encrypted Finance is built on it.
Privacy on chain is one of the hardest problems in the space. There are many beautiful approaches being researched and shipped today. Zero knowledge, fully homomorphic encryption, secure multi party computation, ring signatures, and confidential compute are all valid paths, and the ecosystem is better for having all of them. Different chains have different strengths, and the right privacy primitive is the one that matches what the chain natively offers.
For our Flare deployment we chose Flare Confidential Compute because of what it lets us build for users today, on a live L1, at production scale.
FCC runs the privacy critical code inside attested Trusted Execution Environments. The TEE is a sealed enclave on the CPU itself. Only the code that matches the published attestation hash can ever decrypt the data inside. The chain knows which TEE versions are valid. The chain knows which machines are currently attested. The chain enforces a quorum of these machines for every privileged action. This is part of the consensus surface, not bolted on infrastructure. That is what makes Flare uniquely powerful for private DeFi. The primitive is already there, ready to use.
When you wrap a token with Encrypted Finance, your real address pays into our vault and an encrypted note is emitted on chain. That note is a ciphertext that only you can decrypt. The chain sees a commitment hash. Nothing else. When you act on that note, you sign an EIP 712 instruction and hand it to the FCC dispatcher. The dispatcher fans your instruction out to a quorum of attested TEEs. They must agree on the resulting state transition before anything touches the chain. No single TEE can move your funds. No single operator can collude their way to your balance. The math of the quorum is what protects you.
Inside the enclave we run the actual privacy logic. We decrypt your note. We verify the commitment matches what is on chain. We construct the new note. We sign the resulting on chain call. The enclave then forgets everything. Your spending key never touches our servers in cleartext, and never will.
Flare ships FCC as a first class primitive. The infrastructure is already deployed and live. We do not have to ask permission to run TEEs. We do not have to spin up our own attestation server. We do not have to invent a quorum scheme. The chain already has one. That is a year of infrastructure work we did not have to do, and it lets us focus on the part that matters. Building actual private financial primitives.
Beta lands on Coston2 soon.