> For the complete documentation index, see [llms.txt](https://diffusefi.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://diffusefi.gitbook.io/docs/using-data-feeds/overview.md).

# Diffuse Data Feeds

## How it works

We use a verifiable TEE enclave to perform trustless requests to the REST APIs. The response is then managed by a zkVM fetching the required JSON data. It also wraps the enclave verification into a ZK proof for cheaper on-chain verification.

## Supported Data Sources

We can fetch data from any public REST API and bring it on-chain. We currently focus on data that does not require private personal info for the request (such as wallet private keys). A few examples of the supported Data Sources:

* A CEX, such as Binance or Coinbase.
* An analytics service, such as CoinMarketCap, Alchemy or Dune.
* An RWA data provider.

We provide our Data Feeds on a constantly growing number of chains. For more info about the endpoints, visit [Active Endpoints](/docs/using-data-feeds/active-endpoints.md). If the chain is fully EVM-compatible, then it usually takes 1-2 days to integrate it into our pipelines.

If you have suggestions about new Data Feeds or a new chain you want us to integrate, please reach out to us on our socials:

* [Telegram](https://t.me/zkdiffuse)
* [X/Twitter](https://twitter.com/DiffuseFi)