Question
Provide a concise narrative that clearly states each of (a)–(e) below.
Response
Flare is a layer 1 Ethereum Virtual Machine (EVM) based blockchain built for interoperability, so that smart contracts can acquire data from other blockchains and time series data onchain in a decentralized way. It has two native protocols, the Flare Time Series Oracle (FTSO) for time series data such as prices and the Data Connector, which the whitepaper calls the State Connector, for attesting to events on other blockchains. FAssets build on these protocols to bring non-smart contract assets such as XRP into DeFi on Flare.
(Source: Flare Whitepaper v2, Flare Labs, GitHub, fassets)
The Flare Foundation funds ecosystem growth from its 9,787,578,628 FLR genesis allocation and from the 20,000,000,000 FLR Incentive Pool, which it has drawn on for the FIP.09 DeFi emissions program and for the 2,200,661,869 FLR FAssets Incentive Program that ran from July 2025 through July 2026. Under FIP.16, approved on April 24, 2026, Flare cut annual inflation to 3% and created the Flare Income Reinvestment Entity (FIRE), which routes protocol revenue first to FLR supply reduction and secondarily to ecosystem growth and Foundation sustainability. The scheduled FlareDrop distributions ended on January 30, 2026, and Flare states that no further programmatic FLR distributions are scheduled.
(Source: FLR Token Docs, FIP.09, FAssets Incentive Program, FIP.16, From Activity to Value Accrual, Our Plan for FLR, Beyond FlareDrops)
Flare runs a proof of stake network in which validators secure the chain with staked FLR. FTSO data providers submit price feeds weighted by the vote power that FLR holders delegate to them through wrapped FLR (WFLR), and the Data Connector lets the network attest to events on other blockchains. All FLR paid as transaction fees is burned, and new FLR is minted as inflation that funds FTSO, Data Connector and validator rewards.
(Source: FLR Token Docs, Flare Whitepaper v2, Flare Labs, Flare Explorer API, InflationAllocation Logs, Flare Explorer API, FtsoRewardOffersManager, Flare Explorer API, FastUpdateIncentiveManager, Flare Explorer API, FdcHub, Flare Explorer API, ValidatorRewardManager)
FLR is staked to validators to secure the network, delegated to FTSO data providers for rewards, used to vote on Flare Improvement Proposals as WFLR or staked FLR, and paid as transaction fees, all of which are burned to deter spam.
(Source: FLR Token Docs, Flare Governance Docs)
The Flare Foundation initiates every Flare Improvement Proposal, holders of WFLR and staked FLR accept or reject it by simple majority of votes cast with no quorum, and the Foundation carries out proposals that need offchain or manual execution. Onchain, the GovernanceSettings contract names a 6-of-11 Gnosis Safe as the governance address, with a 3,600-second timelock and eight registered executors, and the Safe signers are not publicly named. FIRE is administered initially by the Foundation with a committee planned, and moving it to joint governance requires a vote with at least 50% of total inflatable supply in favor.
(Source: Flare Governance Docs, Flare Explorer API, GovernanceSettings Genesis Initialisation, Flare Explorer API, GovernanceSettings Logs, Flare Explorer API, Governance Safe Setup Logs, Flare Explorer API, Governance Safe AddedOwner Logs, Flare Explorer API, Governance Safe RemovedOwner Logs, Flare Explorer API, Governance Safe ChangedThreshold Logs, From Activity to Value Accrual, Our Plan for FLR)
Question
For each existing entity: Labs/DevCo (e.g., Founder, CEO, CTO, COO), Foundation (e.g., President, Executive Director, CFO, COO), and DAO / onchain governance leadership (if applicable) list the: (a) full names, (b) official titles, (c) and prior experience of key team members. For any non-existent entity, explicitly mention it does not exist. External links may be included but they will not factor into the score.
Response
Full Name | Entity | Official Title | Prior Experience |
|---|---|---|---|
Hugo Philion | Labs/DevCo | He is Co-founder of Flare and CEO of Flare Labs, and he was described as Flare CEO in June 2026 (FIP.09, Native FLR Spot Listing on Hyperliquid, CoinCentral, Flare CEO Reveals XRPFi Push). | He was a derivatives trader managing portfolios for major funds and then studied machine learning at University College London, where he met Flare's other co-founders (FIP.09, Kraken, Flare Token Disclosure). |
The Flare Foundation exists as a non-profit entity incorporated in the Netherlands, and no director, executive or other officer of the Foundation is publicly named (Flare Whitepaper v2, Flare Governance Docs). | Foundation | No official titles are published for Foundation officers. | No Foundation officers are named, so there is no prior experience to report. |
Flare has no DAO entity. Onchain governance runs through WFLR and staked FLR votes on Foundation-initiated proposals and through a 6-of-11 Gnosis Safe whose signers are not publicly named (Flare Governance Docs, Flare Explorer API, Governance Safe Setup Logs, Flare Explorer API, Governance Safe AddedOwner Logs, Flare Explorer API, Governance Safe RemovedOwner Logs, Flare Explorer API, Governance Safe ChangedThreshold Logs). | DAO/Onchain Governance | No individual governance titles are published for the Safe signers or for the FTSO Management Group members. | No governance officeholders are named, so there is no prior experience to report. |
Question
Provide a structured description of the DAO's governance, powers, and economic rights. If a DAO does not exist, state so. Address the lettered items below. Even if there is no DAO, there must be an answer to (d).
Response
Flare does not have a DAO, and no governance body owns or controls IP. The core smart contract and FAssets repositories are released under the MIT license with a Flare Foundation copyright notice, and Flare Labs built the Flare and Songbird software and licensed it to the Flare Foundation.
(Source: GitHub, flare-smart-contracts-v2 License, GitHub, fassets License, Flare Labs, Flare Governance Docs)
Flare Improvement Proposals are initiated by the Flare Foundation and pass if more than 50% of votes cast by WFLR holders and FLR stakers are in favor, with no quorum. Changes inside protocol smart contracts are executed through governance contract calls, and the Foundation executes proposals that need offchain or manual work. The GovernanceSettings contract at 0x1000000000000000000000000000000000000007 was initialised at genesis with the Gnosis Safe at 0xbe653c54df337f13fcb726101388f4a4803049f3 as the governance address, which its code allows to change only by hard fork. Its event log shows the timelock on governed calls set to 3,600 seconds in September 2022 and eight executor addresses set in August 2024. The Safe was created with nine owners and a threshold of six, and its logs record nine owner additions, seven removals and no threshold change, which leaves a 6-of-11 Safe. The owners and executors are not publicly identified. The FTSO Management Group of eligible data providers votes on chilling misbehaving providers, adding FTSO feeds and FDC attestation types and adjusting parameters under FIP.11 and FIP.12, and its votes pass only when 66% of members vote and more than 50% of members vote in favor, after which the Foundation applies a chill. No standing pause role is disclosed.
(Source: Flare Governance Docs, FIP.02, Flare Explorer API, GovernanceSettings Contract, Flare Explorer API, GovernanceSettings Genesis Initialisation, Flare Explorer API, GovernanceSettings Logs, Flare Explorer API, Governance Safe Setup Logs, Flare Explorer API, Governance Safe AddedOwner Logs, Flare Explorer API, Governance Safe RemovedOwner Logs, Flare Explorer API, Governance Safe ChangedThreshold Logs)
FLR staked to validators earns validator rewards and carries voting power on Flare Improvement Proposals alongside WFLR. Voting power equals eligible WFLR and staked FLR held at a randomly selected Vote Count Block, and holders can transfer their votes to one other address without moving tokens. Stakers and WFLR holders can accept or reject proposals, and the governance docs list the Flare Foundation as the initiator of every proposal type. Since the go-flare v1.14.0 upgrade with a Flare deadline of July 14, 2026, a single validator can hold up to 300 million FLR of stake and validators charge a minimum 20% delegation fee.
(Source: Flare Governance Docs, FLR Token Docs, GitHub, go-flare v1.14.0 Release)
FLR holders have no right to a share of protocol revenue or to distributions from any treasury. All FLR paid as transaction fees is burned, and FIP.16 directs protocol revenue collected by FIRE first to reducing FLR supply. Rewards to stakers, delegators and FTSO participants come from inflation, which the InflationAllocation contract allocates 24.5% to FTSO reward offers, 10.5% to FTSO fast updates, 35% to the FDC hub and 30% to validator rewards. Holders influence treasury and monetary policy only by voting on Foundation-initiated proposals.
(Source: FLR Token Docs, FIP.16, Flare Explorer API, InflationAllocation Logs, Flare Explorer API, FtsoRewardOffersManager, Flare Explorer API, FastUpdateIncentiveManager, Flare Explorer API, FdcHub, Flare Explorer API, ValidatorRewardManager, Flare Governance Docs)
No DAO legal wrapper exists for Flare, so no party holds authority to dissolve one. The governance docs set out no wind-down mechanism for the network's governance. The FIP.09 Emissions Committee is the one governance body with a published dissolution path, which is a governance proposal on Songbird and then Flare to defund and dissolve it.
(Source: Flare Governance Docs, FIP.09)
Question
For the Primary Foundation do the following independently. If an entity does not exist, state that explicitly. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist.
Definitions: The primary Foundation and DevCo can be explained as those entities which are directly involved in the issuance of the native token at launch.
Response
The Flare Foundation is a non-profit entity incorporated in the Netherlands, whose remit covers grants, investments, partnerships, research and development, engineering, marketing, proposing and implementing governance, and community and developer relations. The flare.network website is operated by a related entity, Flare Ecosystems Limited, a company incorporated in the British Virgin Islands.
(Source: Flare Whitepaper v2, Flare Privacy Policy)
The Foundation holds the copyright in the core Flare smart contracts and the FAssets system, which are published under the MIT license in the flare-foundation GitHub organization. The Flare and Songbird node software was built by Flare Labs and licensed to the Foundation. The Foundation discloses no subsidiaries, and the relationship between the Foundation and Flare Ecosystems Limited, the British Virgin Islands company that operates flare.network, is not described.
(Source: GitHub, flare-smart-contracts-v2 License, GitHub, fassets License, Flare Labs, Flare Privacy Policy)
The Foundation is the sole initiator of Flare Improvement Proposals, which pass with more than 50% of votes cast and no quorum, and it executes accepted proposals that need manual action. It allocates the 20,000,000,000 FLR Incentive Pool, from which FIP.09 drew about 510,000,000 FLR for DeFi emissions and the FAssets Incentive Program drew 2,200,661,869 FLR for July 2025 through July 2026. FIP.09 emissions are directed by a six-member Emissions Committee that changes its membership by majority and may not give more than 33% of a quarterly budget to one protocol. The Foundation administers FIRE at launch, and moving FIRE to joint governance requires a vote with at least 50% of total inflatable supply in favor. The Foundation chills FTSO data providers after a Management Group vote passes with 66% participation and more than 50% of members in favor.
(Source: Flare Governance Docs, FIP.09, FAssets Incentive Program, From Activity to Value Accrual, Our Plan for FLR, FIP.02)
The Foundation has no disclosed ownership of or contractual control over Flare Labs. Its influence over Labs is indirect, since Labs licenses its software to the Foundation and Labs CEO Hugo Philion serves on the Foundation-proposed FIP.09 Emissions Committee.
(Source: Flare Labs, FIP.09)
The GovernanceSettings contract was initialised at genesis with a Gnosis Safe as the governance address of Flare's system contracts, and its event log shows a 3,600-second timelock on governed calls and eight executors. The Safe's logs show nine owners and a threshold of six at creation, then nine owner additions, seven removals and no threshold change, which leaves a 6-of-11 Safe. Flare does not publish which entity or individuals hold the Safe keys or the executor addresses, and the Foundation's documented role is to propose and implement governance. The Foundation holds no disclosed separate pause role.
(Source: Flare Explorer API, GovernanceSettings Genesis Initialisation, Flare Explorer API, GovernanceSettings Logs, Flare Explorer API, Governance Safe Setup Logs, Flare Explorer API, Governance Safe AddedOwner Logs, Flare Explorer API, Governance Safe RemovedOwner Logs, Flare Explorer API, Governance Safe ChangedThreshold Logs, Flare Whitepaper v2)
The Foundation received 9,787,578,628 FLR at genesis, of which 85% was escrowed and released over 36 months, and its allocation includes tokens reserved for backers. Its tokens cannot be delegated, cannot claim FlareDrops and cannot vote. Under FIP.16, FIRE collects protocol revenue, including 90% of FDC attestation fees routed to the protocol incentive side, and Foundation sustainability is one of its secondary mandates after supply reduction. FIRE had collected about $29,400 as of September 1, 2026. No transaction fees are directed to the Foundation, because all transaction fees are burned.
(Source: FLR Token Docs, Flare Whitepaper v2, From Activity to Value Accrual, Our Plan for FLR, FIP.16, Crypto Times, Flare FIRE Revenue Doubles)
Question
For the Primary DevCo do the following independently. If an entity does not exist, state that explicitly. Items (a)–(f) apply only if that entity exists; state explicitly that the entity doesn't exist.
Definitions: The primary Foundation and DevCo can be explained as those entities which are directly involved in the issuance of the native token at launch.
Response
Flare Labs is the development company behind Flare and is led by CEO Hugo Philion. Kraken's token disclosure lists its genesis allocation under the name Flare Networks Limited, and the same name appears in the copyright header of the GovernanceSettings contract. Its jurisdiction of incorporation is not published.
(Source: Flare Labs, Kraken, Flare Token Disclosure, Flare Explorer API, GovernanceSettings Contract, FIP.09)
Flare Labs built the software that runs the Flare and Songbird blockchains and licensed it to the Flare Foundation, and it supports the Data Connector and FTSO protocols and is developing FAssets. The public repositories for these products carry Flare Foundation copyright notices under the MIT license. Flare Labs discloses no subsidiaries, and its relationship to the separately allocated Flare VC Fund is not published.
(Source: Flare Labs, GitHub, flare-smart-contracts-v2 License, GitHub, fassets License, FLR Token Docs)
Flare Labs holds no disclosed power over treasury actions or token administration. Its 12,965,300,324 FLR allocation can be delegated to the FTSO and can vote on Flare Improvement Proposals, where votes pass by more than 50% of votes cast. Its CEO Hugo Philion sits on the six-member FIP.09 Emissions Committee, which directs Incentive Pool emissions to dApps by majority within a 33% per-protocol cap.
(Source: FLR Token Docs, Flare Governance Docs, FIP.09)
Flare Labs has no disclosed ownership of or control over the Flare Foundation. It holds indirect influence because it licenses the network software to the Foundation, because its allocation can vote while the Foundation's cannot, and because its CEO sits on the Emissions Committee that directs Foundation-funded emissions.
(Source: Flare Labs, FLR Token Docs, FIP.09)
Flare Labs holds no disclosed pause, upgrade or executor authority. Governed contract calls run through the 6-of-11 Gnosis Safe set as governance address in the GovernanceSettings contract, with a 3,600-second timelock, and Flare does not publish whether any Labs personnel are among its signers.
(Source: Flare Explorer API, GovernanceSettings Genesis Initialisation, Flare Explorer API, GovernanceSettings Logs, Flare Explorer API, Governance Safe Setup Logs, Flare Explorer API, Governance Safe AddedOwner Logs, Flare Explorer API, Governance Safe RemovedOwner Logs, Flare Explorer API, Governance Safe ChangedThreshold Logs)
Flare Labs received 12,965,300,324 FLR at genesis, distributed over the 36-month schedule, and this allocation includes tokens reserved for backers. Labs tokens cannot claim FlareDrops. No transaction fee, revenue or reward stream is directed to Flare Labs.
(Source: FLR Token Docs)
Question
Disclose launch and initial supply details in a single initial allocation schedule covering the token's launch.
Response
The Flare genesis block created 100,000,000,000 FLR on July 14, 2022. At the Token Distribution Event on January 9, 2023, 4,278,738,206 FLR was distributed unlocked to wallets that held XRP on December 12, 2020, and the remaining allocations were released over the following 36 months.
(Source: FLR Token Docs)
The listed buckets total 97,878,611,520 FLR. The derived difference of 2,121,388,480 FLR from the 100,000,000,000 FLR genesis supply matches the about 2.1 billion FLR of backer tokens that Flare agreed to burn.
(Source: FLR Token Docs, Flare Whitepaper v2, Flare to Burn 2.1 Billion FLR)
No fixed price was set for FLR. The tokens were distributed without a sale to XRP holders through more than one hundred exchanges and directly to eligible wallets, and the market set the price when trading opened. Kraken's first FLR/USD trade printed at $0.15 on January 10, 2023, the day OKX opened FLR spot trading.
(Source: Flare TDE Update, Kraken API, FLR/USD Trades, OKX, FLR Airdrop and Spot Trading)
FLR.
(Source: FLR Token Docs)
FLR has no fixed supply and no maximum supply. Genesis created 100,000,000,000 FLR. As of 2026-10-12, CoinGecko reports a total supply of 106,738,740,820 FLR, a circulating supply of 87,152,588,714 FLR and no maximum supply, and the burn address holds about 4,244,359,919 FLR. Derived from these figures, about 10.98 billion FLR of net inflation has been minted since genesis (106.74 billion minus 100 billion plus 4.24 billion burned). Under FIP.16, annual inflation is 3% of inflatable supply with a hard cap of 3,000,000,000 FLR a year, and the InflationAllocation contract logs record a 300 basis point annual inflation rate. All transaction fees are burned.
(Source: FLR Token Docs, CoinGecko API, Flare Networks, Flare Explorer API, Burn Address, FIP.16, Flare Explorer API, InflationAllocation Logs)
(Source: FLR Token Docs, FlareDrops, Flare Whitepaper v2, Backer Agreement and Tokenomics Update, FAssets Incentive Program, Flare Explorer API, FlareSupply Contract)
Question
Address each of the following sub-items based on the project's airdrop status. If a sub-item does not apply to the project's situation, state that explicitly.
Response
Planned but not yet executed airdrop
Not applicable. Both FLR airdrops have been executed, and Flare states that no further programmatic FLR distributions are scheduled.
(Source: Beyond FlareDrops)
Executed airdrop
Flare executed two airdrops. The Initial Token Distribution of 4,278,738,206 FLR went on January 9, 2023 to wallets that held XRP at the December 12, 2020 snapshot, at 0.151095 FLR per XRP out of a total entitlement of 1.0073 FLR per XRP, with exchanges crediting many users. The FlareDrop of 24,246,183,166 FLR was paid in 36 monthly drops ending January 30, 2026 to WFLR holders and stakers pro rata to their balances, and Flare entities, employees and founders could not claim. Per-address amounts are exposed by the Flare Explorer API for the InitialAirdrop contract at 0x410d1879d06c1c38cd963ae3d33b309f796bac66, whose internal transactions list each direct transfer, and for the DistributionToDelegators contract at 0x9c7A4C83842B29bB4A082b0E689CB9474BD938d0, whose AccountClaimed event logs record each FlareDrop claim by address, recipient, month and amount.
(Source: FLR Token Docs, , , , )
Question
Projects must disclose all material terms of market-making arrangements that affect token liquidity. If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. For each market maker, include in a table:
If the project has no agreements or deals with market makers, state that explicitly; doing so earns full credit. If no native tokens were loaned or allocated to market makers, state that explicitly; cash/fiat retainers or fees are not required for this item.
Response
Question
Projects must disclose all material terms of centralized or decentralized exchange listings that affect token liquidity. For each listing, include in a table:
If the project has no agreements or deals with CEX or DEX, state that explicitly; doing so earns full credit; cash/fiat fee amounts are not required for this item.
Response
Question
Disclose all prior token sales by the Project — including fundraising rounds, any material OTC sales to investors, and any discounted market-maker sales. For each sale, provide:
If no prior sales occurred, state that explicitly (e.g., "No prior fundraising, OTC, or discounted MM sales have occurred.").
Response
Question
If any, list prior exploits or incidents that directly affected the token, token supply, tokenholder balances, token contract, minting controls, burn mechanics, or custody of token supply. This question is not asking about general protocol, application, or smart contract exploits unless the incident directly affected the native token itself.
If no prior incidents, state this explicitly (e.g., "No exploits affecting tokenholders or protocol funds as of YYYY-MM-DD").
Response
No exploits affecting FLR tokenholders or protocol funds as of 2026-10-12. The one incident that directly affected FLR was a halt of block production on Flare mainnet that ended on 2025-06-26, during which FLR could not be transferred. Upbit suspended FLR deposits and withdrawals during the halt, as reported on June 27, 2025.
(Source: FTSO EU Telegram, Relay of Flare Outage Announcement, CryptoNews, Upbit Suspends FLR Deposits)
The June 2025 incident was an outage and not an exploit. Block production stopped and resumed once validators installed a software update. Flare's announcement said a detailed explanation of the changes would be shared, and no published root cause was found as of 2026-10-12.
(Source: FTSO EU Telegram, Relay of Flare Outage Announcement)
The outage caused no loss of funds. Flare stated that ledger integrity was not affected and that all user assets remained secure and under user control.
(Source: FTSO EU Telegram, Relay of Flare Outage Announcement)
Question
Describe material risk factors across the three categories below. Each category includes prompts to address at a minimum.
(a) Regulatory, Legal & Tax Risks — Describe how evolving laws and regulations could affect the project by answering, at a minimum, questions like:
Impact of Regulatory Change on TGE and Listings: (If applicable) How could evolving or conflicting laws and regulations affect your ability to complete the TGE, deliver tokens to purchasers, and list or maintain the token on trading venues in key jurisdictions?
Entity-Level Regulatory Impact: (If applicable) How could regulatory or legal changes impact your core entities (Foundation, DevCo, DAO, affiliated service providers), including enforcement actions, licensing requirements, or forced changes to structure or operations?
Tokenholder Tax Treatment: (If applicable) What uncertainties exist around how tokenholders may be taxed, and make clear that tokenholders are responsible for understanding their own tax obligations?
Jurisdictional & User Access Restrictions: (If applicable) If the project restricts access for certain jurisdictions or user types (e.g., U.S. persons, sanctioned countries, retail vs. professional), what are those restrictions and what risks do they create for users and for the project?
(b) Protocol, Technology & Security Risks — Describe risks to network and contract reliability, correctness, and safety by answering, at a minimum, questions like:
Bugs and Design Flaws: (If applicable) What bugs, design flaws, or implementation errors could exist in your core protocol code, smart contracts, and any bridges, rollups, or oracles that you depend on, and how could these lead to loss of funds or disruption of the protocol?
Security Measures & Their Limitations: (If applicable) What security measures have you taken (audits, formal verification, bug bounties), and what types of failures might these measures still fail to detect or prevent?
(c) Token Economics, Unlocks & Incentive Risks — Describe how the token's economic design and supply schedule could affect holders by answering, at a minimum, questions like:
Critical Economic Assumptions: (If applicable) Which economic assumptions (e.g., staking yields, fee revenue, liquidity incentives, MEV capture, demand for blockspace) are critical for protocol security, utility, and governance, and what happens if those assumptions fail?
This Token Transparency Filing is provided for general informational purposes only and does not verify or warrant the accuracy of individual answers.
No airdrop planned or conducted
Not applicable. Flare has conducted the Initial Token Distribution and the FlareDrop airdrops.
(Source: FLR Token Docs)
Validators representing over 85% of stake installed the update and block production resumed, the FTSO resumed price updates and self-corrected, and Flare asked the remaining validators to update.
The outage is resolved and the network has produced blocks since 2025-06-26. Flare's Immunefi bug bounty, launched in July 2024 with rewards up to $250,000 paid in FLR, remains the disclosure channel for vulnerabilities.
The Flare announcement relayed by the FTSO EU provider and the Upbit suspension report are the public references for the June 2025 outage.
(Source: FTSO EU Telegram, Relay of Flare Outage Announcement, CryptoNews, Upbit Suspends FLR Deposits)
Governance Control over Monetary Policy & Rewards: (If applicable) To what extent can governance change monetary policy, fee parameters, or reward allocations (e.g., inflation rate, treasury flows, incentive programs), and how could such changes adversely affect tokenholders?
Response
Impact of Regulatory Change on TGE and Listings:
FLR's TGE, the FlareDrop program and the backer distributions are complete, so the main exposure is to listings. FLR trades on venues including OKX, Kraken, Upbit and Hyperliquid, and exchange support has already been suspended during the June 2025 outage. New listing rules for network tokens, or a regulator treating FLR as a security in a key market, could lead venues to restrict or delist FLR and reduce liquidity.
(Source: Beyond FlareDrops, OKX, FLR Airdrop and Spot Trading, CryptoNews, Upbit Suspends FLR Deposits, Native FLR Spot Listing on Hyperliquid)
Entity-Level Regulatory Impact:
Flare's structure spans a Dutch non-profit Foundation, a development company named Flare Networks Limited whose jurisdiction is not published, and a British Virgin Islands company that operates the website. The Foundation administers FIRE, which buys and burns FLR with protocol revenue, and allocates the Incentive Pool, so rules on token buybacks, market activity or foundation governance could force changes to these programs. Enforcement or licensing action in the Netherlands, the British Virgin Islands or markets where FLR is sold could also restrict how these entities operate.
(Source: Flare Whitepaper v2, Kraken, Flare Token Disclosure, Flare Privacy Policy, From Activity to Value Accrual, Our Plan for FLR)
Tokenholder Tax Treatment:
Flare publishes no tax guidance for holding, wrapping, staking or delegating FLR, and its privacy policy contains no tax clause. The TDE airdrop, the FlareDrops, rFLR emissions and FTSO and staking rewards may be taxed as income on receipt in some jurisdictions and only on disposal in others, and the 12-month rFLR vesting and the early-withdrawal penalty complicate timing and cost basis. Tokenholders are responsible for understanding their own tax obligations.
(Source: Flare Privacy Policy, FlareDrops, New Flare DeFi Emissions Program)
Jurisdictional & User Access Restrictions:
Flare's website privacy policy is governed by British Virgin Islands law with arbitration in the British Virgin Islands and states that the site is not directed at persons in the United Kingdom, and the Flare developer hub carries a UK disclaimer. The network itself has no access restrictions, so access controls fall to exchanges and front ends, which can suspend FLR services as Upbit did in June 2025. These terms make disputes costly for users outside the British Virgin Islands and limit Flare's direct reach to UK users.
(Source: Flare Privacy Policy, Flare Governance Docs, CryptoNews, Upbit Suspends FLR Deposits)
Bugs and Design Flaws:
The June 2025 outage showed that a node software fault can halt block production until validators upgrade, and no published root cause was found as of 2026-10-12. FTSO prices and FDC attestations feed FAssets and DeFi protocols, so faulty or manipulated data could cause wrongful liquidations or mints. FAssets rely on agents and collateral to hold XRP and other assets, and a flaw in the FAssets contracts could lead to loss of bridged funds. Native FLR on Hyperliquid also depends on the LayerZero OFT bridge.
(Source: FTSO EU Telegram, Relay of Flare Outage Announcement, Flare Whitepaper v2, Flare Labs, GitHub, fassets, Native FLR Spot Listing on Hyperliquid)
Security Measures & Their Limitations:
Flare lists audits by Zellic, OpenZeppelin, Coinspect and FYEO, including OpenZeppelin's January 2026 FAssets audit, Zellic's June 2026 review of the FIP.16 smart contracts and Zellic's September 2026 relay audit. It runs an Immunefi bug bounty with rewards up to $250,000. Flare's audits page states that audits do not guarantee the absence of bugs, and these reviews cover code at a point in time, so they can miss flaws in later upgrades, node software and economic attacks on oracle or collateral design.
(Source: Flare Audits, Flare and Immunefi Bug Bounty)
Critical Economic Assumptions:
Network security and oracle quality depend on inflation-funded rewards, with 30% of inflation going to validators and 35% to FTSO providers. FIP.16 assumes that fee burns, higher fees and FIRE buybacks will offset 3% annual inflation, yet FIRE had collected only about $29,400 by September 1, 2026 and protocol-owned MEV capture was not yet fully deployed. If fee revenue and blockspace demand stay low, inflation keeps diluting holders who do not stake or delegate. With FlareDrops ended, WFLR holders no longer earn the FlareDrop reward component.
(Source: Flare Explorer API, InflationAllocation Logs, Flare Explorer API, FtsoRewardOffersManager, Flare Explorer API, FastUpdateIncentiveManager, Flare Explorer API, FdcHub, Flare Explorer API, ValidatorRewardManager, FIP.16, Crypto Times, Flare FIRE Revenue Doubles, FLR Token Docs)
Governance Control over Monetary Policy & Rewards:
Inflation, fees and reward splits change through Flare Improvement Proposals that only the Foundation can initiate and that pass by simple majority of votes cast with no quorum, as FIP.16 did when it cut inflation from 5% to 3%. The Foundation also controls Incentive Pool spending and administers FIRE, and the go-flare v1.14.0 upgrade raised the minimum base fee to 500 gwei. Future proposals could raise inflation, redirect rewards or change fees in ways that lower yields or dilute holders, and holders have no veto outside the vote.
(Source: Flare Governance Docs, FLR Token Docs, GitHub, go-flare v1.14.0 Release, From Activity to Value Accrual, Our Plan for FLR)
