Flare (FLR) price and market data
Vicalis market state
Held for Jun 23, 2026, 6:04 PM
Volatility: Low
Volatility is low. Trading activity is very low. There are no signs of elevated market stress.
FLR Markets
Coin profile
What matters about Flare (FLR)
Flare (FLR) is the native coin of Flare, a Proof-of-Stake, EVM-compatible layer-one blockchain with enshrined data protocols. The Flare Time Series Oracle, or FTSO, aggregates time-series and price estimates from community-selected providers. The Flare Data Connector, or FDC, produces attestations about events outside Flare's state and anchors a proof root onchain. These are not external oracles paid through a separate token; they participate in Flare's own signing and reward system. FLR provides gas, validator staking, governance and vote delegation through WFLR. Consensus staking on the P-chain and smart-contract activity on the C-chain are distinct procedures, while delegating WFLR to an FTSO provider is not the same as delegating stake to a validator. FAssets adds another circuit: overcollateralized representations of external-chain assets use FTSO prices and FDC payment proofs, with FLR eligible for community collateral pools. This integration makes FLR a connecting asset between L1 security, data quality and cross-chain collateral, but it also places those risks inside one economic system.
What it is used for
On the C-chain, FLR pays for transactions and EVM calls, and all transaction fees are burned. A holder can wrap it one-for-one into WFLR to delegate FTSO vote power and participate in governance while retaining compatibility with applications. For consensus staking, FLR is moved from the C-chain to the P-chain and locked with a validator for a selected period; that is a separate action with its own limits and operational exposure. FDC requests carry a fee: a confirmed request rewards data providers, whereas the fee for an unconfirmed request is burned. In FAssets, users can provide FLR to agent collateral pools, while liquidators and challengers help preserve the backing of representations of BTC, XRP, DOGE and other supported assets. Use should be measured through the accuracy and independence of FTSO providers, useful FDC request volume, applications that actually consume proofs, stake distribution and FAssets collateral net of obligations. A large feed or transaction count says little if no economic action follows and rewards simply circulate among related participants.
What can move the price
- More applications that require fast FTSO feeds and verifiable FDC attestations can create specific demand for block space and paid requests. The strongest cases are lending, settlement and cross-chain logic that cannot be replaced easily by a developer's internal server. Recurring requests and independent consumers matter more than the announced number of supported data sources.
- Flare links FLR to validator stake, WFLR delegation and common participation requirements across FTSO, FDC and consensus. If rewards attract independent operators without concentrating weight under a few brands, more coins can remain committed to network roles. The reverse can occur when delegators chase short-term payouts without examining provider quality or concentration.
- FAssets growth can lock more FLR in collateral pools and increase FTSO and FDC use. The net effect still depends on collateral ratios, liquidations, collateral release, protocol rewards and fee burning. More FAssets are constructive only when external backing and redemption liquidity remain sound; nominal issuance supported by weak agents can instead add risk to FLR.
Key risks
- FTSO and FDC inherit network economics, yet data quality still depends on provider conduct and distribution. Correlated sources, concentrated delegations or delays can give a price or attestation sufficient weight even when independence is weaker than it appears. A contract that accepts one proof type without limits or emergency logic magnifies the effect of bad data.
- FLR has several operational states: native C-chain coin, WFLR in contracts and stake on the P-chain. Transfers between chains, address selection, lock duration and two forms of delegation create user-error and temporary-liquidity risk. Wrapping preserves parity at the contract level but adds application exposure; staked FLR cannot be treated as instantly available collateral elsewhere.
- FAssets combines the risk of an external network, agents, FTSO prices, FDC attestations, smart contracts and liquidation liquidity. A sharp move in the underlying asset or a delayed external payment can trigger liquidations and FLR-pool withdrawals even while Flare consensus works normally. Governed parameters and upgrades add model risk: an audit of one release reduces but does not remove the risk introduced by a later version.
What makes it different
Flare belongs in a comparison with both EVM L1s and standalone oracle networks. A conventional L1 supplies consensus and contract execution while developers choose an outside price feed or cross-chain relayer. An oracle network supplies data to many other chains and secures its own operator set. Flare combines these layers: validators and data providers participate in a shared weight and reward system, FTSO supplies enshrined feeds, and FDC anchors Merkle roots of attestations for EVM contracts. That narrows the integration gap and allows FAssets to rely on two protocol services, but it does not erase source-chain or liquidation risk. FLR differs from a pure oracle token because it is also the gas and stake of the base chain; it differs from a typical L1 coin because WFLR delegation and FLR rewards directly participate in producing data. The practical advantage is proven when applications choose the built-in proofs for their quality and security, rather than only because ecosystem subsidies make them cheap.
Market Statistics
Info
What to check before using Flare
A coin price is meaningful only in context: liquidity, trading volume, volatility, market capitalisation and the venues where the asset actually trades.