Curious about a word? Tap a dotted term for its meaning.

Layer 1 / NETWORK PROFILE

Flare

FLR CMC #88 in the snapshot

An EVM smart-contract network with native protocols for price data and verification of external events, designed for applications that depend on information beyond their own ledger.

Profile checked Asset ranks captured 14 Nov 2026Snapshot & methodology ↗

01 / THE PURPOSE

What is Flare for?

Flare brings data acquisition into the network’s infrastructure. Applications can consume time-series feeds through FTSO and request verification of supported external events through the Flare Data Connector, or FDC.

02 / THE ARCHITECTURE

Three questions about the machinery.

01

How does it agree?

Consensus & security

Proof-of-stake validators secure the blockchain. Data-provider participation and weighted protocol voting support the separate data services, so blockchain agreement and the correctness of external information are related but distinct questions.

02

Where do instructions run?

Execution model

Applications use the EVM and can call the network’s data protocols. FAssets uses those protocols with collateral and agents to represent supported external assets in Flare applications.

03

What is the token for?

FLR in the system

FLR pays network transaction fees and supports staking. Wrapped FLR enables delegation of data-provider voting power and participation in governance, with the relevant roles governed by each protocol’s rules.

03 / THE DESIGN CHOICES

What comes with the design?

Each architecture makes choices about security, performance, coordination, and who can participate.

  • Data protocols still depend on supported sources, provider behavior, and the conditions used to decide whether an answer is valid.

  • A collateralized asset representation adds liquidation, agent, contract, and redemption dependencies beyond the original asset’s network.

  • Combining several infrastructure roles requires examining provider concentration across those roles, not only counting validator identities.

04 / IN PRACTICE

Follow one use.

A collateralized application reads an FTSO price before deciding whether a position satisfies its rules. The contract executes on Flare, but its decision is only as useful as the feed and risk parameters it uses.

05 / CHECK THE EXPLANATION

Sources & snapshot.

Network descriptions use the references below. The CoinMarketCap snapshot determines which assets are in scope and their captured rank; it does not assess the quality of a network.

Profile checked 14 Nov 2026. Network designs and ranked positions can change.