3xarch retweeted
It's all coming to light.
Today, cover is coming @Firelightfi☀️
3xarch retweeted
This week:
@Firelightfi phase 2
@FlareNetworks at @token2049, with our CPO Filip Koprivec @j00sko speaking.
Lock in ☀️
3xarch retweeted
This is a great overview that sets out the effect of all the approved Flare Improvement Proposals.
Thank you for writing it up @Anubis_Crypto_
FIP Files: the complete index
Over the last four weeks I went through every Flare Improvement Proposal ever passed. All 16 of them. Every one is marked Final, which means the community voted it through and it's running on the network today.
If you hold, delegate or stake $FLR, these 16 documents are the rules you're playing by. Most people never read them. So I did, one chapter at a time.
Here's the whole series in one place.
Chapter 0: why I started this
teapawt.org/anubis_crypto_/status/…
2023: LAYING THE FOUNDATION
Chapter 1 - FIP.01: Widen FLR distribution, reduce inflation
The most debated vote in Flare's history. The airdrop went to active WFLR holders in 36 monthly drops instead of one big dump, and inflation started its way down from 10%.
teapawt.org/Anubis_Crypto_/status/…
Chapter 2 - FIP.02: FTSO Management Group
Data providers policing data providers. Collude or copy submissions and you get chilled.
teapawt.org/anubis_crypto_/status/…
Chapter 3 - FIP.03: A secondary reward band
A second, wider band so more providers get paid, not just the top quarter. 70/30 split.
teapawt.org/Anubis_Crypto_/status/…
Chapter 4 - FIP.04: New FTSO pairs
BCH and DGB out. ARB, AVAX, BNB, MATIC, SOL, USDC, USDT and XDC in.
teapawt.org/Anubis_Crypto_/status/…
Chapter 5 - FIP.05: Staking opens up
Minimum delegation cut from 10M to 50K FLR, P-chain mirrored to C-chain. Staking stopped being a whales-only thing.
teapawt.org/Anubis_Crypto_/status/…
2024: REBUILDING THE ENGINE
Chapter 6 - FIP.06: Flare Systems Protocol + FTSO Scaling
The hard fork everything since then is built on. Room for up to 1000 feeds.
teapawt.org/anubis_crypto_/status/…
Chapter 7 - FIP.07: FTSO Fast Updates
This is where the ~1.8s price updates come from.
teapawt.org/anubis_crypto_/status/…
Chapter 8 - FIP.08: 19 new feeds and a way to add more
Including BCH, back less than a year after FIP.04 removed it.
teapawt.org/anubis_crypto_/status/…
Chapter 9 - FIP.09: FLR protocol emissions
Around 510M FLR for builders and DeFi liquidity, with 12-month vesting.
teapawt.org/Anubis_Crypto_/status/…
Chapter 10 - FIP.10: Passes for providers
Skip your duties in one protocol too often and you lose the whole epoch's rewards. No more cherry-picking.
teapawt.org/Anubis_Crypto_/status/…
Chapter 11 - FIP.11: The bands flip
The FIP.03 split goes from 70/30 to 40/60, and small parameter tweaks no longer need a full FIP.
teapawt.org/Anubis_Crypto_/status/…
2025-2026: DATA IN, VALUE BACK
Chapter 12 - FIP.12: Flare Data Connector
The successor to State Connector and the reason FAssets can exist at all.
teapawt.org/Anubis_Crypto_/status/…
Chapter 13 - FIP.13: Custom Feeds
Feeds priced by contract logic instead of providers. sFLR went first.
teapawt.org/anubis_crypto_/status/…
Chapter 14 - FIP.14: Web2 attestations
FDC can now read any Web2 API. Prediction markets already use it to settle outcomes.
teapawt.org/Anubis_Crypto_/status/…
Chapter 15 - FIP.15: Delisting weak feeds
A watchlist first, then a vote. Dead feeds don't get to stay forever.
teapawt.org/Anubis_Crypto_/status/…
Chapter 16 - FIP.16: The tokenomics restructure
Inflation from 5% to 3%, and FIRE turning network fees into buybacks and rewards. The one that ties FLR to actual usage instead of new supply.
teapawt.org/anubis_crypto_/status/…
A few things that stood out after reading all of them back to back.
Nothing here passed quietly. The lowest approval ever was FIP.02 at 74.6%. The highest was FIP.06 at 98.2%. Every other proposal cleared 88%.
Inflation went from 10% to 3% across two votes, both public, both on-chain.
And read in order, the direction is hard to miss. 2023 was about who gets FLR. 2024 was about making the oracle fast and hard to game. 2025 and 2026 are about pulling outside data in and sending value back to holders.
That's the full story of @FlareNetworks governance so far, and you can get through it in one evening.
Thanks to everyone who quoted, shared and argued in the replies along the way. You took this series a lot further than I expected.
So here's what I actually want to know: if you could write FIP.17, what would it change?
3xarch retweeted
We are doing our best but sometimes life can be unfair!
Ultimately over time the market figures the value of everything out.
Flare beats Cardano in TVL, DEX volume, and daily transactions… yet Cardano's market cap is still 13x higher.
It’s time for $FLR to start closing that gap.. 👀🔥
3xarch retweeted
XRPL for issuance. Flare for what comes next.
@HugoPhilion on the compute layer: privacy, trading, lending, and collateral for RWAs issued on XRPL.
Clip from XRP Las Vegas with @paulbarron - watch the full talk → youtu.be/9V1TOLn12vo
3xarch retweeted
Come join us on the Q&A Spaces for FIP 16
teapawt.org/i/spaces/1dJrPEmpOOQKX
3xarch retweeted
Just to add to this, we think we are on track both with TEEs and with XRPFi adoption to add Bitcoin later this year.
On the latest @CryptoQueenAU interview from $XRP Australia @wave_of_innov :
Hear @HugoPhilion's response to: “Where does @FlareNetworks fit in as the industry shifts?”
3xarch retweeted
Truly excited to work with @Yellow network.
Breaking🚨SCOOP
Exclusive CLIP #2🚀
$XRP F-Asset [FXRP] EXPANSION to the @Yellow Network!
@FlareNetworks 🔥🔥🔥
Billions in TVL and Trading - Here we come!
RT @HugoPhilion: The Flare Network itself is highly decentralised and robust to geographic internet disruptions.
The Flare Labs team is a…
3xarch retweeted
FXRP supply is increasing markedly. The markets are weak but on Flare the utility is real.
3xarch retweeted
Here are the reasons why I think #flr ☀️ will outperform #ada ATH in Marketcap!
1. Onboarding massive users by bringing true yield to #xrp #btc #doge #xlm through #fassets
2. Inflationary pressure through flaredrops ends 30.01. making the inflation drop to nearly 0% and over 75% of supply in circulation
3. Institutional demand for #xrp and especially the DATs looking for yield on their asset in a safe, non-custodial way!
4. Massive on chain building through free data and built-in Oracle solutions allows real innovation within the web2 and web3 data world.
If you disagree, tell me why not!
3xarch retweeted
2025 ICP realized onchain as cloud where AI builds too: performant, secure, resilient & no-data-loss guarantees
2026=Double Down
— mass market "cloud engines"
— better self-writing apps
— TRUE Web3 no-code
— builders ⬆️🚀
ICP boldly going where no network has gone before 💥
3xarch retweeted
I’ve seen some discussion about FLR’s role in the ecosystem. This will be the subject of a number of governance votes in Q1.
3xarch retweeted
Flare launched in a bear market. We shipped.
Flare emerged into a bull market. We climbed the MCAP rankings. We shipped.
Throw what you will at us.
We will ship and climb.
3xarch retweeted
Must read.
Of all the insurance vectors in DeFi, technical exploits are by far the hardest to underwrite. At @Firelightfi , we’ve spent an absurd amount of time wrestling with this problem and attacking it from multiple angles.
Think about what it means to insure protocols like Aave, Uniswap, or Lido that have never suffered a major security incident. There is no rich history of “similar” failures to anchor a model to. And unlike more traditional insurance domains, technical risk is extremely protocol-specific: past exploits in other lending markets don’t meaningfully quantify technical risk in Aave, just like a Uniswap bug tells you almost nothing about Lido’s staking code.
There is no clean empirical solution to this. But you can get reasonably close with the right structure. At @Firelightfi , we break the problem of technical exploits into three main stages:
Risk Decomposition → Risk Modeling → Model Simulation
1) Risk Decomposition
First, we decompose each protocol into a very granular set of technical vectors (on the order of 70–80 dimensions) that let us quantify risk beyond “has this been hacked before?”.
From there, we extrapolate risk from classes of past exploits that target the same underlying vectors, not just the same protocol category. This only works if you go very deep into the codebase and engineering practices—well beyond reading audit PDFs.
Some of the dimensions we look at:
Code Quality & Complexity
Size/complexity metrics, unsafe patterns, upgrade/proxy architectures, dependency graph hygiene.
Audit & Verification Evidence
Depth and recency of audits, diversity of auditors, formal methods coverage, outstanding findings and how they were handled.
Change Management
Release cadence, freeze windows, CI/CD controls, emergency upgrade levers, canary/partial rollouts.
Privilege & Key Management
Role granularity, timelocks, HSM / MPC custody, operational playbooks, blast radius of key or role compromise.
External Dependencies
Oracles, bridges, L2 settlement guarantees, third-party libraries, upstream protocol invariants.
Runtime Monitoring & Incentives
On-chain/invariant monitoring, anomaly detection, bug bounty structure and payouts, response SLAs.
Incident & Lineage Record
Prior incidents (class, root cause, remediation quality), forked or legacy code lineage, inherited design flaws.
This stage is all about turning “vibes” about protocol safety into structured, machine-readable risk vectors.
2) Risk Modeling
Once we have the risk decomposition, we build a series of candidate risk models aligned with those vectors.
Instead of a single monolithic score, we work with families of models (think: different priors about exploit frequency, severity distributions, dependency failure modes) and calibrate them against:
Known exploit histories in structurally similar components
Simulated attack paths given the specific architecture
Stress scenarios in which multiple vectors degrade at once
The idea is not to pretend we can perfectly predict a black-swannish exploit, but to bound the risk in a way that is transparent, composable, and improvable over time.
3) Risk Simulation
With model candidates in place, we run thousands of simulations across different market and technical conditions to test how these models behave:
How does risk evolve under upgrade churn?
What happens if an upstream oracle or bridge degrades?
How sensitive is expected loss to a single privileged role being compromised?
We’re not trying to produce a magic number. We’re trying to understand where the model breaks, how often, and in which directions—so we can design cover terms, limits, and pricing that reflect reality instead of marketing.
How AI Fits In
Firelight is AI-first by design, and technical exploit analysis is one of the areas where that actually matters:
We use more traditional ML techniques to learn patterns across our 70–80+ risk vectors and how they correlate with historical incidents.
We leverage frontier-scale models to read and reason over complex codebases, spotting patterns and anti-patterns that are hard to catch with static rules alone.
We rely on simulation methods like Monte Carlo to explore edge conditions and tail scenarios in our candidate models.
We apply reinforcement learning–style approaches to iteratively refine model policies and decision thresholds based on simulated outcomes and new data.
And that’s just the beginning. There’s a lot more detail behind each of these layers that we’ll share in future posts.
For now, the key point is this: technical exploits in DeFi are not “uninsurable”—but they are only insurable if you’re willing to decompose the problem ruthlessly, admit uncertainty, and use every tool (including AI) to narrow the gap between what we don’t know and what we can responsibly underwrite.
3xarch retweeted
Flare Fam!
Together with @OkaJustyna54969, we created a short video explaining what Flare is all about. Feel free to use it to spread knowledge about the project within the community. Check it out and share it!
YT link
youtu.be/LDcfv3vrxhw



















