Technology Maxi $FLR. Hidden gem connoisseur. 🚀
The Inner Circle
Joined December 2021
- Tweets20.1K
- Following1K
- Followers1.2K
- Likes47.6K
NotYourAverageJoe retweeted
Indeed the FCC white paper is impressive. There is so much more that Flare can do than what exists within the community narrative. It’s not just programmability for non smart contract coins. In fact this may be the smallest thing that Flare can do (don’t worry we are still launching FBTC).
I’ll be launching a campaign together with partnerships that will totally reposition your thinking about where Flare fits in the blockchain landscape.
NotYourAverageJoe retweeted
🔥 GOOGLE CLOUD + FLARE: THE CONNECTION GOES DEEPER.
Google Cloud isn’t just a name on Flare’s partner list.
It became a network validator and FTSO contributor.
Now Flare Confidential Compute uses Google’s confidential computing infrastructure to process sensitive data and return verifiable onchain results.
That’s a real infrastructure connection.
The next question: Can Flare turn this technology into measurable institutional usage and sustainable economic demand?
Infrastructure first. Adoption next. Revenue is the proof.
#FLR #FlareNetwork #GoogleCloud #XRP
🤖 Made with AI
The papers behind the stack, all public: dev.flare.network/support/wh…
NotYourAverageJoe retweeted
We backed Firelight because they are a highly serious team.
They have launched with some of the biggest partners in the industry from day 1.
There is space in the Firelight vault for additional deposits and Firelight is now available via Flare Smart Accounts.
flare.network/products/flare…
NotYourAverageJoe retweeted
Huge! Congratulations @Firelightfi @jrdothoughts
NotYourAverageJoe retweeted
I have been silently working on something exciting. How to deploy Flare Confidential Compute on Google Cloud. It is in the final testing phase, and I'm very excited. Stay tuned.
NotYourAverageJoe retweeted
Sentora, Veda, Upshift vaults
backed by FXRP @FlareNetworks
Onchain cover from @Firelightfi is live, and every vault it covers is backed by one pool of capital on Flare.
@SentoraHQ first, then operators building on @veda_labs and @upshift_fi.
That pool is staked FXRP: $XRP, made programmable through FAssets.
NotYourAverageJoe retweeted
1/ Today @FinCENnews withdrew two crypto proposals: unhosted-wallet reporting and a Section 311 mixer measure. This is legal change—not another speech about “clarity.” fincen.gov/news/news-release…
NotYourAverageJoe retweeted
One of the clearest examples yet of where FCC can take onchain finance.
Private reserve data from an institution is now influencing a live onchain oracle feed, while the underlying data stays private.
Extend that model to collateral, credit, risk limits or settlement conditions and a lot of institutional workflows become programmable thanks to Flare's infrastructure.
A private piece of institutional data is now directly affecting a live onchain data feed without that private data being revealed.
The USDX/USD Custom Feed on Songbird uses Flare Confidential Compute to combine Hex Trust’s restricted cash reserve data with public bond reserves and the total USDX supply across Flare, Ethereum and Songbird.
The calculation runs inside a hardware-attested secure machine and publishes only the resulting USDX/USD value derived from reserves and supply.
The restricted reserve data stays private, while smart contracts can use the result onchain.
Live feed:
songbird-systems-explorer.fl…
NotYourAverageJoe retweeted
FlareForward is winding down our private coaching, consulting and DeFi University.
Every course we built is going public. Free, for everyone.
We want @FlareNetworks to have the best free education on how DeFi actually works, so the whole ecosystem grows stronger and more knowledgeable over the long term.
The page shows, live, how many people have visited and how many hours of learning the community has put in. We have not seen anything like this given away, and we want to watch that number grow with you.
Start learning: defi.flareforward.com
NotYourAverageJoe retweeted
Token value accrual has become a major topic on CT, with buybacks showing up across more protocols.
Flare is heading in that direction too.
FIP.16 connects protocol revenue from FAssets, FDC, Smart Accounts, MEV and other activity to FLR through FIRE.
That revenue can be used to buy and burn FLR and fund rewards that would otherwise require new issuance.
Still early, and ultimately this only becomes meaningful at scale. But I think the underlying design is clear: as more economic activity happens on Flare, FLR has a mechanism to capture some of it.
Three years ago I started writing about @FlareNetworks because the tokenomics made sense to me before most people were paying attention.
FIP.16 is the proposal that proved that instinct right.
First, the headline number: inflation dropped from 5% to 3% immediately on passage. Not a promise, not a phased plan. Immediate.
Second, and this is the part that actually matters long term: Flare created FIRE, the Flare Income Reinvestment Entity. It collects real fees, from FDC requests, FAssets, Flare Smart Accounts, MEV, and uses them to buy back and burn FLR, plus fund rewards that used to come purely from inflation. That's the shift from "FLR has value because we said so" to "FLR has value because the ecosystem is generating revenue and some of it flows back to the token."
Third, staking got a real weight bump. P-chain stake now counts 5x more than C-chain delegation for governance and rewards. If you've been sitting on delegated WFLR instead of actually staking, this FIP is your nudge to reconsider.
Lastly, the boring but necessary part: FDC fees went up (1 FLR to 20 FLR for most request types), and every provider now has a 20% minimum fee floor. Both changes exist for the same reason, stop a race to the bottom that was quietly undermining network security.
Here's the thing that ties this back to everything else in this series. FIP.16 isn't really about inflation, or FIRE, or staking weights individually. It's Flare admitting that after FIP.01 through FIP.15, the network had enough real usage (FAssets, XRPFi, FDC requests) to stop relying on printing new tokens to fund itself and start relying on what it actually built.
That's not hype. That's just what happens when 16 proposals compound.
NotYourAverageJoe retweeted
A lot of capital is constrained by three things: where the asset lives, where the data lives, and where the computation can happen.
Flare is building around all three.
PMWs let assets stay on their native chains.
FCC lets sensitive computation stay private.
FTSO and FDC bring external data and state into contracts.
Put together, that gives builders a way to coordinate assets, data and compute across different environments without forcing them into the same place.
NotYourAverageJoe retweeted
Integrating Firelight coverage gives protocols on-chain protection that users can verify.
Some of the benefits for protocols:
→ Unlock deposits from risk-conscious users
→ Turn complex on-chain risk into clear, transparent terms
Learn more. 🔥
Firelight makes coverage a native part of a product stack:
• Built directly into vaults
• On-chain and programmatic
• Transparent capacity, premiums and risk parameters
• Fast, stablecoin-denominated payouts
• Composable across a multitude of DeFi primitives
• Rewards aligned with protocol activity
Learn more. docs.firelight.finance/
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.
NotYourAverageJoe retweeted
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.
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
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.
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. ☀️
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.
xitter.cf/Firelightfi/status/209…