Technology Maxi $FLR. Hidden gem connoisseur. 🚀
The Inner Circle
- Tweets 20,048
- Following 1,026
- Followers 1,179
- Likes 47,614
NotYourAverageJoe retweeted
Someone asked Sentora's CEO today if Kraken's DeFi Earn vaults will use Firelight cover.
"all signs point to yes"
Those vaults just passed $902M from 100K+ depositors. Sentora builds them with Kraken and Veda — and Firelight signed with Veda two days ago.
If it lands, the size isn't the interesting part. A Kraken user tapping "Earn" would be protected by staked XRP sitting on Flare, without ever needing to know Flare exists.
5
11
56
1,154
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.
14
16
85
5,393
My reply to Hugo recently sparked some additional ideas that could be possible for Flare. Hopefully some of these can be of some value. @FlareNetworks @HugoPhilion @0xQuantic @j00sko $FLR
1. Parametric Insurance Protocol (Web2Json-settled)
Crop, flight-delay, weather, and shipping-delay insurance where payouts trigger automatically from attested Web2 API data. Leverages FDC Web2Json, which no other L1 has enshrined at the consensus layer — competitors need a third-party oracle with separate trust assumptions.
Audience: Insurtech builders, emerging-market fintechs, institutions.
Value capture: Each policy write and each settlement is an FDC attestation request → 90% of that fee routes to FIRE. High transaction count → burn. Collateral pools could require FLR.
Feasibility: Near-term. Web2Json is live; this is application-layer work.
2. FTSO-Native Perps DEX with Sub-2s Liquidation Engine
A perps venue using block-latency FTSO feeds directly rather than a pull-oracle, enabling tighter liquidation thresholds and lower collateral requirements than chains paying for external oracle updates.
Audience: Traders, market makers, quant funds.
Value capture: Very high transaction density → direct burn. Once MEV capture ships, a high-frequency venue becomes the single largest MEV source on the chain, feeding FIRE.
Feasibility: Near-term but competitive — Flamix and SparkDEX Perps already exist. The differentiator must be the oracle-native liquidation design, not just another perps clone.
3. Proof-of-Reserve Attestation Service
An FDC-powered service that continuously attests to exchange, stablecoin issuer, and DAT (digital asset treasury) reserves across chains, publishing verifiable Merkle proofs on Flare.
Audience: Institutions, CEXs, stablecoin issuers, auditors, regulators.
Value capture: Recurring, subscription-like FDC attestation fees → 90% to FIRE. Genuinely institutional revenue rather than retail speculation.
Feasibility: Near-term. The primitive exists; this is packaging and business development.
4. Native Flare Launchpad with FDC-Verified Vesting
A Foundation-owned launchpad where token locks, vesting schedules, and team wallet behavior are continuously attested on-chain and publicly scored. Closes an actual infrastructure gap.
Audience: Builders raising capital, retail investors.
Value capture: Listing and raise fees payable in FLR, routed to FIRE. Could require FLR staking for allocation tiers — direct staking demand. Keeps value in-ecosystem rather than with TrustSwap.
Feasibility: Near-term. Product and legal work, not novel cryptography.
5. Protocol-Managed-Wallet Payment Rails (no bridge)
Once FCC ships, build remittance and B2B settlement rails where logic executes on Flare but funds settle natively on XRPL — no wrapped asset, no bridge risk. Uniquely enabled by Protocol Managed Wallets, which allow programmable assembly and signing of transactions on external blockchains through smart contract calls on Flare.
Audience: Payment processors, remittance operators, institutions.
Value capture: FCC fees are an explicitly named FIRE revenue stream. High transaction volume → burn.
Feasibility: Long-term. FCC is not yet on mainnet.
6. Verifiable AI Inference Marketplace (FCC)
Developers submit inference jobs to TEE machines; attestation proves which model version ran on which inputs. Flare's own AI skills repo and TeeExtensionRegistry work suggests the groundwork exists.
Audience: AI developers, agent frameworks, enterprises with compliance requirements.
Value capture: Every job is a billable FCC fee → FIRE. A genuinely new revenue category rather than a share of existing DeFi.
Feasibility: Long-term. Requires FCC mainnet plus TEE vendor diversification beyond the current Google Confidential Compute bootstrap. 1/n
1
2
365
7. FXRP-Collateralized Undercollateralized Credit
Institutional credit lines against FXRP where creditworthiness is established through FDC attestations of off-chain financial data (bank statements, audited financials, KYB registries).
Audience: Institutions, market makers, RWA originators.
Value capture: FAssets minting fees (100% to FIRE) scale with FXRP demand. Attestation fees per underwriting event. Deepens the FAssets flywheel.
Feasibility: Medium-term. Needs FCC for confidentiality on sensitive financial data.
8. Sports & Event Prediction Infrastructure Layer
Not another prediction market — the settlement layer other prediction markets use. Flare's docs already cite Ignite Markets using verified Web2 API data to settle sporting outcomes.
Audience: Prediction market builders, fantasy sports, gaming.
Value capture: Every market resolution is an FDC attestation → FIRE. Extremely high event frequency during sports seasons.
Feasibility: Near-term. Live capability, underexploited.
9. Provably-Fair Gaming Primitive (Secure Random)
An SDK wrapping Flare's enshrined 90-second on-chain randomness for lotteries, loot boxes, NFT mints, and on-chain casinos. Most chains rely on Chainlink VRF as a paid external service; here it's protocol-native.
Audience: Game developers, NFT projects, gambling operators.
Value capture: Indirect but high-volume — gaming generates enormous transaction counts, which is exactly what the 500 gwei base fee burn monetizes.
Feasibility: Near-term. Capability is live and almost entirely unmarketed.
10. Institutional RWA Issuance Platform (FCC + FDC)
Tokenized bonds and private credit where covenant compliance is attested via FDC and sensitive terms stay confidential inside TEEs. FCC's first major use case is FAssets V2, replacing the over-collateralized multisig Core Vault with TEE-enforced integrity.
Audience: Asset managers, banks, private credit funds.
Value capture: FCC fees + attestation fees to FIRE. Large ticket sizes, sticky capital, real TVL.
Feasibility: Long-term. Gated on FCC mainnet and regulatory groundwork.
11. FBTC Yield Layer
Replicate the earnXRP model for Bitcoin once FBTC ships. Clearstar's XRP vault demonstrates demand, having grown past 33.7M FXRP versus an original 5M cap.
Audience: BTC holders, institutions.
Value capture: FAssets minting fees route 100% to FIRE — the single most direct existing revenue line. BTC's market size dwarfs XRP's.
Feasibility: Medium-term. FBTC is roadmapped but not shipped.
12. MEV-Aware Institutional Execution Layer
Once protocol-owned block building is live, an RFQ/intent layer offering guaranteed-fair execution with MEV rebated to users rather than extracted — marketed explicitly at institutions who cannot tolerate sandwich risk.
Audience: Institutions, large traders, treasury desks.
Value capture: This is the mechanism through which MEV capture actually reaches FIRE. Potentially the largest single revenue line in FIP.16's design.
Feasibility: Long-term and dependent on Flare shipping the builder architecture.
60
NotYourAverageJoe retweeted
As its Alt SZN (TM) I wanted to recapitulate the Flare offering.
• Flare is the only major L1 with a built in data.
• That data is used to power onchain markets and interoperability with tokens like XRP and Bitcoin which have historically been massively underutilised.
The utility just from this is huge - Firelight, the entire DeFi ecosystem in Flare, Flare smart accounts etc. This is where we are today but the best is yet to come… read on
• Those same data capabilities are being used to assure a verifiable compute layer that sits above Flare.
• Verifiable compute lets you run huge programs (example - a whole LLM) privately and with sufficient security to use the results onchain.
The use cases for the combination of Flare’s data, interoperability and compute are manyfold:
Protocol managed wallets which let a decentralised application on Flare take actions on any chain.
Autonomous crypto or RWA portfolio creation & management.
Private data streams that can interact with applications - so a public app can use data that can’t be exposed publicly but a user can be certain that the data came from the correct source.
Applications built directly on chains like XRP (with baked in privacy).
Private equity or perps markets.
Privacy tooling that can be applied to other markets.
Private and verifiable agents.
These are just a few of the ones that appeal to me.
Everything feeds revenue into FIRE - the Flare mechanism for buying back the FLR token.
We are ALL early.
A short list of apps that could be built on top of FCC:
• Private orderbooks, RFQ systems and dark pools
• Confidential lending, credit and underwriting
• Payroll, treasury and private institutional settlement
• Parametric insurance and private prediction markets
• Agents that hold API keys, policies or signing authority
• External-chain wallets controlled by Flare logic
• Automated rebalancing, market making and treasury execution
• Private Web2 data pulls and custom attestations
• KYC-gated apps with selective disclosure
• Shielded balances and private transfers
• Proprietary trading or risk models
• Heavy offchain computation with only the result posted onchain
• Randomness and specialized oracle services
• Apps that need secrets without falling back to a trusted backend
We have a lot of work to do. ☀️
46
189
647
47,351
NotYourAverageJoe retweeted
Firelight’s $8M seed round is a strong signal of demand for on-chain cover — and it’s built on Flare.
$XRP reaches Flare through FAssets, our core infrastructure, then is staked as FXRP and backs the capital pool behind Firelight’s coverage layer.
Looking forward to seeing staked XRP put to work in some of the most important use cases right now.
nitter.net/Firelightfi/status/209…
Most digital asset security spends on detection, which by definition works after the loss.
Firelight addresses the layer before it: cover for capital exposed to protocol risk, and returns for the capital backing that cover. 🔥
7
47
232
16,964
NotYourAverageJoe retweeted
We have updated some crucial parts of Flare Confidential Compute. We're working on the upgrade guide. Stay tuned!
⚡️ Heads up for teams running FCC TEE extensions on Coston2.
As part of upcoming FSP infrastructure updates, some of the protocol contracts used by the TEE stack will move to new deployments.
If you run your own TEE extension, this will require a small migration on your side.
Expect to update the relevant contract addresses used by your proxy, restart the TEE infrastructure, and refresh the TEE identity associated with that deployment.
We’ll publish the full migration guide with the exact steps and addresses before action is required.
2
11
53
5,770
NotYourAverageJoe retweeted
Ok, so a little bit of controversy after @HugoPhilion's meme post apparently.
Obviously, I prefer serious financial products, and think @FlareNetworks is going to be home to a number of them that are relatively unique in this space.
That said, currently the bulk of the Flare community is...kinda boring.
Now, don't get me wrong, I completely understand the drive to focus on min/maxing yields, squeezing every last bp out of your existing funds, trusting in the power of compounding to catapult your responsible decision making and metered risk taking into generational wealth.
But...it's boring.
It's not fun to talk about.
It's not fun to do.
It's not fun to watch.
Because those products are not supposed to be fun. They are supposed to be reliable, consistent, and boring.
But reliable, consistent, and boring products do not make an enticing ecosystem and community.
So while the spreadsheet obsessed part of my brain hates to do it, I make it a point to take a small part of my onchain income (be it from dex fees, delegation/staking rewards, incentives, stability pool fees, QPY Cloud rewards, etc) and throw it into things someone else built that I think are interesting.
Even if I don't necessarily think I will see a return on those things.
Because I'm not always right.
Because the things I think are important are not always what will build a bigger community and more successful ecosystem.
And, because I want to see more builders, not less, and building is hard when you have an idea, a plan, a drive, but no idea whether it will resonate with anyone else out there.
So ya, I bought some $BUGO to be a part of whatever @BugoFLR ends up doing, because why wouldn't I want to be a part of that community.
And I deposited some $FLR into @FlareBank, because I like the concept and I want to be part of that community too.
And I bought some $FCAT from @thedefimontana's new product, because it seems like it could be a fun thing to mess with and I want to be part of that community too.
And I minted NFTs from @block_bonez and @_DigitalDynamix because @CommunityFlare rocks any why the hell wouldn't I want to support him building here and be a part of his communities.
I try to at least test everything @flareforward puts out, because currently I don't think there is a more dedicated small group of builders/community members on the network and why wouldn't I want to be a part of their community.
And I minted sFLR from @SceptreLS because they were the first to unlock LSTs on Flare and make staking a simple process and why wouldn't I want to be a part of their community.
And I trade perps and supply liquidity for perps on @SparkDexAI because they were the first to bring perps to Flare and have done a lot to mainstream defi activity on the network and why wouldn't I want to be a part of their community.
And I lend and borrow with @Kinetic_Markets because they created the home for the initial explosion of liquidity on Flare and why wouldn't I want to be a part of their community.
And I stake a chunk of my $FXRP with @Firelightfi because what they are building has a ton of potential in this space, and why wouldn't I want to be a part of their community.
And there are countless other things I have tried out, bought, supported, gained from, lost on, etc. Some of them are serious, some are not, and some are in between.
Because the @FlareNetworks isn't just a serious community, with serious people and serious ideas.
It's also a community for experimenting, having fun, shit talking, meme-ing, winning, losing, dreaming, learning and growing.
So anyway...
tl:dr
It's ok to have some fun.
Not everything has to be serious.
Give yourself a play budget.
Be a part of the whole community, not just the part you currently land in.
26
41
152
33,338
NotYourAverageJoe retweeted
This is Flare’s self-policing system working exactly as designed. One operator ended up running validators under two separate infrastructure identities, @xrpen15 did the on-chain digging to prove it and laid it all out on the governance forum, and the provider group is moving straight to a formal vote instead of letting it slide. Most delegators never see this side of the network. Not flashy, but it’s the reason picking a $FLR provider isn’t just a trust exercise
IPMG management proposal initial quorum vote passed with a record landslide for the conditions proposed in the discourse forum.
The @SceptreLS vote for chill action is now live
All qualified providers are encouraged to vote.
portal.flare.network/managem…
portal.flare.network/managem…
2
2
15
853
NotYourAverageJoe retweeted
Had a chat with guys running the Bugo project.
Memes are part of crypto whether you like it or not, but have not been big on Flare - which is IMO a shame.
Would be fun to see some innovative meme ideas come to Flare.
108
45
335
44,302
NotYourAverageJoe retweeted
Flare Smart Accounts explained in one graphic.
FSA let an XRP holder use apps on Flare from their existing XRPL wallet.
The flow is simple:
The user signs a normal XRPL transaction with an instruction in the memo.
FDC verifies that payment on Flare.
MAC routes the verified instruction to the user’s mapped smart account.
The smart account executes the action, whether that is minting FAssets, deposit in a Vault, or interacting with other onchain apps.
No new wallet.
No FLR gas for the user.
Just one XRPL signature that turns XRP into a programmable interface for a much larger onchain economy.
Flare AI Skills explained in one graphic.
Coding agents are powerful, but they don’t automatically know how every protocol works.
Flare AI Skills packages Flare-specific knowledge into structured instructions that agents can load when needed.
That includes protocol architecture, official references, contract interfaces, workflows, code patterns and common pitfalls.
So when you ask an agent to build something using FDC, FAssets, Smart Accounts or other Flare infrastructure, it has relevant technical context available while it works.
The skills can be used by tools such as Claude Code, Cursor and Codex, and because they’re open and modular, new protocol knowledge and workflows can continue to be added.
12
54
1,375
The structural data...
LIQUIDITY CYCLE
Our internal model liquidity for BTC → In a normal cycle bottom we'd expect a much lower trough, this shallow trough is akin to a mid bull market dip.
RISK MODEL
Tracks buy-sided investor liquidity → Structural bottoms happen on sustained down trends to zero. This is a real bottom (>90% probability), not a fake out, ruling out the case we're in a mid-bear market bounce.
COST BASIS
All past cycle bottoms (2012, 2015, 2019, 2022) have seen buying coming in when the cost basis of recent investors drops below the universal cost basis of all investors. → This structural bottom happened without it crossing below, again more akin to a mid bull market dip.
--
There's alpha leak here with models we keep for subscribers, but the subject matter at hand deserves some depth.
20
33
439
62,441
Flare (@FlareNetworks) is Turning Network Fees Into flare-networks:native Buybacks
FIP.16 introduced FIRE, which uses network revenue to buy FLR.
The tokens are then sent to a burn address permanently.
Here’s how it works 👇
bsc.news/post/fip-16-flare-f…
8
31
162
21,980
NotYourAverageJoe retweeted
This how we will turn real network activity into permanent supply removal.
FIP.16 made that mechanism explicit.
The more Flare gets used, the harder that burn engine works.
$FLR burn is starting to ramp up fast.. 🔥
The burn spikes are getting bigger after FIP.16.
More usage = more $FLR burned = becoming deflationary.
Don't just trust it, look at it all live on-chain.
3
12
79
2,187
NotYourAverageJoe retweeted
Reminder: FAssets is not structured like a typical bridge where a large backing pool sits directly exposed behind one smart contract stack.
For most FXRP, the underlying XRP is secured using native XRPL escrow. If the FAssets system is ever compromised, those escrowed flows can be redirected to a custodian instead of simply rolling back into the Core Vault, while the smaller residual XRP exposure outside escrow is covered by substantial overcollateralization in stablecoins and FLR.
In security terms, the architecture is built to reduce attack surface, isolate failure domains, and make a bad event degrade into limited losses rather than the near total drain pattern seen in many bridges.
It’s always super depressing when people at Ripple appear to give glib responses to things that are really serious both to XRP holders and Flare. If I’m misreading your response please accept my sincere apologies in advance.
Additionally, despite the “opinions my own” in bio, the community takes messages from Ripple OG’s like yourself as a sign that Ripple actively discourages Flare and FXRP, which is simply not true.
I don’t know if you have looked much at FXRP but it’s important to understand a few things:
For the VAST MAJORITY of the XRP in the FXRP system, the same method that Ripple uses to secure its massive XRP treasury is used - ie the XRPL Escrow. Given how much and for how long huge amounts of XRP have been sitting in escrows, it seems like a vanishingly small probability that if an issue existed with escrow it would not have already been found. Further if there is an issue with XRPL escrow then FXRP issues are more or less irrelevant.
In the event of a hack on the FXRP system, the funds in the escrow, instead of rolling off of escrow back into the core vault, can be triggered to transfer to a custodian. The remainder of the XRP (usually <20%) that is not secured by the XRPL Escrow is massively over collateralised by stables and FLR.
In sum FXRP is designed to have as small a surface area (measured by gettable funds) as possible. This ideally means that if there is ever an issue with the system it is most likely that any loss would be small as a percentage of the whole system vs the near total losses that we see in other bridges.
2
10
65
1,890
NotYourAverageJoe retweeted
FCC gives data businesses a way to monetize proprietary computation onchain without publishing the IP behind it.
KWeather can sell a verifiable determination that contracts and agents can act on, while the underlying decision logic stays private.
And this is a much bigger design space than simply putting data onchain.
How KWeather described it: a consensus value from many weather sources, computed privately inside FCC, with only the verifiable result going onchain.
Closest analogy is a vote. Who you picked stays private, but the count has to be checkable. That is the property FCC gives this weather data.
2
9
63
3,486
NotYourAverageJoe retweeted
FIP.16 passed 4 months ago, since then the core of the $FLR redesign has began unfolding.
☀️Inflation down 3%
☀️Burns up 20x
☀️Staked capital increased ~35%
☀️4 income streams are now being directed toward FIRE’s mandate of burning and buying back FLR.
@defillama_res published the full breakdown on @DefiLlama.
16
74
287
33,417
NotYourAverageJoe retweeted
The Firelight Protocol roadmap is LIVE!
We have recently completed significant milestones, including our $8M Seed Round and full protocol audits.
Looking ahead, we are preparing for the Firelight Protocol launch and the announcement of our first coverage partners at the end of September!
Here's a detailed timeline of our past, ongoing, and upcoming core milestones.
32
71
265
27,726
NotYourAverageJoe retweeted
The @FlareNetworks Investor Relations dashboard is now live.
Akin to what a traditional equity investor looks for, this dashboard tracks and organizes data across the Flare Network, including:
→ FAssets and FXRP activity
→ Protocol-level activity across 40 tracked deployments
→ FLR tokenomics (supply, inflation, value-accrual mechanics)
→ Staking & network security
Plus one-click access to documentation, blockchain explorer, official websites, and social media accounts.
21
56
184
28,326