⏭️ Blockchain, mobile & fullstack dev 👨‍💻 Developer Relations Engineer @FlareNetworks 🗣️ Speaker, founder 🐈‍⬛ Cat person 🧭 Orienteering 🌱 Vegan

Latvia
Kristaps Grinbergs retweeted
Today FXRP turns one year old. 🥳 In its first year, XRP has moved into a much broader DeFi design space on Flare, with FXRP now used across lending, liquidity, vaults and more. What would you like builders to create around FXRP over the next year?
10
67
2,815
Nobody could have imagined that XRP, which was mostly sitting idle, would now be a major DeFi driver. It was a huge team effort to build and finally launch FAssets. Can't believe it was a year ago.
A year ago today, XRP became programmable as FXRP. What followed was a run of firsts. XRP in onchain vaults. XRP backing onchain cover. XRP in money markets on Ethereum. Flare Smart Accounts makes it one click from XRPL. FCC takes it to confidential computation, with proofs anyone can verify. That is what unlocks deeper institutional use.
3
7
41
2,757
Flare FAssets has been live on mainnet for one year. This is only the beginning. Look at how we went into XRP finance. The next is an even bigger fish. flare.network/products/fasse…
1
4
30
610
Kristaps Grinbergs retweeted
Flare Builder Online Workshops - Session 25: From Private Intent to Onchain Execution: Designing Apps with Flare Confidential Compute nitter.net/i/broadcasts/1qGoNYmZq…
2
15
57
3,208
Kristaps Grinbergs retweeted
Flare Confidential Compute sits on the same foundation. Private intent in. Verifiable execution on chain. Built for the next wave of XRPFi.
1
37
184
18,902
Kristaps Grinbergs retweeted
Flare enables developers to build XRPL-controlled collateralized DeFi applications around XRP. FXRP turns XRP into an ERC-20 asset that smart contracts can use, while Flare Smart Accounts let XRPL transactions trigger EVM execution. From there, applications can compose XRP collateral with lending markets to build borrowing, collateral management and cross-chain credit flows without requiring users to manually operate each underlying contract. Start building with FXRP today: dev.flare.network/fxrp/overv…
8
35
2,968
Kristaps Grinbergs retweeted
New Flare block explorer! With respect to the Flare engineers who maintain the official explorer... it just doesn't feel good enough sometimes. Sometimes I see FLR come in and I have no clue where it went - then I realize - it was sent to the P-chain! That isn't shown on the official explorer. Some other things also just don't make sense like not showing WFLR values when being wrapped/unwrapped at a glance in TX history. Or not seeing your P chain balances. Or not seeing your active or past stakes. Or not filtering spam NFT's and tokens from view. Or not showing USD values for tokens. Or not having a cool fella on the homepage whose head you can pat. That is what Bloksee (without the c) aims to resolve. I still have more feature ideas to come. This is an early experimental app - but ready for you to use today.
18
23
94
14,071
Kristaps Grinbergs retweeted
Our DevRel team will provide a practical walkthrough of an XRP stocks app built with FCC, using the implementation as a case study to cover the architecture, TEE-signed authorizations, execution flow, and key lessons from running it on Coston2.
🧑‍💻 The next @FlareDevHub Workshop will be covering how Flare Confidential Compute can apply to the XRPL. Private intent in. Verifiable execution on chain. One case study, end to end. RSVP: luma.com/p5hie5j4
1
7
35
4,194
Kristaps Grinbergs retweeted
Exploring XRPFi from a developer perspective? 🤔 A few useful starting points: FAssets / FXRP dev.flare.network/fassets/ov… FAssets developer guides dev.flare.network/fassets/de… Smart Accounts dev.flare.network/smart-acco… Flare Data Connector dev.flare.network/fdc/overvi… FTSOv2 dev.flare.network/ftso/guide… Developer tooling dev.flare.network/network/de… Together these resources cover the main building blocks for XRP-native DeFi on Flare: bringing XRP onchain as FXRP, verifying XRPL activity, using XRPL-controlled accounts, accessing price data, and integrating with the wider Flare stack.
3
6
32
742
Kristaps Grinbergs retweeted
Flare has a lot of acronyms. 🧩 Here’s the short version: FTSO = Flare Time Series Oracle Onchain price and data feeds, updated at high frequency. FDC = Flare Data Connector Brings externally verifiable data from other chains and Web2 sources onto Flare. FCC = Flare Confidential Compute Verifiable confidential computation using trusted execution environments. FAssets = Flare Assets Overcollateralized representations of assets such as XRP on Flare. PMW = Protocol Managed Wallets Policy-controlled wallets that let Flare protocols authorize actions on external chains. FSA= Flare Smart Accounts Connect accounts on networks like XRPL to programmable actions on Flare. Different pieces, but one common goal: give smart contracts access to more useful data, assets and computation.
2
9
34
863
Kristaps Grinbergs retweeted
FSA vaults, now easier to follow. How it works before you connect. Mint and deposit are simpler. Withdraw sits on the main screen. Your earnings are front and centre. Try it → fsa.flare.network/vaults
6
44
609
18,921
Weekend project: reverse-engineering water softener hardware to track water usage and measure salt levels in the container, all integrated into Home Assistant.
1
11
464
I'm updating all the FCC guides with the latest changes. We'll improve them significantly so you won't need to mess with the local tunnel setup; it will be Dockerized. We are also working to show how to deploy in a Trusted Execution Environment (TEE) on Google Cloud. Exciting- stay tuned!
2
217
Kristaps Grinbergs retweeted
FCC isn't bolted onto Flare. It reuses the same FSP signing policy and weighted provider set already behind FTSO and FDC. One stack, getting bigger. Coston2 now. Songbird next, flagship use case incoming.
4
42
166
35,771
Kristaps Grinbergs retweeted
Four fee streams are now routing to FIRE. FAssets minting. Redemptions. Destination tags. FDC attestations. One governed pool, one mandate: reduce FLR supply. It's early, it's on-chain, and every dollar is queryable on @Dune → dune.com/flare/fire
8
51
172
40,258
Kristaps Grinbergs 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,356
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
Kristaps Grinbergs retweeted
Idle XRP earns 0%
5
7
46
4,306