Blockchain networks are typically closed systems by design, unable to directly access off-chain data or the state of other blockchains. This constraint means Smart Contracts must rely on external oracles or bridging mechanisms to process real-world data, price feeds, or cross-chain interactions—introducing new trust assumptions and security risks.
In this context, Flare Network introduces a novel approach distinct from traditional oracles by integrating data acquisition capabilities directly into the network protocol layer. Flare’s data protocol serves not only price feeds but also extends to cross-chain state verification, positioning Flare as the “data layer” within blockchain infrastructure and providing essential support for multi-chain applications.
Overall Role of the Flare Data Protocol
Flare’s data acquisition mechanism addresses two core challenges: delivering reliable off-chain data to Smart Contracts and securely acquiring status information from other blockchains.
While traditional solutions typically rely on independent oracle networks, Flare embeds this capability as a native network function, making data access an intrinsic part of the blockchain. This design reduces dependence on external systems and enhances both composability and consistency of on-chain data.
What Is FTSO
FTSO (Flare Time Series Oracle) is Flare’s native time series oracle system, designed to provide dynamic data such as asset prices.
Within this system, network participants submit data estimates (e.g., asset prices). The protocol aggregates these submissions using a weighted process to produce the final data output. Data providers are rewarded based on the accuracy of their submissions, creating an incentive-driven data supply model.
Unlike conventional oracles, FTSO is an integral part of the Flare network, operating directly through on-chain consensus and incentive mechanisms.
What Is Flare Data Connector (FDC)
The Flare Data Connector (FDC) is a core component responsible for acquiring and verifying external state on Flare.
Its primary function is to prove that a specific event or data point has occurred on another blockchain or external system—such as confirming a transaction or verifying that an account meets certain conditions.
The FDC utilizes a distributed verification process to convert external information into on-chain, verifiable data, enabling Smart Contracts to execute logic based on real-world events.
FDC architecture, source: Flare Network
How Flare Data Is Verified and Aggregated
Flare’s data framework processes different data types through distinct mechanisms.
FTSO focuses on continuous data (such as prices), with key steps including data submission, outlier filtering, and weighted averaging. FDC, on the other hand, handles discrete events (like transaction status), ensuring data authenticity through multi-party verification.
Together, these mechanisms enable Flare to handle both “continuously changing data” and “event-based data.”
How Flare Differs from Traditional Oracles
Flare’s data mechanisms differ significantly from traditional oracles.
Traditional oracles operate as independent networks, relying on external nodes to supply data to blockchains. Flare, by contrast, embeds its data protocol directly into the network, making data acquisition a native blockchain function.
Key impacts of this approach include:
- The trust model shifts from “node-dependent” to “network consensus-dependent”
- Lower data access costs
- A more integrated system architecture
Flare’s Application Scenarios
Flare’s data acquisition mechanisms support a wide range of use cases.
In DeFi, FTSO delivers real-time pricing for lending and liquidation. In cross-chain applications, FDC verifies asset states. Across broader Web3 scenarios, these mechanisms enable Smart Contracts that depend on real-world data.
These capabilities position Flare as foundational infrastructure for data-driven applications.
Summary
By combining FTSO and FDC, Flare has built a native data protocol system.
This architecture allows blockchains to access price feeds and cross-chain status directly, reducing reliance on external oracles and enhancing both security and composability.
As the multi-chain ecosystem evolves, embedding data capabilities at the network level represents a new direction for blockchain infrastructure.
FAQs
What is the main function of FTSO?
FTSO provides decentralized time series data—such as crypto asset prices—and is a core component of Flare’s data framework.
What data can FDC verify?
FDC can verify events from other blockchains or external systems, such as whether a transaction has occurred or if an account meets specific conditions.
Does Flare eliminate the need for oracles entirely?
Flare still utilizes oracle mechanisms, but its oracle (FTSO) is embedded within the network, not an external, independent service.
Is FTSO data reliable?
FTSO enhances data accuracy through multi-party submissions and incentive mechanisms, and the aggregation process minimizes the impact of outliers.
Why embed the data protocol into the blockchain?
Embedding the data protocol reduces trust dependencies, strengthens security, and makes data a composable on-chain resource.
