Native data, fast finality, robust SDKs—plus upcoming TEE compute. Flare is the interoperable EVM stack for devs who want to build once and run everywhere ☀️
Joined April 2025
- Tweets4.9K
- Following238
- Followers5.1K
- Likes31.3K
Pinned Tweet
Flare gives developers built-in access to two things applications usually have to source elsewhere: prices and proofs of external events.
FTSO handles decentralized price data, while FDC verifies supported events outside Flare, including activity on other chains.
Flare Confidential Compute extends this further. Sensitive or heavy logic can run in hardware-secured environments and return a result that contracts can verify onchain.
That means a developer can start from verified data, run logic that does not belong in public execution, and use the result inside an application without stitching together a separate oracle, verification and confidential compute stack.
XRPFi is already one example of what this architecture enables.
Data first. Compute next. Then the applications neither could support alone.
FDC attestation fees are now the fastest-growing source of FIRE revenue.
The Flare Data Connector is not just infrastructure sitting underneath Flare. Applications actually using it to verify external events are creating measurable demand for the protocol itself.
FXRP is already one of the clearest examples of that model working: external XRP activity gets verified on Flare, becomes usable by smart contracts, and the data layer gets paid along the way.
More data requests means more protocol revenue.
Great article on @hackernoon about FXRP and its strong DeFi usage.
It’s great that nearly 90% of FXRP is already being used across DeFi, but the more important number might be that around 95% of deployed FXRP stayed there AFTER incentives ended.
Another key number comes from FDC: attestation fees have grown to ~45% of FIRE revenue.
Give it a read here: hackernoon.com/flare-lets-xr…
Flare Devs retweeted
Security update 🔐
This week brought a series of critical vulnerabilities across widely used software, including PHP and other major libraries.
Our team has reviewed our systems. SparkDEX does not run on PHP, so there is no exposure there. Our dependencies are continuously monitored, reviewed, and updated, and we respond promptly as new advisories emerge.
No action is required from users.
Security is a core priority in how we build and operate SparkDEX.
Should anything ever require your attention, we will communicate it here first.
We love to see this. ☀️
The Smart Accounts section of the Systems Explorer can help decode this flow too.
Users can see the original XRPL payment, minting and executor fees, the XRPL sender and mapped Personal Account on Flare, the Firelight curator/vault, and the final decoded action: VaultDeposit.
Note the 0xFE transaction reference shows this used the custom-instruction path.
In simple terms: the XRPL transaction carries a commitment to the action, FDC proves that payment on Flare, and the mapped Smart Account executes the final EVM call.
So a user sees:
XRP → mint FXRP → deposit into Firelight
while a builder can inspect the full path underneath.
Explore this and more in our page: flare-systems-explorer.flare…
If you want to track what is actually happening on Flare, here you can find a few places worth bookmarking:
1. Flare Systems Explorer
Probably the best place to understand the protocol itself. You can inspect FTSO feeds, FDC requests, reward epochs, finalizations, FAssets and Smart Accounts.
flare-systems-explorer.flare…
2. Flare Block Explorer
For the raw chain: transactions, addresses, contracts, events and token activity.
flare-explorer.flare.network…
3. Flare Metrics
Useful for following validators and data providers, including stake, uptime, vote power and rewards. It also tracks FXRP supply, collateral, mint/redemption flows and FIRE.
flaremetrics.io/
4. Flare on DefiLlama
Better for the application layer: TVL, stablecoins, DEX volume, fees and protocol activity.
defillama.com/chain/flare
5. FIRE
If you want to follow how network usage is feeding back into FLR economics, this is worth watching.
flaremetrics.io/fire
dune.com/flare/fire
Together these give you a much better picture of Flare than one headline metric ever will.
Flare Devs retweeted
DefiLlamaからFlare（ @FlareNetworks ）の最新リサーチレポートが公開！
❓どんな内容？
Flareがなぜ「データ」を基盤に置き、XRPやBTCなどの眠っている資産をDeFiでどう安全に活かそうとしているのかを解説しています。
💡何が分かるか
・Flareが他のL1やオラクルと根本的に違う理由
・FAssets（XRPFi等）で資産が動く仕組み
・ 非公開データを安全に扱う最新技術の機密コンピュート（FCC）
・FLRトークノミクスとエコシステムの最新データ
引用元にレポートURLあります！！！！
Blockspace is abundant. Reliable data isn't.
@FlareNetworks built its L1 around the data smart contracts need.
That layer already powers FXRP, with nearly 90% deployed in DeFi, and is extending to private data through Confidential Compute.
Full report: defillama.com/research/repor…
Flare Devs retweeted
Flare Meetup New York 🗽
Flare is hosting a meetup during @RippleSwell on October 27th at The Addison NY, steps away from the Swell venue.
Come meet builders, traders and founders, including @upshift_fi, @SentoraHQ, @Firelightfi and @XRPLJapan, over an open bar and bites.
Space is limited. Request to join: luma.com/pv1hqf61
Flare Devs retweeted
It is my pleasure to announce that @XAODAOLLC proposal number 66 has passed approving deployment of 80% of the DAO treasury of @xrp ripple:native towards @Firelightfi.
To the best of my knowledge this milestone marks the first deployment by a DAO towards a multi-chain DeFi strategy that has the dual purpose of supporting decentralized insurance and earning yield for our members.
I want to thank my co-manager @FMXRP1, @HugoPhilion & the team at @FlareNetworks for the Flare Smart Accounts technology stack, and the amazing product opportunity offered by @Firelightfi .
#XRP + #FLR -> DeFi done right.
New in Flare Smart Accounts: @Firelightfi.
Make your XRP the capital behind a protection layer for DeFi, in one XRPL signature.
Via @XamanWallet, @Ledger , @DCENTWALLETS and @WalletConnect (@bifrostwallet, @Hex_Trust, and @JoeyWallet)
→ fsa.flare.network
Flare Devs retweeted
🐻❄️ﾌﾑﾌﾑ🤔
Flare Japan Communityの投稿動画を楽しみましょう！#TikTok Lite lite.tiktok.com/t/ZSgUBD5Y6/
Flare Devs retweeted
$FLR validators secure the network and
provide prices and event proofs.
FDC proves an $XRP payment on XRPL
before the system mints FXRP.
Around 145M FXRP in circulation.
Roughly 129M deployed across DeFi.
FTSO prices the collateral for FXRP.
I value FDC's proof before FXRP mints
because it verifies the XRP payment.
Roughly 9 in 10 FXRP sit in DeFi.
Flare is built around the idea that data should be part of the network itself.
The validators securing Flare also provide FTSO prices and verify external events through FDC. That gives applications native access to market data and cross-chain proofs from the same underlying provider infrastructure.
FXRP shows how that architecture works in production.
FDC verifies the XRP payment on XRPL, FTSO prices the collateral securing the system, and the system can mint FXRP only after the payment is proven. Around 145M FXRP is in circulation, with roughly 129M deployed across DeFi.
FCC extends the stack to private data and computation, using the same provider set and signing policy that underpin FTSO and FDC. Smart Accounts then let an XRPL transaction carry instructions that can be proven by FDC and executed through the user’s account on @FlareNetworks.
These pieces compose: prices, external proofs, programmable assets, private data and user execution are all part of the same architecture.
Flare Devs retweeted
Top Validators · Oct 21, 2026
Most delegators: Bifrost Wallet (1,112)
Most stake: Flare.Space (1.05B)
Top APR*: LightFTSO (10.83%)
Most free space*: NORTSO (546.7M)
*Reliability 100, live for more than 30 epochs
Flare Devs retweeted
Same pair. Two pools. Different yield 👀
FXRP/USD₮0 on @SparkDexAI right now:
V3.1 · 27.6% APY, all from trading fees
V4 · 24.2% APY, 7.9% fees + 16.3% rewards
Both are worth knowing before you add liquidity 💡
$FXRP $FLR
Flare Devs retweeted
Great report that gets at a core Flare thesis: as more finance moves onchain, more of that value will depend on reliable data and computation that smart contracts can use and trust.
Flare has already proven a big part of that model.
FTSO and FDC are key data protocols that power the system behind FXRP, the programmable version of XRP with the largest DeFi ecosystem ever built around this asset.
Now the stack is expanding into private computation, with FCC already live on Songbird and powering key institutional use cases like proof of reserves.
And the path opens much wider from here: FBTC, private credit for multiple assets, broader DeFi cover, and other financial applications and data that can be enabled with Flare.
If Flare can repeat the FXRP playbook with private data and compute, the market it can serve becomes much bigger than most imagine.
Blockspace is abundant. Reliable data isn't.
@FlareNetworks built its L1 around the data smart contracts need.
That layer already powers FXRP, with nearly 90% deployed in DeFi, and is extending to private data through Confidential Compute.
Full report: defillama.com/research/repor…
Flare Devs retweeted
One way SparkDEX puts Flare’s price data to work is by checking the market before a swap.
Kevlar Hook compares the pool price with @FlareNetworks FTSOv2 reference price, helping the pool decide how to handle the trade.
All on-chain.
Flare Devs retweeted
Flare's Firelight is now DeFi's second-largest insurance protocol with $68.06M in deposits, behind only Nexus Mutual at $99.10M.
Its cover is backed by staked FXRP, Flare's wrapped XRP.
@FlareNetworks
Flare Devs retweeted
Blockspace is abundant. Reliable data isn't.
@FlareNetworks built its L1 around the data smart contracts need.
That layer already powers FXRP, with nearly 90% deployed in DeFi, and is extending to private data through Confidential Compute.
Full report: defillama.com/research/repor…
Flare Devs retweeted
Cover, built into the vault.
@upshift_fi operators can elect @Firelightfi cover without a per-vault integration.
First up: @SentoraHQ's Protected USD and Protected RWA vaults.
The capital behind the cover is is staked FXRP on Flare.
Flare is built around the idea that data should be part of the network itself.
The validators securing Flare also provide FTSO prices and verify external events through FDC. That gives applications native access to market data and cross-chain proofs from the same underlying provider infrastructure.
FXRP shows how that architecture works in production.
FDC verifies the XRP payment on XRPL, FTSO prices the collateral securing the system, and the system can mint FXRP only after the payment is proven. Around 145M FXRP is in circulation, with roughly 129M deployed across DeFi.
FCC extends the stack to private data and computation, using the same provider set and signing policy that underpin FTSO and FDC. Smart Accounts then let an XRPL transaction carry instructions that can be proven by FDC and executed through the user’s account on @FlareNetworks.
These pieces compose: prices, external proofs, programmable assets, private data and user execution are all part of the same architecture.
"Public prices first, then verified external events, then assets from other chains, and finally private data. Smart Accounts close the loop by connecting that stack to the people who hold the assets.
Each Flare product builds on the layers beneath it, which is why the suite is best read as a single architecture" - Flare stack explained by @defillama_res
Flare Devs retweeted
FIP16によりFLRステーキングが急増、計231億FLRがネットワークセキュリティに貢献しています🥩
報酬の重みづけがデリゲートの5倍となったことが大きな影響ですが、ステーキングの注意点含め、ショート動画にまとめてみました📹️
YouTube・Tiktokにもアップしています(リプ欄にリンクあります)
Of the $FLR taking part in the network, 49.2% is now staked. 23.1B FLR.
In April it was about a third. Since FIP.16, stake carries 5x the weight of delegation, and holders keep moving with it.
Stake yours → portal.flare.network
