max ☀️

Starting to roll out Flare 2.0. The future is now.

XRP as "Bitcoin for banks" does have a nice ring, with Flare as the yield layer. Also reminders of use cases for the Flare Data Connector in trade finance deliverables. It is a good time to be building. @FlareNetworks

FLR already has a regulated ETP through @ValourFunds — one of Europe's largest dedicated crypto ETP issuers. European investors can access FLR directly from a standard brokerage account. No wallet. No exchange. The TradFi distribution layer is live. valour.com/en/products/va…

Nice to see $FLR support continuing to grow. Also, nice to see the XRPfi vaults on Flare growing. Nice to see the growth.

Big milestone for @FlareNetworks Users can now move their XRP directly, seamlessly, trustlessly, from an exchange like Binance into a tailor-made onchain financial ecosystem and access yield Proud of @j00sko and the team of engineers who made it happen (This is just the start!)

FAssets is more XRPL-aligned than people think People ask how the FAssets system actually uses XRPL. The honest answer is that the FAssets core flow is built out of native XRPL primitives — four of them — and that's the architecture. 1. Destination tags. Minting FXRP means sending tagged XRP to the core vault. Redemption sends tagged XRP back to wherever the user wants it — an exchange, a custodian, a wallet. It's the same tag primitive XRPL users already rely on every day. EVM ecosystems are now trying to reinvent this with "subaccounts." XRPL has had it from day one. 2. Native signer sets. The core vault itself uses XRPL's built-in signer-set mechanism. Signers are visible on any explorer, and the vault only ever signs two transaction types: payments to agents on redemption, and escrows. Two native operations, both auditable on-chain. 3. Escrow. Large balances in any signer-controlled account benefit from additional protocol-level constraints. So FAssets continuously locks vault XRP into XRPL-native time-locked escrows that release on a rolling schedule. The liquid balance is always sized well above what's needed to keep redemptions flowing smoothly — the rest sits outside the signing scope until expiry, time-locked by the XRPL protocol itself. Why escrow rather than a custom contract? Because escrow is battle-tested, every XRPL explorer can verify the parameters independently, and standard XRPL operations are simple to validate and easy to monitor. 4. Memo fields. XRPL payments can carry memo data, and FAssets uses that to encode what the user wants to happen on Flare after the mint lands — buy a token, deposit into a vault, hit a Smart Account instruction. One XRPL transaction, full sequence on Flare. No new transaction types, no new wallet UX, no forks. Use XRPL the way it's designed. FAssets v1.3 is live on mainnet.

Hello to the 14.25B XRP sitting on exchanges. You can come over now. One withdrawal, destination tag. That's it.

Direct withdrawal of XRP to Flare from exchange. This is such a great use of native XRP functionality, Flares data protocols and the FXRP system.

I miss the days of Gm. Things have changed a lot these past 6 years and my TL is often _far_ from uplifting, but it’s important to stoke the embers of hope / optimism now and then.. And so.. Gm Gm ☀️

RWAs.. and we haven’t yet discussed FTSO custom feeds for provision of SOFR daily, 3month, 6month, historical rates to unlock a broader range of interest rate swap products via Spectra. But that’s for another time.

Flare is: - Layer 1 chain - built-in oracles for price + state - data + data proofs for internet data - secure bridging for XRP, soon BTC - AI + compute (via TEE layer) - Dedicated XRP trading, staking, yield - MEV and chain revenue capture Did I miss anything? @FlareNetworks

Also privacy, a feature enabled by the TEE layer. This will be accompanied by verifiable offchain compute, onchain attestations, consensus learning across models for reliability.

So, @SentoraHQ curate DeFi vaults. They have strict risk mandates. They continue to achieve institutional allocation for their vaults. Firelight, built on @FlareNetworks, harnessing FXRP as input collateral, will provide DeFi cover for their smart yield vault. Onwards we go.

We're partnering with @SentoraHQ to bring native, capital-backed cover to institutional vaults. Built on @FlareNetworks and powered by $XRP, this integration embeds real-time, programmatic protection directly into DeFi capital flows. 🔥

The upcoming updates for the FAsset system could be one of the most important unlocks yet for XRP utility. Why? Because XRPL destination tags are designed to make the bridge far more exchange-native: users should be able to mint FXRP directly from supported exchange withdrawals and redeem directly to supported exchange deposit addresses. That means the path from idle XRP to onchain yield gets much shorter. Flare will enable a flow that can meet XRP liquidity where it already lives! And once that happens, the incentive structure changes. Users get a clearer path to put XRP to work. Exchanges, in turn, have a reason to care, because passive balances become easier to pull into yield-bearing environments. The result is a net positive for everyone: better UX, better capital mobility, and stronger pressure for the market to take XRPFi seriously.

FIRE

I joined @FlareNetworks because I wanted to be part of a smart team with a founder who can filter signal from noise. This FIP, with all the upcoming products, is signal for Flare. Also: this transparent community call on X feels like a solid blueprint for the future.

It hasn’t been the easiest couple of weeks, but this is worth highlighting: Flare is leading the ISO category this week.

12-page proposal. 4,000 X posts overnight. 1,100 people tuned in live. That should tell you something. The easy takeaway is that people care about @FlareNetworks' tokenomics. Here are the top 15 questions and answers from the space, while we work on reviving the recording with @X: