Flare ☀️

A new governance proposal is live: Introduce $FLR Value Capture Framework What it’s about: • Lower inflation: Annual inflation falls from 5% to 3%, and the yearly inflation hard cap drops from 5B FLR to 3B FLR. • Stronger fee burn: the base gas fee rises 20x, from 60 gwei to 1200 gwei, resulting in est. 300M FLR burned per year at current transaction levels. • Protocol-level revenue accrual and FIRE setup: Establish a framework to collect flows from protocol fees and captured MEV from DeFi activity on Flare with scope to further reduce annual inflation. proposals.flare.network/FIP/FIP_16.html

The key security point about FAssets v1.3 is this: Minting will route to the Core Vault, governed by explicit safety limits: hourly caps, daily caps, and delays triggered by large mints. For redemptions, agents still play a role, and the collateralized payout model remains intact. These are different control surfaces with deliberate speed bumps, resulting in lower risk. More rollout details to follow.

Today’s DeFi incident is serious and the industry needs to learn swift lessons from it. A few points on @FlareNetworks and FXRP need to be clear: 1. FXRP is not the same thing as the FXRP OFT rail The precautionary pause announced earlier applies to OFT-based cross-network transfers. Core FXRP / FAssets functionality on Flare continues to operate normally. 2. Canonical FXRP on Flare does not use the same architecture as the rsETH OFT under investigation FAssets on Flare is a trust-minimized system with audited smart contracts, onchain liquidation mechanics, independent challengers, governance controls, and explicit safety limits designed to keep risk visible and bounded. It is built by Flare. 3. Using the LayerZero OFT standard for FXRP transmission to other chains does not mean sharing the same security configuration or the same exposure as rsETH LayerZero security is configurable per pathway, not globally across every route. It appears that rsETH used a low security configuration, which is explicitly warned against in the LayerZero documentation. This is not how FXRP is configured. As a precaution, we have paused the FXRP OFT rail while the incident is being investigated. We will not resume it until the root cause is clearer. We support the industry-wide effort to establish the facts quickly and restore trust.

For those asking specifically about the FXRP OFT pathway: The pause affects OFT-based cross-networking, not core FXRP / FAssets functionality on @FlareNetworks. Canonical FXRP on Flare is not the same architecture as the rsETH OFT path now under investigation. LayerZero security is configured per route. Using the same standard does not imply the same verifier setup or the same risk profile. Flare’s current FXRP OFT pathway requires verification from both LayerZero Labs and Nethermind DVNs before a transaction can proceed. We paused the OFT rail out of caution and will keep it paused until the facts are clearer.

As a precautionary measure, we are temporarily pausing FXRP cross-networking via OFTs between Flare, Ethereum, Base, and other supported networks while the rsETH incident is being investigated. Users holding FXRP on non-Flare networks cannot currently redeem, as redemption requires assets to first be bridged back to Flare. FXRP on Flare continues to function normally apart from OFT-based cross-networking. Minting, redemption, liquidation, and all other in-network functions on Flare remain operational. There is currently no indication of an issue affecting Flare or FAssets. We will share further updates as the situation develops.

What would make FIP.16 a success over the next year or so, for $FLR and for the network? Governance and transparency around MEV capture, milestones delivered cleanly, capture that grows, and value put back to work in the ecosystem. @Hugophilion breaks it down in this clip.

Casual FXRP mint on a Saturday.

I made a quick and easy guide for people to know what tokens are eligible to vote, and where to actually find the 'voting booth' As a bonus you'll get to see how I voted 😊 @FlareNetworks youtu.be/y1eiASABRfc?si… @YouTube

Have any FIP.16 questions before casting your vote? This thread runs though most of them. Read it, and once you're ready, vote: portal.flare.network/proposal/view/…

Weekends are great for building and learning about @FlareNetworks. 🔗 dev.flare.network

📢FLARE HOLDERS FIP-16: Restructure $FLR Tokenomics Voting: ACTIVE For me, less than 2 min w/ @BifrostWallet Voting Portal👇 flare.network/vote Voting Ends: 24 Apr 2026 21:00:00 (UTC+9) Thank you @HugoPhilion & Team Looking GOOD🎉👇

New to voting on Flare? This screen recording runs through the flow end to end on @Bifrostwallet Link to vote: portal.flare.network/proposal/view/…

No lift without the right connections: network activity → burn + fee flows → FIRE They power the growth engine that is FIP.16.

@Tangem @grok This is one way to do it

"@grok how do I summon the entire XRP army with one tweet?"

@HugoPhilion Watch the full X space: youtube.com/watch?v=sFhexU…

FIRE's mandate is to reduce $FLR supply over time while still supporting the ecosystem. Here’s @HugoPhilion on whether FIRE will, or should, be fully automated.

🗳️ Voting for FIP-16 at @FlareNetworks Portal is live! > Connect Bifrost Wallet to portal.flare.network/voting via WalletConnect > Find FIP-16 governance proposal > Vote ✅ If you're curious about what we're voting, here's the FIP-16 breakdown in 8 slides ↓

@binance $FLR <3

You are my _______

@0xQuantic 👀

Running some simulations to try to understand how some of the effects of the FIP might be perceived, I quickly realized we could easily arrive at incredible results. So I’d be cautious about doing this for now and focus on completing one step at a time, while we wait until we can share official dashboards that help track this evolution.