Understand › Data and oracles

Flare, the blockchain for data: why verifiable information will matter

When producing a text, an image or a figure costs almost nothing, what becomes scarce is proof. Flare was built around this idea: data published by the network itself, verifiable and traceable. What that covers, and what it does not prove.

Flare presents itself as “the blockchain for data” (its website). The phrase sounds like a slogan, but it describes a precise technical choice: the protocols that bring data onto the chain are built into the network itself, and run by those who secure it.

To understand why this choice may matter, start with a question that goes beyond crypto: in a world where anything can be produced, how do you know what is true?

When producing costs nothing, proof becomes scarce

Generative AI writes an article, imitates a voice or fabricates a photo in a few seconds, at almost no cost. Content becomes abundant. What remains scarce is the ability to check where a piece of information comes from and whether it has been altered.

The subject is no longer reserved for specialists:

  • In the World Economic Forum’s Global Risks Report 2026, misinformation and disinformation rank 2nd among global risks over two years, according to a survey of more than 1,300 leaders and experts.
  • The European AI regulation requires providers of systems that generate text, images, audio or video to mark that content in a machine-readable format, so that it is detectable as artificial (Article 50, Regulation (EU) 2024/1689). The rule has applied since August 2, 2026; systems already on the market have until December 2, 2026 (Regulation (EU) 2026/1744).
  • The C2PA, a coalition dedicated to content provenance, publishes an open standard for establishing the origin of a piece of digital content and the edits it has undergone.

These three responses point the same way: it is no longer enough to trust a source, people want to be able to check a proof. But they share a limit: a label says that content was generated by an AI, or who signed it. It does not say whether it is accurate.

Blockchains have the same problem, only sharper

A smart contract sees nothing outside its own chain. To know the price of XRP, whether a payment happened on another blockchain, or to read real-world data, it depends on an oracle, a service that brings it the information. And it trusts it without question: if the data is wrong, the contract acts anyway.

The consequences can be severe. According to the indictment filed by the US authorities, a trader obtained about $110 million in cryptocurrency from Mango Markets, a decentralized exchange, in 2022 by manipulating the price its oracle supplied. That oracle computed the price from several exchanges: by pushing up a token’s price on them, the contract was fooled.

For a contract as for a reader, the questions are therefore the same: who provides the data, how is it checked, and can you trace where it comes from?

What Flare builds into the protocol

Flare’s answer fits in one word: enshrined. Its data protocols are not services added by third-party companies: they are part of the network and, according to the official documentation, they “inherit the economic security of the entire network”. They are run by the data providers, whose weight comes from the FLR that holders entrust to them, through staking or WFLR delegation.

The FTSO, for prices. The FTSO publishes data feeds, mostly prices, that contracts read for free. Each feed is supplied by around a hundred independent providers. The fast feeds are updated with every block, about every 1.1 seconds; the anchor feeds are computed every 90 seconds, through a two-step vote (each provider commits to its answer before revealing it) that discards outliers (FTSO, Flare documentation). A hundred independent sources make a manipulation like the one at Mango Markets more expensive, without making it impossible: providers themselves read market prices, and a thinly traded asset remains easier to manipulate.

The FDC, for facts from elsewhere. The FDC attests facts that happened on other blockchains: a payment on the XRP Ledger, a transaction on Ethereum, the validity of an address. An attestation is only accepted if providers representing more than 50% of the weight confirm it. Only a fingerprint of the results (a Merkle root) is written on the chain; any contract can then check an answer against that fingerprint (FDC, Flare documentation). This mechanism is what makes FXRP possible: the network can prove that XRP really was deposited.

The FCC, for data that is not published. The FCC runs computations in hardware enclaves (TEE): the machine proves which code it ran, without its operator being able to read or alter what it processes. The idea is to act on verifiable results drawn from data that stays private. The FCC runs on Songbird, Flare’s canary network; the main network is announced next (FCC, Flare documentation).

Verifiable, sourced, traceable: three different properties

These words are often used together. They do not mean the same thing, and Flare does not provide all three in the same way.

  • Verifiable: anyone can redo the check. An FDC attestation is checked against the fingerprint written on the chain, without trusting whoever presents it.
  • Sourced: you know who provided the information. Data providers are identified, and their weight is public.
  • Traceable: you can go back through the history. Votes, weights and rewards remain on the chain or in public files. This is what lets this site recompute, every epoch, what each validator paid or what the network earned (barometer): every figure points back to a source file.

One limit remains, and it is essential: a blockchain proves that a consensus attested a piece of data, not that the data is true in the world. If every upstream source is wrong, the oracle reproduces the error. What the protocol provides is the number and independence of sources, the cost of cheating (providers commit weight that earns them rewards) and the ability to check after the fact. That is a lot, but it is not a guarantee of truth.

What remains to be shown

The need for verifiable information will grow; that does not mean Flare will be its infrastructure. Three points are worth following, without taking them for granted:

  • The range of data. Flare’s website announces access to “real-world APIs”. But the attestation types documented so far all concern blockchain facts (list of attestation types). On this site, we have not verified any web data attestation in service on the main network.
  • Actual use. An oracle is only worth something if it is used. Part of what FDC users pay goes to FIRE, whose revenue the barometer tracks epoch by epoch: it is one of the most direct measures of demand.
  • Competition. Other oracle networks exist, on every major blockchain. Flare’s advantage, an oracle built into the network, only carries weight if applications choose to build on it.

Nothing in this article is investment advice. For technical terms, see the glossary.