Flare Workshop - Bring Any Web2 Data On Chain
summary
Shows how to take any Web2 API and put it on Flare end-to-end: use the Flare Data Connector to submit an attestation request (encoded bytes), optionally via a verifier server, then the FDC hub contract starts a validator voting round that finalizes in ≤180s. Validators fetch the URL, apply the JQ filter, encode results to a Solidity struct via the AI signature, store a Merkle-based proof on-chain, and return proofs for verification. Demo uses the Hardhat starter repo and a weather-insurance example; API keys become public after attestation.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:14Flare Developer Hub Overview
- 1:43FDC User Workflow Explained
- 5:05Flare Hardhat Starter Repository
- 6:36Example Contract and Script Walkthrough
- 10:06JQ Filter and Data Processing
- 13:02Solidity Struct (AI Signature) Explanation
- 15:33Modifying the Starter Project
- 18:04Q&A: Proof Structure
- 20:07Q&A: API Keys and Data Privacy
- 21:11Q&A: Weather Insurance Example
- 24:59Additional Resources and Closing
related talks
24mWorkshop Bring Any Web2 Data On Chain
21mIntroduction to Flare Protocols
40mTrustless Insurance Market Using Web2 Connectivity
40mTrustless Insurance Market Using FDC Web2 Connectivity
26mPutting the Decentralization in DeFi: Addressing the Critical Problem of Data in Crypto
21mWorkshop - Introduction to TEEs on
20mBuilding the data layer for AI
21mBuild verifiable offchain apps powered by stake and Symbiotic!