New to Flare or need a quick refresher? The Flare Explainers playlist covers FXRP, FAssets, enshrined oracles, rewards, and why Flare is built for data, all through short videos that get straight to the point. youtube.com/watch?v=NPIL1LDk…

A useful piece of Flare infrastructure to understand is the Flare Systems Protocol (FSP). FTSO and FDC rely on FSP for a shared coordination and finalization layer. Data providers independently compute protocol results and sign candidate Merkle roots. Once signatures representing more than 50% of the active voting weight agree, the result can be finalized through the Relay contract. That finalized root can then be used by smart contracts to verify individual pieces of data with a Merkle proof. FSP also coordinates signing policies, validator uptime voting, reward calculation and network randomness. So when you use an FTSO price or verify FDC data, there is a broader protocol running underneath to coordinate who participates, how much weight they have, how results reach consensus, and how they become verifiable onchain. Worth understanding if you’re building deeper into the Flare stack. 🧑‍💻

Flare Systems Deployment v1.7.0 is out. If you run the stack, there’s no urgent upgrade deadline, but a couple of things are worth knowing before you update: • The C-chain indexer now starts much faster and keeps a shorter rolling history. • Run ./populate_config.sh after upgrading, as the indexer configuration changed. • Don’t delete the old Docker volumes during the upgrade if you want to preserve your rollback path. • If you run FDC2 verifiers on Songbird, keep using the dedicated indexer from fdc-suite-deployment. Release: github.com/flare-foundation/… Changelog: github.com/flare-foundation/…

Flare Builder Online Workshops - Session 23: Building Paid AI APIs with x402 & Flare Confidential Compute xitter.cf/i/broadcasts/1jxXgBajE…

⚡️ Next Flare workshop with @fassko tomorrow. Hands-on: wire x402 payments into an AI API endpoint, run the sensitive bits (prompts, model logic, keys, private data) inside Flare Confidential Compute TEEs, and ship a complete flow that settles on Flare.

Devs keep asking us “what should I build on Flare?” This is a possible map. Current XRPFi stack (Morpho markets, yield vaults, Firelight staking, Derive options, one-click FAssets minting…) already live: xrpfi.flare.network/defi Now look at what’s working, and what can be improved, then build the missing pieces. ⚙️

How the FCC works in simple terms: 1. Smart contracts on Flare handle extension registration, TEE attestation, and instruction issuance. 2. Data providers and cosigners relay instructions once they reach the required signature threshold (using the same signing policy as FTSO and FDC). 3. Registered TEE machines verify the threshold, execute the action, and sign the output with a key generated inside the enclave. 4. Signed results (transactions, attestations, or computation outputs) are returned for onchain use. TEE machines must register with reproducible build proofs so their identity and code can be independently verified.

FDC gives smart contracts a standardized way to verify facts that happened outside Flare. Today it supports 7 attestation types. • AddressValidity: check whether an address is valid for a supported chain. • EVMTransaction: verify transaction data from Ethereum, Flare and Songbird. • Web2Json: fetch Web2 data, transform it with JQ and return ABI-encoded output to contracts. • Payment: verify payments on XRP, Bitcoin and Dogecoin. • ConfirmedBlockHeightExists: prove that a sufficiently confirmed block exists. • BalanceDecreasingTransaction: prove that a transaction reduced an address balance. • ReferencedPaymentNonexistence: prove that a specific referenced payment did not occur within a defined time window. FDC can attest both that something happened and, under defined conditions, that something did not happen. Docs: dev.flare.network/

AI + FCC? Sign the devs up for this interesting session with @fassko. 🙌