Understand
Flare glossary
The words of the Flare network, defined simply. Each definition links to its source, usually the official documentation or a governance proposal. Sources read on November 17, 2026.
C
Flare’s Ethereum-compatible chain. This is where the usual wallets, smart contracts, applications, tokens such as WFLR and the data protocols live. When a wallet talks about “the Flare network”, it almost always means the C-chain.
Core Vault
Interoperability
A multisignature vault under the control of governance, where FAssets agents can deposit the original assets they hold. It reduces the collateral agents need to lock up.
See also: FAssets
Sources: Core Vault, Flare documentation · FIP.16, section 4.2
Coston and Coston2
The network
Test networks, with no real value. Coston2 is used to test applications intended for Flare; Coston is used to test protocol changes intended for Songbird.
D
Data provider
Protocols
An entity that takes part in Flare’s data protocols: it submits prices to the FTSO, checks data for the FDC and signs the results. There are about a hundred of them. Its vote power comes from the stake of its validators and from the WFLR delegated to it.
Providers take a fee on the rewards of their stakers and delegators. FIP.16 imposes a minimum fee of 20% across the network.
See also: FSP, FTSO, FDC, Validator
Sources: Flare Systems Protocol, Flare documentation · FIP.16, section 5.2
F
FAssets
Interoperability
A system that brings assets from chains without smart contracts (XRP, bitcoin, dogecoin, litecoin) onto Flare, without a trusted third party. Agents deposit collateral worth more than the value issued (a stablecoin or ETH, plus FLR), then mint the corresponding token (FXRP, FBTC…) when a user sends them the original asset. Redemption works the other way round. The FDC proves the payments, the FTSO provides the prices.
Collateral pools, open to everyone, top up the agents' collateral. Since FIP.16, minting fees and 10% of redemption fees go to FIRE.
See also: FXRP, Core Vault, FDC
A protocol for off-chain computation in secure hardware enclaves (TEE), whose result can be verified on Flare. It is used for private computation, for signing transactions on other chains (the PMW, protocol managed wallets) and for fast attestations. It is live on Coston, Coston2 and, since STP.13 (July 2026), on Songbird; the main network is announced next.
Sources: FCC overview, Flare documentation · STP.13
An oracle built into Flare that brings data from elsewhere onto the chain, for example proof that a payment took place on the XRP Ledger. Data providers check each request; the answer is accepted if more than 50% of the weight confirms it.
There are six attestation types: address validity, EVM transaction, payment, existence of a confirmed block, balance-decreasing transaction, and non-existence of a referenced payment. Attested data is at most 14 days old. The FDC replaced the State Connector (FIP.12, accepted on February 3, 2025). Requests are paid for; since FIP.16, 90% of the fees go to FIRE.
See also: FSP, State Connector, FAssets
Sources: FDC overview, Flare documentation · FIP.12
An entity created by FIP.16 to receive the network’s revenue: 90% of FDC fees, FAssets minting fees, 10% of their redemption fees, a share of FCC fees, the sale of FXRP destination “tags”, and eventually value extracted from transaction ordering (MEV).
Its main mandate is to reduce the supply of FLR as much as possible: replacing inflation in rewards, and buying FLR on the market to burn them. It is administered by the Flare Foundation. Its revenue, epoch by epoch and compared with emission, is tracked on the barometer.
See also: Inflation and emission, FDC, FAssets
Source: FIP.16, sections 4 and 4.5
A layer-1 blockchain compatible with the Ethereum Virtual Machine (EVM), which presents itself as “the blockchain for data”. What sets it apart: data protocols built into the network itself (enshrined), the FTSO for prices and the FDC for data from other chains, run by the same participants who secure the chain.
The network produces a block about every 1.8 seconds, with immediate finality: an accepted block can no longer be reverted. There are four networks: Flare (the main network), Songbird (the canary network), and two test networks, Coston2 and Coston.
FlareContractRegistry
The network
A contract that gives the official address of all the protocol’s other contracts. It has the same address on all four networks: 0xaD67FE66660Fb8dFE9d6b1b4240d8650e30F6019. It is the safe way to find a contract address, rather than copying it from a third-party site.
See also: C-chain
FlareDrops
The token
Monthly payments of FLR to WFLR holders, provided for by FIP.01: the remaining 85% of the distribution, spread over 36 months. The last one took place on January 30, 2026; there are no more.
Sources: FIP.01 · Manage FlareDrops, Flare documentation
The native token of the Flare network, divisible to 18 decimals. It is used to pay transaction fees (which are burned), to stake with validators, to delegate to data providers and to vote on governance proposals.
100 billion FLR were created at the network’s genesis, on July 14, 2022. Distribution to XRP holders began with the TDE on January 9, 2023.
See also: WFLR, Staking, TDE, Inflation and emission
Source: FLR, Flare documentation
The common foundation of the protocols built into Flare. The FSP organises the vote of the data providers, weighted by their weight, and the signing of the results: a result is validated as soon as more than 50% of the weight has signed it (60% in case of delay). The FTSO and the FDC are sub-protocols of the FSP.
See also: FTSO, FDC, Reward epoch, Voting epoch
Sources: Flare Systems Protocol, Flare documentation · Weights and signing, Flare documentation
An oracle built into Flare, which publishes data feeds (mostly cryptocurrency prices) directly on the chain, readable by contracts free of charge. There are two kinds:
- block-latency feeds, updated with every block (about 1.8 seconds);
- anchor feeds, calculated every 90 seconds through a two-step vote (commit, then reveal) among the hundred or so data providers.
The protocol can carry up to 1,000 feeds and keeps two weeks of history.
See also: FSP, Data provider, FDC
FXRP
Interoperability
The FAsset for XRP: a C-chain token backed by real XRP, which can be used in Flare’s applications. It has been live on the main network since September 24, 2025.
See also: FAssets, Smart Accounts
G
Governance
Economics and governance
Changes to the network go through proposals voted on by token holders:
- FIP (Flare Improvement Proposal): proposals for Flare, voted with WFLR and staked FLR. They are rejected by default and pass with more than 50% of the votes cast.
- STP (Songbird Test Proposal): proposals first tested on Songbird, accepted by default unless, with a turnout of at least 75%, more than 50% vote against.
- SIP (Songbird Improvement Proposal): proposals specific to Songbird, modelled on FIPs.
A vote lasts about a week.
See also: WFLR, Staking, Songbird
Sources: Governance, Flare documentation · Proposals directory
I
Inflation and emission
Economics and governance
Newly created FLR used to pay those who secure the network and its protocols: stakers, validators, data providers and their delegators. FIP.01 had set an annual rate of 10%, then 7%, then 5%, capped at 5 billion FLR per year. FIP.16 brought it down to 3%, with a cap of 3 billion.
Each epoch’s emission, split between FTSO, FDC and staking, is tracked on the barometer.
See also: FIRE, Staking, Reward epoch
Sources: FIP.01 · FIP.16, section 2
P
Flare’s chain that keeps the register of validators and of the FLR committed to them. To stake, you first need to transfer your FLR from the C-chain to the P-chain. It uses the word delegation for staking by individuals, hence frequent confusion with WFLR delegation.
See also: C-chain, Validator, Staking
Sources: Network overview, Flare documentation · Register a validator, Flare documentation
Wallets on other blockchains (XRPL, Bitcoin) controlled by smart contracts on Flare. A contract requests a payment; the transaction is assembled and signed by TEE machines that each hold a key, as signers of a “k of n” multisignature account: k keys out of n are enough to authorise the operation. Instructions are passed to the machines only with the agreement of data providers representing more than 50% of the weight, and the FDC then proves whether the payment actually took place.
It is one of the two applications built into the FCC. According to Flare’s documentation, PMW are still in development: they are not available yet.
Sources: FCC overview, Flare documentation · FAQs, Flare documentation
R
Reward epoch
Protocols
A period of 3,360 voting epochs, i.e. about 3.5 days. It is Flare’s basic rhythm: providers' weights are fixed at the start of each epoch, and rewards are calculated and distributed epoch by epoch. All of Flarescope’s figures are calculated at this scale.
See also: Voting epoch, Inflation and emission
S
The native token of Songbird, divisible to 18 decimals, like FLR on Flare. It pays transaction fees on Songbird. In its wrapped form, WSGB, it is used to vote on Songbird’s own proposals: STPs, which test a change before it is proposed on Flare, and SIPs, which concern Songbird only.
SGB is not FLR: the two networks and their tokens are separate. Its initial distribution to XRP holders is covered in the history of Flare.
See also: Songbird, FLR, Governance
Sources: Network overview, Flare documentation · Governance, Flare documentation
Smart Accounts
Interoperability
Accounts that let an XRP Ledger (XRPL) user act on Flare from their XRPL wallet, without holding FLR to pay fees.
Snowman++
The network
The consensus protocol used by Flare on the P-chain and the C-chain: the rule by which validators agree on the next block. It gives the network blocks of about 1.8 seconds and single-block finality.
Songbird
The network
Flare’s “canary” network, with its own token, SGB. New features are deployed there in real conditions before reaching Flare, often through an STP proposal. Its launch is covered in the history of Flare.
See also: SGB, Flare, Governance, Coston and Coston2
Staking
Staking and delegation
Committing FLR on the P-chain to a validator, until a date chosen in advance. It takes at least 50,000 FLR, for 2 weeks minimum. For the whole period, the FLR are locked: no selling, no transfer.
In return, the staker receives a share of the staking rewards and a share of the rewards the validator earns as a data provider. Since FIP.16, P-chain stake weighs 5 times more than delegated WFLR in the calculation of providers' weight, which steers rewards towards staking.
Further reading: Staking or WFLR delegation.
See also: Validator, WFLR delegation, P-chain, FSP
Sources: Register a validator, Flare documentation · FIP.16, section 5.1
State Connector
Protocols
T
The initial distribution of FLR, on January 9, 2023: 15% of the FLR due to XRP holders, based on the snapshot taken on December 12, 2020. The remaining 85% was paid out afterwards in the form of FlareDrops.
See also: FLR, FlareDrops
Sources: FLR, Flare documentation · FIP.01
V
Validator
Staking and delegation
A machine (node) that checks transactions and produces blocks. To register one, the operator must commit at least 1 million FLR of its own for a minimum of 2 months: this is its self-bond. A single entity can run at most 4 validators.
A validator can accept stakers up to 15 times its self-bond. The maximum size of a node went from 200 to 300 million FLR with FIP.16. On Flare, validators are run by data providers: to earn rewards, they need in particular an active self-bond of at least 3 million FLR and an active stake of at least 15 million.
The comparison gives the real yield of each one.
See also: Staking, Data provider, P-chain
Sources: Register a validator, Flare documentation · Rewarding, Flare documentation · FIP.16, section 5.1
Voting epoch
Protocols
A 90-second cycle during which data providers vote on and sign the results of the protocols. A reward epoch contains 3,360 of them.
See also: Reward epoch, FSP
W
A “wrapped” version of FLR, in the standard token format of the C-chain (ERC-20). One WFLR is always worth exactly one FLR: you can wrap and unwrap at will. WFLR are used to delegate vote power to data providers and to vote on governance proposals, without leaving their holder’s wallet.
See also: FLR, WFLR delegation, Governance
WFLR delegation
Staking and delegation
Assigning the vote power of your WFLR to a data provider, on the C-chain. The tokens do not move and remain available at all times. The delegator receives a share of the provider’s rewards, after fees, but no staking reward.
The WFLR weight counted for a single provider is capped at 2.5% of the total WFLR supply. Since FIP.16, a delegated WFLR counts 5 times less than a staked FLR. Note: many wallets also say “delegation” for staking.
See also: WFLR, Staking, Data provider
Sources: Weights and signing, Flare documentation · FIP.16, section 5.1
Does a definition seem wrong or incomplete? The cited sources prevail; this site is independent of the Flare Foundation.