# QUEX > Secure, verifiable and any source data for smart contracts. QUEX is a decentralized data oracle project that lets smart contracts access and verify Web2 data. It uses hardware-secured Trusted Execution Environments to reduce reliance on operators and intermediaries. QUEX is a project building a decentralized data oracle that lets smart contracts securely access, compute, and verify off-chain data from any Web2 source. It targets developers building decentralized finance, real-world asset, and prediction market applications that need trustworthy external data delivered on-chain. Rather than relying on operator reputation or economic incentives alone, it anchors trust in hardware attestation. The system runs oracle executor code inside Trusted Execution Environments built on confidential computing hardware. Each executor generates a private key that never leaves the encrypted virtual machine, and a signed attestation quote is verified and registered on-chain before the executor can respond to requests. Executors with matching codebases form pools that handle data requests and callbacks, with signed results transported on-chain and delivered to a receiving smart contract, which reduces the risk of manipulation, human error, or insider interference. The protocol supports custom data flows, allowing applications to register a combination of recipient contract, callback, oracle pool, and requested action so recurring requests can be made efficiently across supported networks. It provides developer tools and documentation covering architecture, attestation, and integration for teams building on decentralized finance, real-world asset, or prediction market use cases. It is currently active and expanding network support. - Type: Project - Sector: Data & Analytics - Status: Active - Founded: 2023-09-01 - Profile: https://thegrid.id/profiles/quex ## Products - [QUEX Oracle](https://thegrid.id/profiles/quex): QUEX Oracle is a data oracle that lets smart contracts securely fetch, compute, and verify Web2 data using Intel TDX trusted execution environments. Oracles run inside hardware-isolated trust domains that sign their outputs, and on-chain logic verifies these signatures before delivering results to a receiving contract, removing the need to trust individual oracle operators. Data requests are organized into oracle pools and reusable data flows, with pre-funded subscriptions covering callback gas costs, and it supports custom data feeds across multiple EVM-compatible blockchains. (Oracle, Live, Main Product) - [TDX Measurement Verification Tool](https://thegrid.id/profiles/quex): TDX Measurement Verification Tool is a web utility that calculates MRTD and RTMR measurements for Intel TDX trust domains from selected firmware, hardware, and software configurations. Users choose a firmware image, hardware configuration, and payload type, and the tool computes the corresponding measurement values used to verify a trust domain's configuration. It helps developers and data providers confirm that a deployed environment matches expected, tamper-evident configuration measurements. (Developer Tooling, Live) ## Links - [Main](https://quex.tech) - [Documentation](https://docs.quex.tech) - [Blog](https://quex.tech/#media) - [Twitter / X](https://x.com/quex_tech) - [LinkedIn](https://www.linkedin.com/company/quextech) - [Medium](https://quextech.medium.com) - [GitHub](https://github.com/quex-tech) - [Telegram](https://t.me/quex_tech) - [Discord](https://discord.com/invite/NsuE32xHvj) ## 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