What Is Flare (FLR)? A Simple Explanation

What Is Flare (FLR)?
Flare is its own Layer 1 blockchain for apps that want to use verifiable data from other blockchains and external data sources.
The blockchain is EVM-compatible. The Ethereum Virtual Machine, often shortened to EVM, is the environment where many smart contracts run. Because of that compatibility, developers on Flare can work with familiar Ethereum tools and Solidity knowledge.
The network's native token is FLR. You use FLR, among other things, to pay transaction fees, for staking, delegation to data providers, and governance.
An important part of Flare is that external data functions are built into the network. The Flare Time Series Oracle provides price feeds, among other things. The Flare Data Connector helps smart contracts verify certain events on supported external blockchains.
Because of that, apps on Flare can use not only information within the network itself, but also verifiable information from outside it.
Key Takeaways
- Flare is an EVM-compatible Layer 1 blockchain for apps that want to use external data.
- FLR is used for transaction fees, staking, delegation, and governance.
- The FTSO provides decentralized price feeds, among other things.
- The FDC helps smart contracts verify events on external blockchains.
- FAssets make representations of certain external assets usable in Flare apps.
How Does Flare Work?
Flare uses Proof of Stake and Snowman++ to reach agreement on valid transactions and new blocks.
With Proof of Stake, participants lock up FLR as stake. Validators use that stake to help secure the network. They check transactions, take part in consensus, and can be chosen to propose new blocks. The larger a validator's total stake, the greater the chance it will be selected for a task like that.
Snowman++ is the consensus protocol that determines how validators reach agreement. This protocol originally comes from Avalanche's architecture.
Flare also consists of two important blockchains. The P-Chain is used for staking and validators. The C-Chain is EVM-compatible and is used for smart contracts and app transactions.
Anyone who wants to become a validator themselves has to lock up FLR as their own stake. Other users can delegate FLR to a validator. That way, they can help secure the network without running a validator node themselves.
Flare vs Avalanche
The technical foundation of Flare is similar to that of Avalanche. Both networks use Proof of Stake, Snowman++ and an architecture that includes a P-Chain and C-Chain.
The division of tasks is similar too. In both networks, the P-Chain plays a role in validators and staking, while the C-Chain is EVM-compatible and runs smart contracts. That means developers can work on both C-Chains with many familiar Ethereum tools.
Still, Flare and Avalanche are not the same network. In addition to the P-Chain and C-Chain, Avalanche also has an X-Chain and is set up more broadly as a platform where separate Avalanche L1s can also run.
Flare, on the other hand, focuses heavily on making external data available for smart contracts. To do that, the network has its own built-in protocols, such as the Flare Time Series Oracle and the Flare Data Connector.
For example, the FTSO provides price data and other time series data. The FDC can verify certain events on external blockchains. In addition to their role in consensus, validators can also take part in these Flare protocols as data providers.
So the difference is mainly in the purpose the architecture is used for. Avalanche focuses more broadly on blockchain infrastructure and separate L1 networks. Flare uses a similar technical base, but builds protocols on top of it that let smart contracts use verifiable data from outside the network itself.
Flare (FLR) Overview
What Are FAssets on Flare?
FAssets are token representations of assets from blockchains that do not have smart contract functionality themselves. The goal is to make those assets usable in smart contracts and DeFi applications on Flare anyway.
A so-called agent plays an important role in this. An agent is a participant in the FAssets system that holds collateral.
Suppose someone sends a supported asset to such an agent. The FDC then checks whether the transaction actually happened on the original blockchain. If that's correct, the matching FAsset can be minted on Flare as an ERC-20 token.
That way, an asset from a network without native smart contracts can still be used inside apps on Flare. A concrete example is XRP. Native XRP runs on the XRP Ledger, while FXRP is the representation of XRP on Flare.
So FXRP is not the same as native XRP. It represents XRP within the FAssets system and can therefore be used in smart contracts and other Flare applications.
FXRP went live on Flare Mainnet on September 24, 2025, as the first FAsset.
FAssets use overcollateralization. That means agents have to hold more collateral than the value they represent. An additional collateral pool can provide extra security.
FAssets can be redeemed for the underlying asset again. If an agent becomes undercollateralized or does not follow the rules, liquidation can follow. In that case, holders may receive collateral instead of the original asset.
How Does the Flare Time Series Oracle Work?
The Flare Time Series Oracle, usually shortened to FTSO, provides time series data to applications on Flare. Price feeds are a well-known example.
A price feed consists of a series of price updates that a smart contract can use.
FTSOv2 works with about 100 independent data providers. FLR holders can assign voting power to such providers through staking and delegation. The providers then supply data, with their influence depending on the assigned weight.
FTSOv2 uses different types of feeds. Fast block-latency feeds can be updated with new Flare blocks. There are also Scaling feeds that run a full commit-reveal round every 90 seconds.
In such a commit-reveal process, a data provider first cryptographically commits to the value they want to submit, without making that value public right away. Then comes the reveal.
That way, a provider cannot later change the value they submitted based on what other providers sent in.
Next, a consensus value is determined using a weighted median. A provider's influence counts based on the assigned weight.
Providers can receive rewards for correct contributions. If data is missing, inconsistent, or invalid, they may receive less or no reward.
An FTSO feed is still based on external data supplied by providers. So a price feed is not automatically error-free.
How Does Flare Make Blockchain Data Accessible?
The Flare Data Connector, or FDC, helps smart contracts on Flare check specific events and transaction data from supported external blockchains.
For example, an app may want to know whether a payment on Bitcoin, Dogecoin, or the XRP Ledger actually happened.
Such verification is called an attestation.
For that, data providers collect the requested external data and process the answers in a Merkle tree. A Merkle tree is a way to cryptographically summarize a lot of data.
If more than 50% of the relevant signature weight agrees, the result can be used.
Not all data is stored fully on the blockchain. Only the Merkle root is stored on-chain. That is a compact cryptographic summary of the collected answers.
An application can then retrieve an answer along with a Merkle proof. With such a proof, a smart contract can check whether the answer is really part of the stored data.
The FDC only supports predefined types of attestations and selected data sources. In addition to payment verification, the system can, for example, check whether a confirmed block exists, whether an address is valid, whether a balance-reducing transaction took place, or whether a specific payment did not happen.
So Flare cannot automatically read every possible kind of data from every blockchain.
What Is the Difference Between Flare and Ethereum?
Flare and Ethereum both support EVM-based smart contracts. That means developers on both networks can use many of the same Ethereum tools and Solidity knowledge.
One important difference is consensus. Flare uses Snowman++ together with Proof of Stake. Ethereum uses its own Proof-of-Stake protocol, where validators stake ETH and attest to blocks.
The way external data is handled is different too.
Flare has the FTSO and FDC built into the network as protocols. The FTSO provides price feeds, among other things, and the FDC makes certain events on external blockchains verifiable for smart contracts.
Ethereum smart contracts cannot access external data directly. That is why Ethereum applications often use oracles to make information from outside the blockchain available.
The native tokens also play different roles within their own networks. FLR is used for transaction fees and network participation on Flare. ETH is used on Ethereum, among other things, for staking and transaction fees.
What Are the Pros and Cons of Flare?
Flare combines an EVM-compatible blockchain with built-in data features. That creates extra possibilities for applications, but it also adds more technical dependencies and risks.
What Are the Benefits of Flare?
- Developers can build smart contracts with familiar Ethereum tools and Solidity knowledge.
- The FTSO provides time series data, including price feeds, while the FDC can verify specific events on external blockchains.
- FTSOv2 supports both fast block-latency feeds and periodic commit-reveal rounds.
- FAssets can make certain assets from networks without native smart contracts usable inside Flare applications.
- FLR holders can delegate voting power to FTSO data providers without transferring their WFLR to that provider.
These benefits describe how Flare is technically set up. They do not guarantee that individual applications will be safe, cheap, or widely used.
What Are the Downsides and Risks of Flare?
- The FDC only supports specific types of attestations and selected networks.
- The FTSO and FDC still depend on data providers that supply external information.
- Becoming a validator yourself requires a high personal bond in FLR.
- FAssets add extra complexity because they work with smart contracts, agents, collateral pools, and an external blockchain.
- If collateral is insufficient, an FAsset agent can be liquidated. A holder may then receive collateral instead of the original underlying asset.
- FIP proposals for Flare Mainnet are formally submitted by the Flare Foundation. Holders of WFLR and staked FLR can then vote on those proposals.
Conclusion
Flare is an EVM-compatible Layer 1 blockchain that combines smart contracts with built-in features for external data.
The FTSO provides price feeds, among other things, and the FDC helps smart contracts verify certain events on other blockchains. Through FAssets, representations of certain external assets can also be used inside Flare applications.
FLR is used for transaction fees, staking, delegation, and governance.
The downside is that the data features and FAssets in particular add extra technical components and dependencies. The FDC also does not support every data source or event. With that, Flare is mainly trying to solve one problem: giving smart contracts access to verifiable data from inside and outside its own network.