What is the Flare Network?

Updated October 23, 2026

Flare is a blockchain built around a specific problem: smart contracts cannot see outside their own chain. Its oracle and State Connector protocols exist to supply that missing information. Updated September 2026.

Flare at a glance

• Purpose: supplying blockchains with external data and cross-chain information

• Core protocols: a decentralised price oracle and the State Connector

• Oracle function: feeds real-world price data into smart contracts

• State Connector function: lets applications verify events occurring on other blockchains

• Compatibility: EVM compatible, so Ethereum tooling and applications work on it

• Consensus: derived from Avalanche's approach rather than proof of work or standard proof of stake

• Token: FLR, used for transactions, delegation and governance

• Data providers: earn rewards based on the accuracy of the data they supply

• Target sectors: decentralised finance, gaming and supply chain verification

The problem Flare addresses

A smart contract executes deterministically from data already on its own chain. It has no native way to learn a currency's exchange rate, whether a shipment arrived, or what happened on a different blockchain.

This is the oracle problem, and it is a genuine technical constraint rather than a marketing framing. Any contract needing external information depends on a mechanism to supply it, and that mechanism becomes a point of trust in an otherwise trustless system.

The two protocols

The price oracle is decentralised: multiple independent providers submit data, and the network aggregates their submissions rather than relying on a single source.

The State Connector allows applications built on Flare to verify events occurring on other blockchains. Rather than trusting a bridge operator's assertion that a transaction happened elsewhere, a contract can verify it.

That second capability is the more interesting one, because cross-chain bridges have been among the largest sources of loss in crypto. A verification mechanism that does not depend on trusting an intermediary addresses a real failure mode.

Interconnectivity

Flare is EVM compatible, meaning contracts and tooling built for Ethereum work on it without rewriting. For developers this removes most of the cost of supporting an additional chain.

The Flare Network uses two protocols

Its consensus derives from Avalanche's approach, which uses neither proof of work nor conventional proof of stake, prioritising fast finality.

FLR tokenomics

FLR is the network's fuel. It pays transaction fees, and holders can delegate tokens to data providers who supply the oracle.

Providers submitting the most accurate data earn the highest rewards, and delegators share in them. This creates a direct financial incentive for accuracy, which is the intended design: the oracle is only as good as its providers' motivation to be correct.

FLR also functions as a governance token, allowing holders to vote on proposals put forward by the Flare Foundation.

One clarification worth making. The source version of this article presented FLR as having a fixed supply and therefore as an inflation hedge, while also describing delegation rewards paid in the same token. Those two statements pull against each other. Check the current emission schedule in the project's own documentation rather than relying on either characterisation, since reward issuance affects circulating supply regardless of any headline cap.

Potential applications

• Decentralised finance: contracts requiring reliable price feeds for lending, derivatives and stablecoins

• Gaming: verifiable in-game events and cross-chain asset ownership

• Supply chain: recording and verifying real-world logistics events on chain

These are use cases rather than deployments. The relevant question for anyone evaluating the network is how many applications actually run on it and how much data the oracle serves, both of which are measurable rather than speculative.

Price history

FLR has performed poorly since public trading began, with a sustained decline from its early levels.

Flare Price History

The Tokenomics of Flare (FLR)

The Beneficial Results of Interconnectivity

That pattern is common among infrastructure tokens: the technical proposition can be sound while the token price falls, because price responds to the broader crypto cycle and to token supply dynamics rather than to whether the protocol works.

Treat the technology and the token as two separate assessments. A useful network does not guarantee an appreciating token, and the two questions have different evidence attached to them.

How to evaluate Flare yourself

• Check how many applications are live on the network, not how many are described as possible

• Look at oracle usage: how many feeds are active and how many providers participate

• Read the current emission and reward schedule in project documentation

• Assess the technology and the token separately, they answer different questions

• Compare regulated venues in our [[crypto brokers|/crypto-brokers]] section before buying

See related material on evaluating crypto projects in our trading guides.

Flare Network: frequently asked questions

What does Flare do?

It supplies blockchains with external information through a decentralised price oracle and the State Connector, which verifies events on other chains.

What is the State Connector?

A protocol letting applications on Flare verify that an event occurred on a different blockchain, without trusting a bridge operator's assertion.

What is FLR used for?

Paying transaction fees, delegating to oracle data providers to share their rewards, and voting on governance proposals.

How do data providers earn?

Rewards are weighted by the accuracy of the data they submit, which creates a financial incentive for correctness.

Is Flare EVM compatible?

Yes. Contracts and tooling built for Ethereum work on Flare without being rewritten.

Why has the token underperformed?

Infrastructure token prices respond to the broader crypto cycle and supply dynamics rather than to whether the protocol functions. Assess the technology and the token separately.