Pinned post
Flare gives developers built-in access to two things applications usually have to source elsewhere: prices and proofs of external events.
FTSO handles decentralized price data, while FDC verifies supported events outside Flare, including activity on other chains.
Flare Confidential Compute extends this further. Sensitive or heavy logic can run in hardware-secured environments and return a result that contracts can verify onchain.
That means a developer can start from verified data, run logic that does not belong in public execution, and use the result inside an application without stitching together a separate oracle, verification and confidential compute stack.
XRPFi is already one example of what this architecture enables.
Data first. Compute next. Then the applications neither could support alone.
FTSO handles decentralized price data, while FDC verifies supported events outside Flare, including activity on other chains.
Flare Confidential Compute extends this further. Sensitive or heavy logic can run in hardware-secured environments and return a result that contracts can verify onchain.
That means a developer can start from verified data, run logic that does not belong in public execution, and use the result inside an application without stitching together a separate oracle, verification and confidential compute stack.
XRPFi is already one example of what this architecture enables.
Data first. Compute next. Then the applications neither could support alone.
