A focused explanation of the Flare Data Connector (FDC): what it does and how it lets applications confirm that an event happened elsewhere.
FDC stands for Flare Data Connector. Where the FTSO handles continuously-updating data, the FDC handles a different job: confirming that a specific event happened on another system.
It is the networks’ way of answering the question “can we prove this is true?” in a decentralised manner.
Rather than taking one party’s word for it, the FDC relies on many independent checks. When enough independent participants confirm that an event occurred, an application can act on that confirmation with confidence.
This mirrors the attestation idea: a statement is trustworthy because many independent participants vouch for it, not because a single authority asserts it.
A simple way to remember the difference: continuously-updating data → FTSO; one-off proof that a specific event happened → FDC. Both are made trustworthy by broad, independent agreement.
This article is part of the Flare Portal wiki — a free, independent educational reference. It is a conceptual overview and not a substitute for primary technical documentation.