Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
FLR Built-in oracle on the chain
The Flare network uses a different method of price data than most blockchain networks. It does not rely on third-party oracle services, but instead builds the Flare Time Series Oracle (FTSO) as a built-in oracle directly into the network's core protocol, which means that every price feed it produces has the same security guarantees as the chain itself.
Each oracle feed in FTSOv2 inherits the economic security of the entire network, which is critical for DeFi applications that rely on price accuracy: oracles cannot be separated from the consensus of the chain, eliminating the attack surface common in plug-in oracle designs. The system supports up to 1000 feeds covering stocks, commodities and cryptocurrencies, with each feed supported by approximately 100 independent data providers selected by Flare users through delegated pledges.
How the random sampling and commitment-disclosure mechanism works
Provider selection is not static. On each block (approximately 1.8 seconds), a random extraction based on pledge weights selects samples from the network's data provider pool. Selected providers submit small incremental updates to previous prices to keep the feed up to date without having to operate on every block for each provider.
On top of this fast feed, there is a slower anchoring round, which runs approximately every 90 seconds. In this round, all providers participate in the submittion-reveal process: they first submit prices in sealed form and then open them at the same time. Sealed submissions prevent any provider from copying other providers 'answers before submitting, thereby maintaining the true independence of the provider collection. Outlier submissions are filtered out, which prevents bad or manipulated readings from derailing the final price.
The Flare Network encourages data providers to develop their own custom data provider codes, mainly due to the competitive nature of price offers when pursuing FTSO rewards. This competitive dynamic provides providers with economic reasons to submit accurate data rather than free riding.
Commission and Governance
The wrapped $FLR token can be delegated to FTSO data providers, or used for governance, and other uses in EVM-compatible dapps and smart contracts on Flare. Entrusted allows ordinary token holders to align the tokens they pledge with the providers they trust, strengthening the pledge weights that drive the random selection process.
The design positions Flare's oracle as infrastructure rather than an add-on, and the dual-speed architecture (fast per-block feed anchored by regular commitment-reveal rounds) is designed to combine responsiveness with the ability to resist short-term manipulation.
