LfPHP - Flare Linux ☀️ @linuxforphp

If you want more builders on a network, the existing community also has to make experimentation worth it. Try the new apps. Spend a little money. Give feedback. Make early builders feel like people are actually paying attention. That makes the network more attractive to the next developer thinking about where to spend their time. More experiments means more chances to find something that works. Things that work bring users. Users bring more builders. That’s how the network gets stronger.

Darren "Thanasimos" Williams @Thana_Enosys

a day ago

Memes and indie devs can move fast and break things. It's easier to just try things when no one expects them to work every time. That's why it's good to be welcoming to these smaller things as well. @enosys_global can't just try stuff because it seemed cool. We need

9 17 89 17K 2

It's the little things sometimes. FDC transactions are NATIVE to this explorer. It knows you're reaching out to another chain and will put relevant information right in front of you. FDC requests have information such as minimum confirmations on a tx hash that is being proven; within the FDC request you can retrieve data about the TX directly from another chain.

Tim Rowley 🔥 @timrowley_au

2 weeks ago

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

keyboard_arrow_left Previous keyboard_arrow_right Next

18 23 94 14K 16

Friday is for shipping. ☀️ What are you building on Flare today?

FCC introduces protocol-level fees tied to the work performed by the confidential compute stack. One important path runs through FDC. FCC uses FDC to attest and verify deployments and configurations of applications running in the FCC environment. Those FDC requests carry a fee in FLR. Under FIP.16, 90% of the FDC request fee is directed to FIRE, with 10% going to protocol rewards. So FCC usage can contribute to FIRE through the FDC activity it generates. FCC also has its own per-operation fees for instructions sent to TEE machines, separate from normal EVM gas. More FCC usage means more demand for the protocol infrastructure underneath it. dev.flare.network/fcc/overview

⚡️ Going live today at 2pm UTC. Nik will break down the XRP stocks app built with Flare Confidential Compute: keeping conditional orders private inside a TEE, then producing a signed authorization when the execution conditions are met. A practical look at private intent with verifiable onchain execution via FCC.

FXRP is already much more than XRP represented on Flare. Builders can use it today for: • DEX trading + liquidity • lending and borrowing • collateral for RLUSD and other stablecoins • XRP-backed CDPs • staking into stXRP • automated yield vaults • yield markets and structured strategies • options + perps collateral • Hyperliquid spot markets • cross-chain movement via LayerZero OFT • gasless transfers and x402 payments FXRP is an ERC-20 on Flare, redeemable back to XRP, and designed to be composed into applications rather than treated as a dead-end wrapper. Our Dev Hub covers minting, redemption, token integration, gasless payments, x402, OFT bridging and Smart Account flows. dev.flare.network/fxrp/overview

XRPFi gets much more interesting once computation itself can be private. FAssets makes XRP programmable. Smart Accounts let XRPL control execution. FCC adds a new primitive: sensitive data and logic can run inside TEEs, with only a verifiable signed result exposed onchain. That opens a different class of XRPFi applications: private credit underwriting, confidential RFQ/OTC execution, policy-controlled agents and treasuries, institutional workflows, and external-chain actions through PMWs without exposing keys or internal rules. Learn more about FCC here: dev.flare.network/fcc/overview

Bloksee is BUILT FOR FLARE. If you're using FAssets, you need Bloksee. See your FXRP withdrawal end to end with XRP transactions integrated in the same explorer and labeled addresses.

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/overview

The core Smart Accounts flow is simple at the protocol level: An XRPL Payment carries the instruction. The operator observes it, FDC proves it on Flare, and the MasterAccountController resolves the user’s PersonalAccount and dispatches the action. With custom instructions, that same XRPL authorization can trigger arbitrary contract calls on Flare through an EIP-4337-style user operation. XRPL signs. Flare executes. Docs: dev.flare.network/smart-accounts…

Flare ☀️ @FlareNetworks

2 weeks ago

Start on XRPL. Flare Smart Accounts execute on Flare. Today that presents as imbedded wallet flows: mint and deposit in a vault in one click for yield on your XRP. The same pattern can originate a loan: FXRP as collateral, RLUSD out. The mint, the route, the borrow stay under

4 53 226 51K 16

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.

Flare ☀️ @FlareNetworks

2 weeks ago

🧑‍💻 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

3 24 102 34K 8

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.

keyboard_arrow_left Previous keyboard_arrow_right Next

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.

This is a good way to use protocol docs. Not just to get the integration working, but to test the assumptions around payments, signatures and exits before those assumptions reach users. Good iteration from Astryum.

Astryum @Astryum_

2 weeks ago

New interface shipped yesterday. Last night we spent pulling it apart 🔧 We run @0xQuantic's flare-productizer on it, ported to the XRP Ledger. It never touches the code. It reads the app like a first timer, checks every claim against the @FlareDevHub and @XRPLF docs, and asks

0 2 8 6K 0

Current FAssets onchain data, rounded: ~120M FXRP deployed across DeFi. 3.4M+ FXRP DeFi transactions. ~16.5K users. FXRP is becoming a substantial ERC-20 asset base for developers building XRPFi applications on Flare.

future is bright ☀️

Your $FLR rewards are only as good as your validator. Here's this week's top picks. Numbers don't lie. Pull the raw data and see which validators actually hold up: 🔗 flaremetrics.io/validators 🔗 catenalytica.com/dashboard/rewa… Find the validator that fits YOUR profile. $XRP #WFLR

@TeeCeeUncut LOL, It's no secret, this is why I share the filters from @flaremetrics so y'all can see for yourself as well, but the top validators with the best APR is: @Mirhollio with a 12.2% & @knotnodes and @ftsocan with 11.3% $xrp $FLR flaremetrics.io/validators

FCC builders on Coston2: the migration guide for the latest protocol redeploy is now live. If you’re running your own TEE extension stack, you’ll need to point it to the redeployed Relay, FlareSystemsManager and VoterRegistry contracts and complete the required restart/migration steps. 🔗 Follow the guide here: dev.flare.network/fcc/guides/pro…

Flare Devs @FlareDevHub

3 weeks ago

⚡️ 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.

0 8 39 12K 4

We have updated some crucial parts of Flare Confidential Compute. We're working on the upgrade guide. Stay tuned!

Flare Devs @FlareDevHub

3 weeks ago

⚡️ 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.

0 8 39 12K 4