# Flare > The blockchain for data Flare lets users build data‑rich applications on an EVM layer 1 with native data protocols. Flare is a layer 1 blockchain for data‑intensive applications with native protocols including the Flare Time Series Oracle, Flare Data Connector, and FAssets, alongside EVM compatibility. Users can develop apps that access external data while maintaining decentralization and network security. - Type: Network - Sector: Blockchain Platforms - Status: Active - Founded: 2019-01-01 - Profile: https://thegrid.id/profiles/flare ## Products - [Flare Network](https://thegrid.id/profiles/flare): Flare Network is a full-stack layer 1 blockchain designed for data-intensive use cases, featuring enshrined data protocols and EVM compatibility. The network provides fast finality with 1.8-second average block times and enables developers to access external blockchain data and real-world APIs through its native oracle infrastructure. (L1, Live, Main Product) - [Flare Time Series Oracle](https://thegrid.id/profiles/flare): Flare Time Series Oracle (FTSO) is an enshrined oracle that provides decentralized data feeds for crypto, equities, and commodities with block-latency updates every 1.8 seconds. Built directly into Flare's core protocol, it leverages the network's full economic security to deliver fast, cost-effective, and manipulation-resistant price data to smart contracts. (Oracle, Live) - [FAssets](https://thegrid.id/profiles/flare): FAssets enables non‑smart contract assets like XRP, BTC, and DOGE to be used in DeFi on Flare through over‑collateralized minting and redemption. (Bridge, Live) - [Flare Data Connector](https://thegrid.id/profiles/flare): Flare Data Connector (FDC) is an enshrined oracle that enables smart contracts to access secure, attested external data from other blockchains and real-world APIs through cryptographic proofs. The system provides trustless verification using Merkle proofs and supports multiple attestation types including EVM transactions, payment confirmations, and Web2 API data with decentralized consensus from data providers. (Oracle, Live) ## Assets - [Flare (FLR)](https://thegrid.id/profiles/flare): FLR is the native token of Flare Network. It is used for paying transaction fees, staking to secure the network, delegating to data providers, and governance participation. The network provides enshrined oracle infrastructure that allows smart contracts to access external blockchain data and real-world APIs natively, enabling developers to build data-intensive applications without relying on third-party oracle services. (Native) ## Links - [Main](https://flare.network) - [Documentation](https://dev.flare.network/network/overview) - [Governance](https://proposals.flare.network) - [Whitepaper](https://flare.network/whitepapers) - [Blog](https://flare.network/news) - [LinkedIn](https://linkedin.com/company/flarenetwork) - [YouTube](https://www.youtube.com/c/Flare_Networks) - [GitHub](https://github.com/flare-foundation) - [Twitter / X](https://x.com/FlareNetworks) - [Discord](https://discord.gg/flarenetwork) - [Telegram](https://t.me/FlareNetwork) ## Legal This data is provided under two licensing models. Model 1 - open data. The open data core is licensed under the Open Database License (ODbL) — a copyleft/share-alike license allowing free use, modification, and sharing for any purpose. Attribution is required: include "Powered by The Grid" linking to https://thegrid.id wherever the data is used. Derivative databases must be shared under ODbL terms. Trademarks, logos, and brand names (marked "Special TPIP") are not covered by the ODbL. For ML/AI use: training datasets that substantially extract ODbL data are Derivative Databases and must be shared under ODbL if publicly used; models must be attributed in documentation. Model 2 - commercial licenses. The Grid Data Service (TGDS) is also available as a commercial license. See [Web Services Terms](https://about.thegrid.id/legal/web-services-terms) for commercial use that is not covered by the open data service. The following applies to both licensing models. - All data is provided AS IS with no guarantees of accuracy. - The Grid does not provide investment, legal, or tax advice, and - a project's presence in The Grid's data does not imply endorsement. - [Data Licensing & Disclaimers](https://about.thegrid.id/legal/data-licensing-and-disclaimers): Licensing models and disclaimers - [Open Data (ODbL)](https://about.thegrid.id/legal/open-data): Open Database License terms and scope for The Grid's open data service. - [Attribution Guidelines](https://about.thegrid.id/legal/open-data-attribution-guidelines): How to attribute The Grid's data when using the open data service. - [Web Services Terms](https://about.thegrid.id/legal/web-services-terms): commercial Terms for using data services. - [All Legal Documents](https://about.thegrid.id/legal): Full index of terms, policies, and disclosures ## Optional - [TGS Field Descriptions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-field-descriptions.md): Schema field definitions for The Grid's data model - [TGS JSON Structure](https://github.com/The-Grid-Data/workspace-public/blob/main/references/tgs-json-structure.md): Data model structure and relationships - [Product Type Definitions](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-definitions.md): Definitions for each product type - [Product Type Classification](https://github.com/The-Grid-Data/workspace-public/blob/main/references/product-type-classification.md): Guide for classifying products into types - [Grid MCP Guide](https://github.com/The-Grid-Data/workspace-public/blob/main/grid-search/skills/grid-query/references/grid-mcp-guide.md): How to query The Grid programmatically via MCP