XLS-66 and XRP-collateralized DeFi: two different credit primitives for developers. XLS-66 is designed around borrower credit. Liquidity sits in XRPL Single Asset Vaults, loans are fixed-term, underwriting happens offchain, and first-loss capital helps absorb defaults. Building on it means thinking about borrowers, underwriting standards, repayment schedules, loan brokers and default risk. Collateralized DeFi takes a different approach. XRP becomes FXRP, FXRP is deposited into a lending market, and borrowing capacity is determined by the value of the collateral. That requires reliable pricing, liquidity and liquidations rather than borrower underwriting. These models complement each other. XLS-66 can support underwritten credit where the identity and creditworthiness of the borrower matter. FXRP + Smart Accounts can support permissionless XRP-backed credit where the collateral itself secures the debt, while XRPL remains the user control layer.

Flare has NFTs. Flare has gaming. There are no limits to what you can build on Flare. ☀️

A year into FXRP, we’re getting a sneak peek at what @FlareNetworks could become, does Flare’s infrastructure truly turn $XRP into a future-proof asset? But we’re going beyond the basics to delve further. In crypto, you’re usually forced to spin up wallets, hop across bridges, and scrounge up gas tokens just to get moving. Flare has spent the past year cutting that obstacle course down to size, and it begins with two built-in tools: - FTSO supplies prices, while FDC verifies outside events, including XRP payments. Flare’s validators also secure these data protocols, giving its products a shared foundation. - FAssets turns XRP into FXRP for use in DeFi. Minting requires proof of the XRP payment. Redemption agents operate under collateral, challenge and liquidation rules. The Core Vault holds pooled XRP under a Flare-governed multisig, with escrow time locks and withdrawal controls. Agents cannot simply walk away with it. Flare Smart Accounts make access incredibly simple. Sign an XRPL transaction from your current wallet. FDC verifies it, and your linked smart account executes on Flare. The vault flow now needs one signature, no separate EVM key or gas token. By July, Flare reported nearly 24,000 smart accounts and FXRP in DeFi growing from 82 million in February to 144 million. So, what's next? It is Flare Confidential Compute (FCC) FCC is a verifiable computation that keeps sensitive data private, plus protocol-managed wallets that can act on other chains. Songbird first, with broader deployment still ahead. Finally, how all these changes benefits $FLR. FIP.16 cuts annual inflation from 5% to 3%. Transaction fees burn, while FIRE collects specified protocol fees, with supply reduction as its first mandate alongside other governed uses. --- What keeps me upbeat about Flare is how coherently the pieces fit together. FXRP expands what XRP can do, Smart Accounts remove friction for users, and confidential compute opens the door to privacy sensitive apps, while the value flow ultimately routes back to FLR. None of this is starting from zero. Each layer builds on real progress already in place, which makes the Flare faces almost competition and more scalable. That said, activity still has to mature into real, durable revenue over time. Still, after a year of FXRP, there is a functioning baseline, something concrete to iterate on, and a clearer runway toward wider adoption. You are still not bullish enough.

Worth separating this from normal gas fees. FCC can also create value for FIRE by generating paid FDC activity as part of how applications are deployed and verified. That means more FCC usage can translate into more protocol demand beneath the application layer.

Year one of FXRP put XRP to work. FIP.16 made that work pay $FLR. The XRPFi events that already route to FIRE: → FAssets minting → FXRP destination tags → FDC attestations → redemptions Year two is shaping up to have more of those events.

If you are new to Flare please make sure to read this. 👇

New rFLR distribution is out☀️ If you’ve been in eligible DeFi on Flare, check what you’ve accrued. Claim yours on the Emissions tab → portal.flare.network

Luminite is one of the wallets available for exploring XRPFi while retaining access to Flare’s native functionality. Developers can learn more about working with FXRP and Flare assets in the docs: dev.flare.network/fassets/ov…

Friday is for shipping. ☀️ What are you building on Flare today?

A year of FXRP on @FlareNetworks, and XRP-backed onchain cover is live soon. Here is how to get your XRP onto Firelight in Phase 2: → One-click from XRPL via Flare Smart Accounts → Or mint FXRP through FAssets Your XRP, backing the protocols it moves through. 🔥

Today FXRP turns one year old. 🥳 In its first year, XRP has moved into a much broader DeFi design space on Flare, with FXRP now used across lending, liquidity, vaults and more. What would you like builders to create around FXRP over the next year?

A year ago FXRP was a new asset and nobody knew how far builders would take it. One year later, an entire XRPFi stack is forming around it. Builders turned XRP into collateral, liquidity, yield, credit, derivatives and cross-chain infrastructure. Year one was about making XRP programmable and putting it to work. Now build what comes next.

FCC introduces protocol-level fees tied to the work performed by the confidential compute stack. One important path runs through FDC. FCC uses FDC to attest and verify deployments and configurations of applications running in the FCC environment. Those FDC requests carry a fee in FLR. Under FIP.16, 90% of the FDC request fee is directed to FIRE, with 10% going to protocol rewards. So FCC usage can contribute to FIRE through the FDC activity it generates. FCC also has its own per-operation fees for instructions sent to TEE machines, separate from normal EVM gas. More FCC usage means more demand for the protocol infrastructure underneath it. dev.flare.network/fcc/overvi…

FDC can attest to onchain and offchain outcomes. FCC can run private compute against those verified inputs. The resulting activity can generate fees that flow into FIRE. Verifiable triggers, confidential execution, protocol-level value capture. Start building on Flare: dev.flare.network/

👉 A reminder of what’s coming with Firelight: onchain protection that vault builders can integrate directly into their products. Veda is a strong signal of the distribution model. Its infrastructure has powered $32B+ in deposits, and eligible Veda vaults are set to support Firelight protection directly.

Flareのネットワーク活動により生まれた収益はFLRの価値向上など還元される設計です！ FIREには約$45000が集まりました🔥FIREはまだ始まったばかりです、いかにFIREを育てられるか？がポイントになります！

Veda is a big distribution partner for Firelight. Congratulations!

Introducing portfolios to Bloksee! Add multiple wallets to aggregate your balances, NFT's, stakes and even transaction history. You can now also choose to hide NFT's and tokens (and mark as spam) to clean up your page. These features require an account, sign up with your wallet (sign a message) or use an email (encrypted in our DB).

○ Cloud backup is coming to Bifrost Wallet 👀 ○ @FlareNetworks FCC-powered XRP stocks app ○ FXRP is approaching its first anniversary ○ Audits published by @Firelightfi ○ Revenue-sharing meme launchpad take by @HugoPhilion ○ Fully decentralized neobank on XRPL possible via FCC ○ @XRPLF Permission Delegation dropped below the activation threshold ○ Lending v1.1 tested on XRPL Devnet ○ @ClearpoolFin is building XRPL credit rails ○ XRP Ledger joined Open Wallet Standard ○ @XDCNetwork contributors acknowledged in WTO stablecoin report ○ XDC Network at @Sibos 2026 ○ @xdcaitech showed agent payments settling in USDC ↓

Firelight is partnering with @Veda_Labs enabling eligible vaults can integrate on-chain protection. The collateral layer lives on Flare: FXRP, staked as stXRP, backing the pool behind that coverage.

Flare Builder Online Workshops - Session 25: From Private Intent to Onchain Execution: Designing Apps with Flare Confidential Compute nitter.net/i/broadcasts/1qGoNYmZq…