FLARE
FLR
Flare is a blockchain for building applications that are interoperable with other blockchains and the internet. ## What is Flare (FLR)? Flare is an EVM-based Layer 1 blockchain designed to allow developers to build applications that are interoperable with blockchains and the internet. By providing decentralized access to high-integrity data, Flare enables new use cases and monetisation models. ## What makes Flare unique? Flare's native interoperability protocols, the State Connector and the FTSO are secured by the network itself, allowing it to reliably deliver data from a wide variety of off-chain sources in a decentralized way. The Flare Time Series Oracle delivers highly-decentralized price and data feeds to dapps on Flare, without relying on centralized providers. The State Connector protocols enable information, both from other blockchains and the internet to be used securely, scalably and trustlessly with smart contracts on Flare. Risk is minimized by building this decentralized data infrastructure natively into the blockchain, powered by a large number of independent data providers. By incentivizing sets of independent providers to query, acquire, and process data without relying on single, centralized sources, Flare’s core protocols can facilitate the development of interoperable dapps with a broad range of potential innovative use cases. ## What is the Flare (FLR) token used for? FLR is the native token used for payments, transaction fees to prevent spam attacks and staking in validator nodes. FLR can also be wrapped into an ERC-20 variant, WFLR. WFLR tokens serve various functions; they can be delegated to FTSO data providers, for example, or staked to participate in governance. These two uses are not mutually exclusive and do not prevent the tokens from being used in other EVM-compatible dapps and smart contracts on Flare. Wrapped FLR (WFLR) can be minted by depositing native FLR tokens into a smart contract and withdrawing the newly minted
EVERY CLAIM IS SOURCE-LINKED · “—” MEANS NOT VERIFIED, NOT ZERO · METHODOLOGY · REVISIONS
[OVERVIEW]
Mission
Flare is a blockchain for building applications that are interoperable with other blockchains and the internet. ## What is Flare (FLR)? Flare is an EVM-based Layer 1 blockchain designed to allow developers to build applications that are interoperable with blockchains and the internet. By providing decentralized access to high-integrity data, Flare enables new use cases and monetisation models. ## What makes Flare unique? Flare's native interoperability protocols, the State Connector and the FTSO are secured by the network itself, allowing it to reliably deliver data from a wide variety of off-chain sources in a decentralized way. The Flare Time Series Oracle delivers highly-decentralized price and data feeds to dapps on Flare, without relying on centralized providers. The State Connector protocols enable information, both from other blockchains and the internet to be used securely, sc...
Team
Profile source: CoinGecko (coingecko.com · Flare Networks)
[TECHNOLOGY]
Scalability & architecture
- FTSOv2 uses incremental block-latency price updates anchored to 90-second scaling feeds, reducing the cost of repeatedly publishing full price data.Sourcedev.flare.network · Overview
- FDC batches external-data attestations into Merkle roots and lets applications verify individual proofs rather than store every response.Sourcedev.flare.network · Overview
[TOKENOMICS]
[CHART]
TradingView • BINANCE:FLRUSDT[MARKET_DATA]
Last updated: Nov 21, 2026, 11:00 PM UTC
[ECONOMICS]
Trading pairs
| Pair | Exchange | Source |
|---|---|---|
| FLR/USD | Kraken | Source ↗ |
[ECOSYSTEM]
Developer metrics
Community metrics
[UNIQUE_VALUE_PROPOSITION]
Core value proposition
Flare makes external prices and transaction data available inside an EVM chain through native oracle protocols, allowing applications to use assets and information originating outside Flare.Sourcesdev.flare.network · Overviewdev.flare.network · Overview
Key differentiators
FTSOv2 supplies block-latency price feeds backed by a slower full commit-reveal anchor.Sourcedev.flare.network · Overview
FDC brings provider-attested external data into smart contracts with verifiable Merkle proofs.Sourcedev.flare.network · Overview
FAssets applies this infrastructure to representations of external assets, beginning with FXRP on mainnet in September 2025.Sourceflare.network · Fassets Fxrp Is Live On Mainn…
Competitive edge
The differentiator is the combination of data services and an execution environment, with FXRP providing a concrete external-asset use case. Applications still inherit oracle, contract and collateral-management risks.Sourcesdev.flare.network · Overviewflare.network · One Year Of Fxrp On Flare
Target audience
EVM developers needing external data and XRP holders seeking access to lending, collateral and vault applications through FXRP.Sourcesdev.flare.network · Overviewflare.network · One Year Of Fxrp On Flare
[COMPARATIVE]
Competitive positioning
Flare sits between general-purpose smart-contract chains and oracle infrastructure: its documented offering combines native execution, FTSO prices, FDC attestations and FAssets. Assess it as a combined stack rather than comparing headline TPS or treating every external-asset bridge as equivalent.Sourcesdev.flare.network · Consensusdev.flare.network · Overviewdev.flare.network · Overviewflare.network · One Year Of Fxrp On Flare
Strengths
- Built-in price and attestation interfaces reduce the need for each application to assemble its own external-data stack.Sourcesdev.flare.network · Overviewdev.flare.network · Overview
- FXRP provides a shipped application of the data layer rather than only a future interoperability proposal.Sourceflare.network · Fassets Fxrp Is Live On Mainn…
Weaknesses
- External-data correctness depends on provider agreement and underlying sources, beyond consensus on the chain itself.Sourcedev.flare.network · Overview
- FIPs are Foundation-initiated and have no quorum, making participation and proposal agenda important governance considerations.Sourcedev.flare.network · Governance
- FAsset users depend on collateralized agents and a Core Vault as well as smart contracts; FLR exposure is not the same as holding native XRP.Sourceflare.network · One Year Of Fxrp On Flare
Similar projects
[ROADMAP]
Roadmap
FXRP mainnet launchCOMPLETED
- FAssets launched on Flare mainnet with FXRP v1.2 on September 24, 2025.Sourceflare.network · Fassets Fxrp Is Live On Mainn…
FAssets and XRP application expansionCOMPLETED
- The one-year review reports FAssets v1.3 on mainnet in mid-May, Smart Accounts access through Xaman and managed vault deployments. These are project-reported milestones, not independently measured adoption.Sourceflare.network · One Year Of Fxrp On Flare
Risk factors
- FDC and FTSO introduce external-data and provider-liveness dependencies.Sourcesdev.flare.network · Overviewdev.flare.network · Overview
- FXRP adds agent collateral, Core Vault and cross-chain representation risk beyond native-chain execution.Sourceflare.network · One Year Of Fxrp On Flare
- Communication and distribution restrictions can limit product access by jurisdiction.Sourceflare.network · Privacy Policy
Outlook
Bull case: native data services and FXRP applications create useful demand for execution and data. Bear case: oracle failures, collateral stress or weak application uptake outweigh the integration advantage. Monitor audited upgrades and actual application usage rather than extrapolating token value from announced integrations.Sourcesdev.flare.network · Overviewdev.flare.network · Overviewflare.network · One Year Of Fxrp On Flare
[GOVERNANCE]
Governance model
Flare Improvement Proposals are initiated by the Flare Foundation and approved by token-holder voting. Songbird has separate testing and improvement proposal procedures; these should not be conflated with Flare mainnet voting.Sourcedev.flare.network · Governance
Voting mechanism
WFLR and staked FLR determine snapshot voting power. FIPs require more than 50% of votes cast in favor and have no quorum requirement under the documented rules.Sourcedev.flare.network · Governance
Proposal process
The Foundation publishes a proposal, followed by notice, random vote-count block selection and voting on the Flare Portal. Voting normally lasts about one week; proposal-specific rules should be checked.Sourcedev.flare.network · Governance
[SECURITY]
Security audits
- OpenZeppelin · 2026-01View report ↗
- Coinspect · 2025-04View report ↗
Bug bounty program
Flare reports an Immunefi bug bounty for FAssets and prior Code4rena community review. Current reward caps and eligibility were not independently established.Sourceflare.network · One Year Of Fxrp On Flare
Security practices
- Published audit catalog separates FAssets, Smart Accounts, FTSO and other components; users should match deployed contract versions to reviewed scope.Sourcedev.flare.network · Audits
- Flare reports continuous Hypernative monitoring and collateral-and-proof enforcement for FAsset minting and redemption.Sourceflare.network · One Year Of Fxrp On Flare
- FDC requires more than 50% of data-provider signature weight before committing an attestation root. Oracle-provider integrity and availability remain distinct risks from blockchain consensus.Sourcedev.flare.network · Overview
[REGULATORY]
Compliance status
The website states its communications are not intended for people in the United Kingdom and cites FSMA financial-promotion restrictions. This disclaimer is not evidence of a regulatory authorization or a jurisdiction-wide token classification.Sourceflare.network · Privacy Policy
Jurisdictions
- United Kingdom · Website communication restrictionThe published disclaimer directs UK persons to disregard the website and communications.Sourceflare.network · Privacy Policy
[COMMUNITY]
[SOCIAL_MEDIA]
[COMMUNITY_PLATFORMS]
[TECHNICAL_DETAILS]
Block Explorers
Technical specifications
- Source
- CoinGecko
- Source Url
- coingecko.com · Flare Networks
- Categories
- Smart Contract PlatformLayer 1 (L1)DWF Labs Portfolio
- Chain Design
- Flare combines EVM application execution with enshrined price feeds and external-data attestations. FDC proofs validate provider-agreed data against a committed Merkle root; they are not unconditional guarantees that external data sources are correct.Sourcesdev.flare.network · Overviewdev.flare.network · Overview
- Block Interval
- The FTSOv2 documentation describes approximately 1.8 seconds per block; this is a documented interval, not a fresh measured average.Sourcedev.flare.network · Overview
- Consensus Detail
- Snowman++ runs on the P-chain and C-chain. It uses repeated validator sampling, confidence accumulation and stake-weighted soft proposer selection; finality rests on the protocol assumptions rather than proof-of-work confirmations.Sourcedev.flare.network · Consensus
- Supported Platforms