Learn · Basics
What is Flare?
Flare is a layer-1 blockchain that is fully EVM-compatible — but with one unusual property: high-quality data is built directly into the protocol.
Most blockchains can only see their own internal state. They cannot, on their own, know the price of Bitcoin, the result of a sports match, or whether a payment landed on another chain. Flare's design goal is to fix exactly that: it ships enshrined data protocols — oracles that are part of the chain's own consensus rather than bolted on as third-party contracts.
The core protocols
- FTSO (Flare Time Series Oracle) — decentralised price and data feeds, refreshed about every 1.8 seconds (block-latency) and every 90 seconds (anchor feeds). More →
- FDC (Flare Data Connector) — attests external and cross-chain events, returning Merkle proofs a contract can verify. More →
- FAssets — trustless wrapped versions of assets from non-smart-contract chains (BTC, XRP, DOGE). More →
- Smart Accounts — let XRPL users act on Flare without holding FLR. More →
- Confidential Computing (FCC) — hardware-secured computation, in final development. More →
The essentials
- Consensus: Snowman++ (a leaderless, stake-weighted Avalanche-family protocol) with ~1.8s blocks and fast finality.
- Native token: FLR on Flare mainnet (chain ID 14). Wrapping FLR into WFLR unlocks delegation and rewards.
- Networks: Flare mainnet (14), Coston2 testnet (114), the Songbird canary network (19), and the Coston testnet (16).
- Governance: changes ship as Flare Improvement Proposals (FIPs) decided by token-holder vote.
New to all this? The next lesson explains what an oracle is and why a chain needs ~100 independent providers to agree on every number. What is an oracle? →
Last reviewed June 2026