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
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.
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…
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.
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.
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…
