Wrapped Flare

1. Delegating to the Flare Time Series Oracle (FTSO)

Native FLR cannot be delegated directly. To take part in the FTSO system, users first wrap FLR into WFLR. WFLR balances are then used as “vote power” that can be delegated to up to two FTSO data providers per address.

FTSO providers submit price and data feeds to the network and receive FLR rewards based on accuracy. Those rewards are shared with users who delegated WFLR to them, so holding and delegating WFLR is the standard way to earn FTSO rewards.

2. Governance voting

WFLR is also the token used to express governance vote power on Flare. The white paper defines WFLR as the ERC-20 token that tracks and delegates both FTSO vote power and governance vote power, making wrapped tokens the primary instrument for on-chain decision-making.

Holders can either vote directly or delegate their WFLR-based vote power to another address without transferring the tokens themselves. This delegation model lets tokens stay liquid while still participating in oracle and governance processes.

3. Eligibility for FlareDrops and incentive programs

A key ongoing use of WFLR is eligibility for FlareDrops, the monthly FLR distributions to network participants. Official Flare guidance states that users who hold WFLR (and/or stake FLR) during each snapshot period receive a proportional share of each FlareDrop, and delegated WFLR continues to accrue these rewards.

Because WFLR is the token tied to both delegation and drops, many users convert a portion of their FLR into WFLR and keep it wrapped over time to maximize their share of these distributions.

4. General DeFi and dapp interactions

WFLR can be used anywhere an ERC-20–style token is required inside the Flare ecosystem, including:

• As a deposit or liquidity asset in DeFi applications

• As collateral or a reward token in third-party protocols

• For integrations that expect a standard token interface rather than the native gas token

Wrapping FLR into WFLR allows it to interact with smart contracts in a standardized way and simplifies integration with wallets and dapps that recognize token contracts rather than native assets.

5. Maintaining liquidity while delegating

One design goal of WFLR is to let users delegate vote power without locking their tokens. When WFLR is delegated:

• The user keeps full custody of the WFLR

• WFLR remains transferable and can still be used in other on-chain actions

• Vote power follows the user’s WFLR balance automatically, updating if the balance changes

This “detachable vote” behavior means WFLR holders can participate in FTSO and governance while retaining the ability to move or unwrap tokens at any time, subject to gas fees paid in FLR.

Wrapped Flare is not a separate project with its own founding team. It is a core token mechanism of the Flare Network, introduced in the Flare white paper as the way to add programmable governance and delegation functions to the FLR token.

Flare Network itself was founded by:

• Hugo Philion – co-founder and CEO of Flare Networks, with a background as a derivatives trader and a master’s degree in machine learning from University College London (UCL)

• Sean Rowan – co-founder with research and engineering experience in distributed systems and networking, also associated with UCL

• Naïri (Nairi) Usher – co-founder and chief scientist, with a background in quantum information and related research fields

The founders first outlined the network and its original Spark token in the 2020 Flare white paper. Wrapped FLR (WFLR) appears in Flare’s v2.0 documentation as the ERC-20 token issued one-to-one with FLR to enable delegation to the FTSO and governance protocols.

In practice, WFLR is implemented and maintained by the Flare core development team under Flare Networks and Flare Labs, and it is used across the ecosystem by wallets, FTSO providers, and dapps that integrate Flare’s delegation and rewards systems.