Flare’s approach to XRP interoperability goes much further than simply bridging XRP into another ecosystem. The @XRP starts on XRPL. Flare turns it into FXRP through FAssets, with the underlying XRP still backing it. FXRP can then move to @ethereum through its OFT setup and be used as collateral in Morpho, where borrowers access RLUSD liquidity. So the credit market can live on Ethereum while XRP stays native to XRPL and @FlareNetworks handles the layer that makes the asset programmable and portable.

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.

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.

Start building with Flare Smart Accounts using our developer guides: dev.flare.network/smart-acco…

A few possibilities: - Query FTSO feeds and FDC attestations directly from an agent - Pull contract state, events and balances without writing custom plumbing - Let coding agents inspect Flare contracts and generate transactions against them - Build agent workflows around FAssets, staking and Smart Accounts - Give internal dev tools one standard interface into the Flare stack What would you add?

Hello @XRP Build on Flare and do more for XRP and the internet of value. 🧑‍💻

The papers behind the stack, all public: dev.flare.network/support/wh…

Flare’s interoperability stack is starting to come together. FDC verifies what happened on external chains. FAssets brings assets like XRP into Flare. Smart Accounts let XRPL users trigger actions on Flare directly from XRP payments. And with LayerZero we extend assets like FXRP across other ecosystems. These pieces can already be composed into flows like: XRP on XRPL → mint FXRP on Flare → bridge it to another chain, triggered from a single XRPL payment. If you’re building cross-chain apps, start with the guides: dev.flare.network/smart-acco…

Great weekly recap. ⤵️

Firelight is a good example of Flare infrastructure reaching financial products outside the Flare ecosystem. The $30.5M of cover added to Kraken’s USDC vault is powered by Firelight on Flare, with coverage backed by staked FXRP through the FAssets system. Coverage terms and capacity are registered onchain, independent risk assessors validate eligible incidents, and approved payouts are executed programmatically. This gives products like Kraken’s USDC vault access to a shared onchain protection layer without having to build the coverage infrastructure themselves.

Data. Compute. Capital. Building on Flare means combining the most powerful primitives to enable onchain solutions: dev.flare.network/

Flare Confidential Compute provides a way to use private institutional data onchain without exposing the underlying data itself. With USDX, the sensitive reserve data stays inside a confidential computing environment. The code running there is attested, the machine identity is registered onchain, and Flare data providers have to authorize the instruction before the enclave can process it. The enclave reads the private @Hex_Trust data, computes the USDX backing ratio, and only publishes the signed result. Contracts then verify that the signer is an approved machine running approved code before accepting the update into the feed. This gives Flare a path to bring private reserves, credit data, payments data and other restricted financial information into smart contracts without requiring institutions to publish the underlying records.

If you’re building on Flare, bookmark the Dev Corner. It’s where we keep the practical tech materials: tutorials, workshops and technical deep dives showing how to actually use the Flare stack. 🎬 Watch the Dev Corner: youtube.com/playlist?list=PL…

Thinking about running a validator on @FlareNetworks? 🤔 Make sure to read this in detail first, and for any questions left we are always available.

Thanks to Flare Smart Accounts (FSA), an XRPL signature can now be the starting point for a loan that is actually executed across multiple chains. The user authorizes from XRPL. FSA turns that intent into programmable execution, then FXRP can move to Ethereum, get posted as collateral in borrowing/lending markets via Morpho, and RLUSD could be borrowed against it. The user can get the loan without manually operating the Ethereum/Flare side of the flow. XRPL provides the user authority, Flare handles the orchestration, and Ethereum provides the lending market. One signature can coordinate a cross-chain credit workflow instead of forcing the user to manually switch between three different environments. All of this is enabled via FSA and custom instructions: dev.flare.network/smart-acco…

Quick FIRE knowledge check. ⚡️ Under FIP.16, what is FIRE primarily designed to do with revenue generated by Flare’s protocols and network activity? 1. Reduce FLR supply 2. Increase FLR emissions 3. Pay only FTSO rewards

FCC is more than running code inside a TEE. Flare provides the coordination layer around it. A contract sends an instruction, Flare data providers relay and sign it using the network’s weighted signing policy, and the TEE only executes once >50% of signing weight has approved it. Optional cosigners can add another authorization layer. Sensitive inputs can also be encrypted directly to the TEE, processed inside the enclave, and returned only as a signed result. Building with FCC means confidential offchain computation can inherit onchain authorization, attestation and verifiable outputs instead of building that trust layer from scratch. Explore the FCC here: dev.flare.network/fcc/overvi…