Putting the Decentralization in DeFi: Addressing the Critical Problem of Data in Crypto
summary
Claims Flare is an EVM layer‑1 that enshrines data protocols on‑chain rather than outsourcing oracles, running a time‑series oracle that updates every block (~1.8s) with contributions from a minimum of 100 validators and ~67% of FLR staked or delegated to secure feeds. Current ecosystem hits: ~1 million addresses, a community emissions pool of 500 million FLR, connections to 75 chains and 50,000 dapps via Stargate and LayerZero, a trustless over‑collateralized Bitcoin/XRP bridge, and a Google Cloud TEE hackathon launching verifiable offchain compute.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 0:28Bitcoin to third-gen blockchains
- 1:57Limitations of smart contract chains
- 3:00Oracle problems in DeFi
- 5:33Flaws in today’s oracle models
- 6:58Flare’s data protocols
- 8:43Security of Flare’s oracles
- 10:06Risks of re-staking for oracles
- 13:56Enshrining versus re-staking
- 15:24Data-rich dApps on Flare
- 16:49Adoption barriers in blockchains
- 17:57Trusted execution environments
- 20:46Flare and TEEs for UX
- 21:31Next steps for Flare
- 22:54Hackathon with Google Cloud
- 23:14Flare’s ecosystem growth
- 24:43Flare’s growth metrics
- 25:26Summary
related talks
21mIntroduction to Flare Protocols
26mFlare Workshop - Bring Any Web2 Data On Chain
17mDefi the future of finance
30mHow DeFi Is Building A New Tech Stack
21mWorkshop - Introduction to TEEs on
22mDeFi Needs Familiar Entry Points
42m"Fluree: an Immutable, Verifiable, Shareable Database"
27mComposing Next-Gen DApps With DeFi Legos