Flare Network: $149M TVL, 132M FXRP Locked, and a Data Architecture That Oracle Networks Can't Match.
An early snapshot of this network growth as of 14 March could be measured by these 3 metrics: TVL, total FXRP locked, and the number of active participants in the data attestation network. Over 132 million FXRP sat locked in DeFi protocols across the Flare network for a total Flare ecosystem value locked of $149 million.
Brief primer for people who are asking the question what is flare crypto: what started out as "just another Layer 1 token" at Flare's launch has since found its way to a new answer. It's no longer an umbrella explanation for the next chain coming down the pike that picks up enough TVL to warrant its own page on CoinMarketCap. In the case of Flare, the answer to what is flare crypto is both more narrow in scope and in specificity: a system which allows any blockchain, including the XRP Ledger, Bitcoin, Dogecoin, Litecoin and other assets existing outside of smart contract-native ecosystems, to natively access off-chain and cross-chain data without the need for an oracle middleware solution.
The standout in the crowd of dozens of competitors is no accident. The secret sauce is Flare's architecture. Flare Network is anchored to the XRP Ledger for security with proof-of-transfer, and its data connector protocols aren't just bolted on at the application level like oracles on Ethereum. The capabilities to natively verify external state are built in at the protocol level within Flare's consensus layer, and that architectural choice is bearing fruit.
By the Numbers: The Data Challenge That Flare's Architecture Can Solve
By its nature, a blockchain is a closed system. A blockchain can mathematically validate native transactions, but it can't natively validate external state. Oracle networks emerged to solve that data ingestion use case, but the problem wasn't failures. Oracle networks don't fail often, they almost never fail (at scale, at least). The problem was structure. Oracle networks, at their core, are independent trust layers with their own economic security models, their own node operators, and their own attack surface.
DeFi protocols which are building apps on top of oracle systems (BTC/USD prices on Ethereum, etc.) implicitly inherit those trust assumptions, whether they acknowledge it or not. For tokens like XRP which has a $60 billion+ market cap but had been sitting on the sidelines of DeFi due to custody risks and bridging complexity, that extra layer of trust was one bridge too far.
Flare merged the two systems. Instead of outsourcing the data ingestion problem to a third-party network and their own trust profile, validators attest on Flare to external state changes as part of their block production operations. Attestation providers are also Flare validators.
This is at the heart of Flare Time Series Oracle (FTSO) and State Connector, the two protocols that comprise flare crypto from a technical standpoint. It also meant that Flare could never be a general-purpose blockchain that adopts a data ingestion solution down the line. By definition, both were required to co-exist at the protocol level from day one. The limitation has affected everything from the way validators earn fees and incentives, to the utility design of the Flare token.
The result: a data connector architecture with an end state that looks quite different from protocols that bolted on oracle support as an afterthought.
DeFi Protocols Served: Where Flare Fits on the Ecosystem Value Locked Ladder
At the risk of over-explaining the basics, one more detail about the State Connector use case before we return to those three metrics above. The State Connector is what makes Flare different at the technical level. Conceptually it's a "link" to external data sources, but from Flare's perspective, the data itself is still one-way. "Did this transaction settle on the XRP Ledger?" is one question the State Connector can handle, but if the XRP Ledger changes state, those state changes don't get sent back to Flare as a networkwide event.
BTC/USD price is a timeseries value, and multiple updates can occur within an epoch. As in the State Connector use case, validators would attest to a price estimate each epoch and be awarded protocol-computed rewards for the correct value. The incentives (validator rewards for attesting to accurate data) and utilities (utility for delegators to validators who participate in State Connector attestation) multiply each other. FLR price at current partially reflects the value of FLR as a staking token. FLR added utility by delegating to data providers further drives demand for those data providers to stake FLR tokens.
Both for the sets of data they can consume without being throttled for latency or cost considerations, nor through an intermediary node network where that data gets reconciled. That's a relative advantage for DeFi protocols and applications that require that data to power yield-generating use cases or on-chain settlement use cases: microseconds and gas costs mount up at scale.
Why Millions of XRP Holders Decided to Use Flare Network
In Flare, this translated to a custody problem. For projects with backing assets that sit outside of DeFi by default, trust is the baseline level of friction required to clear the "will I use this protocol?" threshold for all who've lived through cycles of boom-and-bust token launches, network hacks, and flash liquidations.
All that was needed in this particular case was to start with an operational smart account solution (accessible through Xaman Wallet, which integrated in March 2025) and a framework (State Connector) to allow DeFi protocols on Flare to safely attest to XRP Ledger information (XRP deposits in this use case). It wasn't XRP-native wallets and user interfaces and marketing that brought XRP holders to Flare. XRP holders did that themselves, after they discovered Flare, or more accurately FLR tokens, through flare airdrops.
The Holders Who Were Reluctant But Downloaded Flare Anyway
Millions of XRP holders were in the same boat for years and years. The market digested regulatory uncertainties at the end of last year; the holder download and on-chain learning curve was and remains one of Flare's biggest stealth upside for its crypto price. The massive movement from 2025 till date in deposit and total locked FXRP positions can be attributable to the new XRP holders that are onboarding Flare for the first time.
Let's face it, although it's difficult to believe, flare crypto doesn't need to mature to the trillions of dollars' worth of XRP being reserved away from the DeFi use case for Flare to be considered an infrastructural triumph.
Expectations of TVL growth over time as well as adoption across many non-smart-contract-native assets are both baked into the current flare price as well as the future price potential. Adoption may be a lagging indicator for a self-fulfilling crypto asset. It's a leading indicator for an asset used to access real-world data sources at network scale. The on-chain data is a live, real-time view of the network: its throughput and whether Flare Network is so many hopeful technological interfaces, or something more.
