# Feeders (Sourcing Layer)
Source: https://www.diadata.org/docs/dia-stack/architecture/core-components/feeders



At the heart of Lumina is a decentralized data collection system composed of feeder nodes operating within the Distributed Feeder Network, responsible for sourcing data and feeding it into the Lasernet chain.

<Frame>
  <img />
</Frame>

## Key components

### **Feeder**

**A Feeder** is a single node in a Distributed Feeder Network that fetches granular market data directly from decentralized exchanges (DEXs), centralized exchanges (CEXs), and third-party data sources. Feeders are responsible for sourcing trade ticks and pushing them to Pods—smart contracts running on DIA's Lasernet—at configurable intervals (e.g. 30 seconds).

There are four main elements that make up a feeder:

<CardGroup>
  <Card title="Scrapers" icon="square-1" href="/dia-stack/architecture/core-components/feeders#scrapers" />

  <Card title="Collector" icon="square-2" href="/dia-stack/architecture/core-components/feeders#collector" />

  <Card title="Processor" icon="square-3" href="/dia-stack/architecture/core-components/feeders#processor" />

  <Card title="Pods" icon="square-4" href="/dia-stack/architecture/core-components/feeders#pods" />
</CardGroup>

#### Scrapers

The expected input for a scraper is a set of pair tickers such as `BTC-USDT`. Tickers are always capitalized and symbols separated by a hyphen. It's the role of the scraper to format the pair ticker such that it can subscribe to the corresponding (websocket) stream.

#### Collector

The collector gathers trades from all running scrapers. As soon as it receives a signal through a trigger channel it bundles trades in *atomic tradesblocks*. An atomic tradesblock is a set of trades restricted to one market on one exchange, for instance `BTC-USDT` trades on Binance exchange. These tradesblocks are sent to the `Processor`.

#### Processor

The processor is a 2-step aggregation procedure:

<Steps>
  <Step title="Step 1">
    Aggregate trades from an atomic tradesblock. The type of aggregation can be
    selected through an environment variable (see Feeder/main). The only
    assumption on the aggregation implementation is that it returns a `float64`.
  </Step>

  <Step title="Step 2">
    Aggregate filter values obtained in step 1. The selection of aggregation
    method and assumptions are identical to Step 1. The obtained scalar value is
    sent to the Oracle feeder.
  </Step>
</Steps>

#### Pods

Pods (or feeder contracts) are a simple key-value oracle contracts assigned to each feeder node. They store the value obtained from the Processor. It is worth mentioning that the trigger mechanism for starting a new cycle of the data collection flow can be implemented on-chain using the feeder contract.

Find out more about the feeder structure and how to run your own feeder [here](/guides/general-guides/run-a-feeder).

## Staking Incentives

To encourage honest behavior, oracle feeders will be rewarded for successful operations and penalized for harmful actions. These incentives ensure that dishonest behavior is punished and becomes economically unviable.

Rewards and penalties will primarily be based on uptime and accuracy, measured by the timeliness of updates and the accuracy of prices compared to other feeders. Initially, feeders will gather the last traded price for assets from centralized exchanges (CEXs). For decentralized exchanges (DEXs), we will use trade simulation-based price estimation, which simulates trades to obtain current exchange rates. This approach ensures more accurate pricing, particularly for assets that are infrequently traded.


# DIA Chain Information
Source: https://www.diadata.org/docs/dia-stack/architecture/core-components/lasernet/chain-information



## Lasernet Overview

DIA Lasernet serves as the core aggregation layer in the Lumina oracle architecture. As an Ethereum Layer-2 rollup, it provides a trustless and transparent environment where feeder nodes submit price data to their assigned Pods (smart contracts), and aggregators process this data into final oracle values. The chain ensures full data transparency, and verifiability for DIA oracles.

Learn more about how Lasernet works in the [Lumina architecture](/dia-stack/architecture/core-components/lasernet/overview) section.

## Chain Information

### Mainnet

|                    |                                                                                       |
| ------------------ | ------------------------------------------------------------------------------------- |
| **Chain name**     | DIA Lasernet                                                                          |
| **Chain ID**       | 1050                                                                                  |
| **Block explorer** | [https://explorer.diadata.org/](https://explorer.diadata.org/)                        |
| **RPC URL**        | [https://rpc.diadata.org/](https://rpc.diadata.org/)                                  |
| **Websocket**      | wss\://rpc.diadata.org                                                                |
| **Gas token**      | [DIA on ETH](https://etherscan.io/address/0x84ca8bc7997272c7cfb4d0cd3d55cd942b3c9419) |

### Testnet

|                    |                                                                                                       |
| ------------------ | ----------------------------------------------------------------------------------------------------- |
| **Chain name**     | DIA Lasernet Testnet                                                                                  |
| **Chain ID**       | 100640                                                                                                |
| **Block explorer** | [https://testnet-explorer.diadata.org](https://testnet-explorer.diadata.org)                          |
| **RPC URL**        | [https://testnet-rpc.diadata.org](https://testnet-rpc.diadata.org)                                    |
| **Websocket**      | wss\://testnet-rpc.diadata.org                                                                        |
| **Gas token**      | [DIA on ETH Sepolia](https://sepolia.etherscan.io/address/0xa35a89390FcA5dB148859114DADe875280250Bd1) |
| **Faucet**         | [https://faucet.diadata.org/](https://faucet.diadata.org/)                                            |


# Overview
Source: https://www.diadata.org/docs/dia-stack/architecture/core-components/lasernet/overview



DIA Lumina employs a flexible and trustless system for processing data into final outputs. After Feeders collect and aggregate data, they're stored in their assigned contract (Pods) on the Lasernet rollup. The final aggregation happens on the meta-contract which collects data from Pods using customizable rules and produces a final value to deliver cross-chain.

## Key Components

## **Lasernet**

As the backbone of the system, Lasernet is an optimistic Ethereum Layer-2 rollup. It serves as an open data repository that handles the full lifecycle of data, minimzing trust and supporting full verifiability. The Lasernet chain is built for scalability using the Arbitrum Orbit Stack to handle large oracle transactions at a low cost.

The DIA Lumina oracle consists of two major components:

<CardGroup>
  <Card title="Pods" icon="square-1">
    the collection of key-value smart contract that collect price data from each
    feeder.
  </Card>

  <Card title="Aggregator" icon="square-2">
    a contract that collates these prices from the key-value contracts and
    provides an automatically refreshed reading of the latest market price.
  </Card>
</CardGroup>

An exemplary Lumina data flow can be seen here. [Feeders](/dia-stack/architecture/core-components/feeders) scrape trades from exchanges and submit these as last prices into their Pods on Lasernet.

The final aggregation of these values is done through the meta-contract (or the Aggregator). To ensure the accuracy of the final value, the meta-contract uses a *threshold* to require a minimum number of valid price submissions before considering the data reliable. Additionally, a *timeout period* in seconds is enforced to discard any outdated price data, so that only fresh and relevant information is used in the final calculation (e.g. 5 data submissions within 1 min).

<Frame>
  <img />
</Frame>

## **Pods**

These are smart contracts that securely store on-chain data. They receive regular updates from their assigned Feeders, ensuring that asset prices are accurate and up-to-date. Feeders make price data openly available for all users on the network.

Each decentralized Lumina feeder writes data into its own oracle contract. This feeder contract is a basic key-value store which stores oracle updates accessible by a key, such as `BTC/USD`. The data stored for each entry is the last price of the asset and the timestamp of that price.

### Data Packing

In order to pack the data efficiently, the entries (price and timestamp) are packed into the same `uint256` when an update is written to the key-value store.

```javascript theme={"system"}
function setValue(string memory key, uint128 value, uint128 timestamp)
        public
        onlyRole(UPDATER_ROLE)
   {
        uint256 cValue = (((uint256)(value)) << 128) + timestamp;

        values[key] = cValue;

        emit OracleUpdate(key, value, timestamp);
    }
```

### Read Data Updates

You can optionally interact with the individual feeder contracts directly by calling `getValue()` that returns the latest price update stored for the requested asset.

1. Call `getValue(pairName)` with `pairName` being the full pair name such as BTC/USD. The quote asset is always in USD for any asset.

2. The response of the call contains two values:

   * The current asset price in USD with a fix-comma notation of 8 decimals.

   * The UNIX timestamp of the last oracle update.

## **Aggregator**

A smart contract that picks data from multiple Pods and creates a final median value (also referred to as a meta-contract). Multiple Aggregator smart contracts can be deployed, creating a flexible framework for users. Aggregators operate with customizable rulesets (custom sources, aggregation windows, and more), allowing them to cater to different use cases. Aggregators also have the option to benchmark data against external sources for additional security.

The meta-contract exposes a simple `Read` function called `getValue()`. It has one parameter `pairKey`, which consists of the symbol of the queried asset and `/USD` to denominate its price in US Dollars. For instance, the latest Bitcoin price is queried by calling `getValue("BTC/USD")`.

The function then returns two values:

1. The value of the asset in US Dollars, with 8 decimals.

2. The timestamp of the block with the latest calculation result.

The oracle has several safeguards against becoming stale or having not enough feeders providing updates.

### How it works

#### Price Aggregation Methodology

The current version of the meta-contract supports the median methodology which is calculated by collecting values from all registered Pods (or feeder contracts), filtering out outdated values based on the timeout period, and ensuring a minimum number of valid values (threshold) are available. The remaining valid values are sorted through a Quicksort algorithm, and the middle value is selected as the median.

Later iterations of the meta-contract will allow selecting different methodologies for each price evaluation.

#### Roles

Each meta-contract has an `admin` address that can setup the meta-contract for its specific usage. The admin is able to add and remove feeders, set a threshold of required feeders, and set a timeout duration after which a feeder update is considered stale.

#### Registering Feeders

The meta-contract needs to learn about available Pods in the Distributed Feeder Network. The admin can add as many feeders as they wish to the price evaluation using the `addOracle()` method. The required parameter of that method is the address of a Pod on Lasernet. After an oracle is added, its latest prices are immediately part of the price evaluation.

#### Removing Feeders

If needed, oracle feeders can also be removed by the admin. The required parameter of that method is is the address of a feeder contract on Lasernet. Removal is immediate, so any call made to `getValue()` from the removal block onwards will not include data from the removed feeder any more.

#### Acceptance Threshold

To make price discovery more robust, a threshold needs to be set by the admin. This threshold corresponds to the number of feeders that need to have submitted a price to reach a valid consensus.

You can find all of the deployedcontracts on Lasernet for Lumina components [here](/guides/dia-deployments).

## Key Benefits

<CardGroup>
  <Card title="Full Data Transparency" icon="square-check">
    From data collection, storage and computation, every step in the process is
    transparent, traceable and verifiable.
  </Card>

  <Card title="Permissionless Flexibility" icon="square-check">
    Lumina's modular design allows developers to deploy their own custom
    Aggregators, offering unmatched flexibility for different data needs.
    Alternatively, DIA offers the Oracle Builder, a no-code solution for the
    same purpose.
  </Card>
</CardGroup>


# Architecture Overview
Source: https://www.diadata.org/docs/dia-stack/architecture/core-components/overview

Explore how Lumina handles the flow of data and updates across the network using its robust and modular architecture.

The data flow is broken down into the following phases:

<CardGroup>
  <Card title="Feeders (Sourcing Layer)" href="/dia-stack/architecture/core-components/feeders" icon="circle-1" />

  <Card title="Lasernet (Aggregation Layer)" href="/dia-stack/architecture/core-components/lasernet/overview" icon="circle-2" />

  <Card title="Spectra (Cross-chain Messaging Layer)" href="/dia-stack/architecture/core-components/spectra" icon="circle-3" />
</CardGroup>

Explore the data sources that are used to power the Lumina oracle:

<CardGroup>
  <Card title="Data Sources" href="/dia-stack/architecture/data-sources/overview" icon="globe" />
</CardGroup>


# Spectra (Cross-chain Messaging Layer)
Source: https://www.diadata.org/docs/dia-stack/architecture/core-components/spectra



DIA Lumina achieves full interoperability, delivering oracle data to any blockchain with minimal friction through the Spectra protocol, a message passing layer powering both the push and pull oracle models.

## **Data Delivery Methods**

Spectra is an interchain message passing protocol formed by a network of nodes, running a custom instance of Hyperlane, an open interoperability framework. It facilitates secure and rapid transmission of oracle data to any blockchain, without the need for chain-specific integrations.

The Spectra validators observe messages on the mailboxes of the destination and origin chains. The messages are then checked through the ISM (Interchain Security Module) and delivered to these components:

* RequestOracle (Pull oracle)

* PushOracleReceiver (Push oracle)

The gas for processing messages are funded by imposing a fee for calling `request()` on *RequestOracle*, or `handle()` on the *PushOracleReceiver* contracts. The fees are transferred to the ProtocolFeeHook – an instance of Hyperlane's [Post-Dispatch](https://docs.hyperlane.xyz/docs/protocol/core/post-dispatch-hooks-overview#post-dispatch-hooks-overview) hooks - that are then withdrawn manually to the Spectra gas wallet.

Let's explore how Spectra contributes to the flow of messages in the Push and Pull oracle models and how that translates to the data you receive on the destination chain.

### Pull Model

<Frame>
  <img />
</Frame>

* User initiates a request to the RequestOracle contract and pays a fee.

* RequestOracle processes the request on the origin chain (e.g. Ethereum), creates a message containing the request details (destination chain id, OracleRequestRecipient address, exchange pair, ...etc), then dispatches it through the Mailbox.

* The validators observes the mailbox and picks up the request. once it verifies its validity through the ISM and signs it, the relayer carries out the message delivery to the mailbox of the destination chain (DIA lasernet).

* OracleRequestRecipient receives and validates the message through the ISM, and passes it forward to OracleTrigger that fetches the values from the [Aggregator](/dia-stack/architecture/core-components/lasernet/overview#aggregator) or meta-contract. It then creates a message with the latest price, and dispatches it back to Lasernet's mailbox.

* Message is picked up by Spectra protocol and sent back to the RequestOracle which then checks for data freshness and adds the value to the `updates`mapping.

### Push Model

<Frame>
  <img />
</Frame>

* Go feeder service initiates a price update based on certain parameters (such as deviation, heartbeat, & refresh frequency) on the origin chain (DIA's lasernet).

* OracleTrigger processes the update request, reads the latest price from the meta-contract, creates a message, & dispatches it through the Mailbox.

* The validators observes the mailbox and picks up the update request. once it verifies its validity through the ISM and signs it, the relayer carries out the message delivery to the mailbox of the destination chain.

* PushOracleReceiver receives the update, validates the message through the ISM, checks for the data freshness, the adds the value to the `updates`mapping.

### Fees

Cost of updating data on the destination chain is calculated as follows:

```bash theme={"system"}
uint256 gasUsedPerTx = 97440; // Fixed gas amount
uint256 gasPrice = tx.gasprice; // Current network gas price
uint256 cost = gasUsedPerTx * gasPrice; // Total fee
```

## Key Benefits:

<CardGroup>
  <Card title="Deploy Anywhere, Fast" icon="square-check">
    Cross-chain data delivery is made simple through Spectra, dramatically
    reducing time to market for developers, and allowing data to be transmitted
    across blockchains with minimal friction and no chain-specific setup.
  </Card>
</CardGroup>


# CEXes Data
Source: https://www.diadata.org/docs/dia-stack/architecture/data-sources/cexes-data



### Centralized Cryptocurrency Exchanges

All trading data is retrieved through Rest APIs or websocket APIs, developed and maintained by the respective trading platform. See the below table for detailed information on all sources. We remark that by the very nature of a websocket API, there is no retrieval frequency, instead, trading data comes in continuously as it is produced.

| Exchange                                                                                                                                     | API Link                                                                                                   | See live data                                                                                              |
| -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| <img alt="" /> [**Binance**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BinanceScraper.go)         | [Binance Websocket Documentation](https://binance-docs.github.io/apidocs/spot/en/#trade-streams)           | [https://www.diadata.org/app/source/defi/Binance/](https://www.diadata.org/app/source/defi/Binance/)       |
| <img alt="" /> [**Bitfinex**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BitfinexScraper.go)       | [Bitfinex Websocket Documentation](https://docs.bitfinex.com/docs/ws-general)                              | [https://www.diadata.org/app/source/defi/Bitfinex/](https://www.diadata.org/app/source/defi/Bitfinex/)     |
| <img alt="" /> [**BitMax**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BitmaxScraper.go)           | [Bitmax API Documentation](https://bitmax-exchange.github.io/bitmax-pro-api/#bitmax-pro-api-documentation) | [https://www.diadata.org/app/source/defi/Bitmax/](https://www.diadata.org/app/source/defi/Bitmax/)         |
| <img alt="" /> [**BitMart**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BitMartScraper.go)         | [BitMart API Documentation](https://www.bitmart.com/open-api-guide/en)                                     | [https://www.diadata.org/app/source/defi/BitMart/](https://www.diadata.org/app/source/defi/BitMart/)       |
| <img alt="" /> [**BitMex**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BitMexScraper.go)           | [BitMex API Documentation](https://www.bitmex.com/app/apiOverview)                                         | [https://www.diadata.org/app/source/defi/BitMex/](https://www.diadata.org/app/source/defi/BitMex/)         |
| <img alt="" /> **BitStamp**                                                                                                                  | [BitStamp API Documentation](https://www.bitstamp.net/api/)                                                | [https://www.diadata.org/app/source/defi/Bitstamp/](https://www.diadata.org/app/source/defi/Bitstamp/)     |
| <img alt="" /> [**Bybit**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/ByBitScraper.go)             | [Bybit API Documentation](https://bybit-exchange.github.io/docs/inverse/#t-introduction)                   | [https://www.diadata.org/app/source/defi/ByBit/](https://www.diadata.org/app/source/defi/ByBit/)           |
| <img alt="" /> [**Coinbase**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/CoinBaseScraper.go)       | [Coinbase Websocket Documentation](https://docs.pro.coinbase.com/)                                         | [https://www.diadata.org/app/source/defi/CoinBase/](https://www.diadata.org/app/source/defi/CoinBase/)     |
| <img alt="" /> [**Crypto.com**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/CryptoDotComScraper.go) | [Crypto.com API Documentation](https://exchange-docs.crypto.com/spot/index.html#introduction)              | [https://www.diadata.org/app/source/defi/Crypto.com/](https://www.diadata.org/app/source/defi/Crypto.com/) |
| <img alt="" /> [**GateIO**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/GateIOScraper.go)           | [GateIO Websocket Documentation](https://www.gate.io/docs/websocket/index.html)                            | [https://www.diadata.org/app/source/defi/GateIO/](https://www.diadata.org/app/source/defi/GateIO/)         |
| <img alt="" /> [**Kraken**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/KrakenScraper.go)           | [Kraken Rest API Documentation](https://www.kraken.com/features/api#public-market-data)                    | [https://www.diadata.org/app/source/defi/Kraken/](https://www.diadata.org/app/source/defi/Kraken/)         |
| <img alt="" /> [**KuCoin**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/KuCoinScraper.go)           | [Kucoin API Documentation](https://docs.kucoin.com/#websocket-feed)                                        | [https://www.diadata.org/app/source/defi/KuCoin/](https://www.diadata.org/app/source/defi/KuCoin/)         |
| <img alt="" /> [**MEXC**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/MEXCScraper.go)               | [MEXC API Documentation](https://mxcdevelop.github.io/APIDoc/)                                             | [https://www.diadata.org/app/source/defi/MEXC/](https://www.diadata.org/app/source/defi/MEXC/)             |
| <img alt="" /> [**OKEx**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/OKExScraper.go)               | [OKEx Websocket Documentation](https://www.okex.com/docs/en/#ws_swap-README)                               | [https://www.diadata.org/app/source/defi/OKEx/](https://www.diadata.org/app/source/defi/OKEx/)             |
| <img alt="" /> [**Bitget**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BitgetScraper.go)           | [Bitget Websocket Documentation](https://www.bitget.com/api-doc/common/websocket-intro)                    | [https://www.diadata.org/app/source/defi/Bitget/](https://www.diadata.org/app/source/defi/Bitget/)         |


# DEXes Data
Source: https://www.diadata.org/docs/dia-stack/architecture/data-sources/dexes-data

In contrast to centralized exchanges, in decentralized exchanges, it is possible to retrieve trading data directly from the respective blockchain by subscribing to the corresponding pool events.

## Decentralized Cryptocurrency Exchanges (DEXes)

<Info>
  In order to supply data to our community as quickly as possible, we retrieved
  the trading data for a few exchanges through Rest APIs (see table below).
  However, we remark that we are implementing data retrieval through the
  blockchain directly to reduce unnecessary dependencies. This concerns *all*
  decentralized exchanges.
</Info>

| Exchange                                                                                                                                            | Blockchain                                                                 | See live data                                                                                                                                                                                                                                                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [**AerodromeSlipstream**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV3Scraper.go#L108)            | Base                                                                       | [https://www.diadata.org/app/source/defi/AerodromeSlipstream/](https://www.diadata.org/app/source/defi/AerodromeSlipstream/)                                                                                                                                                                                                                               |
| [**Aerodrome V1**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/VelodromeScraper.go#L70)                    | Base                                                                       | [https://www.diadata.org/app/source/defi/AerodromeV1/](https://www.diadata.org/app/source/defi/AerodromeV1/)                                                                                                                                                                                                                                               |
| <img alt="" />[**ApeSwap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)               | BNB Chain                                                                  | [https://www.diadata.org/app/source/defi/Apeswap/](https://www.diadata.org/app/source/defi/Apeswap/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**Arthswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)              | Astar                                                                      | [https://www.diadata.org/app/source/defi/Arthswap/](https://www.diadata.org/app/source/defi/Arthswap/)                                                                                                                                                                                                                                                     |
| [**Ayin**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/AyinScraper.go)                                     | Alephium                                                                   | [https://www.diadata.org/app/source/defi/Ayin/](https://www.diadata.org/app/source/defi/Ayin/)                                                                                                                                                                                                                                                             |
| <img alt="" />[**Balancer v2**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BalancerV2Scraper.go)          | -Ethereum <br /> -Polygon <br /> -Arbitrum                                 | [Ethereum](https://www.diadata.org/app/source/defi/BalancerV2/), [Polygon](https://www.diadata.org/app/source/defi/BalancerV2-Polygon/), [Arbitrum](https://www.diadata.org/app/source/defi/BalancerV2-Arbitrum/) sources                                                                                                                                  |
| <img alt="" />[**Beets**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)                 | Fantom                                                                     | [https://www.diadata.org/app/source/defi/Beets/](https://www.diadata.org/app/source/defi/Beets/)                                                                                                                                                                                                                                                           |
| [**Bifrost**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BifrostScraper.go)                               | Bifrost                                                                    | [https://www.diadata.org/app/source/defi/Bifrost/](https://www.diadata.org/app/source/defi/Bifrost/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**Biswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)                | BNB Chain                                                                  | [https://www.diadata.org/app/source/defi/Biswap/](https://www.diadata.org/app/source/defi/Biswap/)                                                                                                                                                                                                                                                         |
| [**Bitflow**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/BitflowScraper.go)                               | Stacks                                                                     | [https://www.diadata.org/app/source/defi/Bitflow/](https://www.diadata.org/app/source/defi/Bitflow/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**Camelot**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go#L193)          | Arbitrum                                                                   | [https://www.diadata.org/app/source/defi/Camelot/](https://www.diadata.org/app/source/defi/Camelot/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**Camelot v3**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/camelotv3/camelotv3.go)         | Arbitrum                                                                   | [https://www.diadata.org/app/source/defi/CamelotV3/](https://www.diadata.org/app/source/defi/CamelotV3/)                                                                                                                                                                                                                                                   |
| <img alt="" />[**Curve**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/CurvefiScraper.go)                   | -Ethereum <br /> -Arbitrum <br /> -Fantom <br /> -Moonbeam <br /> -Polygon | [Ethereum](https://www.diadata.org/app/source/defi/Curvefi/), [Arbitrum](https://www.diadata.org/app/source/defi/Curvefi-Arbitrum/), [Fantom](https://www.diadata.org/app/source/defi/Curvefi-Fantom/), [Moonbeam](https://www.diadata.org/app/source/defi/Curvefi-Moonbeam/), [Polygon](https://www.diadata.org/app/source/defi/Curvefi-Polygon/) sources |
| <img alt="" />[**Dfyn**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)                  | Polygon                                                                    | [https://www.diadata.org/app/source/defi/DFYN/](https://www.diadata.org/app/source/defi/DFYN/)                                                                                                                                                                                                                                                             |
| <img alt="" />[**Diffusion**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)             | EVMOS                                                                      | [https://www.diadata.org/app/source/defi/Diffusion/](https://www.diadata.org/app/source/defi/Diffusion/)                                                                                                                                                                                                                                                   |
| <img alt="" />[**Hermes**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)                | Metis                                                                      | [https://www.diadata.org/app/source/defi/Hermes/](https://www.diadata.org/app/source/defi/Hermes/)                                                                                                                                                                                                                                                         |
| <img alt="" />[**Huckleberry**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Moonriver                                                                  | [https://www.diadata.org/app/source/defi/Huckleberry/](https://www.diadata.org/app/source/defi/Huckleberry/)                                                                                                                                                                                                                                               |
| [**Hydration**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/HydrationScraper.go)                           | Hydration                                                                  | [https://www.diadata.org/app/source/defi/Hydration/](https://www.diadata.org/app/source/defi/Hydration/)                                                                                                                                                                                                                                                   |
| <img alt="" />[**Maverick**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/MaverickScraper.go)               | Ethereum                                                                   | [https://www.diadata.org/app/source/defi/Maverick/](https://www.diadata.org/app/source/defi/Maverick/)                                                                                                                                                                                                                                                     |
| <img alt="" />[**Netswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)               | Metis                                                                      | [https://www.diadata.org/app/source/defi/Netswap/](https://www.diadata.org/app/source/defi/Netswap/)                                                                                                                                                                                                                                                       |
| [**NileV1**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go#L237)                         | Linea                                                                      | [https://www.diadata.org/app/source/defi/NileV1/](https://www.diadata.org/app/source/defi/NileV1/)                                                                                                                                                                                                                                                         |
| [**NileV2**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV3Scraper.go#L106)                         | Linea                                                                      | [https://www.diadata.org/app/source/defi/NileV2/](https://www.diadata.org/app/source/defi/NileV2/)                                                                                                                                                                                                                                                         |
| <img alt="" />[**OmniDEX**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)               | Telos                                                                      | [https://www.diadata.org/app/source/defi/OmniDex/](https://www.diadata.org/app/source/defi/OmniDex/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**Orca**](https://github.com/diadata-org/diadata/tree/master/pkg/dia/scraper/exchange-scrapers/orca)                                 | Solana                                                                     | [https://www.diadata.org/app/source/defi/Orca/](https://www.diadata.org/app/source/defi/Orca/)                                                                                                                                                                                                                                                             |
| <img alt="" />[**Osmosis**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/OsmosisScraper.go)                 | Cosmos                                                                     | [https://www.diadata.org/app/source/defi/Osmosis/](https://www.diadata.org/app/source/defi/Osmosis/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**PancakeSwap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Binance Smart Chain                                                        | [https://www.diadata.org/app/source/defi/PanCakeSwap/](https://www.diadata.org/app/source/defi/PanCakeSwap/)                                                                                                                                                                                                                                               |
| <img alt="" />[**PancakeSwapV3**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)         | Binance Smart Chain                                                        | [https://www.diadata.org/app/source/defi/PanCakeSwapV3/](https://www.diadata.org/app/source/defi/PanCakeSwapV3/)                                                                                                                                                                                                                                           |
| <img alt="" />[**Pangolin**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)              | Avalanche                                                                  | [https://www.diadata.org/app/source/defi/Pangolin/](https://www.diadata.org/app/source/defi/Pangolin/)                                                                                                                                                                                                                                                     |
| [**Pearlfi**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go#L243)                        | Unreal                                                                     | [https://www.diadata.org/app/source/defi/Pearlfi/](https://www.diadata.org/app/source/defi/Pearlfi/)                                                                                                                                                                                                                                                       |
| <img alt="" />[**Quickswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)             | Polygon                                                                    | [https://www.diadata.org/app/source/defi/Quickswap/](https://www.diadata.org/app/source/defi/Quickswap/)                                                                                                                                                                                                                                                   |
| [**RamsesV1**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go#L239)                       | Arbitrum                                                                   | [https://www.diadata.org/app/source/defi/RamsesV1/](https://www.diadata.org/app/source/defi/RamsesV1/)                                                                                                                                                                                                                                                     |
| [**RamsesV2**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV3Scraper.go#L104)                       | Arbitrum                                                                   | [https://www.diadata.org/app/source/defi/RamsesV2/](https://www.diadata.org/app/source/defi/RamsesV2/)                                                                                                                                                                                                                                                     |
| <img alt="" /> [**Solarbeam**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)            | Moonriver                                                                  | [https://www.diadata.org/app/source/defi/Solarbeam/](https://www.diadata.org/app/source/defi/Solarbeam/)                                                                                                                                                                                                                                                   |
| <img alt="" /> [**Spookyswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Fantom                                                                     | [https://www.diadata.org/app/source/defi/Spookyswap/](https://www.diadata.org/app/source/defi/Spookyswap/)                                                                                                                                                                                                                                                 |
| <img alt="" /> [**Stellaswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Moonbeam                                                                   | [https://www.diadata.org/app/source/defi/Stellaswap/](https://www.diadata.org/app/source/defi/Stellaswap/)                                                                                                                                                                                                                                                 |
| <img alt="" /> [**SushiSwap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)            | -Ethereum <br /> -Arbitrum <br /> -Fantom <br /> -Polygon                  | [Ethereum](https://www.diadata.org/app/source/defi/SushiSwap/), [Arbitrum](https://www.diadata.org/app/source/defi/SushiSwap-arbitrum/), [Fantom](https://www.diadata.org/app/source/defi/SushiSwap-fantom/), [Polygon](https://www.diadata.org/app/source/defi/SushiSwap-polygon/) sources                                                                |
| <img alt="" /> [**Tethys**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)               | Metis                                                                      | [https://www.diadata.org/app/source/defi/Tethys/](https://www.diadata.org/app/source/defi/Tethys/)                                                                                                                                                                                                                                                         |
| [**Thena**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go#L241)                          | Binance Smart Chain                                                        |                                                                                                                                                                                                                                                                                                                                                            |
| [**ThenaV3**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV3Scraper.go#L97)                         | Binance Smart Chain                                                        |                                                                                                                                                                                                                                                                                                                                                            |
| <img alt="" /> [**Trader Joe**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Avalanche                                                                  | [https://www.diadata.org/app/source/defi/TraderJoe/](https://www.diadata.org/app/source/defi/TraderJoe/)                                                                                                                                                                                                                                                   |
| <img alt="" /> [**Trader Joe 2.1**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/traderjoe2.1/traderjoe.go) | Avalanche                                                                  | [https://www.diadata.org/app/source/defi/TraderJoeV2.1-Arbitrum/](https://www.diadata.org/app/source/defi/TraderJoeV2.1-Arbitrum/)                                                                                                                                                                                                                         |
| [**Trader Joe 2.2**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/TraderJoeScraper.go#L112)                 | Avalanche                                                                  | [https://www.diadata.org/app/source/defi/TraderJoeV2.2-Avalanche/](https://www.diadata.org/app/source/defi/TraderJoeV2.2-Avalanche/)                                                                                                                                                                                                                       |
| <img alt="" /> [**Trisolaris**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Aurora                                                                     | [https://www.diadata.org/app/source/defi/Trisolaris/](https://www.diadata.org/app/source/defi/Trisolaris/)                                                                                                                                                                                                                                                 |
| <img alt="" /> [**Ubeswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)              | Celo                                                                       | [https://www.diadata.org/app/source/defi/Ubeswap/](https://www.diadata.org/app/source/defi/Ubeswap/)                                                                                                                                                                                                                                                       |
| <img alt="" /> [**Uniswap V2**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)           | Ethereum                                                                   | [https://www.diadata.org/app/source/defi/Uniswap/](https://www.diadata.org/app/source/defi/Uniswap/)                                                                                                                                                                                                                                                       |
| <img alt="" /> [**Uniswap V3**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV3Scraper.go)           | -Ethereum <br /> -Arbitrum <br /> -Polygon <br /> -Celo <br /> -Base       | [Ethereum](https://www.diadata.org/app/source/defi/UniswapV3/), [Arbitrum](https://www.diadata.org/app/source/defi/UniswapV3-Arbitrum/), [Polygon](https://www.diadata.org/app/source/defi/UniswapV3-polygon/), [Celo](https://www.diadata.org/app/source/defi/UniswapV3-Celo/), [Base](https://www.diadata.org/app/source/defi/UniswapV3-Base/) sources   |
| [**Velar**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/VelarScraper.go)                                   | Stacks                                                                     | [https://www.diadata.org/app/source/defi/Velar/](https://www.diadata.org/app/source/defi/Velar/)                                                                                                                                                                                                                                                           |
| <img alt="" /> [**Velodrome**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/velodrome/velodrome.go)         | Optimism                                                                   | [https://www.diadata.org/app/source/defi/Velodrome/](https://www.diadata.org/app/source/defi/Velodrome/)                                                                                                                                                                                                                                                   |
| <img alt="" /> [**Wanswap**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/UniswapV2Scraper.go)              | Wanchain                                                                   | [https://www.diadata.org/app/source/defi/Wanswap/](https://www.diadata.org/app/source/defi/Wanswap/)                                                                                                                                                                                                                                                       |
| <img alt="" /> [**Zenlink**](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/ZenlinkScraper.go)                | -Bifrost <br /> -Bifrost-Polkadot                                          | [Bifrost](https://www.diadata.org/app/source/defi/Zenlink/), and [Bifrost-Polkadot](https://www.diadata.org/app/source/defi/Zenlink-bifrost-polkadot/) sources                                                                                                                                                                                             |


# Data Sources
Source: https://www.diadata.org/docs/dia-stack/architecture/data-sources/overview



Every price point starts with raw trading data from cryptocurrency exchanges (CEXes, & DEXes). We go straight to the source, capturing and storing trade data with the highest precision possible.

Explore the sources that power our token price feeds:

<CardGroup>
  <Card title="CEXes data" href="/dia-stack/data-sources/cexes-data" icon="angle-right" />

  <Card title="DEXes data" href="/dia-stack/data-sources/dexes-data" icon="angle-right" />
</CardGroup>

For an up-to-date list of data sources, visit:

<CardGroup>
  <Card title="Data Sources | DIA App" href="https://www.diadata.org/app/source/defi/" icon={<img className="m-0" src="/images/data-products/favicon-new.png" />} />
</CardGroup>

## Verifiable Randomness

Explore how DIA leverages drand's distributed randomness beacon to provide verifiable, unbiased random numbers for on-chain applications like games, lotteries, and NFT drops:

<CardGroup>
  <Card title="Distributed Randomness Beacon" href="/dia-stack/architecture/data-sources/randomness" icon="angle-right" />
</CardGroup>

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp’s needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>


# Distributed Randomness Beacon
Source: https://www.diadata.org/docs/dia-stack/architecture/data-sources/randomness

DIA leverages Drand's distributed randomness beacon to provide verifiable, unbiased random numbers on-chain

To offer distributed and verifiable randomness on-chain, DIA leverages [drand](https://drand.love/)'s distributed randomness beacon. The beacon is run by a group of independent actors called the League of Entropy.

The [League of Entropy](https://www.cloudflare.com/leagueofentropy/) is a collaborative project to provide a verifiable, decentralized randomness beacon. A decentralized randomness beacon combines randomness from multiple independent high entropy sources to generate a truly unbiased random number for anyone that may need a public source of randomness.

Please visit the project site at [drand.love](https://drand.love/) for the most up-to-date information on current operations. To learn how the how distributed randomness beacon is built please [visit this link](https://drand.love/docs/specification/).

## What is randomness?

Randomness is the property of lacking any sensible predictability. It is very difficult to create random events on-chain due to the deterministic nature of any EVM or EVM-like environment.

Centralized randomness is susceptible for attacks by the randomness source, as a single non-random outcome cannot be distinguished from a random one. Thus, having a single RNG provide randomness via an oracle is not enough.

## Who needs randomness?

Random numbers can be very relevant for on-chain applications such as games, lotteries, prediction markets, or NFT launches.

Relying on pseudo-random values like the last blockhash can be manipulated by miners and is not advisable.

Drand run distributed nodes to produce their randomness beacon. They use [Pedersen's DKG (Distributed Key Generation) protocol](https://drand.love/docs/cryptography/#distributed-key-generation-dkg) to create collective private/public key. Participants in their League of Entropy then generate randomness in rounds and broadcast it together with its signature.

## On-chain publishing process

From random number generation to on-chain distribution, DIA xRandom operates as follows:

1. **Drand randomness generation:** in every drand epoch (currently set at 30s for the existing LoE beacons, but [planned to be decreased](https://drand.love/blog/2022/02/21/multi-frequency-support-and-timelock-encryption-capabilities/) on future "unchained" beacons) each of the nodes that form the drand network generates a partial signature, which it broadcasts to the rest of the nodes. Once any node has enough, i.e., a threshold number of signatures, it computes the new randomness beacon, which is the hash of the signature aggregate.

2. **Drand randomness propagation and consumption**: the new beacon is propagated through the network to all other nodes. Any node can verify and accept or reject the hash of the signature (i.e., beacon) that it received. Any client or application can consume randomness out of band (i.e., without needing to be part of the drand network) either through [the public HTTP APIs](https://drand.love/developer/http-api/) or through [libp2p's pubsub protocol](https://drand.love/developer/gossipsub/#public-endpoints), Gossipsub. Clients can also verify that the randomness they received is indeed the one produced by the drand network.

3. **DIA on-chain distribution:** the final randomness signature is shipped on-chain as an oracle smart contract. In order to effectively and securely execute these on-chain transactions, DIA has built a robust, decentralised node infrastructure — dubbed DIA xNode. DIA xNode is a network of third-party, decentralized node providers that grant DIA the blockchain infrastructure to push data on-chain ensuring high rate limits.

## Risk Mitigation

It is important to understand the risks of the randomness oracle before using it and to be able to mitigate them.

An extensive risk evaluation of the underlying [drand.love](https://drand.love/) protocol can be found [in their documentation](https://drand.love/docs/security-model/#notations). All risks listed there also affect the randomness guest oracle, as it serves as an underlying data provider.

Additionally, there are new risks introduced by using the oracle.

| Risk                                   | Possible Mitigation                                                                               |
| -------------------------------------- | ------------------------------------------------------------------------------------------------- |
| Oracle stops serving data              | Check that the oracle has recent updates in its history.                                          |
| Specific Round is missed by the oracle | Have your dApp use the next round if a certain round is unavailable (but later ones exist).       |
| Oracle serves compromised data         | Check the associated BLS signature provided by drand (Note: Currently not availabe on most EVMs). |


# Fundamental Feeds
Source: https://www.diadata.org/docs/dia-stack/data-products/fundamental-feeds

Derive asset values from their fundamentals rather than market prices. Ideal for stablecoins, synthetic assets, and yield-bearing tokens.

Fundamental Feeds provide an alternative to market-based pricing by calculating an asset's value directly from its fundamentals.
Instead of relying on exchange trades or liquidity-driven mechanisms, these feeds derive price from objective on-chain or off-chain proofs of collateral, redemption logic, and reserve holdings.

This makes them particularly relevant for synthetic assets, stablecoins, yield-bearing tokens, and structured vaults.

# Features

* Independent of market volatility or liquidity distortions.
* Transparent methodology based on verifiable reserves, liabilities, and contract logic.
* Applicable across DeFi instruments ranging from liquid staking tokens to stablecoins and vaults.

# Methodologies

## Contract Exchange Rate

For tokens with built-in exchange logic (e.g. stETH, aUSDC, cDAI), price is calculated from the ratio of underlying assets to total shares:

$$
exchangeRate = totalUnderlying / totalShares
$$

## Reserve-Backing

For collateral-backed assets, reserves are divided by circulating supply to produce a backing-based fundamental value:

$$
fundamentalPrice = reserves / supply
$$

Reserves may consist of multiple assets held across wallets.

## Net Asset Value (NAV)

For vault-based tokens, price equals the value of assets minus liabilities, divided by outstanding tokens:

$$
fundamentalPrice = (assets - liabilities) / totalSupply
$$

## Redemption Value

For mint/burn models, the fundamental value corresponds to the amount of underlying assets received when redeeming one token. This is typically retrievable directly from the redemption contract.

## Proof of Reserves

For custodial or synthetic assets, feeds can publish the total value of reserves as reported by verified custodians or proof-of-reserve attestations:

$$
reserveValue = \sum_{i=1}^{n} (reserves_i \times price_i)
$$

# Architecture Flow Overview

<Frame>
  <img />
</Frame>

* Each feeder is pulling balance sheets (reserves, supply).
* Lasernet is the ledger where all feeders submit their reports.
* The aggregator contract is consolidating those reports into one official number.
* The messaging layer is delivering that number to every chain where it's needed.
* Protocols then rely on this official number to decide risk and operations.

# Use Cases

* **Stablecoins**: Validate peg integrity by comparing market price to backing-based fundamental value.
* **Yield-bearing Tokens (LSTs, aTokens, cTokens)**: Track accruing value through exchange rates.
* **Vaults and Structured Products**: Monitor NAV in real time to ensure accurate token pricing.
* **Synthetic Assets**: Ensure collateralization ratios remain healthy through reserve-backed valuations.

# Developer Notes

Fundamental Feeds can operate alongside traditional market price feeds. Protocols can consume both sources to implement safeguards such as:

* Depeg monitoring (triggering alerts if fundamental value diverges from market price).
* Fallback mechanisms to fundamental pricing when market feeds become unreliable.
* Enhanced transparency by exposing raw inputs such as reserve addresses or contract state.

If you're interested in integrating Fundamental Feeds into your project, request a custom oracle below:

<CardGroup>
  <Card title="Request a Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>


# Real-World Asset Feeds
Source: https://www.diadata.org/docs/dia-stack/data-products/rwa-price-feeds

DIA xReal is designed for Real-World Asset (RWA) applications, bringing hundreds of data feeds for stocks, commodities, FX rates, and more on-chain.

## Overview

DIA xReal is designed for Real-World Asset (RWA) applications, bringing hundreds of data feeds for stocks, commodities, FX rates, and more on-chain.

It consists of two core components:

<CardGroup>
  <Card title="xReal Price Feeds" icon="square-1">
    Secure, transparent price oracles for RWA-powered dApps (options, futures,
    tokenized index funds & more)
  </Card>

  <Card title="xReal Custom Solutions" icon="square-2">
    On-demand oracles for tokenized assets, bond yields, FX rates, & real-world
    financial metrics
  </Card>
</CardGroup>

You can access all the available RWA data feeds & integration options below:

<Card title="Real-World Asset (RWA) Price Feed Oracles | DIA App" href="https://www.diadata.org/app/rwa/" icon={<img className="m-0" src="/images/data-products/favicon-new.png" />} />

## Learn More

<CardGroup>
  <Card title="Request a Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />

  <Card title="RWA Price APIs" href="/reference/apis/rwa-prices" icon="server" />

  <Card title="Methodologies" href="/guides/methodologies-overview" icon="chart-line" />

  <Card title="Fetch Price Data" href="/guides/how-to-guides/fetch-price-data" icon="chart-line" />

  <Card title="Supported Networks" href="/guides/chain-guides-overview" icon="network-wired" />
</CardGroup>


# Token Price Feeds
Source: https://www.diadata.org/docs/dia-stack/data-products/token-price-feeds

DIA token price feeds provide smart contracts with real-time price information of cryptocurrencies, transparently sourced from high-volume DEXs and CEXs.

## xMarket Overview

DIA xMarket feeds provide smart contracts **real-time price information of 3,000+ cryptocurrencies**, transparently sourced from 100+ trusted, high-volume DEXs and CEXs.

The feeds facilitate the development of DeFi use cases such as money markets, lending/borrowing, synthetic asset issuance, options, derivatives and futures markets, and many more.

Browse all tokens that DIA's data library currently supports via the link below. New assets can also be supported on demand.

<Card title="Token Price Feeds|DIA App" href="https://www.diadata.org/app/price/" icon={<img className="m-0" src="/images/data-products/favicon-new.png" />} />

You can also check the list of data sources on the app.

<Card title="Data Sources|DIA App" href="https://www.diadata.org/app/source/defi/" icon={<img className="m-0" src="/images/data-products/favicon-new.png" />} />

## How It Works

<Frame>
  <img />
</Frame>

Each [feeder](/reference/architecture/data-sourcing#feeder) in the Decentralized Feeder Network runs scrapers that collect real-time trade data from CEXes and DEXes for specific trading pairs (e.g., BTC-USDT) that are then forwarded to the Collector which bundles them into atomic tradeblocks (grouped by market and exchange). The Processor then performs a two-step aggregation: first aggregating trades within each atomic tradeblock into a single value, then combining these values into a final price, which is submitted to the designated Pod (feeder contract) on-chain.

This enables your dApp to access first-party and verifiable data delivered from our decentralized feeder network!

## Learn More

<CardGroup>
  <Card title="Request a custom oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />

  <Card title="Fetch Price Data" href="/guides/how-to-guides/fetch-price-data" icon="code" />

  <Card title="Methodologies" href="/guides/methodologies-overview" icon="chart-line" />

  <Card title="Token Price APIs" href="/reference/apis/token-prices" icon="server" />

  <Card title="Data Sources" href="/dia-stack/architecture/data-sources/overview" icon="database" />
</CardGroup>


# Verifiable Randomness
Source: https://www.diadata.org/docs/dia-stack/data-products/verifiable-randomness

DIA xRandom provides smart contracts with unpredictable random numbers.

## xRandom Overview

DIA xRandom leverages [drand](https://drand.love/)'s distributed randomness beacon, enabling verifiable, unpredictable and unbiased random numbers. Currently, the randomness is updated every 30 seconds and is expected to upgrade soon.

The randomness oracle enables the creation of on-chain applications including but not limited to on-chain gaming, lotteries, prediction markets, and NFT launches​.

Browse the latest randomness rounds in the DIA App:

<Card title="Randomness|DIA App" href="https://www.diadata.org/app/randomness/" icon={<img className="m-0" src="/images/data-products/favicon-new.png" />} />

## Learn More

<CardGroup>
  <Card title="Request a Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />

  <Card title="Integrate DIA xRandom" href="/guides/how-to-guides/generate-randomness" icon="code" />

  <Card title="What is Randomness?" href="https://www.youtube.com/watch?v=7HALDJr8V3g" icon="question" />

  <Card title="Challenges of on-chain randomness" href="https://youtu.be/32d7QvFXoIk?feature=shared" icon="triangle-exclamation" />

  <Card title="Distributed Randomness Beacon" href="/dia-stack/architecture/data-sources/randomness" icon="shuffle" />

  <Card title="Oracle Contract" href="/guides/general-guides/smart-contracts/diarandomoracle.sol" icon="file-code" />
</CardGroup>


# DIA Stack Overview
Source: https://www.diadata.org/docs/dia-stack/overview

DIA is a fully on-chain, trustless oracle architecture featuring permissionless access and modular design, powered by an Ethereum Layer-2 core. Developed by DIA, open for all.

## Introduction to DIA

DIA's architecture focuses on maximizing decentralization and trustless execution. It is composed of state-of-the-art modular components that use Lasernet, DIA’s native Ethereum layer-2 rollup, as its core settlement layer for critical data operations such as computation and verification.

DIA tackles traditional blockchain oracles' issues through its rollup-powered architecture:

* Independent nodes fetch data directly from sources (CEXs, DEXs, more)
* Data is submitted on-chain to DIA Lasernet – DIA's ETH L2 rollup
* Processing and aggregation of data happen on-chain
* Transactions are settled on-chain transparently

## Features

<CardGroup>
  <Card title="Crypto-economic security" icon="lock">
    Decentralized data sourcing by independent Feeder nodes, backed by staked
    assets.
  </Card>

  <Card title="Any asset from any chain" icon="link">
    DIA’s first-party data sourcing capabilities one of its core benefit,
    enabling unlimited asset coverage.
  </Card>

  <Card title="Deploy anywhere, fast" icon="rocket">
    Seamless data transmission to any chain significantly reduces time to market
    and friction in the developer UX.
  </Card>

  <Card title="Open and permissionless" icon="user-group">
    Anyone can contribute to the system’s security or self-deploy and manage
    oracles contracts.
  </Card>

  <Card title="Full data transparency" icon="eye">
    From granular data sourcing to immutable processing trails, the stack
    ensures that everything is fully traceable.
  </Card>

  <Card title="No trust assumptions" icon="circle-check">
    Data computation happens on-chain via smart contracts, enabling full
    verifiability of the end-to-end process.
  </Card>
</CardGroup>

## Data Flow: From Source to Feed

DIA is composed of three main stages, each critical to ensuring the accuracy, reliability, and accessibility of your data.

<Frame>
  <img alt="" />
</Frame>

| Component                        | Description                                                                                                                                                                                                                                                     | Learn more                                                            |
| -------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| **Feeders (Sourcing Layer)**     | Collect real-time data from decentralized exchanges (DEXs), centralized exchanges (CEXs), and other sources through **Feeders**. Learn how our decentralized network of nodes ensures that your data is accurate, timely, and sourced directly from the market. | [Feeders](/dia-stack/architecture/core-components/feeders)            |
| **Lasernet (Aggregation Layer)** | Process and verify the collected data using **Pods** and **Aggregators** within the **LaserNet** infrastructure. Dive into how these components transform raw data into reliable and secure price feeds for your dApp.                                          | [Lasernet](/dia-stack/architecture/core-components/lasernet/overview) |
| **Spectra (Messaging Layer)**    | Deliver processed data across multiple blockchains using **Spectra**, our industry-leading cross-chain messaging protocol. Discover how LaserNet makes it easy to integrate DIA’s oracle data into any blockchain environment.                                  | [Spectra](/dia-stack/architecture/core-components/spectra)            |

For a breakdown of each process, read the [Architecture](/dia-stack/architecture/core-components/overview) section.


# Overview
Source: https://www.diadata.org/docs/guides/chain-guides-overview

Chain-specific guides for accessing DIA oracle price feeds on each supported blockchain network.

<Info>
  [Bring DIA Oracles to Your Blockchain
  Network](/guides/how-to-guides/request-a-custom-oracle)
</Info>

<CardGroup>
  <Card title="Alephium" href="/guides/chain-specific-guide/alephium" />

  <Card title="Arbitrum" href="/guides/chain-specific-guide/arbitrum" />

  <Card title="Astar" href="/guides/chain-specific-guide/astar" />

  <Card title="Aurora" href="/guides/chain-specific-guide/aurora" />

  <Card title="Avalanche" href="/guides/chain-specific-guide/avalanche" />

  <Card title="Base" href="/guides/chain-specific-guide/base" />

  <Card title="GEB Network" href="/guides/chain-specific-guide/bevm" />

  <Card title="BNB Chain" href="/guides/chain-specific-guide/bnb-chain" />

  <Card title="Boba Network" href="/guides/chain-specific-guide/boba-network" />

  <Card title="BOB Build on Bitcoin" href="/guides/chain-specific-guide/bob-build-on-bitcoin" />

  <Card title="Celo" href="/guides/chain-specific-guide/celo" />

  <Card title="Clover" href="/guides/chain-specific-guide/clover" />

  <Card title="Cross Finance (CrossFi)" href="/guides/chain-specific-guide/crossfi" />

  <Card title="Edu Chain" href="/guides/chain-specific-guide/edu-chain" />

  <Card title="Ethereum" href="/guides/chain-specific-guide/ethereum" />

  <Card title="ETHPar" href="/guides/chain-specific-guide/ethpar" />

  <Card title="Evmos" href="/guides/chain-specific-guide/evmos" />

  <Card title="Fantom" href="/guides/chain-specific-guide/fantom" />

  <Card title="Fuse" href="/guides/chain-specific-guide/fuse" />

  <Card title="Gnosis Chain" href="/guides/chain-specific-guide/gnosis-chain" />

  <Card title="GOAT Network" href="/guides/chain-specific-guide/goat-network" />

  <Card title="Hydration" href="/guides/chain-specific-guide/hydration" />

  <Card title="Kadena" href="/guides/chain-specific-guide/kadena" />

  <Card title="Linea" href="/guides/chain-specific-guide/linea" />

  <Card title="LUKSO" href="/guides/chain-specific-guide/lukso" />

  <Card title="Metis" href="/guides/chain-specific-guide/metis" />

  <Card title="Moonbase" href="/guides/chain-specific-guide/moonbase" />

  <Card title="Moonbeam" href="/guides/chain-specific-guide/moonbeam" />

  <Card title="Moonriver" href="/guides/chain-specific-guide/moonriver" />

  <Card title="Nervos" href="/guides/chain-specific-guide/nervos" />

  <Card title="OKT Chain (OKX)" href="/guides/chain-specific-guide/okt-chain" />

  <Card title="Optimism" href="/guides/chain-specific-guide/optimism" />

  <Card title="Plume" href="/guides/chain-specific-guide/plume" />

  <Card title="Polygon" href="/guides/chain-specific-guide/polygon" />

  <Card title="Polygon zkEVM" href="/guides/chain-specific-guide/polygon-zkevm" />

  <Card title="Shiden" href="/guides/chain-specific-guide/shiden" />

  <Card title="Shibuya" href="/guides/chain-specific-guide/shibuya" />

  <Card title="Shido" href="/guides/chain-specific-guide/shido" />

  <Card title="Somnia" href="/guides/chain-specific-guide/somnia" />

  <Card title="Sonic" href="/guides/chain-specific-guide/sonic" />

  <Card title="Soroban" href="/guides/chain-specific-guide/soroban" />

  <Card title="Stacks" href="/guides/chain-specific-guide/stacks" />

  <Card title="Superseed" href="/guides/chain-specific-guide/superseed" />

  <Card title="Swell" href="/guides/chain-specific-guide/swell" />

  <Card title="Telos" href="/guides/chain-specific-guide/telos" />

  <Card title="Unichain" href="/guides/chain-specific-guide/unichain" />

  <Card title="Units Network" href="/guides/chain-specific-guide/units-network" />

  <Card title="Velas" href="/guides/chain-specific-guide/velas" />

  <Card title="W Chain" href="/guides/chain-specific-guide/w-chain" />

  <Card title="Wanchain" href="/guides/chain-specific-guide/wanchain" />

  <Card title="XRPL" href="/guides/chain-specific-guide/xrp-ledger-xrpl" />

  <Card title="zkSync" href="/guides/chain-specific-guide/zksync" />
</CardGroup>


# Alephium
Source: https://www.diadata.org/docs/guides/chain-specific-guide/alephium

dApps built on Alephium can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

# Token Price Feeds

## Oracle details

| Chain   | Address                                                                                                                                |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [285zrkZTPpUCpjKg9E3z238VmpUBQEAbESGsJT6yX7Rod](https://explorer.alephium.org/addresses/285zrkZTPpUCpjKg9E3z238VmpUBQEAbESGsJT6yX7Rod) |
| Testnet | [216wgM3Xi5uBFYwwiw2T7iZoCy9vozPJ4XjToW74nQjbV](https://testnet.alephium.org/addresses/216wgM3Xi5uBFYwwiw2T7iZoCy9vozPJ4XjToW74nQjbV)  |

## Oracle configuration

|                                       |                                                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.2% and 120 seconds                                                                                                       |
| **Heartbeat**                         | 10mins                                                                                                                     |

## Asset feeds

| Asset Ticker | getValue(key) | Asset Markets                                                                                                  |
| ------------ | ------------- | -------------------------------------------------------------------------------------------------------------- |
| BTC          | BTC/USD       | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)     |
| USDC         | USDC/USD      | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)   |
| ETH          | ETH/USD       | [ETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)    |
| WBTC         | WBTC/USD      | [WBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/)   |
| USDT         | USDT/USD      | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)   |
| ALPH         | ALPH/USD      | [ALPH markets](https://www.diadata.org/app/price/asset/Alephium/tgx7VNFoP9DJiFMFgXXtafQZkUvyEdDHT9ryamHJYrjq/) |
| AYIN         | AYIN/USD      | [AYIN markets](https://www.diadata.org/app/price/asset/Alephium/vT49PY8ksoUL6NcXiZ1t2wAmC7tTPRfFfER8n3UCLvXy/) |

## How to access data

Locate one of the deployed contracts (either testnet or mainnet) and call the `getValue` function. This function expects one parameter, which is the symbols of the asset you want to retrieve and a “/USD”, so for example for the Bitcoin price the parameter must be “BTC/USD”.

This will return two values:

1. The price of the asset, with 8 decimals.

2. The timestamp of the last update in Unix time format, in UTC timezone.

Below is the `DIAOracle` contract implementation in [Ralph](https://docs.alephium.org/ralph/):

```js theme={"system"}
Contract DIAOracle(
    mut admin: Address
) extends DIAOracleBase(admin) implements IDIAOracle {
    mapping[ByteVec, DIAOracleValue] onchainValues

    event OracleUpdate(key: ByteVec, value: U256, timestamp: U256)

    const MaxBatchSize = 10

    enum ErrorCodes {
        InvalidBatchSize = 1
        InvalidKey = 2
    }

    pub fn getValue(key: ByteVec) -> DIAOracleValue {
        if (!onchainValues.contains!(key)) {
            panic!(ErrorCodes.InvalidKey)
        }

        return onchainValues[key]
    }

    @using(preapprovedAssets = true)
    pub fn setValue(key: ByteVec, value: U256, timestamp: U256) -> () {
        checkAdmin(callerAddress!())
        updateValue{admin -> ALPH: mapEntryDeposit!()}(key, value, timestamp)
    }

    @using(preapprovedAssets = true)
    pub fn setMultipleValues(
        keys: [ByteVec; 10],
        values: [U256; 10],
        timestamps: [U256; 10],
        batchSize: U256
    ) -> () {
        checkAdmin(callerAddress!())
        assert!(batchSize <= MaxBatchSize, ErrorCodes.InvalidBatchSize)

        for (let mut i = 0; i < batchSize; i = i + 1) {
            updateValue{admin -> ALPH: mapEntryDeposit!()}(
                keys[i],
                values[i],
                timestamps[i]
            )
        }
    }

    @using(preapprovedAssets = true)
    fn updateValue(key: ByteVec, value: U256, timestamp: U256) -> () {
        if (!onchainValues.contains!(key)) {
            onchainValues.insert!(admin, key, DIAOracleValue{value, timestamp})
        } else {
            onchainValues[key] = DIAOracleValue{value, timestamp}
        }

        emit OracleUpdate(key, value, timestamp)
    }
}
```

***

# Verifiable Randomness

## Oracle details

| Chain            | Address                                                                                                                               |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Alephium Mainnet | [v1v4cBXP9L7M9ryZZCx7tuXuNb9pnDLGb3JJkPBpbR1Z](https://explorer.alephium.org/addresses/v1v4cBXP9L7M9ryZZCx7tuXuNb9pnDLGb3JJkPBpbR1Z)  |
| Alephium Testnet | [217k7FMPgahEQWCfSA1BN5TaxPsFovjPagpujkyxKDvS3](https://testnet.alephium.org/addresses/217k7FMPgahEQWCfSA1BN5TaxPsFovjPagpujkyxKDvS3) |

## Oracle configuration

The oracle uses [drand](https://drand.love/) randomness from the quicknet mainnet to provide randomness on Alephium.

## How to access data

To consume randomness data, you'll need to invoke the `getLastRound` method on the oracle contract. It will return the round ID of the latest update.

Using this round ID, you can call `getRandomValue` and will receive a return value of that randomness, the round ID and the BLS signature from the drand API.

Note that round IDs are used round-robin and will repeat after 1000 iterations.

Below is the `DIARandomOracle` contract implementation in [Ralph](https://docs.alephium.org/ralph/):

```js theme={"system"}
Contract DIARandomOracle(
    mut admin: Address,
    mut lastRound: U256
) extends DIAOracleBase(admin) implements IDIARandomOracle {

    mapping[U256, DIARandomValue] randomValues

    event OracleUpdate(
        round: U256,
        randomness: ByteVec,
        signature: ByteVec
    )

    const MaxSlot = 1000

    enum ErrorCodes {
        InvalidRound = 1
        RoundKeyNotExist = 2
        RoundIsExpired = 3
    }

    pub fn getLastRound() -> U256 {
        return lastRound
    }

    pub fn getRandomValue(realRound: U256) -> DIARandomValue {
        let roundKey = realRound % MaxSlot
        assert!(randomValues.contains!(roundKey), ErrorCodes.RoundKeyNotExist)

        let randomValue = randomValues[roundKey]
        assert!(randomValue.round == realRound, ErrorCodes.RoundIsExpired)
        return randomValue
    }

    @using(preapprovedAssets = true, updateFields = true)
    pub fn setRandomValue(value: DIARandomValue) -> () {
        checkAdmin(callerAddress!())
        assert!(value.round > lastRound, ErrorCodes.InvalidRound)

        let roundKey = value.round % MaxSlot
        lastRound = value.round

        if (randomValues.contains!(roundKey)) {
            randomValues[roundKey] = value
        } else {
            randomValues.insert!(admin, roundKey, value)
        }

        emit OracleUpdate(value.round, value.randomness, value.signature)
    }
}
```

You can learn more [here](/dia-stack/data-products/verifiable-randomness).

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Alephium. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Arbitrum
Source: https://www.diadata.org/docs/guides/chain-specific-guide/arbitrum

dApps built on Arbitrum can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

Demo oracles are available for testing the new fully verifiable & decentralized [Lumina stack](/dia-stack/overview) on Arbitrum Mainnet & Testnet:

<Accordion title="Token Price Feeds">
  #### Oracle Contracts

  ##### Mainnet

  | Chain   | Oracle Type | Address                                                                                                              |
  | ------- | ----------- | -------------------------------------------------------------------------------------------------------------------- |
  | Mainnet | Push Oracle | [0xA42217338614B7e67D022C52D1CD38e02D619bb0](https://arbiscan.io/address/0xa42217338614b7e67d022c52d1cd38e02d619bb0) |

  ##### Testnet

  | Chain   | Oracle Type | Address                                                                                                                      |
  | ------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
  | Sepolia | Push Oracle | [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://sepolia.arbiscan.io/address/0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0) |

  #### Oracle Configuration

  |                                       |                    |
  | ------------------------------------- | ------------------ |
  | **Pricing Methodology**               | Median             |
  | **Deviation (%) & Refresh Frequency** | 2% and 120 seconds |
  | **Heartbeat**                         | 12h                |

  #### Available Asset Feeds

  | Asset Ticker | updates(key) | Asset Markets                                                                                                |
  | :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
  | ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
  | BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
  | DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
  | USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
</Accordion>

<Accordion title="RWA Price Feeds">
  #### Oracle Contracts

  #### Mainnet

  | Chain   | Oracle Type | Address                                                                                                              |
  | ------- | ----------- | -------------------------------------------------------------------------------------------------------------------- |
  | Mainnet | Push Oracle | [0xEB3b12FB37090ACc6773B59619799941536FA198](https://arbiscan.io/address/0xEB3b12FB37090ACc6773B59619799941536FA198) |

  ### Oracle Configuration

  |                                       |                    |
  | ------------------------------------- | ------------------ |
  | **Pricing Methodology**               | Median             |
  | **Deviation (%) & Refresh Frequency** | 1% and 120 seconds |
  | **Heartbeat**                         | 24h                |

  #### Available Asset Feeds

  * APPL
  * XAU/USD
  * USD/EUR
</Accordion>

***

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Additional Details

You can find the contract addresses for the Arbitrum bridge's components on mainnet and testnet below:

<Accordion title="Mainnet">
  * [MailBox
    Contract](https://arbiscan.io/address/0x979ca5202784112f4738403dbec5d0f3b9daabb9)
  * [ISM
    Contract](https://arbiscan.io/address/0x92f0f4c9f769ed83609cd2ccd1acce224bbc8cbf)
  * [Protocol Fee Hook
    Contract](https://arbiscan.io/address/0x048050547eb6e68cB37Fb21EEafEad40CF2CbdbB)
</Accordion>

<Accordion title="Testnet">
  * [MailBox
    Contract](https://sepolia.arbiscan.io/address/0x598face78a4302f11e3de0bee1894da0b2cb71f8)
  * [ISM
    Contract](https://sepolia.arbiscan.io/address/0xb869617a3CFcdA07A4cC230d996120074e7c817e)
  * [Protocol Fee Hook
    Contract](https://sepolia.arbiscan.io/address/0x611c8b288c642336136a436d7125ac49fa71468b)
</Accordion>

Learn more about DIA's cross-chain messaging layer [here](/dia-stack/architecture/core-components/spectra).

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Arbitrum. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Astar
Source: https://www.diadata.org/docs/guides/chain-specific-guide/astar

dApps built on Astar can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Aurora
Source: https://www.diadata.org/docs/guides/chain-specific-guide/aurora

dApps built on Aurora can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

### Oracle Contracts

| Chain   | Address                                                                                                                              |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| Mainnet | [0xf4e9C0697c6B35fbDe5a17DB93196Afd7aDFe84f](https://explorer.aurora.dev/address/0xf4e9C0697c6B35fbDe5a17DB93196Afd7aDFe84f)         |
| Testnet | [0xf4e9C0697c6B35fbDe5a17DB93196Afd7aDFe84f](https://explorer.testnet.aurora.dev/address/0xf4e9C0697c6B35fbDe5a17DB93196Afd7aDFe84f) |

### Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                    |
| **Heartbeat**                         | 30 minutes                                                                                              |

### Available Asset Feeds

| Asset Ticker | getValue(key) | Asset Markets                                                                                                |
| ------------ | ------------- | ------------------------------------------------------------------------------------------------------------ |
| BTC          | BTC/USD       | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| USDC         | USDC/USD      | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
| DIA          | DIA/USD       | [DIA markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |

***

## How to Access Data

### getValue Method

To consume price data, you'll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on Aurora mainnet. If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0xf4e9C0697c6B35fbDe5a17DB93196Afd7aDFe84f;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Aurora. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Avalanche
Source: https://www.diadata.org/docs/guides/chain-specific-guide/avalanche

dApps built on Avalanche can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Avalanche. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Base
Source: https://www.diadata.org/docs/guides/chain-specific-guide/base

dApps built on Base can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

### Oracle Contracts

#### Mainnet

| Contract    | Address                                                                                                               |
| ----------- | --------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0xA42217338614B7e67D022C52D1CD38e02D619bb0](https://basescan.org/address/0xa42217338614b7e67d022c52d1cd38e02d619bb0) |

#### Testnet

| Contract    | Address                                                                                                                       |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://sepolia.basescan.org/address/0x9bb71344ed950f9cfd85ee1c7258553b01d95fa0) |

### Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 2% and 120 seconds                                                                                      |
| **Heartbeat**                         | 12h                                                                                                     |

### Available Asset Feeds

| Asset Ticker | updates(key) | Asset Markets                                                                                                |
| :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
| ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
| BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
| USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |

***

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Additional Details

You can find the contract addresses for the Base bridge's components on mainnet and testnet below:

<Accordion title="Mainnet">
  * [MailBox
    Contract](https://arbiscan.io/address/0x979ca5202784112f4738403dbec5d0f3b9daabb9)
  * [ISM
    Contract](https://arbiscan.io/address/0x92f0f4c9f769ed83609cd2ccd1acce224bbc8cbf)
  * [Protocol Fee Hook
    Contract](https://arbiscan.io/address/0x048050547eb6e68cB37Fb21EEafEad40CF2CbdbB)
</Accordion>

<Accordion title="Testnet">
  * [MailBox
    Contract](https://sepolia.basescan.org/address/0x6966b0e55883d49bfb24539356a2f8a673e02039)
  * [ISM
    Contract](https://sepolia.basescan.org/address/0xb869617a3cfcda07a4cc230d996120074e7c817e)
  * [Protocol Fee Hook
    Contract](https://sepolia.basescan.org/address/0x611C8b288c642336136a436d7125AC49FA71468B)
</Accordion>

Learn more about DIA's cross-chain messaging layer [here](/dia-stack/architecture/core-components/spectra).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# GEB Network
Source: https://www.diadata.org/docs/guides/chain-specific-guide/bevm

dApps built on GEB Network can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on BNB Chain. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# BNB Chain
Source: https://www.diadata.org/docs/guides/chain-specific-guide/bnb-chain

dApps built on BNB Chain can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on BNB Chain. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# BOB Build on Bitcoin
Source: https://www.diadata.org/docs/guides/chain-specific-guide/bob-build-on-bitcoin

dApps built on BOB Build on Bitcoin can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on BOB Build on Bitcoin. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Boba Network
Source: https://www.diadata.org/docs/guides/chain-specific-guide/boba-network

dApps built on Boba Network can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Celo
Source: https://www.diadata.org/docs/guides/chain-specific-guide/celo

dApps built on Celo can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Clover
Source: https://www.diadata.org/docs/guides/chain-specific-guide/clover

dApps built on Clover can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# CrossFi
Source: https://www.diadata.org/docs/guides/chain-specific-guide/crossfi

dApps built on CrossFi can leverage DIA oracles to access up-to-date asset price information.

# Token Price Feeds

## Oracle Details

| Chain   | Address                                                                                                                   |
| ------- | ------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0x859e221ada7cebdf5d4040bf6a2b8959c05a4233](https://xfiscan.com/address/0x859e221ada7cebdf5d4040bf6a2b8959c05a4233)      |
| Testnet | [0x33df80cdf0c9ff686261b11263d9f4a3ccc3d07f](https://test.xfiscan.com/address/0x33df80cdf0c9ff686261b11263d9f4a3ccc3d07f) |

## Oracle Configuration

|                                       |                                                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                                       |
| **Heartbeat**                         | 24h                                                                                                                        |

## Available Asset Feeds

### Mainnet

| Asset Ticker | getValue(key) | Asset Markets                                                                                                |
| ------------ | ------------- | ------------------------------------------------------------------------------------------------------------ |
| USDT         | USDT/USD      | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/) |
| USDC         | USDC/USD      | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
| XFI          | XFI/USD       | [XFI Markets](https://www.diadata.org/app/price/asset/Ethereum/0xC8CeED65E236F7d6fB378b8715f9e6912e486A54/)  |

### Testnet

| Asset Ticker | getValue(key) | Asset Markets                                                                                                         |
| :----------- | :------------ | :-------------------------------------------------------------------------------------------------------------------- |
| WETH         | WETH/USD      | [WETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/)          |
| WBTC         | WBTC/USD      | [WBTC Markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/)          |
| USDT         | USDT/USD      | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)          |
| DAI          | DAI/USD       | [DAI Markets](https://www.diadata.org/app/price/asset/Ethereum/0x6B175474E89094C44Da98b954EedeAC495271d0F/)           |
| USDC         | USDC/USD      | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)          |
| FRAX         | FRAX/USD      | [FRAX Markets](https://www.diadata.org/app/price/asset/Ethereum/0x853d955aCEf822Db058eb8505911ED77F175b99e/)          |
| LINK         | LINK/USD      | [LINK Markets](https://www.diadata.org/app/price/asset/Ethereum/0x514910771AF9Ca656af840dff83E8264EcF986CA/)          |
| WBNB         | WBNB/USD      | [WBNB Markets](https://www.diadata.org/app/price/asset/BinanceSmartChain/0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c/) |
| EUR          | EUR/USD       | [EUR Markets](https://www.diadata.org/app/price/asset/Fiat/978/)                                                      |
| XFI          | XFI/USD       | [XFI Markets](https://www.diadata.org/app/price/asset/Ethereum/0xC8CeED65E236F7d6fB378b8715f9e6912e486A54/)           |

## How to Access Data

### getValue Method

To consume price data, you’ll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on CrossFi Testnet. If you pass `WBTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}

pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0x859e221ada7cebdf5d4040bf6a2b8959c05a4233;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

***

# Verifiable Randomness

### Oracle Details

| Chain   | Address                                                                                                                   |
| ------- | ------------------------------------------------------------------------------------------------------------------------- |
| Testnet | [0xad19b5b3a0bf2bacf028ed6cc9e3fc153cb405b6](https://test.xfiscan.com/address/0xad19b5b3a0bf2bacf028ed6cc9e3fc153cb405b6) |

### Oracle Configuration

The oracle uses [drand](https://drand.love/) randomness from quicknet to provide randomness on CrossFi.

### How to Access Data

To consume randomness data, you'll need to invoke the `getLastRound` method on the oracle contract. It will return the round ID of the latest update.

Using this round ID, you can call `getRandomValue` and will receive a return value of that randomness, the round ID and the BLS signature from the drand API.

Note that round IDs are used round-robin and will repeat after 1000 iterations.

Refer to the [Solidity guide](/guides/how-to-guides/generate-randomness/solidity) for detailed steps on fetching random values from the oracle in your contract. You can learn more about the randomness protocol [here](/dia-stack/data-products/verifiable-randomness).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Edu Chain
Source: https://www.diadata.org/docs/guides/chain-specific-guide/edu-chain

dApps built on EduChain can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                                   |
| ------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0x56BddAc934157c213c37864e3443E5196b47a1d1](https://educhain.blockscout.com/address/0x56BddAc934157c213c37864e3443E5196b47a1d1)          |
| Testnet | [0x6626f442ebc679f7e35bc62e36e3c1e8820c81c9](https://edu-chain-testnet.blockscout.com/address/0x6626f442eBc679f7e35bC62E36E3c1e8820C81C9) |

## Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                    |
| **Heartbeat**                         | 24h                                                                                                     |

## Available Asset Feeds

| Asset Ticker | getValue(key) | Asset Markets                                                                                                        |
| ------------ | ------------- | -------------------------------------------------------------------------------------------------------------------- |
| EDU          | EDU/USD       | [EDU markets](https://www.diadata.org/app/price/asset/BinanceSmartChain/0xBdEAe1cA48894A1759A8374D63925f21f2Ee2639/) |
| ETH          | ETH/USD       | [ETH markets](http://diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)               |
| WBTC         | WBTC/USD      | [WBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/)         |
| USDC         | USDC/USD      | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)         |
| USDT         | USDT/USD      | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)         |
| DAI          | DAI/USD       | [DAI markets](https://www.diadata.org/app/price/asset/Ethereum/0x6B175474E89094C44Da98b954EedeAC495271d0F/)          |
| ARB          | ARB/USD       | [ARB markets](https://www.diadata.org/app/price/asset/Arbitrum/0x912CE59144191C1204E64559FE8253a0e49E6548/)          |
| wstETH       | wstETH/USD    | [wstETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0/)       |
| GRAIL        | GRAIL/USD     | [GRAIL markets](https://www.diadata.org/app/price/asset/Arbitrum/0x3d9907F9a368ad0a51Be60f7Da3b97cf940982D8/)        |

***

## How to Access Data

### getValue Method

To consume price data, you’ll need to invoke the `getValue` method on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#access-the-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from the oracle on EduChain testnet using the **IDIAOracleV2** interface. If you pass `WBTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 8258705325665 is \$82,587.05325665) along with the Unix timestamp of the last price update.

```js theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer {

    address immutable ORACLE = 0x6626f442ebc679f7e35bc62e36e3c1e8820c81c9;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Ethereum
Source: https://www.diadata.org/docs/guides/chain-specific-guide/ethereum

dApps built on Ethereum can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

### Oracle Contracts

#### Testnet

| Contract    | Address                                                                                                                       |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://sepolia.etherscan.io/address/0x9bb71344ed950f9cfd85ee1c7258553b01d95fa0) |

### Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 2% and 120 seconds                                                                                      |
| **Heartbeat**                         | 12h                                                                                                     |

### Available Asset Feeds

| Asset Ticker | updates(key) | Asset Markets                                                                                                |
| :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
| ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
| BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
| USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |

***

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Additional Details

You can find the contract addresses for the Ethereum bridge's components on testnet below:

<Accordion title="Testnet">
  * [MailBox
    Contract](https://sepolia.etherscan.io/address/0xffaef09b3cd11d9b20d1a19becca54eec2884766)
  * [ISM
    Contract](https://sepolia.etherscan.io/address/0xb869617a3cfcda07a4cc230d996120074e7c817e)
  * [Protocol Fee Hook
    Contract](https://sepolia.etherscan.io/address/0x611c8b288c642336136a436d7125ac49fa71468b)
</Accordion>

Learn more about DIA's cross-chain messaging layer [here](/dia-stack/architecture/core-components/spectra).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# ETHPar
Source: https://www.diadata.org/docs/guides/chain-specific-guide/ethpar

dApps built on ETHPar can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                  |
| ------- | ------------------------------------------------------------------------------------------------------------------------ |
| Mainnet | [0xA3014376A788b55450c5C1F2bA2A8694a79f0b97](https://dora.ethpar.net/address/0xA3014376A788b55450c5C1F2bA2A8694a79f0b97) |

## Oracle Configuration

|                                       |                                                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                                       |
| **Heartbeat**                         | 24h                                                                                                                        |

## Available Asset Feeds

| Asset Ticker | getValue(key) | Asset Markets                                                                                                |
| ------------ | ------------- | ------------------------------------------------------------------------------------------------------------ |
| WBTC         | WBTC/USD      | [WBTC Markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/) |
| WETH         | WETH/USD      | [WETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/) |

***

## How to Access Data

### getValue Method

To consume price data, you’ll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on ETHPar mainnet. If you pass `WBTC/USD` as the key, it will return the most recent price of WBTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0xA3014376A788b55450c5C1F2bA2A8694a79f0b97;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Evmos
Source: https://www.diadata.org/docs/guides/chain-specific-guide/evmos

dApps built on Evmos can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Fantom
Source: https://www.diadata.org/docs/guides/chain-specific-guide/fantom

dApps built on Fantom can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Fuse
Source: https://www.diadata.org/docs/guides/chain-specific-guide/fuse

dApps built on Fuse can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Gnosis Chain
Source: https://www.diadata.org/docs/guides/chain-specific-guide/gnosis-chain

dApps built on Gnosis Chain can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# GOAT Network
Source: https://www.diadata.org/docs/guides/chain-specific-guide/goat-network

dApps built on GOAT Network can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain              | Address                                                                                                                        |
| :----------------- | :----------------------------------------------------------------------------------------------------------------------------- |
| GOAT Alpha Mainnet | [0x458DAfFcB1507835AAB0C8F2722d1196E9a4fFaB](https://explorer.goat.network/address/0x458DAfFcB1507835AAB0C8F2722d1196E9a4fFaB) |

## Oracle Configuration

| Parameter                         | Value                                                                                                                      |
| :-------------------------------- | :------------------------------------------------------------------------------------------------------------------------- |
| Pricing Methodology               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| Deviation (%) & Refresh Frequency | 0.5% and 120 seconds                                                                                                       |
| Heartbeat                         | 24h                                                                                                                        |

## Available Asset Feeds

### Mainnet

| Asset Ticker | getValue(**key**) | Asset Markets                                                                                                 |
| :----------- | :---------------- | :------------------------------------------------------------------------------------------------------------ |
| BTC          | BTC/USD           | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)    |
| USDT         | USDT/USD          | [USDT Markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)  |
| USDC         | USDC/USD          | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)  |
| ETH          | ETH/USD           | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)   |
| DOGE         | DOGE/USD          | [DOGE Markets](https://www.diadata.org/app/price/asset/Dogechain/0x0000000000000000000000000000000000000000/) |

***

## How to Access Data

### getValue Method

To consume price data, you'll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on GOAT Network mainnet. If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0x458DAfFcB1507835AAB0C8F2722d1196E9a4fFaB;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on GOAT Network. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Hydration
Source: https://www.diadata.org/docs/guides/chain-specific-guide/hydration

dApps built on Hydration can leverage DIA oracles to access up-to-date asset price information.

## Oracle Details

### WBTC, DOT, USDT and USDC oracle

| Chain   | Address                                                                                                                               |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0xdee629af973ebf5bf261ace12ffd1900ac715f5e](https://explorer.evm.hydration.cloud/address/0xdEe629af973ebF5bf261aCe12ffD1900ac715f5e) |
| Testnet | [0xc756bd338a97c1d2faab4f13b5444a08a1566917](https://explorer.evm.hydration.cloud/address/0xc756bd338a97c1d2faab4f13b5444a08a1566917) |

### tBTC, Aave, ETH, wstETH, sUSDs, & sUSDe oracle

| Chain   | Address                                                                                                                               |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0x48ae7803cd09c48434e3fc5629f15fb76f0b5ce5](https://explorer.evm.hydration.cloud/address/0x48Ae7803Cd09c48434E3FC5629F15fb76f0b5cE5) |
| Testnet | [0x5d8320f3ced9575d8e25b6f437e610fc6a03bf52](https://explorer.evm.hydration.cloud/address/0x5d8320f3ced9575d8e25b6f437e610fc6a03bf52) |

## Oracle Configuration

|                                       |                                                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                                       |
| **Heartbeat**                         | 24h                                                                                                                        |

## Available Asset Feeds

### Mainnet

| Asset Ticker | Adapter Address                                                                                                                       | Asset Markets                                                                                                  |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| WBTC         | [0xeDD9A7C47A9F91a0F2db93978A88844167B4a04f](https://explorer.evm.hydration.cloud/address/0xeDD9A7C47A9F91a0F2db93978A88844167B4a04f) | [WBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/)   |
| DOT          | [0xFBCa0A6dC5B74C042DF23025D99ef0F1fcAC6702](https://explorer.evm.hydration.cloud/address/0xFBCa0A6dC5B74C042DF23025D99ef0F1fcAC6702) | [DOT markets](https://www.diadata.org/app/price/asset/Polkadot/0x0000000000000000000000000000000000000000/)    |
| USDT         | [0x8b0DDfB8F56690eAde9ECa23a7d90E153C268d5B](https://explorer.evm.hydration.cloud/address/0x8b0DDfB8F56690eAde9ECa23a7d90E153C268d5B) | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)   |
| USDC         | [0x17711BE5D63B2Fe8A2C379725DE720773158b954](https://explorer.evm.hydration.cloud/address/0x17711BE5D63B2Fe8A2C379725DE720773158b954) | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)   |
| tBTC         | [0xe5AcDfB0d5EC5cE34F7448B41ef4a97c4e83D9c1](https://explorer.evm.hydration.cloud/address/0xe5AcDfB0d5EC5cE34F7448B41ef4a97c4e83D9c1) | [tBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x18084fbA666a33d37592fA2633fD49a74DD93a88/)   |
| Aave         | [0x9E85d33FD87342762710FB4a1471df1Dc7bb5f8C](https://explorer.evm.hydration.cloud/address/0x9E85d33FD87342762710FB4a1471df1Dc7bb5f8C) | [Aave markets](https://www.diadata.org/app/price/asset/Ethereum/0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9/)   |
| ETH          | [0x1AF549Fe19A9B73D094173C41e18BF7F357F594b](https://explorer.evm.hydration.cloud/address/0x1AF549Fe19A9B73D094173C41e18BF7F357F594b) | [ETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)    |
| wstETH       | [0x52bBB0BC38C42D60b24EBF0C617E8218D2aB6d36](https://explorer.evm.hydration.cloud/address/0x52bBB0BC38C42D60b24EBF0C617E8218D2aB6d36) | [wstETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0/) |
| sUSDs        | [0x4b32bfFC6aCD751446E79e8687ef3815fD7924FD](https://explorer.evm.hydration.cloud/address/0x4b32bfFC6aCD751446E79e8687ef3815fD7924FD) | [sUSDs markets](https://www.diadata.org/app/price/asset/Ethereum/0xa3931d71877C0E7a3148CB7Eb4463524FEc27fbD/)  |
| sUSDe        | [0x22CDEa305Cee63D082E79F8C5Db939EEcD0265D0](https://explorer.evm.hydration.cloud/address/0x22CDEa305Cee63D082E79F8C5Db939EEcD0265D0) | [sUSDe markets](https://www.diadata.org/app/price/asset/Ethereum/0x9D39A5DE30e57443BfF2A8307A4256c8797A3497/)  |

### Testnet

| Asset Ticker | Adapter Address                            | Asset Markets                                                                                                |
| ------------ | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| WBTC         | 0xC9cCBe99bdD9538871f9756Ca5Ea64C2267cb0a7 | [WBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/) |
| DOT          | 0x422E745797EC0Ef399c17cE3E2348394F2944727 | [DOT markets](https://www.diadata.org/app/price/asset/Polkadot/0x0000000000000000000000000000000000000000/)  |
| USDT         | 0xb4aC9f0E6E207D5d81B756F8aF6efe3fe7B0E72c | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/) |
| USDC         | 0xEE7aFb45c094DC9fA404D6A86A7d795d4aA33D28 | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
| tBTC         | 0x9f7abE73e656DB45F56B1d3755940CB3fc82Fcaa | [tBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x18084fbA666a33d37592fA2633fD49a74DD93a88/) |
| Aave         | 0xC9E1415Eb64281aD449f50C454873d92F312d6fE | [Aave markets](https://www.diadata.org/app/price/asset/Ethereum/0x7Fc66500c84A76Ad7e9c93437bFc5Ac33E2DDaE9/) |

***

## How to Access Data

### getValue Method

To consume price data, you’ll need to invoke the `getValue` method on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from the oracle on Hydration testnet using the IDIAOracleV2 interface. If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```js theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0xc756bd338a97c1d2faab4f13b5444a08a1566917;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

### Adapter Contracts

To consume price data from our oracle, you can use the adapter smart contract located at the [adapter address](/guides/chain-specific-guide/hydration#asset-feeds) for each asset. This will allow you to access the same methods on the `AggregatorV3Interface` such as `getRoundData` & `latestRoundData`. You can learn more [here](/guides/how-to-guides/migrate-to-dia).

This is a sample contract for consuming the `WBTC/USD` price feed on Hydration mainnet:

```solidity theme={"system"}
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.13;

interface DiaAssetSpecificCallingConvention {
    function latestRoundData() external view returns (
        uint80 roundId,
        int256 answer,
        uint256 startedAt,
        uint256 updatedAt,
        uint80 answeredInRound
    );
}

contract DIAOracleSample {
    address wbtcAdapter = 0xeDD9A7C47A9F91a0F2db93978A88844167B4a04f;

    function getWBTCLatestPrice() external view returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        // Call the Chainlink adapter's latestRoundData function
        (, int256 answer, , uint256 updatedAt, ) =
            DiaAssetSpecificCallingConvention(wbtcAdapter).latestRoundData();

        latestPrice = uint128(uint256(answer));
        timestampOflatestPrice = uint128(updatedAt);

        return (latestPrice, timestampOflatestPrice);
    }
}
```

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Kadena
Source: https://www.diadata.org/docs/guides/chain-specific-guide/kadena

dApps built on Kadena can leverage DIA oracles to access up-to-date asset price information.

DIA Oracles on Kadena are open source, and their source code is available in [this repository](https://github.com/diadata-org/dia-kadena-oracles). dApps built on Kadena can leverage DIA oracles to access up-to-date asset price information. These deployed oracles are designed for production environments and come with a predefined list of supported assets and settings.

If dApps require a custom oracle with different assets and configurations, please [contact DIA on Telegram](https://t.me/DIAOracles_Support_Bot).

## Oracle Details

As Kadena allows for several chains in parallel, it is important to retrieve the price from the correct chain. Currently, DIA oracles are deployed on these chains:

| Network ID | Chain ID | DIA Contract Identifier                                 |
| ---------- | -------- | ------------------------------------------------------- |
| mainnet01  | 1        | `n_bfb76eab37bf8c84359d6552a1d96a309e030b71.dia-oracle` |
| mainnet01  | 2        | `n_bfb76eab37bf8c84359d6552a1d96a309e030b71.dia-oracle` |
| mainnet01  | 4        | `n_bfb76eab37bf8c84359d6552a1d96a309e030b71.dia-oracle` |
| testnet04  | 4        | `n_bfb76eab37bf8c84359d6552a1d96a309e030b71.dia-oracle` |

### Chainweb EVM Testnet 20

| Network ID | Chain ID | DIA Contract Address                                                                                                                                    |
| ---------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| chain20    | 5920     | [`0x2e034f073ee95db83b5498b90a53dd9b26525355`](https://chain-20.evm-testnet-blockscout.chainweb.com/address/0x2E034F073eE95Db83B5498B90a53DD9B26525355) |

## Oracle Configuration

| Parameter                         | Value                                                                                                                      |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Pricing Methodology               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| Deviation (%) & Refresh Frequency | 0.5% and 120 seconds                                                                                                       |
| Heartbeat                         | 24h                                                                                                                        |

## Asset Feeds

The Kadena oracle includes the following price feeds. Use the Query Symbol as a parameter in the `get-value` (or `getValue` for chainweb EVM) function to receive the latest price information for any of these assets.

| Asset                  | Query Symbol | Sources Overview                                                                                                     |
| ---------------------- | ------------ | -------------------------------------------------------------------------------------------------------------------- |
| Bitcoin (BTC)          | BTC/USD      | [BTC Sources](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)           |
| USD Coin (USDC)        | USDC/USD     | [USDC Sources](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)         |
| Staked ETH (stETH)     | STETH/USD    | [stETH Sources](https://www.diadata.org/app/price/asset/Ethereum/0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84/)        |
| Ether (ETH)            | ETH/USD      | [ETH Sources](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)          |
| Wrapped Bitcoin (WBTC) | WBTC/USD     | [WBTC Sources](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/)         |
| Moonbeam (GLMR)        | GLMR/USD     | [GLMR Sources](https://www.diadata.org/app/price/asset/Moonbeam/0x0000000000000000000000000000000000000000/)         |
| Optimism (OP)          | OP/USD       | [OP Sources](https://www.diadata.org/app/price/asset/Optimism/0x4200000000000000000000000000000000000042/)           |
| DIA Token (DIA)        | DIA/USD      | [DIA Sources](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)          |
| Arbitrum (ARB)         | ARB/USD      | [ARB Sources](https://www.diadata.org/app/price/asset/Arbitrum/0x912CE59144191C1204E64559FE8253a0e49E6548/)          |
| Binance Coin (BNB)     | BNB/USD      | [BNB Sources](https://www.diadata.org/app/price/asset/BinanceSmartChain/0x0000000000000000000000000000000000000000/) |
| Avalanche (AVAX)       | AVAX/USD     | [AVAX Sources](https://www.diadata.org/app/price/asset/Avalanche/0x0000000000000000000000000000000000000000/)        |
| Celo Dollar (CUSD)     | CUSD/USD     | [CUSD Sources](https://www.diadata.org/app/price/asset/Celo/0x765DE816845861e75A25fCA122bb6898B8B1282a/)             |
| Kadena (KDA)           | KDA/USD      | [KDA Sources](https://www.diadata.org/app/price/asset/Kadena/0x0000000000000000000000000000000000000000/)            |
| Gnosis (GNO)           | GNO/USD      | [GNO Sources](https://www.diadata.org/app/price/asset/Ethereum/0x6810e776880C02933D47DB1b9fc05908e5386b96/)          |
| Wrapped Ether (WETH)   | WETH/USD     | [WETH Sources](https://www.diadata.org/app/price/asset/Ethereum/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/)         |

Learn more about DIA's [data sourcing](/dia-stack/architecture/data-sourcing) and [data computation](/dia-stack/architecture/data-computation) architecture.

## How to Access Data

Locate one of the deployed contracts (either testnet or mainnet) and call the `get-value` (or `getValue` for chainweb EVM) function. This function expects one parameter, which is the symbols of the asset you want to retrieve and a “/USD”, so for example for the Bitcoin price the parameter must be “BTC/USD”.

This will return two values:

1. The price of the asset, with 8 decimals.

2. The timestamp of the last update in Unix time format, in UTC timezone.

You can also refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/solidity) for detailed steps on fetching price data from the oracle in your EVM contract.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Kadena. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Linea
Source: https://www.diadata.org/docs/guides/chain-specific-guide/linea

dApps built on Linea can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Linea. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# LUKSO
Source: https://www.diadata.org/docs/guides/chain-specific-guide/lukso

dApps built on LUKSO can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                                           |
| ------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0x245ad685F4D89D30fD1a14682C030c6128d08d17](https://explorer.execution.mainnet.lukso.network/address/0x245ad685F4D89D30fD1a14682C030c6128d08d17) |

## Oracle Configuration

|                                       |                                                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                                       |
| **Heartbeat**                         | 24h                                                                                                                        |

## Available Asset Feeds

| Asset Ticker | Adapter Address                                                                                                                                   | Asset Markets                                                                                                  |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- |
| EUR          | [0xbCfD839664B5Ad4D0C0C58db0c716D7a28dCd15E](https://explorer.execution.mainnet.lukso.network/address/0xbCfD839664B5Ad4D0C0C58db0c716D7a28dCd15E) | [EUR markets](https://www.diadata.org/app/price/asset/Fiat/978/)                                               |
| LYX          | [0x3153e4d03Cf97B230fc9c9d0ECCE5b2F0834d130](https://explorer.execution.mainnet.lukso.network/address/0x3153e4d03Cf97B230fc9c9d0ECCE5b2F0834d130) | [LYX markets](https://www.diadata.org/app/price/asset/Lukso/0x0000000000000000000000000000000000000000/)       |
| GBP          | [0x7EA5b4bb2D89B1EfEF00FCC95E139B77Da27d460](https://explorer.execution.mainnet.lukso.network/address/0x7EA5b4bb2D89B1EfEF00FCC95E139B77Da27d460) | [GBP markets](https://www.diadata.org/app/price/asset/Fiat/826/)                                               |
| BTC          | [0xD19856Bd3Dbd9Cb00BaC76Fc90603FA3bB05aCEA](https://explorer.execution.mainnet.lukso.network/address/0xD19856Bd3Dbd9Cb00BaC76Fc90603FA3bB05aCEA) | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)     |
| ETH          | [0xc7f3aceBe05482eeCD668df1FCF1B59e6d14f77b](https://explorer.execution.mainnet.lukso.network/address/0xc7f3aceBe05482eeCD668df1FCF1B59e6d14f77b) | [ETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)    |
| wstETH       | [0x18f2182B37d46deC1dc236Cf3Aad3a02981796cB](https://explorer.execution.mainnet.lukso.network/address/0x18f2182B37d46deC1dc236Cf3Aad3a02981796cB) | [wstETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x7f39C581F595B53c5cb19bD0b3f8dA6c935E2Ca0/) |
| DAI          | [0x1bB6c1A90c9449A14C184Dd141D2c7d7b788a679](https://explorer.execution.mainnet.lukso.network/address/0x1bB6c1A90c9449A14C184Dd141D2c7d7b788a679) | [DAI markets](https://www.diadata.org/app/price/asset/Ethereum/0x6B175474E89094C44Da98b954EedeAC495271d0F/)    |
| USDC         | [0xc675A8d220E1ba6d14a77C9FbcFDd5f9474BD07A](https://explorer.execution.mainnet.lukso.network/address/0xc675A8d220E1ba6d14a77C9FbcFDd5f9474BD07A) | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)   |
| USDT         | [0xC00c10499DEF24352475Ae873C51FaFcFC894f03](https://explorer.execution.mainnet.lukso.network/address/0xC00c10499DEF24352475Ae873C51FaFcFC894f03) | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)   |
| stETH        | [0x2b94002cfFA638B37E4DDe54EDfcF6Efdcb29E6A](https://explorer.execution.mainnet.lukso.network/address/0x2b94002cfFA638B37E4DDe54EDfcF6Efdcb29E6A) | [stETH markets](https://www.diadata.org/app/price/asset/Ethereum/0xae7ab96520DE3A18E5e111B5EaAb095312D7fE84/)  |

***

## How to Access Data

### getValue Method

To consume price data, you'll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface). Below is an example of a contract consuming data from our oracle on LUKSO mainnet. If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0x245ad685F4D89D30fD1a14682C030c6128d08d17;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

### Adapter Contracts

To consume price data from our oracle, you can use the adapter smart contract located at the [adapter address](/guides/chain-specific-guide/lukso#asset-feeds) for each asset. This will allow you to access the same methods on the `AggregatorV3Interface` such as `getRoundData` & `latestRoundData`. You can learn more [here](/guides/how-to-guides/migrate-to-dia).

This is a sample contract for consuming the `BTC/USD` price feed:

```solidity theme={"system"}
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.13;

interface DiaAssetSpecificCallingConvention {
    function latestRoundData() external view returns (
        uint80 roundId,
        int256 answer,
        uint256 startedAt,
        uint256 updatedAt,
        uint80 answeredInRound
    );
}

contract DIAOracleSample {
    address btcAdapter = 0xD19856Bd3Dbd9Cb00BaC76Fc90603FA3bB05aCEA;

    function getBTCLatestPrice() external view returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        // Call the Chainlink adapter's latestRoundData function
        (, int256 answer, , uint256 updatedAt, ) =
            DiaAssetSpecificCallingConvention(btcAdapter).latestRoundData();

        latestPrice = uint128(uint256(answer));
        timestampOflatestPrice = uint128(updatedAt);

        return (latestPrice, timestampOflatestPrice);
    }
}
```

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on LUKSO. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Metis
Source: https://www.diadata.org/docs/guides/chain-specific-guide/metis

dApps built on Metis can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Moonbase
Source: https://www.diadata.org/docs/guides/chain-specific-guide/moonbase

dApps built on Moonbase can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Moonbeam
Source: https://www.diadata.org/docs/guides/chain-specific-guide/moonbeam

dApps built on Moonbeam can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Moonriver
Source: https://www.diadata.org/docs/guides/chain-specific-guide/moonriver

dApps built on Moonriver can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Nervos
Source: https://www.diadata.org/docs/guides/chain-specific-guide/nervos

dApps built on Nervos can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

To consume price data, invoke a read function on the oracle contract that takes an asset key as a parameter. For example, If you pass `BTC/USD` as the key, it will return the most recent price of `BTC` in `USD` with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# OKT Chain (OKX)
Source: https://www.diadata.org/docs/guides/chain-specific-guide/okt-chain

dApps built on OKT Chain can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Optimism
Source: https://www.diadata.org/docs/guides/chain-specific-guide/optimism

dApps built on Optimism can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

### Oracle Contracts

#### Mainnet

| Contract    | Address                                                                                                                          |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0x048050547eb6e68cB37Fb21EEafEad40CF2CbdbB](https://optimistic.etherscan.io/address/0x048050547eb6e68cb37fb21eeafead40cf2cbdbb) |

#### Testnet

| Contract    | Address                                                                                                                                |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://sepolia-optimism.etherscan.io/address/0x9bb71344ed950f9cfd85ee1c7258553b01d95fa0) |

### Oracle Configuration

|                                       |                    |
| ------------------------------------- | ------------------ |
| **Pricing Methodology**               | Median             |
| **Deviation (%) & Refresh Frequency** | 2% and 120 seconds |
| **Heartbeat**                         | 12h                |

***

### Available Asset Feeds

| Asset Ticker | updates(key) | Asset Markets                                                                                                |
| :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
| ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
| BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
| USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |

***

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Additional Details

You can find the contract addresses for the Optimism bridge's components on mainnet and testnet below:

<Accordion title="Mainnet">
  * [MailBox
    Contract](https://optimistic.etherscan.io/address/0xd4C1905BB1D26BC93DAC913e13CaCC278CdCC80D)
  * [ISM
    Contract](https://optimistic.etherscan.io/address/0xe74b7d236a97eed9026926073cbb436638266888)
  * [Protocol Fee Hook
    Contract](https://optimistic.etherscan.io/address/0x0ec9C62333E29243B04C934bC924c169c1255027)
</Accordion>

<Accordion title="Testnet">
  * [MailBox
    Contract](https://sepolia-optimism.etherscan.io/address/0x6966b0E55883d49BFB24539356a2f8A673E02039)
  * [ISM
    Contract](https://sepolia-optimism.etherscan.io/address/0xb869617a3CFcdA07A4cC230d996120074e7c817e)
  * [Protocol Fee Hook
    Contract](https://sepolia-optimism.etherscan.io/address/0x611C8b288c642336136a436d7125AC49FA71468B)
</Accordion>

Learn more about DIA's cross-chain messaging layer [here](/dia-stack/architecture/core-components/spectra).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Plume
Source: https://www.diadata.org/docs/guides/chain-specific-guide/plume

dApps built on Plume can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Plume. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Polygon
Source: https://www.diadata.org/docs/guides/chain-specific-guide/polygon

dApps built on Polygon can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Polygon. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Polygon zkEVM
Source: https://www.diadata.org/docs/guides/chain-specific-guide/polygon-zkevm

dApps built on Polygon zkEVM can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Shibuya
Source: https://www.diadata.org/docs/guides/chain-specific-guide/shibuya

dApps built on Shibuya can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Shiden
Source: https://www.diadata.org/docs/guides/chain-specific-guide/shiden

dApps built on Shiden can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Shido
Source: https://www.diadata.org/docs/guides/chain-specific-guide/shido

dApps built on Shido can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Somnia
Source: https://www.diadata.org/docs/guides/chain-specific-guide/somnia

dApps built on Somnia can leverage DIA oracles to access up-to-date asset price information

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                                  |
| ------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0xbA0E0750A56e995506CA458b2BdD752754CF39C4](https://shannon-explorer.somnia.network/address/0x9206296Ea3aEE3E6bdC07F7AaeF14DfCf33d865D) |
| Testnet | [0x9206296ea3aee3e6bdc07f7aaef14dfcf33d865d](https://shannon-explorer.somnia.network/address/0x9206296Ea3aEE3E6bdC07F7AaeF14DfCf33d865D) |

## Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                    |
| **Heartbeat**                         | 24h                                                                                                     |

## Available Asset Feeds

### Mainnet

| Asset Ticker | Adapter address                                                                                                                  | Asset Markets                                                                                                |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| USDT         | [0x936C4F07fD4d01485849ee0EE2Cdcea2373ba267](https://explorer.somnia.network/address/0x936C4F07fD4d01485849ee0EE2Cdcea2373ba267) | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/) |
| USDC         | [0x5D4266f4DD721c1cD8367FEb23E4940d17C83C93](https://explorer.somnia.network/address/0x5D4266f4DD721c1cD8367FEb23E4940d17C83C93) | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
| BTC          | [0xb12e1d47b0022fA577c455E7df2Ca9943D0152bE](https://explorer.somnia.network/address/0xb12e1d47b0022fA577c455E7df2Ca9943D0152bE) | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| ARB          | [0x6a96a0232402c2BC027a12C73f763b604c9F77a6](https://explorer.somnia.network/address/0x6a96a0232402c2BC027a12C73f763b604c9F77a6) | [ARB markets](https://www.diadata.org/app/price/asset/Arbitrum/0x912CE59144191C1204E64559FE8253a0e49E6548/)  |
| SOL          | [0xa4a3a8B729939E2a79dCd9079cee7d84b0d96234](https://explorer.somnia.network/address/0xa4a3a8B729939E2a79dCd9079cee7d84b0d96234) | [SOL markets](https://www.diadata.org/app/price/asset/Solana/0x0000000000000000000000000000000000000000/)    |
| SOMI         | [0x1f5f46B0DABEf8806a1f33772522ED683Ba64E27](https://explorer.somnia.network/address/0x1f5f46B0DABEf8806a1f33772522ED683Ba64E27) | [SOMI markets](https://www.diadata.org/app/price/asset/Somnia/0x0000000000000000000000000000000000000000/)   |

### Testnet

| Asset Ticker | Adapter address                                                                                                                          | Asset Markets                                                                                                |
| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| USDT         | [0x67d2c2a87a17b7267a6dbb1a59575c0e9a1d1c3e](https://shannon-explorer.somnia.network/address/0x67d2C2a87A17b7267a6DBb1A59575C0E9A1D1c3e) | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/) |
| USDC         | [0x235266D5ca6f19F134421C49834C108b32C2124e](https://shannon-explorer.somnia.network/address/0x235266D5ca6f19F134421C49834C108b32C2124e) | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
| BTC          | [0x4803db1ca3A1DA49c3DB991e1c390321c20e1f21](https://shannon-explorer.somnia.network/address/0x4803db1ca3A1DA49c3DB991e1c390321c20e1f21) | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| ARB          | [0x74952812B6a9e4f826b2969C6D189c4425CBc19B](https://shannon-explorer.somnia.network/address/0x74952812B6a9e4f826b2969C6D189c4425CBc19B) | [ARB markets](https://www.diadata.org/app/price/asset/Arbitrum/0x912CE59144191C1204E64559FE8253a0e49E6548/)  |
| SOL          | [0xD5Ea6C434582F827303423dA21729bEa4F87D519](https://shannon-explorer.somnia.network/address/0xD5Ea6C434582F827303423dA21729bEa4F87D519) | [SOL markets](https://www.diadata.org/app/price/asset/Solana/0x0000000000000000000000000000000000000000/)    |
| SOMI         | [0xaEAa92c38939775d3be39fFA832A92611f7D6aDe](https://shannon-explorer.somnia.network/address/0xaEAa92c38939775d3be39fFA832A92611f7D6aDe) | [SOMI markets](https://www.diadata.org/app/price/asset/Somnia/0x0000000000000000000000000000000000000000/)   |

***

## How to Access Data

### getValue Method

To consume price data, you’ll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on Sepolia testnet. If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0x9206296ea3aee3e6bdc07f7aaef14dfcf33d865d;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

### Adapter contracts

To consume price data from our oracle, you can use the adapter smart contract located at the [adapter address](/guides/how-to-guides/fetch-price-data/chain-specific-guide/somnia#asset-feeds) for each asset. This will allow you to access the same methods on the `AggregatorV3Interface` such as `getRoundData` & `latestRoundData`. You can learn more [here](/guides/how-to-guides/migrate-to-dia).

This is a sample contract for consuming the `$SOMI` price feed:

```solidity theme={"system"}
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.13;

interface DiaAssetSpecificCallingConvention {
    function latestRoundData() external view returns (
        uint80 roundId,
        int256 answer,
        uint256 startedAt,
        uint256 updatedAt,
        uint80 answeredInRound
    );
}

contract DIAOracleSample {
    address somiAdapter =

    function getSOMILatestPrice() external view returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        // Call the Chainlink adapter's latestRoundData function
        (, int256 answer, , uint256 updatedAt, ) =
            DiaAssetSpecificCallingConvention(somiAdapter).latestRoundData();

        latestPrice = uint128(uint256(answer));
        timestampOflatestPrice = uint128(updatedAt);

        return (latestPrice, timestampOflatestPrice);
    } // SOMI:1.23125165
}
```

***

## Lumina Stack Feeds

<Note>
  Explore these demo oracles to see how DIA Lumina Stack works. [Request a
  custom oracle](#request-a-custom-oracle) and unlock the full power of tailored
  data feeds for your dApp.
</Note>

Demo oracles are available for testing the new fully verifiable & decentralized [Lumina stack](/dia-stack/overview) on Somnia testnet.

### Oracle Details

| Chain   | Contract    | Address                                                                                                                                  |
| ------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Testnet | Push Oracle | [0xFb1462A649A92654482F8E048C754333ad85e5C0](https://shannon-explorer.somnia.network/address/0xFb1462A649A92654482F8E048C754333ad85e5C0) |

### Oracle Configuration

|                                       |                    |
| ------------------------------------- | ------------------ |
| **Pricing Methodology**               | Median             |
| **Deviation (%) & Refresh Frequency** | 1% and 120 seconds |
| **Heartbeat**                         | 24h                |

### Asset Feeds

| Asset Ticker | updates(key) | Asset Markets                                                                                                |
| :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
| ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
| BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
| USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |

### Additional Details

You can find the contract addresses for the Somnia bridge’s components on testnet below:

<Accordion title="Testnet">
  * [MailBox
    Contract](https://shannon-explorer.somnia.network/address/0x7d498740A4572f2B5c6b0A1Ba9d1d9DbE207e89E)
  * [ISM
    Contract](https://shannon-explorer.somnia.network/address/0xdBEf26113A6c84f2E1Ad13Bbb43898e4Ff4286dc)
  * [Protocol Fee Hook
    Contract](https://shannon-explorer.somnia.network/address/0x67f4e6b2EE6535F9D3Eca74E63a665F8c888C2bc)
</Accordion>

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Somnia. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp’s needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Sonic
Source: https://www.diadata.org/docs/guides/chain-specific-guide/sonic

dApps built on Sonic can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

### Oracle Contracts

#### Mainnet

| Contract    | Address                                                                                                                |
| ----------- | ---------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0x048050547eb6e68cB37Fb21EEafEad40CF2CbdbB](https://sonicscan.org/address/0x048050547eb6e68cb37fb21eeafead40cf2cbdbb) |

### Oracle Configuration

|                                       |                    |
| ------------------------------------- | ------------------ |
| **Pricing Methodology**               | Median             |
| **Deviation (%) & Refresh Frequency** | 2% and 120 seconds |
| **Heartbeat**                         | 12h                |

***

### Available Asset Feeds

| Asset Ticker | updates(key) | Asset Markets                                                                                                |
| :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
| ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
| BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
| USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |

***

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Additional Details

You can find the contract addresses for the Sonic bridge's components on mainnet below:

<Accordion title="Mainnet">
  * [MailBox
    Contract](https://sonicscan.org/address/0x3a464f746D23Ab22155710f44dB16dcA53e0775E)
  * [ISM
    Contract](https://sonicscan.org/address/0xE74B7D236A97eED9026926073cBb436638266888)
  * [Protocol Fee Hook
    Contract](https://sonicscan.org/address/0x0ec9C62333E29243B04C934bC924c169c1255027)
</Accordion>

Learn more about DIA's cross-chain messaging layer [here](/dia-stack/architecture/core-components/spectra).

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Sonic. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Soroban
Source: https://www.diadata.org/docs/guides/chain-specific-guide/soroban

dApps built on Soroban can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

To consume price data, invoke a read function on the oracle contract that takes an asset key as a parameter. For example, If you pass `BTC/USD` as the key, it will return the most recent price of `BTC` in `USD` with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Stacks
Source: https://www.diadata.org/docs/guides/chain-specific-guide/stacks

dApps built on Stacks can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                                                  |
| ------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [SP1G48FZ4Y7JY8G2Z0N51QTCYGBQ6F4J43J77BQC0.dia-oracle](https://explorer.hiro.so/txid/SP1G48FZ4Y7JY8G2Z0N51QTCYGBQ6F4J43J77BQC0.dia-oracle?chain=mainnet) |
| Testnet | [ST1S5ZGRZV5K4S9205RWPRTX9RGS9JV40KQMR4G1J.dia-oracle](https://explorer.hiro.so/txid/ST1S5ZGRZV5K4S9205RWPRTX9RGS9JV40KQMR4G1J.dia-oracle?chain=testnet) |

## Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 5% and 120 seconds                                                                                      |
| **Heartbeat**                         | 15 minutes                                                                                              |

## Available Asset Feeds

The Stacks oracle includes the following asset feeds:

| Asset Ticker | Asset Blockchain | Asset Address                                                     | Asset Sources                                                                                                                    |
| ------------ | ---------------- | ----------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| STX          | Stacks           | 0x0000000000000000000000000000000000000000                        | [STX Market](https://www.diadata.org/app/price/asset/Stacks/0x0000000000000000000000000000000000000000/)                         |
| stSTX        | Stacks           | SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG.ststx-token              | [stSTX Market](https://www.diadata.org/app/price/asset/Stacks/SP4SZE494VC2YC5JYG7AYFQ44F5Q4PYV7DVMDPBG.ststx-token/)             |
| DIKO         | Stacks           | SP2C2YFP12AJZB4MABJBAJ55XECVS7E4PMMZ89YZR.arkadiko-token          | [DIKO Market](https://www.diadata.org/app/price/asset/Stacks/SP2C2YFP12AJZB4MABJBAJ55XECVS7E4PMMZ89YZR.arkadiko-token/)          |
| WELSH        | Stacks           | SP3NE50GEXFG9SZGTT51P40X2CKYSZ5CC4ZTZ7A2G.welshcorgicoin-token    | [WELSH Market](https://www.diadata.org/app/price/asset/Stacks/SP3NE50GEXFG9SZGTT51P40X2CKYSZ5CC4ZTZ7A2G.welshcorgicoin-token/)   |
| VELAR        | Stacks           | SP1Y5YSTAHZ88XYK1VPDH24GY0HPX5J4JECTMY4A1.velar-token             | [VELAR Market](https://www.diadata.org/app/price/asset/Stacks/SP1Y5YSTAHZ88XYK1VPDH24GY0HPX5J4JECTMY4A1.velar-token/)            |
| ALEX         | Stacks           | SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.age000-governance-token | [ALEX Market](https://www.diadata.org/app/price/asset/Stacks/SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.age000-governance-token/) |
| sBTC         | Stacks           | SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token              | [sBTC Market](https://www.diadata.org/app/price/asset/Stacks/SM3VDXK3WZZSA84XXFKAFAF15NNZX32CTSG82JFQ4.sbtc-token/)              |
| aeUSDC       | Stacks           | SP3Y2ZSH8P7D50B0VBTSX11S7XSG24M1VB9YFQA4K.token-aeusdc            | [aeUSDC Market](https://www.diadata.org/app/price/asset/Stacks/SP3Y2ZSH8P7D50B0VBTSX11S7XSG24M1VB9YFQA4K.token-aeusdc/)          |
| USDh         | Stacks           | SPN5AKG35QZSK2M8GAMR4AFX45659RJHDW353HSG.usdh-token-v1            | [USDh Market](https://www.diadata.org/app/price/asset/Stacks/SPN5AKG35QZSK2M8GAMR4AFX45659RJHDW353HSG.usdh-token-v1/)            |
| BTC          | Bitcoin          | 0x0000000000000000000000000000000000000000                        | [BTC Market](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)                        |

***

## How to Access Data

You can query for assets like `"STX/USD"` or `"stSTX/USD"` in the `get-value()` read function. It returns two values:

1. The price of STX/USD with 8 decimals

2. The timestamp of the last update (UTC timezone)

Below is the DIA oracle contract implementation in [Clarity](https://docs.stacks.co/concepts/clarity):

```solidity theme={"system"}
(impl-trait .trait-dia-oracle.dia-oracle-trait)

(define-constant err-unauthorized (err u100))

(define-data-var oracle-updater principal tx-sender)

(define-map values
    (string-ascii 32)
    { value: uint, timestamp: uint }
)

(define-public (set-value (key (string-ascii 32)) (value uint) (timestamp uint))
    (begin
        (try! (check-is-oracle-updater))
        (update-value { key: key, value: value, timestamp: timestamp })
        (ok true)
    )
)

(define-public (set-multiple-values (entries (list 10 { key: (string-ascii 32), value: uint, timestamp: uint })))
    (begin
        (try! (check-is-oracle-updater))
        (map update-value entries)
        (ok true)
    )
)

(define-public (change-oracle-updater (new-oracle-updater principal))
    (begin
        ;; #[filter(new-oracle-updater)]
        (try! (check-is-oracle-updater))
        (var-set oracle-updater new-oracle-updater)
        (print
            {
                action: "oracle-updater-changed",
                data: { old-updater: tx-sender, new-updater: new-oracle-updater }
            }
        )
        (ok true)
    )
)

(define-read-only (get-oracle-updater)
    (var-get oracle-updater)
)

(define-read-only (get-value (key (string-ascii 32)))
    (ok (default-to { value: u0, timestamp: u0 } (map-get? values key)))
)

(define-private (check-is-oracle-updater)
    (ok (asserts! (is-eq tx-sender (var-get oracle-updater)) err-unauthorized))
)

(define-private (update-value (entry { key: (string-ascii 32), value: uint, timestamp: uint }))
    (begin
        (map-set values
            (get key entry)
            { value: (get value entry), timestamp: (get timestamp entry) }
        )
        (print { action: "updated", data: entry })
    )
)
```

Learn more about DIA’s [data sourcing](/dia-stack/architecture/data-sourcing) and [data computation](/dia-stack/architecture/data-computation) architecture.

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Stacks. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Superseed
Source: https://www.diadata.org/docs/guides/chain-specific-guide/superseed

dApps built on Superseed can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                                 |
| ------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0xF526dC0D2B73488d32b58E55C17Cef5a53AD002A](https://explorer.superseed.xyz/address/0xF526dC0D2B73488d32b58E55C17Cef5a53AD002A)         |
| Testnet | [0x6f021bF081840F96bdd90fd756b700072C7E68A5](https://sepolia-explorer.superseed.xyz/address/0x6f021bF081840F96bdd90fd756b700072C7E68A5) |

## Oracle Configuration

| Parameter                         | Value                                                                                                   |
| --------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Pricing Methodology               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| Deviation (%) & Refresh Frequency | 0.5% and 120 seconds                                                                                    |
| Heartbeat                         | 24h                                                                                                     |

## Available Asset Feeds

### Mainnet

| Asset Ticker | Adapter Address                                                                                                                 | Asset Markets                                                                                                |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| WETH         | [0xAdEfc2264c21A05D3f83bf7694438F81E119620B](https://explorer.superseed.xyz/address/0xAdEfc2264c21A05D3f83bf7694438F81E119620B) | [WETH markets](https://www.diadata.org/app/price/asset/Ethereum/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/) |
| cbBTC        | [0x7F760344c9Cde8DD342120FA0F908CE0Cd42B1E6](https://explorer.superseed.xyz/address/0x7F760344c9Cde8DD342120FA0F908CE0Cd42B1E6) | [cbBTC markets](https://www.diadata.org/app/price/asset/Base/0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf/)    |

### Testnet

| Asset Ticker | Adapter Address                                                                                                                         | Asset Markets                                                                                                |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| WETH         | [0xA09A4e4297a06e284a4ACdf2Ca1F9998d5280F6e](https://sepolia-explorer.superseed.xyz/address/0xA09A4e4297a06e284a4ACdf2Ca1F9998d5280F6e) | [WETH markets](https://www.diadata.org/app/price/asset/Ethereum/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/) |
| cbBTC        | [0x61790e8F9bf02E4272E273F2615eD4fc7d8F95D9](https://sepolia-explorer.superseed.xyz/address/0x61790e8F9bf02E4272E273F2615eD4fc7d8F95D9) | [cbBTC markets](https://www.diadata.org/app/price/asset/Base/0xcbB7C0000aB88B473b1f5aFd9ef808440eed33Bf/)    |

***

## How to Access Data

### getValue Method

To consume price data, you’ll need to invoke the `getValue` method on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#access-the-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on Superseed mainnet using the IDIAOracleV2 interface. If you pass `WETH/USD` as the key, it will return the most recent price of WETH in USD with 8 decimal places (e.g. 177101990135 is \$1,771.01990135) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128,
             uint128);
}

contract DIAOracleSample {

    address immutable ORACLE = 0xF526dC0D2B73488d32b58E55C17Cef5a53AD002A;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

### Adapter contracts

To consume price data from our oracle, you can use the adapter smart contract located at the [adapter address](/guides/chain-specific-guide/superseed#asset-feeds) for each asset. This will allow you to access the same methods on the `AggregatorV3Interface` such as `getRoundData` & `latestRoundData`. You can learn more [here](/guides/how-to-guides/migrate-to-dia).

This is a sample contract for consuming the `WETH/USD` price feed on Superseed mainnet:

```solidity theme={"system"}
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.13;

interface DiaAssetSpecificCallingConvention {
    function latestRoundData() external view returns (
        uint80 roundId,
        int256 answer,
        uint256 startedAt,
        uint256 updatedAt,
        uint80 answeredInRound
    );
}

contract DIAOracleSample {
    address wethAdapter = 0xF526dC0D2B73488d32b58E55C17Cef5a53AD002A;

    function getWETHLatestPrice() external view returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        // Call the Chainlink adapter's latestRoundData function
        (, int256 answer, , uint256 updatedAt, ) =
            DiaAssetSpecificCallingConvention(wethAdapter).latestRoundData();

        latestPrice = uint128(uint256(answer));
        timestampOflatestPrice = uint128(updatedAt);

        return (latestPrice, timestampOflatestPrice);
    }
}
```

***

## Oracle Grants Program

The DIA Oracle Grants Program provides zero-cost oracle access for up to 1 year, covering deployment and update costs to accelerate dApp development on Superseed. Learn more about the grant here:

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Swell
Source: https://www.diadata.org/docs/guides/chain-specific-guide/swell

dApps built on Swell can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Telos
Source: https://www.diadata.org/docs/guides/chain-specific-guide/telos

dApps built on Telos can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Unichain
Source: https://www.diadata.org/docs/guides/chain-specific-guide/unichain

dApps built on Unichain can leverage DIA oracles to access up-to-date asset price information.

<Note>
  Explore these demo oracles to see how DIA works. For production deployments,
  [request a custom oracle](#request-a-custom-oracle) and unlock the full power
  of tailored data feeds for your dApp.
</Note>

## Demo Oracles

### Oracle Contracts

#### Testnet

| Contract    | Address                                                                                                                      |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Push Oracle | [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://sepolia.uniscan.xyz/address/0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0) |

### Oracle Configuration

|                                       |                    |
| ------------------------------------- | ------------------ |
| **Pricing Methodology**               | Median             |
| **Deviation (%) & Refresh Frequency** | 2% and 120 seconds |
| **Heartbeat**                         | 12h                |

***

### Available Asset Feeds

| Asset Ticker | updates(key) | Asset Markets                                                                                                |
| :----------- | :----------- | :----------------------------------------------------------------------------------------------------------- |
| ETH          | ETH/USD      | [ETH Markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)  |
| BTC          | BTC/USD      | [BTC Markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)   |
| DIA          | DIA/USD      | [DIA Markets](https://www.diadata.org/app/price/asset/Ethereum/0x84cA8bc7997272c7CfB4D0Cd3D55cd942B3c9419/)  |
| USDC         | USDC/USD     | [USDC Markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |

***

## How to Access Data

To consume price data, use the [`updates` method](/guides/how-to-guides/fetch-price-data/push-based-oracles) for Push-based oracles.

The price updates are stored in both methods in an `updates` mapping. When accessing the `updates` mapping through the key `BTC/USD`, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

Below is a sample contract that consumes the `BTC/USD` price feed:

### updates Method

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

## Additional Details

You can find the contract addresses for the Unichain bridge's components on testnet below:

<Accordion title="Testnet">
  * [MailBox
    Contract](https://sepolia.uniscan.xyz/address/0xDDcFEcF17586D08A5740B7D91735fcCE3dfe3eeD)
  * [ISM
    Contract](https://sepolia.uniscan.xyz/address/0xb869617a3CFcdA07A4cC230d996120074e7c817e)
  * [Protocol Fee Hook
    Contract](https://sepolia.uniscan.xyz/address/0x611C8b288c642336136a436d7125AC49FA71468B)
</Accordion>

Learn more about DIA's cross-chain messaging layer [here](/dia-stack/architecture/core-components/spectra).

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Units Network
Source: https://www.diadata.org/docs/guides/chain-specific-guide/units-network

dApps built on Units Network can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                     |
| ------- | --------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0xc9783a5BaBE78D979B7EB5AD43Ea3B57Acb17034](https://explorer.unit0.dev/address/0xc9783a5BaBE78D979B7EB5AD43Ea3B57Acb17034) |

## Oracle Configuration

|                                       |                                                                                                                            |
| ------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                                       |
| **Heartbeat**                         | 24h                                                                                                                        |

## Available Asset Feeds

| Asset Ticker | getValue(key) | Asset Markets                                                                                                |
| ------------ | ------------- | ------------------------------------------------------------------------------------------------------------ |
| WETH         | WETH/USD      | [WETH markets](https://www.diadata.org/app/price/asset/Ethereum/0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/) |
| WBTC         | WBTC/USD      | [WBTC markets](https://www.diadata.org/app/price/asset/Ethereum/0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599/) |
| USDC         | USDC/USD      | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/) |
| USDT         | USDT/USD      | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/) |

***

## How to Access Data

### getValue Method

To consume price data, you'll need to invoke the `getValue` method on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#access-the-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on Units Network. If you pass `WBTC/USD` as the key, it will return the most recent price of WBTC in USD with 8 decimal places (e.g.11796077504693 is \$117,960.77504693) along with the Unix timestamp of the last price update.

```solidity theme={"system"}

pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0xc9783a5BaBE78D979B7EB5AD43Ea3B57Acb17034;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Velas
Source: https://www.diadata.org/docs/guides/chain-specific-guide/velas

dApps built on Velas can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# W Chain
Source: https://www.diadata.org/docs/guides/chain-specific-guide/w-chain

dApps built on W Chain can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                                                                           |
| ------- | --------------------------------------------------------------------------------------------------------------------------------- |
| Mainnet | [0x47A04f0a1FA94c14f9FcB4EA0dC63aDdbC9Ecbe5](https://scan.w-chain.com/address/0x47A04f0a1FA94c14f9FcB4EA0dC63aDdbC9Ecbe5)         |
| Testnet | [0x57e70667575c50c26D60BE6Db56e54B579d8CC22](https://scan-testnet.w-chain.com/address/0x57e70667575c50c26D60BE6Db56e54B579d8CC22) |

## Oracle Configuration

|                                       |                                                                                                         |
| ------------------------------------- | ------------------------------------------------------------------------------------------------------- |
| **Pricing Methodology**               | [MAIR](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) |
| **Deviation (%) & Refresh Frequency** | 0.5% and 120 seconds                                                                                    |
| **Heartbeat**                         | 24h                                                                                                     |

## Available Asset Feeds

### Mainnet

| Asset Ticker | Adapter Address                                                                                                           | Asset Markets                                                                                                        |
| ------------ | ------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| BTC          | [0x34E793Bed54bcd6a7EE9479D8E7fDdD957ACd252](https://scan.w-chain.com/address/0x34E793Bed54bcd6a7EE9479D8E7fDdD957ACd252) | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)           |
| ETH          | [0x1145b9bad680089c8724Df0FAB1E68c7871E12a8](https://scan.w-chain.com/address/0x1145b9bad680089c8724Df0FAB1E68c7871E12a8) | [ETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)          |
| SOL          | [0x07CEb7db57759EB6D0b68CAb0cF49a08A52B06bd](https://scan.w-chain.com/address/0x07CEb7db57759EB6D0b68CAb0cF49a08A52B06bd) | [SOL markets](https://www.diadata.org/app/price/asset/Solana/0x0000000000000000000000000000000000000000/)            |
| BNB          | [0x512a846569442a9E69E595A3f030898A1cc052Ec](https://scan.w-chain.com/address/0x512a846569442a9E69E595A3f030898A1cc052Ec) | [BNB markets](https://www.diadata.org/app/price/asset/BinanceSmartChain/0x0000000000000000000000000000000000000000/) |
| USDC         | [0x9A581384B1A54D0863E20fa7bC6aafd68eB070B3](https://scan.w-chain.com/address/0x9A581384B1A54D0863E20fa7bC6aafd68eB070B3) | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)         |
| USDT         | [0x29047678110de15199AEb74332EDeCC4C3F83599](https://scan.w-chain.com/address/0x29047678110de15199AEb74332EDeCC4C3F83599) | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)         |
| POL          | [0x9c42bcc40Ba59F87047434eC5fd9E3960A9d133C](https://scan.w-chain.com/address/0x9c42bcc40Ba59F87047434eC5fd9E3960A9d133C) | [POL markets](https://www.diadata.org/app/price/asset/Ethereum/0x455e53908C49407DDe25B8293c72529b80b9b605/)          |
| XRP          | [0x3f3C850720A2838905cc1Dd50f4A3F5e03F84E92](https://scan.w-chain.com/address/0x3f3C850720A2838905cc1Dd50f4A3F5e03F84E92) | [XRP markets](https://www.diadata.org/app/price/asset/Ripple/0x0000000000000000000000000000000000000000/)            |
| WCO          | [0x58f903ec136c589447fA8db5d22210919c5bc51f](https://scan.w-chain.com/address/0x58f903ec136c589447fA8db5d22210919c5bc51f) | [WCO markets](https://www.diadata.org/app/price/asset/WChain/0x0000000000000000000000000000000000000000/)            |

### Testnet

| Asset Ticker | Adapter Address                                                                                                                   | Asset Markets                                                                                                        |
| ------------ | --------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| BTC          | [0x9D0134e6fbB244dDa210189A5Dfe29BB85FF1E94](https://scan-testnet.w-chain.com/address/0x9D0134e6fbB244dDa210189A5Dfe29BB85FF1E94) | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)           |
| ETH          | [0x6cD4023d7da60c305F1BD2a361DAa7dEeCc8d336](https://scan-testnet.w-chain.com/address/0x6cD4023d7da60c305F1BD2a361DAa7dEeCc8d336) | [ETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)          |
| SOL          | [0xef07fB27696597e9b248Ee7B265D715a8e130f36](https://scan-testnet.w-chain.com/address/0xef07fB27696597e9b248Ee7B265D715a8e130f36) | [SOL markets](https://www.diadata.org/app/price/asset/Solana/0x0000000000000000000000000000000000000000/)            |
| BNB          | [0x5cb4129280cf34bd3D4c3127D910948896752877](https://scan-testnet.w-chain.com/address/0x5cb4129280cf34bd3D4c3127D910948896752877) | [BNB markets](https://www.diadata.org/app/price/asset/BinanceSmartChain/0x0000000000000000000000000000000000000000/) |
| USDC         | [0xc305427D51eBf5555Df717A562729F1853645e7c](https://scan-testnet.w-chain.com/address/0xc305427D51eBf5555Df717A562729F1853645e7c) | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)         |
| USDT         | [0x30eFF71073F6ba6E46bF15A417CdB301009c2d69](https://scan-testnet.w-chain.com/address/0x30eFF71073F6ba6E46bF15A417CdB301009c2d69) | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)         |
| POL          | [0xa8c64239F9939530bf84357D7A9e281986781Ade](https://scan-testnet.w-chain.com/address/0xa8c64239F9939530bf84357D7A9e281986781Ade) | [POL markets](https://www.diadata.org/app/price/asset/Ethereum/0x455e53908C49407DDe25B8293c72529b80b9b605/)          |
| XRP          | [0xBc22d07df5baf273d55eCD7027BdaA70EbCa3076](https://scan-testnet.w-chain.com/address/0xBc22d07df5baf273d55eCD7027BdaA70EbCa3076) | [XRP markets](https://www.diadata.org/app/price/asset/Ripple/0x0000000000000000000000000000000000000000/)            |
| WCO          | [0x9a242f634A324f3621813A7f197206f6AC407b86](https://scan-testnet.w-chain.com/address/0x9a242f634A324f3621813A7f197206f6AC407b86) | [WCO markets](https://www.diadata.org/app/price/asset/WChain/0x0000000000000000000000000000000000000000/)            |

***

## How to access data

### getValue Method

To consume price data, you'll need to invoke the [`getValue` method](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) on the oracle contract which you can access through the [DIA Oracle library](/guides/how-to-guides/fetch-price-data/solidity#solidity-library) or the [interface](/guides/how-to-guides/fetch-price-data/solidity#using-the-diaoraclev2-interface).

Below is an example of a contract consuming data from our oracle on W Chain mainnet. If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with **8 decimal places** (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

```solidity theme={"system"}
pragma solidity ^0.8.13;

interface IDIAOracleV2 {
    function getValue(string memory) external view returns (uint128, uint128);
}

contract DIAOracleV2Consumer{

    address immutable ORACLE = 0x47A04f0a1FA94c14f9FcB4EA0dC63aDdbC9Ecbe5;

    function getPrice(string memory key)
    external
    view
    returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        (latestPrice, timestampOflatestPrice) =
                 IDIAOracleV2(ORACLE).getValue(key);
    }
}
```

See the full example [here](/guides/how-to-guides/fetch-price-data/solidity).

### Adapter contracts

To consume price data from our oracle, you can use the adapter smart contract located at the [adapter address](/guides/chain-specific-guide/w-chain#asset-feeds) for each asset. This will allow you to access the same methods on the `AggregatorV3Interface` such as `getRoundData` & `latestRoundData`. You can learn more [here](/guides/how-to-guides/migrate-to-dia).

This is a sample contract for consuming the `BTC/USD` price feed on W Chain mainnet:

```solidity theme={"system"}
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.13;

interface DiaAssetSpecificCallingConvention {
    function latestRoundData() external view returns (
        uint80 roundId,
        int256 answer,
        uint256 startedAt,
        uint256 updatedAt,
        uint80 answeredInRound
    );
}

contract DIAOracleSample {
    address btcAdapter = 0x34E793Bed54bcd6a7EE9479D8E7fDdD957ACd252;

    function getBTCLatestPrice() external view returns (
        uint128 latestPrice,
        uint128 timestampOflatestPrice
    ) {
        // Call the Chainlink adapter's latestRoundData function
        (, int256 answer, , uint256 updatedAt, ) =
            DiaAssetSpecificCallingConvention(btcAdapter).latestRoundData();

        latestPrice = uint128(uint256(answer));
        timestampOflatestPrice = uint128(updatedAt);

        return (latestPrice, timestampOflatestPrice);
    }
}
```

***

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# Wanchain
Source: https://www.diadata.org/docs/guides/chain-specific-guide/wanchain

dApps built on Wanchain can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# XRP Ledger (XRPL)
Source: https://www.diadata.org/docs/guides/chain-specific-guide/xrp-ledger-xrpl

dApps built on XRPL can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## Oracle Details

| Chain   | Address                                                                      |
| ------- | ---------------------------------------------------------------------------- |
| Mainnet | **Provider:** diadata (hex. 64696164617461) <br />**Oracle Document ID:** 42 |
| Testnet | **Provider:** diadata (hex: 64696164617461) <br />**Oracle Document ID:** 1  |

## Oracle Configuration

|                                   |                                                                                                                            |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| Pricing Methodology               | [VWAPIR](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) |
| Deviation (%) & Refresh Frequency | 1% and 120 seconds                                                                                                         |
| Heartbeat                         | 24h                                                                                                                        |

## Gas Wallets

The gas wallets used to push updates to the oracle are the following:

| Chain   | Address                                                                                                    |
| ------- | ---------------------------------------------------------------------------------------------------------- |
| Mainnet | [rP24Lp7bcUHvEW7T7c8xkxtQKKd9fZyra7](https://livenet.xrpl.org/accounts/rP24Lp7bcUHvEW7T7c8xkxtQKKd9fZyra7) |
| Testnet | [r3U1mL5u2SCPr4mApqYyF96nvwvKoGf7aH](https://testnet.xrpl.org/accounts/r3U1mL5u2SCPr4mApqYyF96nvwvKoGf7aH) |

## Available Asset Feeds

| Asset Ticker | Asset Ticker (Hex)                       | Asset Markets                                                                                                 |
| ------------ | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
| BTC          | 4254430000000000000000000000000000000000 | [BTC markets](https://www.diadata.org/app/price/asset/Bitcoin/0x0000000000000000000000000000000000000000/)    |
| ETH          | 4554480000000000000000000000000000000000 | [ETH markets](https://www.diadata.org/app/price/asset/Ethereum/0x0000000000000000000000000000000000000000/)   |
| XRP          | 5852500000000000000000000000000000000000 | [XRP markets](https://www.diadata.org/app/price/asset/XRPL/0x0000000000000000000000000000000000000000/)       |
| RLUSD        | 524C555344000000000000000000000000000000 | [RLUSD markets](https://www.diadata.org/app/price/asset/XRPL/rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De/)             |
| USDC         | 5553444300000000000000000000000000000000 | [USDC markets](https://www.diadata.org/app/price/asset/Ethereum/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/)  |
| USDT         | 5553445400000000000000000000000000000000 | [USDT markets](https://www.diadata.org/app/price/asset/Ethereum/0xdAC17F958D2ee523a2206206994597C13D831ec7/)  |
| EUROP        | 4555524F50000000000000000000000000000000 | [EUROP markets](https://www.diadata.org/app/price/asset/Ethereum/0x888883b5F5D21fb10Dfeb70e8f9722B9FB0E5E51/) |

## How to Access Data

The DIA oracle object can be retrieved with the [ledger\_entry API](https://xrpl.org/resources/dev-tools/websocket-api-tool#ledger_entry-oracle) call by specifying the account and oracle\_document\_id.

This is the Request JSON for mainnet:

```json theme={"system"}
{
  "id": "example_get_oracle",
  "command": "ledger_entry",
  "oracle": {
    "account": "rP24Lp7bcUHvEW7T7c8xkxtQKKd9fZyra7",
    "oracle_document_id": 42
  },
  "ledger_index": "validated"
}
```

It will return the current price of all the assets in hexadecimal format, which can then be converted to decimal and scaled to obtain the actual price with 8 decimal places.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# zkSync
Source: https://www.diadata.org/docs/guides/chain-specific-guide/zksync

dApps built on zkSync can leverage DIA oracles to access up-to-date asset price information.

[DIA](https://diadata.org/) is a cross-chain oracle provider that sources granular market data from diverse exchanges, including CEXs and DEXs. Its data sourcing is thorough, enabling unparalleled transparency and customizability for resilient price feeds for 20,000+ assets. Its versatile data processing and delivery ensures adaptability and reliability for any decentralized application.

## How to Access Data

Refer to the [Solidity guide](/guides/how-to-guides/fetch-price-data/) for detailed steps on fetching price data from the oracle in your contract.

If you pass `BTC/USD` as the key, it will return the most recent price of BTC in USD with 8 decimal places (e.g. 9601458065403 is \$96,014.58065403) along with the Unix timestamp of the last price update.

## Request a Custom Oracle

DIA offers highly customizable oracles that are individually tailored to each dApp's needs. Each oracle can be customized in the following ways, including:

* Data Sources & Asset Feeds
* Pricing Methodologies
* Update Triggers (Frequency, Deviation, Heartbeat, ...etc)

Get a tailored oracle for your dApp, request one below:

<CardGroup>
  <Card title="Request Custom Oracle" href="/guides/how-to-guides/request-a-custom-oracle" icon="angle-right" />
</CardGroup>

## Support

For developer assistance, connect with the DIA team directly on [Discord](https://discord.gg/ZvGjVY5uvs) or [Telegram](https://t.me/diadata_org).


# DIA Deployments
Source: https://www.diadata.org/docs/guides/dia-deployments

Complete list of DIA contract deployments for the Lumina components on DIA Lasernet Testnet& Mainnet.

Explore the deloyments for the Lumina components on DIA Lasernet. If you're unfamiliar with Lumina stack's infrastructure, read the [Lumina Core Components](/dia-stack/architecture/core-components/overview) page to learn more.

## Token Price Feeds

### Mainnet

| Contract               | Address                                                                                                                       |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| MailBox                | [0xa016e5E7Ce70E78ba7B914299B3c2d44f69Ad392](https://explorer.diadata.org/address/0xa016e5E7Ce70E78ba7B914299B3c2d44f69Ad392) |
| OracleRequestRecipient | [0xA42217338614B7e67D022C52D1CD38e02D619bb0](https://explorer.diadata.org/address/0xA42217338614B7e67D022C52D1CD38e02D619bb0) |
| DIAOracleMetaV2        | [0x5eeB8c00CD8F189f62c9BAD352C0C474429F8A27](https://explorer.diadata.org/address/0x5eeB8c00CD8F189f62c9BAD352C0C474429F8A27) |
| OracleTrigger          | [0x92F0f4C9F769ed83609CD2ccD1ACcE224bBC8cBF](https://explorer.diadata.org/address/0x92F0f4C9F769ed83609CD2ccD1ACcE224bBC8cBF) |
| ISM                    | [0xE74B7D236A97eED9026926073cBb436638266888](https://explorer.diadata.org/address/0xE74B7D236A97eED9026926073cBb436638266888) |

### Testnet

| Contract               | Address                                                                                                                               |
| ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
| MailBox                | [0x16cD72271498bcaD5aeB9f2D785bA82dC5AfA5E2](https://testnet-explorer.diadata.org/address/0x16cD72271498bcaD5aeB9f2D785bA82dC5AfA5E2) |
| OracleRequestRecipient | [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://testnet-explorer.diadata.org/address/0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0) |
| DIAOracleMetaV2        | [0x0087342f5f4c7AB23a37c045c3EF710749527c88](https://testnet-explorer.diadata.org/address/0x0087342f5f4c7AB23a37c045c3EF710749527c88) |
| OracleTrigger          | [0xb869617a3CFcdA07A4cC230d996120074e7c817e](https://testnet-explorer.diadata.org/address/0xb869617a3CFcdA07A4cC230d996120074e7c817e) |
| ISM                    | [0x61D217a26D0Bff1D2b4c6f5880e621071326aadC](https://testnet-explorer.diadata.org/address/0x61D217a26D0Bff1D2b4c6f5880e621071326aadC) |

## RWA Price Feeds

### Mainnet

| Contract               | Address                                                                                                                       |
| ---------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| MailBox                | [0xa016e5E7Ce70E78ba7B914299B3c2d44f69Ad392](https://explorer.diadata.org/address/0xa016e5E7Ce70E78ba7B914299B3c2d44f69Ad392) |
| OracleRequestRecipient | [0xA42217338614B7e67D022C52D1CD38e02D619bb0](https://explorer.diadata.org/address/0xA42217338614B7e67D022C52D1CD38e02D619bb0) |
| DIAOracleMetaV2        | [0x30F5A368a1426851C23E90467F6dCc688116194A](https://explorer.diadata.org/address/0x30F5A368a1426851C23E90467F6dCc688116194A) |
| OracleTrigger          | [0x8ed69fd34A1e29b6c6012e89C555b83b5DC7Dad5](https://explorer.diadata.org/address/0x8ed69fd34A1e29b6c6012e89C555b83b5DC7Dad5) |
| ISM                    | [0xE74B7D236A97eED9026926073cBb436638266888](https://explorer.diadata.org/address/0xE74B7D236A97eED9026926073cBb436638266888) |

## Learn More:

<CardGroup>
  <Card title="Lumina Core Components" href="/dia-stack/architecture/core-components/overview" icon="chevron-right" />

  <Card title="DIA Chain Information" href="/dia-stack/architecture/core-components/lasernet/chain-information" icon="chevron-right" />
</CardGroup>


# DIA Staking
Source: https://www.diadata.org/docs/guides/general-guides/dia-staking



## \$DIA Staking Overview

Staking in DIA Lumina is the security layer. Stakers (token holders and [Feeders](https://www.diadata.org/blog/post/dia-distributed-feeder-network/)) lock up [**\$DIA**](https://www.diadata.org/token/) to secure oracle operations. Feeders are responsible for submitting accurate and timely data onchain and are incentivized to act reliably to earn rewards.

In this system, staking directly underpins the economic and security model of DIA oracles. Over time, Feeders and delegators will earn performance-based rewards; delivering inaccurate data can lead to penalties. This will evolve into a slashing and delegation framework, where token holders can back feeders of their choice and get rewarded for supporting network reliability.

Learn more about the Staking layer:

<Card title="The Staking Layer Behind Trustless Oracle Updates | DIA Blog" href="https://www.diadata.org/blog/post/dia-oracle-staking-layer/" />

## How It Works

Follow [this video tutorial](https://youtu.be/ufJqdPrAb8Q) or the following instructions below. If you have any questions, get in touch with us via [Telegram](https://t.me/diadata_org).

<Note>
  Staking is currently unavailable to residents of the UK, US, or Canada due to
  local regulatory requirements.
</Note>

### Staking

<Steps>
  <Step title="Head to the staking page">
    [https://www.diadata.org/app/staking/](https://www.diadata.org/app/staking/)

    Check if there are available staking opportunities. If so, connect your wallet on DIA Lasernet to get started.

    To add Lasernet to your wallet, go to the [Chain Information page](/resources/chain-information).
  </Step>

  <Step title="Wrap your DIA tokens">
    [https://www.diadata.org/app/staking/wrap/](https://www.diadata.org/app/staking/wrap/)

    Enter the DIA amount you want to exchange for wDIA, review the transaction details, and hit "Wrap".
  </Step>

  <Step title="Stake your wDIA tokens">
    [https://www.diadata.org/app/staking/](https://www.diadata.org/app/staking/)

    Select an amount of wDIA tokens (min. 1 wDIA), check the transaction preview and if everything looks great, hit "Stake".

    Staking takes place on DIA Lasernet Mainnet and requires gas fees to be paid for the transactions (in DIA).
  </Step>

  <Step title="Review your portfolio">
    Review your portfolio to see your staked wDIA tokens, APR, and accrued rewards. Below are the stake statuses:

    * `x Staking`: total amount of wDIA tokens staked
    * `x Unstaking`: total amount of wDIA tokens unstaking
    * `x Available`: total amount of wDIA & DIA tokens available to stake
    * `x Claimable`: total amount of wDIA tokens claimable after the unstaking period
  </Step>
</Steps>

### Un-staking

<Steps>
  <Step title="Head to your portfolio">
    [https://www.diadata.org/app/staking/](https://www.diadata.org/app/staking/)

    Review your stakes under "Staked pools" section.
  </Step>

  <Step title="Make a request to unstake">
    Click on the "Unstake" button next to the stake that you want to unstake. This will change the status of your stake to `Unstaking`.

    By doing this, you're initiating the unstaking process which will take 7 days to complete. Once the cooldown period is over, you can claim your prinicpal along with the rewards.
  </Step>

  <Step title="Withdraw your stake and claim rewards">
    Once the cooldown period is over, you can click on the "Claim" button to withdraw your stake and claim rewards.

    Your stake and rewards will be available in your wallet as wDIA tokens.
  </Step>

  <Step title="(Optional) Un-wrap your wDIA tokens">
    [https://www.diadata.org/app/staking/wrap/](https://www.diadata.org/app/staking/wrap/)

    You can un-wrap your rewards to DIA tokens by entering an amount of wDIA tokens and clicking "Unwrap".
  </Step>
</Steps>

## Audit

The staking smart contract has been audited by Mixbytes. The full audit report can be found here:

<Card title="DIA Lumina Staking Security Audit Report.pdf" href="https://github.com/mixbytes/audits_public/tree/master/DIA/Lumina%20Staking" icon="file-pdf" />


# Run a Feeder
Source: https://www.diadata.org/docs/guides/general-guides/run-a-feeder

Running a feeder is a way to contribute to the decentralization of the data sourcing process in DIA's feeder network, making the ecosystem robust and giving dApps access to real-time and verifiable data.

<Info>
  Please refer to our
  [Wiki](https://github.com/diadata-org/decentral-feeder/wiki) page and
  [GitHub](https://github.com/diadata-org/decentral-feeder) repository for the
  latest documentation on feeder nodes and releases.
</Info>

Start by reviewing the [hardware specifications](/guides/general-guides/run-a-feeder/hardware-specs) and proceed to [running the node](/guides/general-guides/run-a-feeder/setting-up-the-node) based on your preferred deployment method.

If you're interested in becoming an official feeder in DIA's feeder network, please reach out to our team over our [dedicated communication channels](/guides/resources/community-and-support).


# Hardware Specs
Source: https://www.diadata.org/docs/guides/general-guides/run-a-feeder/hardware-specs



| Hardware | Normal Usage | Peak Usage  |
| -------- | ------------ | ----------- |
| Memory   | \~100 MiB    | \~500 MiB   |
| CPU      | \~0.1 cores  | \~0.3 cores |
| Storage  | Minimal      | N/A         |

The storage is minimal because no historical data is stored on the nodes; only real-time data is pushed directly to smart contracts. These resource needs can be sufficiently met by a minimal, entry-level virtual machine from most cloud providers with the following specifications:

* 1 vCPU

* 1 GB RAM

* 10 GB Storage

## Cost Projections

### **Standalone VM**

The cost of operating the decentral-feeder primarily depends on the infrastructure selected by the node operator. The following prices are estimates and may vary depending on factors such as region, additional services, network usage, and other considerations.

| Cloud Provider               | Monthly Costs |
| ---------------------------- | ------------- |
| Hetzner (CX22)               | \~\$4         |
| Amazon AWS (t2.micro)        | \~\$9         |
| DigitalOcean (Basic Droplet) | \~\$5         |

### **Kubernetes Clusters**

The costs of running feeder nodes in our Kubernetes clusters are generally higher compared to standalone VMs. It also depends on your setup and the additional overhead of managing Kubernetes infrastructure and other services.

## Performance Metrics

* Our nodes are configured with 20-100 websocket connections open in parallel, and a transaction is being sent every 1-20 seconds so a similar configuration would be expected

* You can use public RPC endpoints to fetch data and submit txns onchain. However, they’re mostly good for testing purposes so we recommend setting up a private endpoint for consistent usage. Here are some of our recommendations:

<CardGroup>
  <Card title="Chainstack" href="https://chainstack.com/" icon="server" />

  <Card title="Alchemy" href="https://www.alchemy.com/" icon="flask" />

  <Card title="Ankr" href="https://www.ankr.com/" icon="anchor" />

  <Card title="Quicknode" href="https://www.quicknode.com/" icon="bolt" />
</CardGroup>


# Setting Up the Node
Source: https://www.diadata.org/docs/guides/general-guides/run-a-feeder/setting-up-the-node



<Info>
  Make sure you familiraize yourself with the data flow in the Lumina system before proceeding with the node setup. To learn more, checkout the architecture guide [here](/reference/architecture).
</Info>

## Requirements

* Ensure that Docker or Docker Compose is installed on your machine.

* Clone the [decentral-feeder repository](https://github.com/diadata-org/decentral-feeder) to your local machine.

* The container has minimal resource requirements, making it suitable for most machines, including Windows, macOS, Linux, and Raspberry Pi, as long as Docker is installed.

* An ETH private key from MetaMask or any other Eth wallet. Alternatively to generate private key effortlesly eth-keys tool can be used for this [ethereum/eth-keys](https://github.com/ethereum/eth-keys)

* DIA tokens in your wallet. If you're using testnet, you can access the faucet [here](https://faucet.diadata.org/).

Next, select your preferred deployment method:

<CardGroup>
  <Card title="Docker compose" href="/how-to-guides/run-a-feeder/setting-up-the-node/docker-compose" icon="docker">
    Suitable for a single container setup and quick testing
  </Card>

  <Card title="Docker run" href="/how-to-guides/run-a-feeder/setting-up-the-node/docker-run" icon="docker">
    Suitable for simple setups without orchestration
  </Card>

  <Card title="Kubernetes" href="/how-to-guides/run-a-feeder/setting-up-the-node/kubernetes" icon="code">
    Ideal for production environments requiring scalability and high availability
  </Card>
</CardGroup>


# Docker Compose
Source: https://www.diadata.org/docs/guides/general-guides/run-a-feeder/setting-up-the-node/docker-compose



## Configure Environment Variables

<Steps>
  <Step>
    Navigate to the docker-compose folder where `docker-compose.yaml` file is located.

    ```bash theme={"system"}
    cd docker-compose
    ```
  </Step>

  <Step>
    Create a `.env` file in the same folder. it should contain the following variables:

    * `NODE_OPERATOR_NAME`: A unique and descriptive name identifying the organization or entity running the node. This name is used for monitoring and should be chosen carefully to ensure it is both meaningful and recognizable (e.g., include your organization name or geographical region). Providing a clear name helps distinguish your node in dashboards and logs.

    * `CHAIN_ID`: set the chain ID value

    * `PRIVATE_KEY`: Your private key for the deployment.

    * `DEPLOYED_CONTRACT`: The contract address. Initially, leave this empty during the first deployment to retrieve the deployed contract.

    <Info>
      The following pushgateway vars are **mandatory** for official DIA node operators. If you're an official operator, please reach out to the team to get these credentials. For developers testing the system, these credentials are **optional** and can be skipped.
    </Info>

    * `PUSHGATEWAY_URL`: The Pushgateway endpoint used for pushing metrics to Prometheus.

    * `PUSHGATEWAY_USER`: to allow decentralized-feeder authenticate towards the monitoring server.

    * `PUSHGATEWAY_PASSWORD`: to allow decentralized-feeder authenticate towards the monitoring server.

    For additional environment variable configurations, refer to [Adding Exchange Pairs](https://github.com/diadata-org/decentral-feeder/wiki/Adding-exchange-pairs) and [Watchdog environment variables](https://github.com/diadata-org/decentral-feeder/wiki/Enabling-watchdogs).

    E.g. Env file:

    ```bash theme={"system"}
    NODE_OPERATOR_NAME=
    CHAIN_ID=
    PRIVATE_KEY=
    DEPLOYED_CONTRACT=
    PUSHGATEWAY_URL=
    PUSHGATEWAY_USER=
    PUSHGATEWAY_PASSWORD=
    ```
  </Step>

  <Step>
    Open a terminal in the `docker-compose` folder and start the deployment by running:

    ```bash theme={"system"}
    docker-compose up
    ```
  </Step>
</Steps>

## Retrieve Deployed Contract

<Steps>
  <Step>
    Once the container is deployed with `DEPLOYED_CONTRACT` env variable empty the logs will display the deployed contract address in the following format:

    ```bash theme={"system"}
    │ time="2024-11-25T11:30:08Z" level=info msg="Contract pending deploy: 0xxxxxxxxxxxxxxxxxxxxxxxxxx."
    ```
  </Step>

  <Step>
    Copy the displayed contract address (e.g., `0xxxxxxxxxxxxxxxxxxxxxxxxxx`) and stop the container with

    ```bash theme={"system"}
    docker rm -f <container_name>
    ```
  </Step>

  <Step>
    Check if the container is running correctly by viewing the logs. Run the following command:

    ```bash theme={"system"}
    docker-compose logs -f
    ```
  </Step>

  <Step>
    Look for logs similar to the example below, which indicate a successful startup:

    ```bash theme={"system"}
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - Atomic filter value for market Binance:SUSHI-USDT with 20 trades: 0.7095307176575745."                                                                  │
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - Atomic filter value for market Simulation:UNI-USDC with 1 trades: 8.008539500390082."                                                                   │
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - Atomic filter value for market Crypto.com:USDT-USD with 5 trades: 0.99948."                                                                             │
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - filter median for MOVR: 9.864475653518195."                                                                                                             │
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - filter median for STORJ: 0.4672954012114179."                                                                                                           │
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - filter median for DIA: 0.9839597410694259."                                                                                                             │
    │ time="2024-10-29T13:39:35Z" level=info msg="Processor - filter median for WETH: 2626.9564003841315."
    ```
  </Step>
</Steps>

## Remove Container (Optional)

<Steps>
  <Step>
    You can optionally cleanup the deployment once you're done by running:

    ```bash theme={"system"}
    docker rm -f <container_name>
    ```
  </Step>

  <Step>
    Verify the container has been removed:

    ```bash theme={"system"}
    docker ps -a
    ```
  </Step>
</Steps>


# Docker Run
Source: https://www.diadata.org/docs/guides/general-guides/run-a-feeder/setting-up-the-node/docker-run



<Steps>
  <Step>
    Using the same [ENV variables](/how-to-guides/run-a-feeder/setting-up-the-node/docker-compose), run the feeder with `DEPLOYED_CONTRACT` initially empty:

    ```bash theme={"system"}
    docker run -d \
      -e NODE_OPERATOR_NAME= \
      -e PRIVATE_KEY= \
      -e CHAIN_ID= \
      -e DEPLOYED_CONTRACT= \
      -e PUSHGATEWAY_URL= \
      -e PUSHGATEWAY_USER= \
      -e PUSHGATEWAY_PASSWORD= \
      --name decentralized-feeder \
      diadata/decentralized-feeder:<VERSION>
    ```
  </Step>

  <Step>
    Retrieve the logs to get the deployed contract address. See the expected logs [here](/how-to-guides/run-a-feeder/setting-up-the-node/docker-compose#retrieve-deployed-contract).

    ```bash theme={"system"}
    docker logs <container_name>
    ```
  </Step>

  <Step>
    Stop the container, update the `DEPLOYED_CONTRACT` value, and restart:

    ```bash theme={"system"}
    docker stop <container_name>

    docker run -d \
      -e NODE_OPERATOR_NAME= \
      -e PRIVATE_KEY= \
      -e CHAIN_ID= \
      -e DEPLOYED_CONTRACT= \
      -e PUSHGATEWAY_USER= \
      -e PUSHGATEWAY_PASSWORD= \
      -e EXCHANGEPAIRS= \
      --name decentralized-feeder \
      diadata/decentralized-feeder:<VERSION>
    ```
  </Step>

  <Step>
    Retrieve the logs to verify the container is running as expected

    ```bash theme={"system"}
    docker logs <container_name>
    ```
  </Step>
</Steps>

For additional environment variable configurations, refer to [Adding Exchange Pairs](https://github.com/diadata-org/decentral-feeder/wiki/Adding-exchange-pairs) and [Watchdog environment variables](https://github.com/diadata-org/decentral-feeder/wiki/Enabling-watchdogs).


# Kubernetes
Source: https://www.diadata.org/docs/guides/general-guides/run-a-feeder/setting-up-the-node/kubernetes



<Steps>
  <Step>
    Create a Kubernetes `Deployment` manifest. Replace `<VERSION>` with the desired version:

    ```yaml theme={"system"}
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: decentralized-feeder
      namespace: default
    spec:
      replicas: 1
      selector:
        matchLabels:
          app: decentralized-feeder
      template:
        metadata:
          labels:
            app: decentralized-feeder
        spec:
          containers:
          - name: feeder-container
            image: diadata/decentralized-feeder:<VERSION>
            env:
            - name: PRIVATE_KEY
              valueFrom:
                secretKeyRef: {key: private_key_secret, name: private_key_secret}
            - name: NODE_OPERATOR_NAME
              value: ""
            - name: DEPLOYED_CONTRACT
              value: ""
            - name: CHAIN_ID
              value: ""
            - name: EXCHANGEPAIRS
              value: ""
            - name: PUSHGATEWAY_URL
              value: ""
            - name: PUSHGATEWAY_USER
              value: ""
            - name: PUSHGATEWAY_PASSWORD
              value: ""
            - containerPort: 8080
    ```

    For additional environment variable configurations, refer to [Adding Exchange Pairs](https://github.com/diadata-org/decentral-feeder/wiki/Adding-exchange-pairs) and [Watchdog environment variables](https://github.com/diadata-org/decentral-feeder/wiki/Enabling-watchdogs).
  </Step>

  <Step>
    Run the feeder with `DEPLOYED_CONTRACT` set to an empty string (`""`) in the Kubernetes manifest.

    ```bash theme={"system"}
    kubectl apply -f deployment.yaml
    ```
  </Step>

  <Step>
    Monitor the logs for the deployed contract address. See the expected logs [here](/how-to-guides/run-a-feeder/setting-up-the-node/docker-compose#retrieve-deployed-contract).

    ```bash theme={"system"}
    kubectl logs <pod-name>
    ```
  </Step>

  <Step>
    Update the `DEPLOYED_CONTRACT` value in the manifest with the retrieved contract address.
  </Step>

  <Step>
    Apply the updated manifest:

    ```
    kubectl apply -f deployment.yaml
    ```
  </Step>
</Steps>


# OracleRequestRecipient.sol
Source: https://www.diadata.org/docs/guides/general-guides/smart-contracts/OracleRequestRecipient.sol



```solidity theme={"system"}
// SPDX-License-Identifier: GPL-3.0
pragma solidity 0.8.29;

import { Ownable } from "@openzeppelin/contracts/access/Ownable.sol";

import { IMessageRecipient } from "./interfaces/IMessageRecipient.sol";
import { IOracleTrigger } from "./interfaces/oracle/IOracleTrigger.sol";
import { TypeCasts } from "./libs/TypeCasts.sol";

import { IInterchainSecurityModule, ISpecifiesInterchainSecurityModule } from "./interfaces/IInterchainSecurityModule.sol";
import "@openzeppelin/contracts/security/ReentrancyGuard.sol";

using TypeCasts for address;


contract OracleRequestRecipient is
    Ownable,
    IMessageRecipient,
    ISpecifiesInterchainSecurityModule,
    ReentrancyGuard
{

    IInterchainSecurityModule public interchainSecurityModule;

    mapping(uint32 => mapping(bytes32 => bool)) public whitelistedSenders;

    address private oracleTriggerAddress;

    event ReceivedCall(address indexed caller, string key);

    event WhitelistUpdated(
        uint32 indexed origin,
        bytes32 indexed sender,
        bool status
    );

    event OracleTriggerUpdated(
        address indexed oldAddress,
        address indexed newAddress
    );

    event InterchainSecurityModuleUpdated(
        address indexed previousISM,
        address indexed newISM
    );


    event TokensRecovered(address indexed recipient, uint256 amount);

    error EmptyOracleRequestData();
    error OracleTriggerNotSet();
    error SenderNotWhitelisted(bytes32 sender, uint32 origin);
    error UnauthorizedCaller(address caller);
    error InvalidSenderAddress();
    error AlreadyWhitelisted(bytes32 sender, uint32 origin);
    error InvalidISMAddress();
    error InvalidOracleTriggerAddress();
    error InvalidReceiver();
    error NoBalanceToWithdraw();
    error TransferFailed();

    function handle(
        uint32 _origin,
        bytes32 _sender,
        bytes calldata _data
    ) external payable virtual override nonReentrant {
        if (_data.length == 0) revert EmptyOracleRequestData();
        if (oracleTriggerAddress == address(0)) revert OracleTriggerNotSet();

        if (!whitelistedSenders[_origin][_sender])
            revert SenderNotWhitelisted(_sender, _origin);

        address sender = address(uint160(uint256(_sender)));

        if (msg.sender != IOracleTrigger(oracleTriggerAddress).getMailBox()) {
            revert UnauthorizedCaller(msg.sender);
        }

        string memory key = abi.decode(_data, (string));

        emit ReceivedCall(sender, key);

        IOracleTrigger(oracleTriggerAddress).dispatch{ value: msg.value }(
            _origin,
            sender,
            key
        );
    }

    function addToWhitelist(
        uint32 _origin,
        bytes32 _sender
    ) external onlyOwner {
        if (_sender == bytes32(0)) {
            revert InvalidSenderAddress();
        }

        if (whitelistedSenders[_origin][_sender]) {
            revert AlreadyWhitelisted(_sender, _origin);
        }

        whitelistedSenders[_origin][_sender] = true;
        emit WhitelistUpdated(_origin, _sender, true);
    }

    function removeFromWhitelist(
        uint32 _origin,
        bytes32 _sender
    ) external onlyOwner {
        if (_sender == bytes32(0)) {
            revert InvalidSenderAddress();
        }
        whitelistedSenders[_origin][_sender] = false;
        emit WhitelistUpdated(_origin, _sender, false);
    }

    function setInterchainSecurityModule(address _ism) external onlyOwner {
        if (_ism == address(0)) {
            revert InvalidISMAddress();
        }
        emit InterchainSecurityModuleUpdated(
            address(interchainSecurityModule),
            _ism
        );

        interchainSecurityModule = IInterchainSecurityModule(_ism);
    }

    function setOracleTriggerAddress(
        address _oracleTrigger
    ) external onlyOwner {
        if (_oracleTrigger == address(0)) {
            revert InvalidOracleTriggerAddress();
        }
        emit OracleTriggerUpdated(oracleTriggerAddress, _oracleTrigger);

        oracleTriggerAddress = _oracleTrigger;
    }

    receive() external payable {}

    function retrieveLostTokens(address receiver) external onlyOwner {
        if (receiver == address(0)) {
            revert InvalidReceiver();
        }
        uint256 balance = address(this).balance;
        if (balance == 0) {
            revert NoBalanceToWithdraw();
        }
        (bool success, ) = payable(receiver).call{ value: balance }("");
        if (!success) {
            revert TransferFailed();
        }
        emit TokensRecovered(receiver, balance);
    }

    function getOracleTriggerAddress() external view returns (address) {
        return oracleTriggerAddress;
    }
}
```


# PushOracleReceiver.sol
Source: https://www.diadata.org/docs/guides/general-guides/smart-contracts/PushOracleReceiver.sol



```solidity theme={"system"}
// SPDX-License-Identifier: GPL-3.0
pragma solidity 0.8.29;

import { Ownable } from "@openzeppelin/contracts/access/Ownable.sol";
import { IPushOracleReceiver } from "./interfaces/oracle/IPushOracleReceiver.sol";
import { IInterchainSecurityModule } from "./interfaces/IInterchainSecurityModule.sol";
import { ProtocolFeeHook } from "./ProtocolFeeHook.sol";
import { TypeCasts } from "./libs/TypeCasts.sol";

contract PushOracleReceiver is IPushOracleReceiver, Ownable {
    using TypeCasts for address;

    IInterchainSecurityModule public interchainSecurityModule;
    address payable public paymentHook;
    address public trustedMailBox;
    mapping(string => Data) public updates;

    error InvalidISMAddress();

    modifier validateAddress(address _address) {
        if (_address == address(0)) revert InvalidAddress();
        _;
    }

    function handle(
        uint32 _origin,
        bytes32 _sender,
        bytes calldata _data
    ) external payable override validateAddress(paymentHook) {
        if (msg.sender != trustedMailBox) revert UnauthorizedMailbox();
        if (address(interchainSecurityModule) == address(0))
            revert InvalidISMAddress();

        (string memory key, uint128 timestamp, uint128 value) = abi.decode(
            _data,
            (string, uint128, uint128)
        );

        if (updates[key].timestamp >= timestamp) {
            return;
        }

        Data memory newData = Data({ timestamp: timestamp, value: value });
        updates[key] = newData;

        emit ReceivedMessage(key, timestamp, value);

        uint256 gasPrice = tx.gasprice;
        uint256 fee = ProtocolFeeHook(payable(paymentHook)).gasUsedPerTx() *
            gasPrice;

        bool success;
        {
            (success, ) = paymentHook.call{ value: fee }("");
        }

        if (!success) revert AmountTransferFailed();
    }

    function setInterchainSecurityModule(
        address _ism
    ) external onlyOwner validateAddress(_ism) {
        emit InterchainSecurityModuleUpdated(
            address(interchainSecurityModule),
            _ism
        );
        interchainSecurityModule = IInterchainSecurityModule(_ism);
    }

    function setPaymentHook(
        address payable _paymentHook
    ) external onlyOwner validateAddress(_paymentHook) {
        emit PaymentHookUpdated(paymentHook, _paymentHook);
        paymentHook = _paymentHook;
    }

    function setTrustedMailBox(
        address _mailbox
    ) external onlyOwner validateAddress(_mailbox) {
        emit TrustedMailBoxUpdated(trustedMailBox, _mailbox);
        trustedMailBox = _mailbox;
    }

    function retrieveLostTokens(
        address receiver
    ) external onlyOwner validateAddress(receiver) {
        uint256 balance = address(this).balance;
        if (balance == 0) revert NoBalanceToWithdraw();

        (bool success, ) = payable(receiver).call{ value: balance }("");
        if (!success) revert AmountTransferFailed();
        emit TokensRecovered(receiver, balance);
    }
    receive() external payable {}

    fallback() external payable {}
}
```


# DIAOracleV2.sol
Source: https://www.diadata.org/docs/guides/general-guides/smart-contracts/diaoraclev2.sol



```javascript theme={"system"}
pragma solidity 0.7.4;

contract DIAOracleV2 {
    mapping (string => uint256) public values;
    address oracleUpdater;

    event OracleUpdate(string key, uint128 value, uint128 timestamp);
    event UpdaterAddressChange(address newUpdater);

    constructor() {
        oracleUpdater = msg.sender;
    }

    function setValue(string memory key, uint128 value, uint128 timestamp) public {
        require(msg.sender == oracleUpdater);
        uint256 cValue = (((uint256)(value)) << 128) + timestamp;
        values[key] = cValue;
        emit OracleUpdate(key, value, timestamp);
    }

    function getValue(string memory key) external view returns (uint128, uint128) {
        uint256 cValue = values[key];
        uint128 timestamp = (uint128)(cValue % 2**128);
        uint128 value = (uint128)(cValue >> 128);
        return (value, timestamp);
    }

    function updateOracleUpdaterAddress(address newOracleUpdaterAddress) public {
        require(msg.sender == oracleUpdater);
        oracleUpdater = newOracleUpdaterAddress;
        emit UpdaterAddressChange(newOracleUpdaterAddress);
    }
}
```


# DIARandomOracle.sol
Source: https://www.diadata.org/docs/guides/general-guides/smart-contracts/diarandomoracle.sol



```solidity theme={"system"}
pragma solidity ^0.8.0;

contract DIARandomOracle {

struct Random {
   string randomness;
   string signature;
   string previousSignature;
}

    mapping (uint256 => Random) public values;
    uint256 public lastRound = 0;

    address public oracleUpdater;

    event OracleUpdate(string key, uint128 value, uint128 timestamp);
    event UpdaterAddressChange(address newUpdater);

    constructor() {
        oracleUpdater = msg.sender;
    }

    function setRandomValue(uint256 _round, string memory _randomness,string memory _signature,string memory _previousSignature) public {
             require(msg.sender == oracleUpdater,"not a updater");
             require(lastRound<_round, "old round");
             lastRound = _round;
             values[_round] = Random(_randomness,_signature,_previousSignature);
    }

    function getValue(uint256 _round) external view returns ( Random memory) {
        return values[_round];
    }

    function updateOracleUpdaterAddress(address newOracleUpdaterAddress) public {
        require(msg.sender == oracleUpdater,"not a updater");
        oracleUpdater = newOracleUpdaterAddress;
        emit UpdaterAddressChange(newOracleUpdaterAddress);
    }

    function getRandomValueFromRound(uint256 _round ) external view returns (string memory){
        return values[_round].randomness;
    }
     function getRandomValueFromRoundWithSignature(uint256 _round ) external view returns (Random memory){
        return values[_round];
    }

    function getLastRound()public view returns(uint256){
        return lastRound;
    }
}
```


# Build a Scraper
Source: https://www.diadata.org/docs/guides/general-guides/tutorials

Develop applications and sources on top of DIA using our open-source infrastructure.

DIA has a dedicated infrastructure for testing various integrations into the system. In the following pages you can learn how it works.

Start here:

<CardGroup>
  <Card title="Development Cluster Stack" href="/guides/how-to-guides/tutorials/development-cluster-stack" icon="arrow-right" />
</CardGroup>

Or proceed directly to the scraper integration tutorials:

<CardGroup>
  <Card title="Add a new exchange scraper" href="/guides/how-to-guides/tutorials/add-a-new-exchange-scraper" icon="arrow-right" />

  <Card title="Add a new foreign scraper" href="/guides/how-to-guides/tutorials/add-a-new-foreign-scraper" icon="arrow-right" />

  <Card title="Add a new liquidity scraper" href="/guides/how-to-guides/tutorials/add-a-new-liquidity-scraper" icon="arrow-right" />
</CardGroup>


# Add a New Exchange Scraper
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/add-a-new-exchange-scraper



#### Add your scraper

> Before you begin writing a scraper, please check if the exchange offers integration through WebSockets. If it does, implement the scraper using the WebSocket protocol instead of a RESTful API.

To scrape data from an exchange data source, called "**MySource**" for instance, follow these steps:

<Steps>
  <Step>
    Create a new file in the directory `pkg/dia/scraper/exchange-scrapers/` with the filename `MySourceScraper.go`.
  </Step>

  <Step>
    To allow the platform to call your scraper, implement a scraper that conforms to the [APIScraper](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/APIScraper.go#L81) interface from the *scrapers* package:

    ```js theme={"system"}
    type APIScraper interface {
    	io.Closer
    	ScrapePair(pair dia.Pair) (PairScraper, error)
    	FetchAvailablePairs() (pairs []dia.Pair, err error)
    	Channel() chan *dia.Trade
    }
    ```

    Start building your scraper by writing a function with the signature `NewMySourceScraper(exchangeName string) *MySourceScraper`. We suggest that this function calls a `mainLoop()` method in a go routine, constantly receiving trade information through the trade channel of *MySourceScraper* as long as the channel is open.

    In order to implement the interface, it is necessary to include the `ScrapePair` method, which returns a *MySourcePairScraper* for a specific pair, so our main collection method can iterate over all possible trading pairs. Note that *MySourcePairScraper* should respect and implement the [`PairScraper`](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/APIScraper.go#L103) interface

    Also, to ensure proper error handling and cleanup, it is recommended to include a method `Error()`, which returns an error as soon as the scraper's channel closes. Additionally, `Close()` and `cleanup()` methods should be included to handle the closing and shutting down of channels.

    > For a better understanding of how to set up a scraper, you can refer to the [`CoinBaseScraper.go`](https://github.com/diadata-org/diadata/blob/master/pkg/dia/scraper/exchange-scrapers/CoinBaseScraper.go) file, as it provides an example of an existing exchange scraper and its overall structure and logic.
  </Step>

  <Step>
    To make the scraper visible to the system, add a reference to it in `Config.go` in the *dia* package:

    ```js theme={"system"}
    const (
      MySourceExchange = "MySource"
    )
    ```
  </Step>

  <Step>
    Add a case for your scraper in the switch statement in the `pkg/dia/scraper/exchange-scrapers/APIScraper.go` file:

    ```js theme={"system"}
    func NewAPIScraper(exchange string, key string, secret string) APIScraper {
    	switch exchange {
    	case dia.MySourceExchange:
    		return NewMySourceScraper(key, secret, dia.MySourceExchange)
    	}
    }
    ```
  </Step>

  <Step>
    Finally, add exchange's pairs to `config/MySourceExchange.json` config:

    ```js theme={"system"}
    {
      "Coins": [
        {
          "Exchange": "MySource",
          "ForeignName": "QUICK-USD",
          "Ignore": false,
          "Symbol": "QUICK"
        }
      ]
    }
    ```
  </Step>
</Steps>

#### Steps to run the scraper locally

<Steps>
  <Step>
    Modify the `build/Dockerfile-genericCollector` and `build/Dockerfile-pairDiscoveryService` files and add the following two lines before the `RUN go mod tidy` step:

    ```js theme={"system"}
    COPY . /diadata
    RUN go mod edit -replace github.com/diadata-org/diadata=/diadata
    ```
  </Step>

  <Step>
    Build the necessary service containers by running the following commands:

    ```js theme={"system"}
    minikube image build -t diadata.pairdiscoveryservice:latest -f build/Dockerfile-pairDiscoveryService .
    minikube image build -t diadata.exchangescrapercollector:latest -f build/Dockerfile-genericCollector .
    ```
  </Step>

  <Step>
    Create a manifest for the new exchange scraper by creating a new `mysource.yaml` file. You can refer to existing files for guidance or use the following template:

    ```yaml theme={"system"}
    apiVersion: "v1"
    kind: Pod
    metadata:
      name: "exchangescraper-mysource"
    spec:
      containers:
      - name: exchangescraper-mysource
        image: diadata.exchangescrapercollector:latest
        imagePullPolicy: Never
        command: ["collector"]
        args: ["-exchange=MySource", "-mode=current", "-pairsfile=true"]
        env:
        - name: USE_ENV
          value: "true"
        - name: POSTGRES_USER
          value: "postgres"
        - name: POSTGRES_PASSWORD
          value: "password"
        - name: POSTGRES_DB
          value: "postgres"
        - name: POSTGRES_HOST
          value: "postgres.default.svc.cluster.local"
        - name: INFLUXURL
          value: "http://influx.default.svc.cluster.local:8086"
        - name: INFLUXUSER
          value: "test"
        - name: INFLUXPASSWORD
          value: "testtest"
        - name: REDISURL
          value: "redis.default.svc.cluster.local:6379"
        - name: KAFKAURL
          value: "kafka.default.svc.cluster.local:9094"
      initContainers:
      - name: pairdiscovery-mysource
        image: diadata.pairdiscoveryservice:latest
        imagePullPolicy: Never
        command: ["pairDiscoveryService"]
        args: ["-exchange=MySource", "-mode=verification"]
        env:
        - name: USE_ENV
          value: "true"
        - name: POSTGRES_USER
          value: "postgres"
        - name: POSTGRES_PASSWORD
          value: "password"
        - name: POSTGRES_DB
          value: "postgres"
        - name: POSTGRES_HOST
          value: "postgres.default.svc.cluster.local"
        - name: INFLUXURL
          value: "http://influx.default.svc.cluster.local:8086"
        - name: INFLUXUSER
          value: "test"
        - name: INFLUXPASSWORD
          value: "testtest"
        - name: REDISURL
          value: "redis.default.svc.cluster.local:6379"
        - name: KAFKAURL
          value: "kafka.default.svc.cluster.local:9094"
    ```
  </Step>

  <Step>
    Before running the manifest, create a new entry in the database for the new exchange:

    ```
    kubectl exec -it deployment/postgres -- psql -U postgres -c "INSERT INTO exchange (exchange_id, "name", centralized, bridge, contract, blockchain, rest_api, ws_api, pairs_api, watchdog_delay, scraper_active) VALUES(gen_random_uuid(), 'MySource', true, false, '', '', '', 'wss://mysource.com', 'https://mysource.com', 300, true);"
    ```
  </Step>

  <Step>
    Deploy the manifest using the following *kubectl* command:

    ```
    kubectl create -f mysource.yaml
    ```
  </Step>
</Steps>

Hooray  Your scraper should now be running.

### Exchanges Command

CEX

```bash theme={"system"}
pairDiscoveryService -exchange=ExchangeName -mode=verification
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=ExchangeName -mode=current -pairsfile=true
```

DEX

```bash theme={"system"}
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=ExchangeName -mode=current -pairsfile=true
```

### Exchange Test

```bash theme={"system"}
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=EXCHANGE_NAME -mode=current -pairsfile=true
```

Centralized:

* Bitfinex: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=Bitfinex -mode=current -pairsfile=true`

  * rm ./collector.go && cp /mnt/env-context/cmd/exchange-scrapers/collector/collector.go ./collector.go && go mod edit -replace github.com/diadata-org/diadata=/mnt/env-context && go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install -a && collector -exchange=Bitfinex -mode=current -pairsfile=true

* Bittrex: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=Bittrex -mode=current -pairsfile=true`

* CoinBase: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=CoinBase -mode=current -pairsfile=true`

* MEXC: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && collector -exchange=MEXC -mode=current -pairsfile=true`

Decentralized:

* PlatypusFinance

* Orca: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && SOLANA_URI_REST=https://try-rpc.mainnet.solana.blockdaemon.tech/ collector -exchange=Orca -mode=current -pairsfile=true`


# Add a New Foreign Scraper
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/add-a-new-foreign-scraper



Implement `ForeignScrapperer` interface at `pkg/dia/scraper/foreign-scrapers/Scrapper.go` file

```js theme={"system"}
type ForeignScrapperer interface {
	UpdateQuotation() error
	GetQuoteChannel() chan *models.ForeignQuotation
}
```

Add the scraper implementation a `MyForeignScraper.go` Golang file to `pkg/dia/scraper/foreign-scrapers/` folder and add the next implementations:

```js theme={"system"}
func (scraper *MyForeignScraper) Pool() chan dia.Pool {}
func (scraper *MyForeignScraper) Done() chan bool {}
```

<Steps>
  <Step>
    Add a constructor for the scraper:

    ```js theme={"system"}
    func NewMyForeignScraper(exchange dia.Exchange) *MyForeignScraper {}
    ```
  </Step>

  <Step>
    Add `MyForeignScraper` case at scraper file `cmd/foreignscraper/foreign.go`:

    ```js theme={"system"}
    switch *scraperType {
    	case "MyForeignScraper":
    		log.Println("Start scraping data")
    		sc = scrapers.NewMyForeignScraper(ds)
    }
    ```
  </Step>
</Steps>

## Foreign Command

```js theme={"system"}
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && foreignscraper -foreignType=ForeignType
```

## Foreign Test

```js theme={"system"}
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && foreignscraper -foreignType=FOREIGN_TYPE
```


# Add a New Liquidity Scraper
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/add-a-new-liquidity-scraper



Implement `LiquidityScraper` interface at `pkg/dia/scraper/liquidity-scrapers/ScraperInterface.go` file

```js theme={"system"}
type LiquidityScraper interface {
	Pool() chan dia.Pool
	Done() chan bool
}
```

<Steps>
  <Step>
    Add a scraper implementation, `MyLiquidityScraper.go` file to `pkg/dia/scraper/liquidity-scrapers/` folder implement the functions:

    ```js theme={"system"}
    func (scraper *MyLiquidityScraper) Pool() chan dia.Pool {}
    func (scraper *MyLiquidityScraper) Done() chan bool {}
    ```
  </Step>

  <Step>
    Add a constructor for the scraper:

    ```js theme={"system"}
    func NewMyLiquidityScraper(exchange dia.Exchange) *MyLiquidityScraper {}
    ```
  </Step>
</Steps>

## Liquidity Command

```js theme={"system"}
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && liquidityScraper -exchange=ExchangeName
```

## Liquidity Test

```js theme={"system"}
go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && liquidityScraper -exchange=EXCHANGE_NAME
```

* PlatypusFinance: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && liquidityScraper -exchange=PlatypusFinance`

* Orca: `go mod tidy -go=1.16 && go mod tidy -go=1.17 && go install && SOLANA_URI_REST=https://try-rpc.mainnet.solana.blockdaemon.tech/ liquidityScraper -exchange=Orca`


# Additional Notes
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/additional-notes



## Access data endpoints and UIs

### Kubernetes Dashboard

To start the Kubernetes Dashboard, use the following command:

```js theme={"system"}
minikube dashboard --url=true --port=8083
```

Once the dashboard service is ready, you can visit the web interface in your browser.

### Data stores

Forward the ports of the data stores services to localhost:

* PostgreSQL Database: `kubectl port-forward deployment/postgres 5432:5432`

* Redis Cache: `kubectl port-forward deployment/redis 6379:6379`

* InfluxDB Database: `kubectl port-forward deployment/influx 8086:8086`

### Other routes available after forward:

* REST Server: port 8081

* GraphQL: port 1111, and [Web UI](http://localhost:1111/)

* Kafka: port 8080, and [AKHQ Web UI](http://localhost:8080/)

* Grafana: port 3000, and [Web UI](http://localhost:3000/)

## Contribute to DIA main package

```js theme={"system"}
go mod edit -replace github.com/diadata-org/diadata=/mnt/env-context
```

## Debug Influx writes

To debug InfluxDB writes, just change points in batch to see more frequent writes to influx (`pkg/model/db.go`):

```js theme={"system"}
influxMaxPointsInBatch = 10
```

## Use a custom pre-populated image data

A `.testenv.local` file at root folder is required to pull private images from Docker:

```js theme={"system"}
data_docker_registry=docker.io
data_docker_username=my_user
data_docker_password="my_password"
data_docker_email=my_email@domain.com
```

Change image of pre-populated data from [`deployments/k8s-yaml/data-postgres-prepopulated.yaml`](https://github.com/diadata-org/diadata/blob/74070895a72a0add703c8268e31870a7f63d3e4b/deployments/k8s-yaml/data-postgres-prepopulated.yaml#L20) file


# Development Cluster Stack
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/development-cluster-stack



### Data

* Influx

* PostgreSQL

* Redis

* Kafka

### Services

* Filterblock

* Tradesblock

### Scrapers

* Foreign

* Liquidity

* Collector

### Development Specific

* Ping jobs

* Prepare job (when install does not depend on external image)

### Additional

* Grafana

  * Loki

  * Influx

### Helms being tested

* DIA Helm chart: DIA platform

* Influx: Timeseries db

* Grafana: Dashboard for monitoring

* Loki: Logging the services

* [Jaeger Tracing](https://www.jaegertracing.io/): Tracing system for services

* kube-prometheus: Monitoring Minikube cluster


# DIA Test‐Space with Docker Compose
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/dia-test-space-with-docker-compose

Developing, Testing, and Building the DIA platform with Docker Compose

## Prepare

```js theme={"system"}
# Start data store services
(
  cd deployments/local/exchange-scraper
  docker compose -f docker-compose.yml up --build --force-recreate -d
)

# Define env variables needed
export USE_ENV=true
export INFLUXURL=http://localhost:8086
export INFLUXUSER=test
export INFLUXPASSWORD=testtest
export POSTGRES_USER=postgres
export POSTGRES_PASSWORD=password
export POSTGRES_HOST=localhost
export POSTGRES_DB=postgres
export REDISURL=localhost:6379

# Set config directory
export DIA_CONFIG_DIR=./config

# Set local directory as Go dependency
go mod edit -replace "github.com/diadata-org/diadata=$(pwd)" cmd/exchange-scrapers/collector/go.mod
```

## Scrapers

### CEX (Kraken as example)

#### Prepare

```js theme={"system"}
# Initialize the exchange and blockchain metadata
go run ./cmd/services/blockchainservice/main.go

# Prepare pairs metadata
go run ./cmd/services/pairDiscoveryService/main.go -exchange=Kraken -mode=verification
```

#### Run the scraper

```js theme={"system"}
go run ./cmd/exchange-scrapers/collector/collector.go -exchange=Kraken -mode=storeTrades
```

### DEX (CurveFi as example)

#### Prepare

```js theme={"system"}
# Set needed RPC variables
export ETHEREUM_URI_REST=https://rpc.ankr.com/eth
export ETHEREUM_URI_WS=wss://eth-mainnet.g.alchemy.com/v2/7X9hL_lpF-Utavuv1aT49SWkWu9oYZTq

# Prepare the assets metadata
go run ./cmd/assetCollectionService/main.go -source=assetlists -secret=eth_assets -caching=true
go run ./cmd/assetCollectionService/main.go -source=assetlists -secret=non_eth_assets -caching=true
go run ./cmd/assetCollectionService/main.go -source=assetlists -secret=fiat_assets -caching=true
go run ./cmd/assetCollectionService/main.go -source=Curvefi -caching=true

# Prepare and populate pools
go run ./cmd/liquidityScraper/main.go -exchange=Curvefi
```

#### Run the scraper

```js theme={"system"}
go run ./cmd/exchange-scrapers/collector/collector.go -exchange=Curvefi -mode=storeTrades
```

## Clean

```js theme={"system"}
unset USE_ENV
unset INFLUXURL
unset INFLUXUSER
unset INFLUXPASSWORD
unset POSTGRES_USER
unset POSTGRES_PASSWORD
unset POSTGRES_HOST
unset POSTGRES_DB
unset REDISURL
unset DIA_CONFIG_DIR
unset ETHEREUM_URI_REST
unset ETHEREUM_URI_WS
```

### Advanced usage

#### Access services between Docker Composes

On prepare step if you want to connect services between other Compose files, create a `deployments/local/exchange-scraper/docker-compose.override.yml` file:

```js theme={"system"}
version: "3.3"

services:
  influxdb:
    networks:
      - dia-bridge

networks:
  dia-bridge:
    driver: bridge
```

And instead of run the services using this command:

```js theme={"system"}
# Start data store services
(
  cd deployments/local/exchange-scraper
  docker compose -f docker-compose.yml -f docker-compose.override.yml up --build --force-recreate -d
)
```

Now in other Compose file just use like this:

```yaml theme={"system"}
version: "3"

networks:
  exchange-scraper_dia-bridge:
    external: true

services:
  service-x:
    image: service-x-image
    networks:
      - exchange-scraper_dia-bridge
```

Now in Docker context, `service-x` can resolve the `http://influxdb:8086` hostname


# DIA Test‐Space with Minikube
Source: https://www.diadata.org/docs/guides/general-guides/tutorials/dia-test-space-with-minikube

Developing, Testing, and Building the DIA platform with Minikube

## Preparing the local files

<Steps>
  <Step title="Clone repo and change directory">
    ```bash theme={"system"}
    git clone git@github.com:diadata-org/diadata.git
    cd diadata
    ```
  </Step>
</Steps>

## Preparing a local cluster

> Note: Minikube runs on a virtualization layer on the host. The [docker](https://minikube.sigs.k8s.io/docs/drivers/docker/) driver is usually the recommended and default option and should be seen as a requirement. For other supported drivers, please refer to [Minikube's official documentation](https://minikube.sigs.k8s.io/docs/drivers/). You can also check [Minikube's handbook](https://minikube.sigs.k8s.io/docs/handbook/) for advanced command usage.

<Steps>
  <Step>
    First, install dependencies: [Minikube](https://github.com/kubernetes/minikube#installation) and [Docker](https://www.docker.com/).
  </Step>

  <Step>
    Next, start the development environment by running the following command to start a Minikube node:

    ```bash theme={"system"}
    ./testenv.sh start
    ```
  </Step>

  <Step>
    Build the necessary service containers by executing the following commands:

    ```bash theme={"system"}
    ./testenv.sh build
    ```
  </Step>

  <Step>
    Run the installation script to set up the necessary services (Redis cache, Kafka streams, PostgreSQL, and InfluxDB databases) by executing the following commands:

    ```bash theme={"system"}
    ./testenv.sh install
    ```

    Now that you have the local cluster running, you are ready to start.
  </Step>

  <Step>
    Import the test data from the diadata snapshot service. This requires the default structure to be empty and created inside the postgres server. The script will automatically download the snapshot, install it and remove the downloaded snapshot again:

    ```bash theme={"system"}
    ./testenv.sh snapshot
    ```
  </Step>
</Steps>

## Other useful commands

To stop the cluster:

```bash theme={"system"}
./testenv.sh stop
```

To delete the cluster node:

```bash theme={"system"}
./testenv.sh delete
```


# Fetch Price Data
Source: https://www.diadata.org/docs/guides/how-to-guides/fetch-price-data

Learn how to fetch token price data from DIA's decentralized oracle network.

DIA offers multiple ways to access price data from oracles. The methods differ based on the oracle type (Push or Pull) and whether you're consuming the oracle through the Nexus or Lumina stack.

## Oracle Access Methods

<Note>
  The how-to guides are specifically for EVM-compatible chains. For non-EVM
  chains (like Stacks, Alephium, etc.), Please refer to the [chain-specific
  guides](/guides/chain-guides-overview) for chain-specific
  implementation details.
</Note>

<CardGroup>
  <Card title="updates Method" icon="upload" href="/guides/how-to-guides/fetch-price-data/push-based-oracles">
    Access Push-based oracles through the Lumina Stack that automatically update price feeds at fixed
    intervals or when price deviations exceed thresholds.
  </Card>

  <Card title="request Method" icon="download" href="/guides/how-to-guides/fetch-price-data/pull-based-oracles">
    Access Pull-based oracles through the Lumina Stack that fetch price data
    on-demand when your contract requests it.
  </Card>

  <Card title="getValue Method" icon="terminal" href="/guides/how-to-guides/fetch-price-data/solidity">
    Direct value retrieval using the standard DIA oracle interface through the Nexus Stack. Simple
    method for getting current price values.
  </Card>
</CardGroup>

## When to Use Each Method

The method to use depends on the deployed oracle contract you're planning to consume on each chain through the available stacks (Nexus or Lumina). We specify the methods available for each chain in their dedicated [chain-specific guide](/guides/chain-guides-overview).


# request Method
Source: https://www.diadata.org/docs/guides/how-to-guides/fetch-price-data/pull-based-oracles

[Pull (or also known as Request Based Oracle) oracle](/reference/architecture/data-delivery#pull-model) model enables the creation of requests for asset prices on a source blockchain. These requests are sent through a mailbox on the current chain and ultimately delivered to the DIA chain, which retrieves and delivers the required price data.

## How It Works

### Request Creation

A request is made from the source chain for an asset symbol whose price is required (e.g. ETH/USD) which then passes through the chain's mailbox to be then delivered to the destination chain. You can check the available contract address on testnet based on the destination chain you're reading from [here](/guides/chain-guides-overview).

The request body is formatted as follows in JavaScript:

```javascript theme={"system"}
const key = "ETH/USD"; // Assuming key is an address or a bytes32 value

const requestBody = abiCoder.encode(
  ["string"], // Types of the parameters
  [key] // Values to encode
);
```

And this is how it is formatted in Solidity:

```solidity theme={"system"}
bytes memory requestBody = abi.encode("WBTC/USD");
```

### Message Delivery Process

Once a request is created, it is transmitted to the Hyperlane mailbox. The message is then relayed to the `OracleRequestRecipient` contract , where the price data is fetched from the Oracle Metadata Contract.

### Response and Callback

Upon receiving the request, the DIA chain initiates a transaction to deliver the message back to the end contract on the source chain. The recipient contract on the source chain must implement the IMessageRecipient interface, which includes a handle function that will receive the price quotation.

## Making a Price Request

### Solidity

```solidity theme={"system"}
// SPDX-License-Identifier: MIT
pragma solidity 0.8.29;

import { RequestOracle } from "@dia-data/contracts-spectra/RequestOracle.sol";

contract PullOracleSample {
    address public constant DIA_RECIPIENT = 0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0; // DIA testnet
    uint32 public constant DESTINATION_DOMAIN = 100640; // DIA testnet chain id

    RequestOracle public diaOracle;
    string public key = "BTC/USD";

    constructor(address _requestOracle) {
        diaOracle = RequestOracle(payable(_requestOracle));
    }

    /*
    * To calculate the request fee on each chain, you can check the script below:
    * https://github.com/diadata-org/Spectra-interoperability/blob/main/contracts/scripts/sendTestMessage.mjs#L111
    */
    function requestPrice(string memory key) external payable {
        diaOracle.request{value: msg.value}(
            DIA_RECIPIENT,
            DESTINATION_DOMAIN,
            abi.encode(key)
        );
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

### JavaScript

In this example, we’ll be sending an ETH/USD price request from Base Sepolia to DIA Lasernet. Start by cloning the `Spectra Interoperability` repository to your local machine and switching to the `deploy`branch:

<Card title="GitHub - diadata-org/Spectra-interoperability" href="https://github.com/diadata-org/Spectra-interoperability" icon="github" />

```bash theme={"system"}
git clone https://github.com/diadata-org/Spectra-interoperability.git
git checkout deploy
```

Then install the node packages and compile the contracts using hardhat:

```bash theme={"system"}
npm install
npx hardhat compile
```

Next, `cd contracts` folder, and export your wallet's private key in your terminal as follows:

```javascript theme={"system"}
export PRIVATE_KEY=[paste_here]
```

Now, the `sendMessage.mjs` script will trigger a `request` transaction to fetch the latest price of ETH/USD from DIA lasernet. To run the script:

```bash theme={"system"}
npx hardhat run scripts/sendMessage.mjs --network base_sepolia
```

You can also run the script on other networks by changing the value passed to the `--network` flag (e.g. `--network sepolia`).

Once the price update takes place on the destination chain, which you can track from the [hyperlane explorer](/reference/cross-chain-messaging), you can check the txn logs for the `ReceivedMessage`event on the pull oracle contract or call the `updates`function.

<Frame>
  <img />
</Frame>

The price returned is around 2,718\$!


# updates Method
Source: https://www.diadata.org/docs/guides/how-to-guides/fetch-price-data/push-based-oracles

The [Push Oracle ](/reference/architecture/data-delivery#push-model)model enables contracts to receive real-time updates based on predefined criteria such as fixed intervals, specific price deviations, or a combination of both. This design provides flexibility and efficiency for decentralized applications needing accurate and timely data.

### Usage

The Oracle maintains updates as a mapping, where each key maps to a Data struct containing the latest timestamp and value.

The `updates` mapping is a key-value store where:

* Key: A unique identifier, typically a string, representing the asset or data type (e.g., DIA/USD, BTC/USD).
* Value: A Data struct containing:
  * key: The identifier of the data entry (redundant for reference but useful for integrity checks).
  * timestamp: The timestamp of the latest update.
  * value: The most recent value associated with the key.

Here's an example of a `DIAOracleSample` contract that consumes the `BTC/USD` price feed:

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { PushOracleReceiver } from "@dia-data/contracts-spectra/PushOracleReceiver.sol";

contract DIAOracleSample {

    PushOracleReceiver public diaOracle;
    string public key = "BTC/USD";

    constructor(address _oracle) {
        diaOracle = PushOracleReceiver(payable(_oracle));
    }

    function getPrice()
    external
    view
    returns (
        uint128 timestampOflatestPrice,
        uint128 latestPrice
    ) {
        (timestampOflatestPrice, latestPrice) =
                 diaOracle.updates(key);
    }
}
```

To deploy the contract, provide the oracle address for the destination chain you're reading from. You can find the contract addresses in the [chain-specific guides](/guides/chain-guides-overview).

As an example, if you want to access the oracle on Ethereum Sepolia, you'll pass the Push Oracle address: [0x9bb71344Ed950F9cFD85EE1C7258553B01d95FA0](https://sepolia.etherscan.io/address/0x9bb71344ed950f9cfd85ee1c7258553b01d95fa0) to the constructor above. You can also change the key to any of the supported assets (e.g. `DIA/USD`).


# getValue Method
Source: https://www.diadata.org/docs/guides/how-to-guides/fetch-price-data/solidity

There are two ways that you can access the oracle in your dApp. You can either declare an IDIAOracleV2 interface or import the solidity library.

## Using DIAOracleV2 Interface

The following is an example of how to retrieve price value from a standard DIA oracle. For the purpose of this example, we will be using the following demo oracle on Ethereum: [0xCD5F...f3cB](https://sepolia.etherscan.io/address/0xcd5f78206ca1ff96ff4c043c61a2299b2febf3cb).

<Steps>
  <Step>
    Access any DIA oracle smart contract.
  </Step>

  <Step>
    Call `getValue(pair_name)` with `pair_name` being the full pair name such as `BTC/USD`. You can use the "Read" section on Etherscan to execute this call.
  </Step>

  <Step>
    The response of the call contains four values:

    1. The current asset's price in USD with a fix-comma notation of 8 decimals.

    2. The [UNIX timestamp](https://www.unixtimestamp.com/) of the last oracle update.

    ```solidity theme={"system"}
    pragma solidity ^0.8.13;

    interface IDIAOracleV2 {
        function getValue(string memory) external view returns (uint128,
                 uint128);
    }

    contract DIAOracleSample {

        address diaOracle;

        constructor(address _oracle) {
            diaOracle = _oracle;
        }

        function getPrice(string memory key)
        external
        view
        returns (
            uint128 latestPrice,
            uint128 timestampOflatestPrice
        ) {
            (latestPrice, timestampOflatestPrice) =
                     IDIAOracleV2(diaOracle).getValue(key);
        }
    }
    ```
  </Step>
</Steps>

Find the detailed description of the functions and how to run tests on our GitHub page:

<Frame>
  <Card title="GitHub - diadata-org/DIA-integration-sample" href="https://github.com/diadata-org/DIA-integration-sample" icon="github" />
</Frame>

## Using Solidity Library

DIA has a dedicated Solidity library to facilitate the integration of DIA oracles in your own contracts. The library consists of two functions, `getPrice` and `getPriceIfNotOlderThan`.

### Access the library

```solidity theme={"system"}
import { DIAOracleLib } from "./libraries/DIAOracleLib.sol";
```

### Methods

#### getPrice

```solidity theme={"system"}
function getPrice(
        address oracle,
        string memory key
        )
        public
        view
        returns (uint128 latestPrice, uint128 timestampOflatestPrice);
```

Returns the price of a specified asset along with the update timestamp.

Parameters:

| Name   | Type    | Description                                  |
| ------ | ------- | -------------------------------------------- |
| oracle | address | Address of the oracle that we want to use    |
| key    | string  | The asset that we want to use e.g. "ETH/USD" |

Return Values:

| Name                   | Type    | Description                                            |
| ---------------------- | ------- | ------------------------------------------------------ |
| latestPrice            | uint128 | Price of the specified asset returned by the DIAOracle |
| timestampOflatestPrice | uint128 | The update timestamp of the latest price               |

#### getPriceIfNotOlderThan

```solidity theme={"system"}
function getPriceIfNotOlderThan(
        address oracle,
        string memory key,
        uint128 maxTimePassed
        )
        public
        view
        returns (uint128 price, bool inTime)
    {
```

Checks if the oracle price is older than `maxTimePassed`

Parameters:

| Name          | Type    | Description                                                                   |
| ------------- | ------- | ----------------------------------------------------------------------------- |
| oracle        | address | Address of the oracle that we want to use                                     |
| key           | string  | The asset that we want to use e.g. "ETH/USD"                                  |
| maxTimePassed | uint128 | The maximum acceptable time passed in seconds since the the price was updated |

Return Values:

| Name   | Type    | Description                                                                                            |
| ------ | ------- | ------------------------------------------------------------------------------------------------------ |
| price  | uint128 | Price of the specified asset returned by the DIAOracle                                                 |
| inTime | bool    | A boolian that is `true` if the price was updated at most maxTimePassed seconds ago, otherwise `false` |

Find a detailed integration example and how to run a test on our GitHub page:

<Card title="GitHub - diadata-org/DIAOracleLib" href="https://github.com/diadata-org/DIAOracleLib" icon="github" />

### Sample contract

```solidity theme={"system"}
pragma solidity ^0.8.13;

import { DIAOracleLib } from "./libraries/DIAOracleLib.sol";

contract DIAOracleSample {
    error PriceTooOld();

    address diaOracle;

    constructor(address _oracle) {
        diaOracle = _oracle;
    }

    function getPrice(
        string memory key
    ) external view returns (uint128 latestPrice) {
        (latestPrice, ) = DIAOracleLib.getPrice(diaOracle, key);
    }

    function checkPriceAge(
        string memory key,
        uint128 maxTimePassed
    ) external view returns (uint128 price) {
        bool inTime;
        (price, inTime) = DIAOracleLib.getPriceIfNotOlderThan(
            diaOracle,
            key,
            maxTimePassed
        );

        if (!inTime) revert PriceTooOld();
    }
}
```


# Fund your Oracle
Source: https://www.diadata.org/docs/guides/how-to-guides/fund-the-oracle

Oracles require a constant stream of updates, thus gas costs reimbursement for updates is needed. To achieve this, all oracles deployed by DIA have a dedicated wallet which calls oracle contracts for updates. This is referred to as the "gas wallet".

## How it works

Each oracle deployed by DIA has a gas wallet, which is the only entity capable of calling for an oracle update. The wallet initiates the transaction to import a new value into the oracle smart contract, based on the [data feed's update parameters](/guides/methodologies/data-processing/update-triggers) (that have been previously configured).

For the gas wallet to perform new oracle contract updates, it must have a sufficient balance of the blockchain's native token to cover the transaction's gas costs.

The gas wallet can be funded with a one-time lump sum, allowing it to keep updating for a while. However, monitoring the gas wallet's balance is necessary to ensure continuity in the oracle's operations.

DIA has set up internal gas wallet balance trackers. We recommend protocols to actively monitor them to ensure that the wallet balance remains sufficient for pushing new oracle updates.

## Estimate Updates Count for Oracles

DIA has a dedicated endpoint for asset historical updates count to help you estimate the number of oracle updates. This allows to foresee potential gas costs that would be required for running the oracle.

## Get historical Oracle updates count

`GET` `https://api.diadata.org/v1/assetUpdates/:blockchain/:address/:deviation/:updateFreq`

The endpoint returns information on the asset deviation and updates count if it was used in the oracle. It takes price change (deviation) and oracle's ticker frequency as the main parameters to determine estimated updates count based on historical data.

*Example:* [*https://api.diadata.org/v1/assetUpdates/Ethereum/0x0000000000000000000000000000000000000000/20/120*](https://api.diadata.org/v1/assetUpdates/Ethereum/0x0000000000000000000000000000000000000000/20/120)

By default it will return data for the last 24h but you can configure the timeframe with starttime and endtime parameters. See example below: [https://api.diadata.org/v1/assetUpdates/Ethereum/0x0000000000000000000000000000000000000000/20/120?starttime=1661736336\&endtime=1661761536](https://api.diadata.org/v1/assetUpdates/Ethereum/0x0000000000000000000000000000000000000000/20/120?starttime=1661736336\&endtime=1661761536)

#### Path Parameters

| Name         | Type    | Description                                                                                                   |
| ------------ | ------- | ------------------------------------------------------------------------------------------------------------- |
| blockchain\* | String  | A valid blockchain from GET /v1/blockchains, e.g., Bitcoin.                                                   |
| address\*    | String  | A valid asset address from GET /v1/token/:symbol, e.g., 0x000000000000000000000000000000000000000 for BTC.    |
| deviation\*  | Integer | Deviation measure in per mille, e.g. 20 will result in 2% deviation                                           |
| updateFreq\* | Integer | Oracle's price feed ticker frequency in seconds, e.g. 120 will calculate asset price in 2 minute trade blocks |
| starttime    | Integer | Unix timestamp setting the start of the return array                                                          |
| endtime      | Integer | Unix timestamp setting the end of the return array                                                            |


# Generate Randomness
Source: https://www.diadata.org/docs/guides/how-to-guides/generate-randomness

This guide shows you how to use the randomness oracle within your smart contract and get verifiable random numbers available to your dApp!

You can find deployed Randomness oracle contracts for each chain [here](/guides/chain-guides-overview). For EVM chains, follow the instructions in the Solidity guide:

<Card title="Solidity Guide" href="/guides/how-to-guides/generate-randomness/solidity" icon="chevron-right" />

## Learn more

<CardGroup>
  <Card title="Verifiable Randomness" href="/dia-stack/data-products/verifiable-randomness" icon="chevron-right" />

  <Card title="Distributed Randomness Beacon" href="/dia-stack/architecture/data-sources/randomness" icon="chevron-right" />
</CardGroup>


# Solidity
Source: https://www.diadata.org/docs/guides/how-to-guides/generate-randomness/solidity

DIA uses the drand.love public randomness beacon, and updates its oracle with round number, randomness and signature. Anyone can access published random values via round ID.

```json theme={"system"}
{
	"round": 1597683,
	"randomness": "24138936fcbf7fc3951c928158be6998cee3af622142d0790333608d17a5c5f6",
	"signature": "8c04905c0adf34f1fb007915d9ccc7d07b97305fc63952726f9367c87f36ab687c5e190c151f6ac4d760a9e009fc54230adb8513885449d649a229bc727be9ff347bdbce1c609cebf993b6ae57133fbcf23f96b15dbd3510cb5f2ade6b30b647",
	"previous_signature": "ada42197a2db89866da4c44348f77f7868e41e961ec32e636b912d43c625386afae9e54944ac573047dbd227ee495b52059586c8d8cd0edfe18cc15ca0666a66651da1d62b12af2d0fac19735bed9298690a593571965c3ad7c7b11947e76ec0"
}
```

The DIA randomness smart contract is structured as follows

```solidity theme={"system"}
pragma solidity ^0.8.0;

contract DIARandomOracle {

  struct Random {
    string randomness;
    string signature;
    string previousSignature;
  }

  mapping (uint256 => Random) public values;
  uint256 public lastRound = 0;

  address public oracleUpdater;

  event OracleUpdate(string key, uint128 value, uint128 timestamp);
  event UpdaterAddressChange(address newUpdater);

  constructor() {
    oracleUpdater = msg.sender;
  }

  function setRandomValue(uint256 _round, string memory _randomness, string memory _signature, string memory _previousSignature) public {
    require(msg.sender == oracleUpdater,"not a updater");
    require(lastRound<_round, "old round");
    lastRound = _round;
    values[_round] = Random(_randomness, _signature, _previousSignature);
  }

  function getValue(uint256 _round) external view returns (Random memory) {
    return values[_round];
  }

  function updateOracleUpdaterAddress(address newOracleUpdaterAddress) public {
    require(msg.sender == oracleUpdater,"not a updater");
    oracleUpdater = newOracleUpdaterAddress;
    emit UpdaterAddressChange(newOracleUpdaterAddress);
  }

  function getRandomValueFromRound(uint256 _round) external view returns (string memory) {
    return values[_round].randomness;
  }

  function getRandomValueFromRoundWithSignature(uint256 _round) external view returns (Random memory) {
    return values[_round];
  }

  function getLastRound() public view returns(uint256) {
    return lastRound;
  }
}
```

Users can call `getLastRound()`to obtain the ID of the latest published round. To obtain the randomness of a certain round, users can call `getRandomValueFromRound(uint256 _round)`using the obtaines round ID.

The signature can also be requested by calling `getRandomValueFromRoundWithSignature(uint256 _round)`.

Please be aware that you should always let all inputs commit before any randomness is used in a later round. For example, if you build a lottery, only call randomness after the last participant has committed their stake. To show this in an example, we will build a simple dice game.

<Frame>
  <iframe title="Overview of DIA xRandom #Randomness #Oracle | DIA Developer Tutorial" />
</Frame>

## Example: Dice Game

Imagine a simple game where two players play against each other. Both throw a dice and the user with the higher rolled number wins. In case of a draw, nobody wins. Both players need to "seed" the game with an initial number between 1 and 6, that will be added to the randomness (modulo 6). It is a fair game where everyone has a 50% chance of winning.

```solidity theme={"system"}
pragma solidity ^0.8.0;


import "../DIARandomOracle.sol";

contract DiceGame {
  address public randomOracle;
  uint256 seed1 = 0;
  uint256 seed2 = 0;
  uint256 latestRoundId = 0;

  constructor(address oracle) {
    randomOracle = oracle;
  }

  function getRandomValue(uint256 _round) public view returns (string memory) {
    return DIARandomOracle(randomOracle).getRandomValueFromRound(_round);
  }

  function commitPlayer1(uint256 seed) external {
    require(seed > 0, "Seed must be between 1 and 6");
    require(seed < 7, "Seed must be between 1 and 6");

    seed1 = seed;
    latestRoundId = DIARandomOracle(randomOracle).getLastRound();
  }

  function commitPlayer2(uint256 seed) external {
    require(seed > 0, "Seed must be between 1 and 6");
    require(seed < 7, "Seed must be between 1 and 6");

    seed2 = seed;
    latestRoundId = DIARandomOracle(randomOracle).getLastRound();
  }

  function rollDice() public view returns (uint) {
    require(seed1 > 0, "Player 1 needs to commit their seed!");
    require(seed2 > 0, "Player 2 needs to commit their seed!");

    uint _round = latestRoundId + 10;

    require(DIARandomOracle(randomOracle).getLastRound() >= _round, "Wait for the randmoness round to roll your dice.");

    string memory rand = getRandomValue(_round);
    uint256 player1result = (uint256(keccak256(abi.encodePacked(rand))) + seed1) % 6;
    uint256 player2result = (uint256(keccak256(abi.encodePacked(rand))) + seed2) % 6;

    seed1 = 0;
    seed2 = 0;

    if (player1result > player2result) {
      return 1;
    } else if (player2result > player1result) {
      return 2;
    } else {
      return 0;
    }
  }
}
```

Both players need to commit their seeds. The latest published roundID is stored for the duration of the game. When both committed their values and the wait time of 10 rounds has passed, the dice can be rolled and the player ID of the winner is returned (or 0 in case of a draw).

<Info>
  Make sure to never directly query the latest randomness value, otherwise the miner and the randomness oracle can interfere with the result. Always commit values before the randomness is used in a later round.
</Info>


# Migrate from Chainlink
Source: https://www.diadata.org/docs/guides/how-to-guides/migrate-to-dia

The `DiaAssetSpecificCallingConvention` contract is compatible with `AggregatorV3Interface`, allowing developers to read price data from a DIA oracle contract deployed for each asset by calling `latestRoundData()` and returning the latest available price of that specific asset.

<Card title="Chainlink Adapter" href="https://github.com/diadata-org/AssetSpecificCallingConvention/blob/main/contracts/DiaAssetSpecificCallingConvention.sol" icon="github" />


# Request a Custom Oracle
Source: https://www.diadata.org/docs/guides/how-to-guides/request-a-custom-oracle

DIA offers highly customizable oracles that are individually tailored to each dApp’s needs. Each oracle can be customized in several ways, ensuring that the data and oracle remain robust and resilient to market volatily.

Get in touch with us:

<CardGroup>
  <Card title="Integrations team" icon="telegram" href="https://t.me/DIAOracles_Support_Bot">
    For a consultation with the DIA team, get in touch via Telegram. The team will gather the requirements and create a solution proposal for you.

    [Contact Us](https://t.me/DIABDteam)
  </Card>

  <Card title="Forum request" icon="file-lines" href="https://forum.diadata.org/">
    If you already have a specific implementation in mind, you can directly and autonomously submit a request via the DIA Forum.

    [Submit a CDR](https://forum.diadata.org/)
  </Card>
</CardGroup>


# Methodologies
Source: https://www.diadata.org/docs/guides/methodologies-overview

Learn how DIA processes data and applies pricing methodologies for delivering reliable oracle feeds.

## Data Processing

<CardGroup>
  <Card title="Trades Collection" href="/guides/methodologies/data-processing/trades-collection" icon="chart-line" />

  <Card title="Price Aggregation" href="/guides/methodologies/data-processing/price-aggregation" icon="layer-group" />

  <Card title="Update Triggers" href="/guides/methodologies/data-processing/update-triggers" icon="rotate" />
</CardGroup>

## Pricing Methodologies

<CardGroup>
  <Card title="IR - Interquartile Range Filter" href="/guides/methodologies/pricing-methodologies/ir-interquartile-range-filter" icon="angle-right" />

  <Card title="MAIR - Moving Average with Interquartile Range" href="/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter" icon="angle-right" />

  <Card title="VWAP - Volume Weighted Average Price" href="/guides/methodologies/pricing-methodologies/vwap-volume-weighted-average-price" icon="angle-right" />

  <Card title="VWAPIR - Volume Weighted Average Price with Interquartile Range" href="/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter" icon="angle-right" />

  <Card title="LSD Fair Price" href="/guides/methodologies/pricing-methodologies/lst-fair-price" icon="angle-right" />
</CardGroup>


# Price Aggregation
Source: https://www.diadata.org/docs/guides/methodologies/data-processing/price-aggregation

With all [aggregated data from multiple sources](trades-collection), DIA performs many layers of processing to build high-quality feeds resilient to bad actors. All steps can be customized with tailor-made methodologies to best serve each use case.

## Step 1: Data cleaning and outlier detection

The price estimation process needs to be resilient against trades with prices diverting from the current market price. Reasons for diverting trades can be market manipulation, errors or flash crashes on certain exchanges, among others.

To avoid these irregularities, the first processing step involves data cleaning and outliers removal, to avoid building a feed using data that is completely away from the median. Detecting and excluding outliers is an important processing task, especially in low-volume and illiquid markets. Otherwise, a single low-volume trade can offset the price estimation and serve as a base token for other assets, leading to a chain reaction of misaligned price data.

How does this look in practice? By applying an Interquartile Range (IR) filter, DIA excludes data points and entire sets that lie outside of an acceptable range relative to the interquartile range. The filter analyses all trades of a predefined time range and sorts them by their recorded price. After that, this range of prices is divided into four price blocks, the quartiles. The boundaries of the full price range determine the boundaries of the first and the last quartile. To clear out outliers, any trades falling into the first or the last quartile are filtered out and subsequently, only trades falling into the "middle" quartiles move forward into further processing.

<CardGroup>
  <Card title="Learn more about outliers and market manipulation" href="/guides/methodologies/pricing-methodologies/ir-interquartile-range-filter" icon="angle-right" />
</CardGroup>

## Step 2: Price determination methodology application

Now that we understand how the process of clearing diverting trade data works, how is the final price actually calculated from all remaining data points? To retrieve a single USD price value for every asset, DIA uses trade-based price determination methodologies. These filters are functions to get a single price point from a collection of trades in a block.

Filters are calculated for each asset on each exchange individually, as well as for each asset on all exchanges combined. This combined filter result represents the result closest to the true "whole market" that can be determined by this system. As each use case requires different data needs, DIA can provide multiple filters to best serve the requirements of each application.

Let’s look at a couple of examples:

* **Volume Weighted Average Price (VWAP):** is a methodology for trade-based price determination that takes into account the different volumes of trades. All trades from the queried time range are collected and weighted by their volume. Weighting means that the (normalized) volume of the trade is multiplied by its executed price. This is done by accumulating the previously calculated volume-price-products of all trades and dividing them by the sum of all volumes combined.
* **Moving Average with Interquartile Range Filter (MAIR):** in this case, all the trades collected in the queried time range are ordered by timestamp. For each second in this time range, a block is created where trades are put into. As soon as the collection of all trades for each block is finalized, then it's weighted against the volume for each data point and the weighted average price is taken to arrive at the final price

<CardGroup>
  <Card title="See all pricing methodologies" href="/guides/methodologies-overview" icon="angle-right" />
</CardGroup>

Additionally, DIA can always implement new on-demand methodologies as well as build new methodologies together with users.


# Trades Collection
Source: https://www.diadata.org/docs/guides/methodologies/data-processing/trades-collection



## Granular trade data sourcing

By leveraging a network of WebSockets and decentralized node providers, DIA Nexus retrieves token trade ticks and metadata from exchanges. This, in turn, represents an enormous data availability (≈15bn trades/day) to, later on, enable DIA to capture the highest data precision and build flexible and customizable price feeds.

Trades for every asset pair get recorded and collected into blocks of 120 seconds into the DIA Nexus platform. For each block, a range of filters are applied. These are functions to get a single price point from the collection of trades in a block. For example, the Moving Average filter returns the volume-weighted moving average of the trades block.

Filters are calculated for each asset pair on each exchange individually, as well as for each asset on all exchanges combined. This combined filter result represents the result closest to the true "whole market" that can be determined by this system. Learn more about [token filters here](/guides/methodologies-overview).

## Type of data sources and their aggregation

DIA Nexus retrieves trading data from as close to the data source as possible in order to ensure the highest precision possible. The data retrieval is processed through a series of asset collectors:

* For **centralised exchanges** such as Coinbase, Kraken or Binance, DIA scrapers collect trades directly from the exchange's databases. The data collection happens in retrieval periods from 1 to 7 seconds and varies from exchange to exchange. All trading data is retrieved through Rest APIs or WebSocket APIs, developed and maintained by the respective trading platform. More on [CEX trade data collection](/dia-stack/architecture/data-sources/cexes-data).
* For **decentralised exchanges**, DIA collects data from decentralized exchanges on various blockchains by subscribing to swap events in the corresponding liquidity pools – LPs. In contrast to centralized exchanges, in decentralized exchanges, it is possible to retrieve trading data directly from the respective blockchain by subscribing to the corresponding pool events. Examples of sources are Uniswap, curve.finance or PancakeSwap. [More on DEX trade data collection](/dia-stack/architecture/data-sources/dexes-data).

## On oracle feed manipulation and risk

One of the biggest risks for DeFi and Web3 applications is not having enough sources for its oracle and using a feed that relies on one single market. These single-source oracles, as explained in the beginning, are relatively easily exposed to price manipulations and man-in-the-middle attacks.

DIA is designed to avoid these scenarios by leveraging multiple markets as sources, including CEXs and DEXs and enabling the customisation of methodologies and sources to cater best for the needs of specific use cases. So far in DeFi’s (short) history, a failure in the oracle node network has never been the reason for a loss of funds, but attacks on the markets that provide the price data to the sources. Take for instance the example of the Cream Finance attack in October 2021.

DIA prioritises the transparency aspect of its data and oracle services and enables any dApp developer and user to know precisely how the data feeding the application is built, what data sources are been used, and what methodologies are been applied.


# Update Triggers
Source: https://www.diadata.org/docs/guides/methodologies/data-processing/update-triggers

The price feed is created and published via an API endpoint, utilizing the previously [selected data sources](trades-collection) and [computational methodologies](price-aggregation).

This feed can be accessed off-chain using either RestAPI or DIA GraphQL, which allows for greater adaptability and direct modification of feed attributes.

Off-chain **and on-chain delivery methods can be configured with custom** ***update triggers***, enhancing the feed's usability and reliability across various applications.

## Update triggers

Update triggers are the rules that dictate how oracles refresh to mirror the most recent value of the data feed. These triggers are adaptable and can be tailored to optimally cater to particular scenarios, such as the price feeds of assets with low liquidity.

Each oracle can be customized to push data feed updates live based on the following parameters:

| Trigger                     | Description                                                                    | Example                   |
| --------------------------- | ------------------------------------------------------------------------------ | ------------------------- |
| **Time-based (push)**       | Updates are triggered in predefined time intervals (seconds, minutes or hours) | *15 minutes*              |
| **Deviation-based (push)**  | Updates are triggered by a deviation from the last reported value.             | *5% deviation*            |
| **Time + deviation (push)** | The oracle will update whenever any of the two conditions is met.              | *5% deviation + 24h time* |


# IR: Interquartile Range Filter
Source: https://www.diadata.org/docs/guides/methodologies/pricing-methodologies/ir-interquartile-range-filter

This section describes how we filter for outliers in ourprice determination system.

## Outliers and Market Manipulation

The price estimation process needs to be robust against trades with prices that are diverting from the current market price of an asset pair. Reasons for diverting trades can be market manipulation, errors, flash crashes on certain exchanges, or other market irregularities.

Detecting and excluding outliers and market manipulation is an important data processing task, especially in small and (somewhat) intransparent markets. Otherwise, a single low-volume trade can offset the price estimation and serve as a base token for other assets, leading to a chain reaction of misaligned price data.

We calculate our cryptocurrency spot-prices using 120-second moving average (SMA) with a weighting of trade volumes (VWAP). Small volume trades have a proportionally smaller influence on the determined price than bigger volume trades. In order to create reliable pricing, we also exclude data points and sets entirely that lie outside of an [acceptable range](https://en.wikipedia.org/wiki/Interquartile_range#Outliers) relative to the [interquartile range](https://en.wikipedia.org/wiki/Interquartile_range) of all data points.

### Data Preprocessing

The Interquartile Range filter in DIA examined all trades in a trades block (i.e. all trades in the predefined time range) and sorts them by their recorded price.

After that, this range of prices is divided into four price blocks, the *Quartiles*. The boundaries of the full price range also determine the boundaries of the first and the last quartile.

To clear out outliers, any trades falling into the first or the last quartile are filtered out and subsequently, only trades falling into the "middle" quartiles are returned to the caller.

### Advanced Filtering

After this clearing process is finished, the data is ready to be processed further in other filters like the [Moving Average](/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter) or [Volume Weighted Average Price](/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter) filter.


# LST Fair Price
Source: https://www.diadata.org/docs/guides/methodologies/pricing-methodologies/lst-fair-price



The usual structure for calculating fair price of Liquid Staked Tokens (LST) is as follows:

$$
LST_{fairprice} = BaseAssetPrice \times (LockedBaseAsset / IssuedLST)
$$

The main components of the formula are:

1. *BaseAssetPrice* - price of the non-staked asset which is locked against LST (e.g. for stETH, ETH acts as a base asset)

2. *LockedBaseAsset* - number of base assets locked in the LST smart contract (e.g. for stETH, quantity of ETH locked in stETH smart contract)

3. *IssuedLST* - amount of LST tokens issued (e.g. for stETH, total supply of stETH represents it)

This is the standard methodology and the data is queried directly from the Smart Contract of the LST issuer. It allows sudden devaluation in case malicious actor manages to mint a large amount of LST tokens and ensures that the issuer is keeping the funds safe.

Depending on the contract type we apply the following logic for valuation:

* If the assets can be redeemed 1:1 (e.g. stETH), price will always be the same as the base asset, even though the collateralization rate is higher (if collateralization ratio is lower, the price will be adjusted to negative side)

* If the LST asset increases in value against the base asset because rewards are not paid out directly but rather represent a share of the total pool, the pricing will be dynamic depending on the reewards accrued in the pool (e.g. rETH)

These are the standard methodologies applied to the feeds but some assets might require custom methodologies.


# MAIR: Moving Average with Interquartile Range Filter
Source: https://www.diadata.org/docs/guides/methodologies/pricing-methodologies/mair-moving-average-with-interquartile-range-filter



The MAIR (Moving Average with Interquartile Range Clearing) filter is the application of the Moving Average filter to data that was previously cleared by the [Interquartile Range](/guides/methodologies/pricing-methodologies/ir-interquartile-range-filter) filtering system.

## Trade Collection

All trades from the queried time range are ordered by timestamp.

For each second in the time range, there exists a "slot" where trades are put into.

## Price Calculation

As soon as all trades in the block have been finalized (usually 120 seconds per block), for each 1 second slot the closing price is taken.

These slots are then weighted against the volume for each data point and the weighted average price is taken to arrive at the final price.

The result is then returned as the result of the filter operation.

## Filter Application

The MAIR filter is used in DIA's price determination. Our price quotations are the latest MAIR-120 filter values, i.e., the filter results from a 120 second interval of all recorded trades for an asset.

## Implementation

The filter is implemented as part of the FiltersBlockService [in this file in our Github repository](https://github.com/diadata-org/diadata/blob/master/internal/pkg/filtersBlockService/FilterMA.go).


# VWAP: Volume Weighted Average Price
Source: https://www.diadata.org/docs/guides/methodologies/pricing-methodologies/vwap-volume-weighted-average-price

This page contains information about the VWAP pricing methodology.

VWAP (Volume Weighted Average Price) is a methodology for trade-based price determination that takes into account the different volumes of trades.

## Trade Collection

All trades from the queried time range are collected and weighted by their volume. Weighting means that the (normalized) volume of the trade is multiplied by its executed price.

## Price Calculation

As soon as the block has been finalized, the VWAP price of these prices is calculated. This is done by accumulating the previously calculated volume-price-products of all trades and dividing them by the sum of all volumes combined.

The result is then returned as the result of the filter operation.

## Filter Application

The VWAP filter is used in DIA's price determination. Our API can display the latest VWAP filter values, i.e., the filter results from a 120 second interval of all recorded trades for an asset.

## Implementation

The filter is implemented as part of the FiltersBlockService in [this file in our Github repository](https://github.com/diadata-org/diadata/blob/master/internal/pkg/filtersBlockService/FilterVWAP.go).


# VWAPIR: Volume Weighted Average Price with Interquartile Range Filter
Source: https://www.diadata.org/docs/guides/methodologies/pricing-methodologies/vwapir-volume-weighted-average-price-with-interquartile-range-filter

This page contains information about the VWAPIR pricing methodology.

The VWAPIR (Volume Weighted Average Price with Interquartile Range Clearing) filter is the application of the [Volume Weighted Average Price](/guides/methodologies/pricing-methodologies/vwap-volume-weighted-average-price) filter to data that was previously cleared by the [Interquartile Range](/guides/methodologies/pricing-methodologies/ir-interquartile-range-filter) filtering system.

## Filter Application

The VWAPIR filter is used in DIA's price determination. Our API can display the latest MEDIR-120 filter values, i.e., the filter results from a 120 second interval of all recorded trades for an asset.

## Implementation

The filter is implemented as part of the FiltersBlockService in [this file in our Github repository](https://github.com/diadata-org/diadata/blob/master/internal/pkg/filtersBlockService/FilterVWAPIR.go).


# Oracle Grants
Source: https://www.diadata.org/docs/guides/oracle-grants

A grant initiative designed to accelerate dApp development across blockchains by covering oracle gas fees for builders.

<CardGroup>
  <Card title="Zero-cost oracle access" icon="gift">
    Developers get subsidies for DIA oracle usage up to 1 year, covering
    deployment and update costs. Removes costs so dApps can go live.
  </Card>

  <Card title="Builders ship – Chains thrive" icon="rocket">
    Chains attract more builders and TVL by eliminating oracle costs. DIA
    oracles gain adoption across more ecosystems.
  </Card>
</CardGroup>

## Who is eligible?

Any developer building an oracle-dependent dApp on any of the chains participating in the grant.

<Card title="DIA Oracle Grants Program | Apply Now" href="https://www.diadata.org/blockchain-oracle-grant/" />


# Quickstart
Source: https://www.diadata.org/docs/guides/quickstart



These integration guides provide everything you need to start integrating DIA oracles into your dApp. You can also explore the methodologies we use, and other general guides such as running a feeder node. Here's what you'll find:

<CardGroup>
  <Card title="How-to Guides" icon="wrench" href="/guides/how-to-guides/fetch-price-data">
    Learn how to fetch price data, generate randomness, fund oracles, and migrate
    from other providers.
  </Card>

  <Card title="Chain-Specific Guides" icon="link" href="/guides/chain-guides-overview">
    Step-by-step instructions for each supported blockchain, including contract
    addresses, oracle configurations, and code examples in Solidity and other
    languages.
  </Card>

  <Card title="Methodologies" icon="book" href="/guides/methodologies-overview">
    Explore pricing methodologies (MAIR, VWAPIR, etc.), data sourcing process, &
    update triggers.
  </Card>

  <Card title="General Guides" icon="book-open" href="/guides/general-guides/smart-contracts/diaoraclev2.sol">
    Access smart contracts, learn how to run a feeder, build custom scrapers, & how DIA staking works.
  </Card>
</CardGroup>

### Oracle Grants Program

Get **zero-cost oracle access** for up to 1 year across all supported chains. Learn more about the program below:

<Card title="Apply for DIA Oracle Grants" href="/guides/oracle-grants" icon="angle-right" />

### Getting Started

Choose your blockchain from the [list of supported networks](/guides/chain-guides-overview), or explore our [how-to guides](/guides/how-to-guides/fetch-price-data) to understand DIA's oracles integration process.


# Audits
Source: https://www.diadata.org/docs/guides/resources/audits



## Lumina Stack Audits

### Spectra Cross-chain Messaging Layer

<Card title="DIA Multi Scope Security Audit Report.pdf | MixBytes" href="https://github.com/mixbytes/audits_public/blob/master/DIA/Multi%20Scope/DIA%20Multi%20Scope%20Security%20Audit%20Report.pdf" icon="file-pdf" />

### Lumina Staking

<Card title="DIA Lumina Staking Security Audit Report.pdf | MixBytes" href="https://github.com/mixbytes/audits_public/blob/master/DIA/Lumina%20Staking/DIA%20Lumina%20Staking%20Security%20Audit%20Report.pdf" icon="file-pdf" />

## Nexus Stack Audits

### DIAOracleV2 contract

<Card title="02_Smart Contract Audit_DIA_Oracle_v2.pdf | Chainsulting" href="https://content.gitbook.com/content/7BgHS2yasVJB3IUNwbdE/blobs/IB3aeLtX0zoB7evp6Fi4/02_Smart%20Contract%20Audit_DIA_Oracle_v2.pdf" icon="file-pdf" />


# Community & Support
Source: https://www.diadata.org/docs/guides/resources/community-and-support



You can connect with us and find support through the following channels:

<CardGroup>
  <Card title="Forum" href="https://forum.diadata.org/" icon="file-lines" />

  <Card title="Twitter/X" href="https://x.com/DIAdata_org" icon="x-twitter" />

  <Card title="Discord" href="https://discord.com/invite/ZvGjVY5uvs" icon="discord" />

  <Card title="Github" href="https://github.com/diadata-org/" icon="github" />
</CardGroup>


# Research
Source: https://www.diadata.org/docs/guides/resources/research

This section represents DIAs research efforts aimed at providing genuine data for the users.

Here are some examples of our work:

<CardGroup>
  <Card title="Return Rates in Crypto Farming" href="/resources/research/return-rates-in-crypto-farming" icon="chart-line" />

  <Card title="Crypto Volatility Index" href="/resources/research/cvi" icon="chart-line" />
</CardGroup>

<Check>
  DIA research is dedicated for expanding the oracles ecosystem with novel
  solutions. Treat these as indicative of our work and feel free to contact us
  if you'd like to develop something new & exciting!
</Check>


# Compounded Rates
Source: https://www.diadata.org/docs/guides/resources/research/compounded-rates

In order to reduce the impact of outliers in daily fluctuations of financial markets, many financial products use simple or compounded averages of a given reference rate. For instance, on every business day the New York Federal Reserve Bank publishes the average rate of the Secured Overnight Financing Rate, compounded over the last 30 calendar days under the name of SOFR30.

## Standard Methodology

Here, we present the methodology of compounded rates that is used by large banks such as the New York Federal Reserve Bank (compounded SOFR) and the Bank of England (compounded SONIA).

Consider a unit investment over a time period of $dc$ calendar days containing $db \leq dc$ business days. Let $r_i$ be an interest rate that is published once every business day and assume that the business day convention is such that the year has $N$ days. Then, the compounded gain $G$ over the whole interest period results to

$$
G = \prod_{i=1}^{d_i} \left( 1 + \frac{r_i \times n_i}{N} \right).
$$

We remark that for constant interest rates $r_i = r$ and $n_i = 1$ this simplifies to the well-known compounded gain formula $G = (1 + \frac{r}{N})^{d_b}$. However, in general, the rate factor $n_i$ is an integer value that accounts for $i$ being a business day or a non-business day. More precisely, if $i$ is a business day followed by $k$ non-business days, we set $n_i = k + 1$. For instance, if $i$ is followed by a business day, i.e., $k = 0$, we have $n_i = 1$. For a friday, which is usually followed by two non-business days, we would have $n_i = 3$. Now, in order to get the average interest $I$ from the compounded gain $G$, we subtract the original investment and normalize, thus obtaining

$$
I = \frac{N}{d_c} \left[ \prod_{i=1}^{d_s} \left( 1 + \frac{r_i \times n_i}{N} \right) - 1 \right]
$$

which is the formulation of compounded rates used by the FED and the BOE amongst others.

Sources: [https://www.newyorkfed.org/medialibrary/Microsites/arrc/files/2019/Users\_Guide\_to\_SOFR.pdf](https://www.newyorkfed.org/medialibrary/Microsites/arrc/files/2019/Users_Guide_to_SOFR.pdf)

[https://www.bankofengland.co.uk/paper/2020/supporting-risk-free-rate-transition-through-the-provision-of-compounded-sonia](https://www.bankofengland.co.uk/paper/2020/supporting-risk-free-rate-transition-through-the-provision-of-compounded-sonia)

## DIA Methodology

The methodology from the previous section has a special feature in that it mixes compounded and non-compounded rates. More precisely, investments are not compounded for weekends and holidays. This behaviour is reflected in the rate factor $n_i$. In the Index IDIA​ presented below, investments are compounded over all calendar days in the respective interest period.

Consider a unit investment over a time period of $d_c$ calendar days. Let $r_i$ be an interest rate that is published once every business day and assume that the business day convention is such that the year has $N$ days. We define an interest rate $r_i$ such that $r_i$ coincides with $r_i$ on business days and is set to the rate of the previous business day if $i$ is a holiday or a weekend. In this straightforward manner we obtain an interest rate for all *calendar days* and can now set

$$
I_{DIA} = \frac{N}{d_c} \left[ \prod_{j=1}^{d_c} \left( 1 + \frac{r_j}{N} \right) - 1 \right].
$$

Link to API documentation: Coming soon!


# Crypto Volatility Index
Source: https://www.diadata.org/docs/guides/resources/research/cvi

The CVI is calculated on top of bid/ask information received from crypto (BTC) option markets. First of all, the current level of the orderbook is recorded and placed into a timestamped order. Instruments for each strike price are monitored, both for Call and Put options.

Instruments are named uniquely to identify them. For example, BTC-03JUN2020-6000-C is the name of a Bitcoin call option expiring at 3rd of June 2020 for a strike price of 6000 USD.

To calculate the CVI, the option levels of two dates are considered: The next Friday that is at least one month away from now and the first Friday with available options before that date. With that we ensure that the future market is observed appropriately.

<Info>
  Options typically expire on Fridays only, thus we can only observe them for these dates.
</Info>

The CVI is then calculated using this formula:

$$
x = 100 \cdot \sqrt{
\left\{
T_1 \sigma_1^2 \left( \frac{N_{T_2} - N_{30}}{N_{T_2} - N_{T_1}} \right)
+ T_2 \sigma_2^2 \left( \frac{N_{30} - N_{T_1}}{N_{T_2} - N_{T_1}} \right)
\right\}
\cdot \frac{N_{365}}{N_{30}}
}
$$

where N describe the minutes until the respective event (e.g. minutes in a year, 30 days or minutes until expiry of option T1). T1 and T2 are the fractions of minutes left until expiry of these options compared to the minutes in a full year.

The variances are calculated as such:

$$
\sigma^2 = \frac{2}{T} \sum_{i} \frac{\Delta K_i}{K_i^2} e^{RT} Q(K_i)
$$

with the sum of deltas being defined as the intervals between strike prices for each strike price. R is the risk-free lending rate and Q(k) is used to describe the average of the bid-ask-spread for an option K\_i.

The CVI starts at a value of 1000.


# Polkadot Medianizer
Source: https://www.diadata.org/docs/guides/resources/research/polkadot-medianizer

This example demonstrates the functionality of the Laminar chain's oracle pallet including the aggregation of price values.

## Laminar Chain

The Laminar chain is built using the [Substrate framework](https://substrate.dev). In our example we are going to setup a network consisting if two nodes, one is operated by Alice and one is operated by Bob.

### Setup

First we download the Laminar chain [sources](https://github.com/laminar-protocol/laminar-chain) and bootstrap the network. After that we execute the following statements in the chain's directory.

```bash theme={"system"}
example$ git clone https://github.com/laminar-protocol/laminar-chain.git
example$ cd laminar-chain
example/laminar-chain$ make init
example/laminar-chain$ make build
```

`make init` will setup the environment by downloading and installing all necessary dependencies and the required toolchain.

`make build` builds the chain's code so we can execute it.

After that copy the `chainSpec.json` file from this repository into the chain's directory. More on the spec file will be explained a little bit later.

### Cleanup

When running a node being part of the laminar chain network it creates and stores lots of data because it's constantly building new blocks and extending the actual blockchain. We are going to store all that data in a subdirectory of `/tmp` for each node (its base directory). If the base directory doesn't exist it will be created but it is necessary to purge all data of a specific node on subsequent launches:

```bash theme={"system"}
example/laminar-chain$ SKIP_WASM_BUILD= cargo run -- purge-chain --base-path /tmp/alice
```

This wipes the base directory of Alice's node. For wiping Bob's node's data adjust the base-path parameter accordingly. The action asks for confirmation which is given by answering with `y`.

**Bootstrap the network**

We are going to launch Alice's node first:

```
example/laminar-chain$ SKIP_WASM_BUILD= cargo run -- --base-path /tmp/alice --chain=chainSpec.json --alice --port 30333 --ws-port 9945 --rpc-port 9933
```

* This creates and runs a node that stores its data in the specified base directory.

* We also pass the chain specification file into the node. We use this file to configure the scenario in which all participating parties will own a sufficient amount of gas in order to be able to "pay" for their transmitted transactions.

* The parameter `--alice` will make Alice the node's authority uses her predefined key pair.

* We specify three ports: One for the other peers to connect to the node, a websocket port for the off-chain worker to connect to and a port for incoming RPCs.

After that we fire up Bob's node and tell it to connect to Alice. So in another terminal session we are executing

```bash theme={"system"}
example/laminar-chain$ SKIP_WASM_BUILD= cargo run -- --base-path /tmp/bob --chain=chainSpec.json --bob --port 30334 --ws-port 9946 --rpc-port 9934 --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp
```

The main difference is the `bootnodes` parameter which specifies the network and identity information of Alice's node.

### Use the Laminar chain's oracle

Now the two nodes start working together and our laminar chain network is ready for playing with the oracle.

**About oracles**

A blockchain oracle is an interface for the chain to the real world and vice versa. By feeding off-chain data to the oracle they enter the chain's scope and can get processed by smart contracts. In this case our oracle is called an **inbound oracle**. For our example imagine a smart contract that operates on currency prices. It might trigger an action as soon as the price for a specific currency exceeds a specific value. By feeding the current prices from external sources periodically to the oracle we provide the smart contract with the required input data on-chain.

**Oracle pallet**

A Substrate chain's runtime consists of modules called pallets. In the case of Laminar one of these pallets is our [oracle](https://github.com/open-web3-stack/open-runtime-module-library/tree/master/oracle). It can be interacted with in two ways:

1. Feeding new key-value pairs to the oracle via signed transactions.

2. Retrieving key-value pairs from the oracle either by other modules on-chain or by off-chain workers via RPC.

The Laminar implementation configures the oracle pallet to use the type `CurrencyId` as key type. That means it can be one of the predefined values *FBTC*, *FETH*, *FEUR*, etc. The value uses the type `Price`.

In this example we are going to use an off-chain worker to feed currency prices and fetch them afterwards.

**Our off-chain worker**

The component we create to simulate new price reports and oracle queries lives off-chain and will be written in Typescript. It is completely separate from anything stored on the Laminar chain itself. We rather interact with the chain through specific calls made using the [Polkadot API for JavaScript](https://polkadot.js.org/docs/api). This API defines the technical aspects of how we can interact with the chain (and specifically with the oracle), i. e. how to build transactions and make RPCs. For the specific parameters regarding the Laminar chain we also make use of the [Laminar chain JS SDK](https://github.com/laminar-protocol/laminar-chain.js).

Let's start by switching the directory

```bash theme={"system"}
example/laminar-chain$ cd ..
example$ mkdir medianizer
example/medianizer$ touch package.json
```

and setting up the dependencies in the `package.json` file:

```json theme={"system"}
{
  "name": "medianizer-example",
  "version": "0.1.0",
  "description": "",
  "main": "index.ts",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1",
    "start": "node --require ts-node/register index.ts"
  },
  "dependencies": {
    "@laminar/api": "^0.2.0-beta.144",
    "@polkadot/api": "^3.8.1"
  },
  "devDependencies": {
    "ts-node": "^9.1.1",
    "typescript": "^4.1.5"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}
```

Next step is coding the off-chain worker in the file `index.ts`. We import the required types

```ts theme={"system"}
import { ApiPromise, WsProvider, Keyring } from "@polkadot/api";
import { options } from "@laminar/api";
```

and build the frame for the program:

```ts theme={"system"}
const run = async () => {
  // Everything is going to happen here in this block ...
};

export default run;

if (require.main === module) {
    run().then(() => process.exit(0))
}
```

Now we can run

```bash theme={"system"}
example/medianizer$ yarn install
example/medianizer$ yarn start
```

for fetching the dependencies and launching the program. However nothing is going on right now so let's write the actual code. From now on we put everything into the async block that we just prepared.

We start creating an API object:

```ts theme={"system"}
const wsProvider = new WsProvider('ws://localhost:9945');
const api = await ApiPromise.create({
    ...options({}),
    provider: wsProvider });
```

Please note that our API object uses a websocket to communicate with the node. And this websocket connects to port 9945 which we have specified above when firing up Alice's node. So all the requests are submitted to her node.

Next step is configuring the key material. We want to transmit signed transactions that contain the prices to be fed in the oracle. Therefore the off-chain worker needs to know the key pairs of Alice, Bob and Charlie (yes, he's also going to take part in this example). Usually the key pairs would be imported, e. g. from a file. But as for the chain nodes we use the predefined key material which is addressed by `//[Name]`. We derive those key pairs from the keyring we create specifying the key pair format SR25519.

```ts theme={"system"}
const keyring = new Keyring({ type: 'sr25519'});

const alice = keyring.addFromUri("//Alice");
const bob = keyring.addFromUri("//Bob");
const charlie = keyring.addFromUri("//Charlie");
```

Alice wants to trigger a transaction that feeds the oracle. If we start typing `api.tx.` the code completion shows us the available extrinsics but the oracle isn't one of them. That's because the default methods of the Substrate runtime are known at compile time but not the custom chain specific extrinsics that might be part of the runtime. Let's find out what's really available by querying the node:

```ts theme={"system"}
const transactions = await api.tx;
console.log(transactions);
```

When executing the program we get a list of much more actually available extrinsics - and one of them is `laminarOracle`. The list tells us even more about the oracle: the available query method `feedValues`. This is exactly what we needed to know\.x

Now Alice reports a current BTC price of 1, i. e. she feeds the oracle with the corresponding key-value pair:

```ts theme={"system"}
await api.tx['laminarOracle'].feedValues([['FBTC', 1]] as any).signAndSend(alice);
```

This line consists of several interesting pieces:

1. We use the API object to trigger an extrinsic (`tx` for transaction). The available extrinsics depend on the used chain. In this case we address the oracle pallet of the laminar chain which is addressed by `laminarOracle`.

2. On that extrinsic we call the method `feedValues` in order to submit key-value pairs that should be fed into the oracle. In this case we just submit a single key-value pair for the Bitcoin price.

3. As this operation is a transaction that is going to be included in a block and costs Alice some gas it needs to be signed by her. This is what happens in the last part of the line.

When this line returns the transaction has been finalized and we can now query the oracle with the current Bitcoin price. But there's again the question of how to do that. As mentioned earlier the oracle offers retrieving the current values via RPC. So let's find out the available RPCs:

```ts theme={"system"}
const methods = await api.rpc.rpc.methods;
console.log(methods);
```

The output again gives us what we need. Two calls should catch our attention: `oracle_getAllValues` and `oracle_getValue`. That means we have the two functions `getAllValues` and `getValue` available for the RPC `oracle.`

Now we query the current BTC price:

```ts theme={"system"}
const result = await api.rpc['oracle'].getValue('Laminar', 'FBTC');
console.log(`Current aggregated BTC price: ${result}`);
```

As you can see we use an RPC as the query doesn't change the state of the chain and therefore the operation is free. We specify the correct RPC (which is `oracle`) and query the value to the key associated with the Bitcoin price (which is `FBTC`). The output is a pair of two values: The current price and the timestamp of the transaction that contained the feeding operation.

That's it! Now we can run the program again with `yarn start`. The oracle will be fed and queried and the output is the expected BTC price of 1.

**Data aggregation**

In the previous section we fed the oracle with one single data point and queried the oracle to retrieve a value. It isn't surprising at all that we read the value that we had written into the oracle just before. But it requires a closer look to what value is actually returned by `getValue`. The oracle pallet states that this method returns a "combined value" which indicates that there is some data aggregation happening.

In fact the way the prices of each currency are aggregated is entirely up to the chain implementation. Currently the Laminar chain doesn't implement any aggregation algorithm but the oracle pallet comes with a default implementation: It takes all fed values of a specific currency submitted within the last 3 days and returns the median value. If there aren't any values to calculate the median from it just returns the most recent value.

Let's try it out. Disable the lines of the previous section that interacted with the oracle (via tx and RPC) and add the following:

```ts theme={"system"}
const feedPrice = async (value: string, sender: any, completion: () => void) => {
    const unsub = await api.tx['laminarOracle'].feedValues([['FBTC', value]] as any).signAndSend(sender, (result) => {
        if (result.status.isInBlock) {
            console.debug(`Transaction included at blockHash ${result.status.asInBlock}`);
        } else if (result.status.isFinalized) {
            console.debug(`Transaction finalized at blockHash ${result.status.asFinalized}`);
            unsub();
            completion();
        }
    });
};
```

For more convenience we define a function `feedPrice` which takes a price value and a sender and triggers the transaction accordingly. We use the [subscription API](https://polkadot.js.org/docs/api/start/api.query.subs) of Polkadot JS in order to make sure that we wait for every transaction to be finalized in a block. Now our three users submit their values:

```ts theme={"system"}
await new Promise<void>((resolve) => { feedPrice("1", alice, resolve); });
await new Promise<void>((resolve) => { feedPrice("5", bob, resolve); });
await new Promise<void>((resolve) => { feedPrice("10", charlie, resolve); });

const result = await api.rpc['oracle'].getValue('Laminar', 'FBTC');
console.log(result);
```

When we query the oracle for the BTC price it returns the median value of 5 as expected.

**Important!** Remember to purge the chain status and restart the two nodes before executing the code of this section.

## TL;DR - Quick demo

```bash theme={"system"}
mkdir example
cd example
```

Download sources for the example and the laminar chain:

```bash theme={"system"}
git clone https://github.com/diadata-org/medianizer-example.git
git clone https://github.com/laminar-protocol/laminar-chain.git
```

Setup laminar chain:

```bash theme={"system"}
cd laminar-chain
make init
make build
cp ../medianizer-example/chain/chainSpec.json .
```

Run first chain node (Answer with "y" when asked for confirmation before purging):

```bash theme={"system"}
SKIP_WASM_BUILD= cargo run -- purge-chain --base-path /tmp/alice

SKIP_WASM_BUILD= cargo run -- --base-path /tmp/alice --chain=chainSpec.json --alice --port 30333 --ws-port 9945 --rpc-port 9933 --node-key 0000000000000000000000000000000000000000000000000000000000000001
```

Run second chain node (e.g. in another terminal session):

```bash theme={"system"}
SKIP_WASM_BUILD= cargo run -- purge-chain --base-path /tmp/bob

SKIP_WASM_BUILD= cargo run -- --base-path /tmp/bob --chain=chainSpec.json --bob --port 30334 --ws-port 9946 --rpc-port 9934 --bootnodes /ip4/127.0.0.1/tcp/30333/p2p/12D3KooWEyoppNCUx8Yx66oV9fJnriXwCcXwDDUA2kj6vnc6iDEp
```

After both nodes have started to communicate with each other run medianizer example (in yet another terminal session):

```bash theme={"system"}
cd ../medianizer-example
yarn install
yarn start
```


# Return Rates in Crypto Farming
Source: https://www.diadata.org/docs/guides/resources/research/return-rates-in-crypto-farming

A basic introduction to some fundamental concepts in crypto asset farming

Decentralized Finance (DeFi) has attracted a lot of attention in the recent years. A rather new and hot topic inside the world of DeFi is yield farming, which allows to earn passive income on token holdings using various investment strategies coded into smart contracts. There is an ever growing number of products labeled as yield farming. Many of those are advertised with an APY (Annual Percentage Yield) rate. We emphasize that in this context, the term APY is to be read with caution. In classical finance, it refers to the annual rate of return in an investment and is a predefined rate. Hence, an investor can be sure to obtain the corresponding interest in their investment. However, most farming products heavily rely on the investment strategy in volatile crypto markets. In contrast to APYs in lending and borrowing, rates published in farming are either APYs of past periods or projections based on past data.

## Pool Rates

Due to the complexity of this topic, our first step consists of publishing the pool rates as emitted in the smart contracts of various farming products such as *yearn.finance* or *CVault*. The basic idea of pool rates is pretty straightforward and can be understood as follows. Consider a farming pool of token X and let $A_X(i)$ be the amount of token X at block number $i$. Assume, farming starts at block number $i_0$, then we have the following equation

$$
A_X(i) = A_X(i_0) \cdot p_X(i)
$$

where $p_X(i)$ is the price corresponding to the pool of token X . Initially, $i = i_0$​ and hence $p_X(i_0) = 1$. Motivated by this fact, we write

$$
p_X(i) = 1 + r_X(i)
$$

Here, $r_X(i)$ is the *pool rate* corresponding to the pool of token X.

As the initial supply $A_X(i_0)$ is constant, the price depends on the evolution of $A_X(i)$ and hence on the pool's investment strategy - if the number of tokens $A_X(i)$ increases with block number $i$, so will the pool rate. In other words, the return of an investment is determined by the change in the pool rate. The following example illustrates the relation between the pool rate and the return on an investment. We remark that in general, as for interest rates in traditional finance, differences of pool rates can be used for simple interest calculation as well as for compounded interest.

**Example:** Assume an investor puts an amount of 100 tokens X into an empty pool at block number 10000000. With the notation from above this means $i_0 = 10000000$ and $A_X(10000000) = 100$. Further assume that 1000 blocks later, the investment strategy has increased the number of tokens in the pool to 101 tokens, so $A_X(10001000) = 101$. The return on the initial investment after these 1000 blocks can be obtained by the difference of the pool rates at blocks 10001000 and 10000000 respectively. Indeed, we have $p_X(10000000) = 1$ and thus $r_X(10000000) = 0$. By the above equation for $A_X(i)$ we have $p_X(10001000) = \frac{A_X(10001000)}{A_X(1000000)} = \frac{101}{100}$ and thus $r_X(10001000) = \frac{1}{100}$. This yields

$$
r_X(10001000) - r_X(10000000) = \frac{1}{100}
$$

and hence a return rate of 1%.

Again, whether the amount of tokens in a pool increases or decreases solely depends on the investment strategy. The return rates for past time ranges can be computed by considering pool rate differences, such as done in the example above. In order to estimate future return rates, one can apply mathematical methods which allow for the estimation of future values based on past data. The simplest way of doing so is to fit a linear function to the data, which is also known under the name of (linear) regression. However, for most cases, such simple models do not yield good results for bigger time ranges. Mathematicians have tackled such problems since a long time and there is a wide range of techniques available. Nowadays, many of these are used under the name of *machine learning*.

## Total Debt Systems

A slightly different approach for farming is presented by other platforms such as *Synthetix*. Apart from constant fee rates on transactions such as trades, the dynamical return rate depends on the average return of all investments on the platform. The corresponding gains (or losses) for the investors are paid out periodically, for instance weekly. We will first explain the general mechanism and then illustrate it with an example.

Consider a platform with n different pools associated to an investment strategy. In most cases, the investment strategy is short or long on a cryptocurrency, represented by a minted synthetic asset. Assume an investor makes an investment by buying from a pool of such a token X worth $p_0$ US-Dollar (it could be any other currency obviously). She thereby increases the so-called system's *total debt* from the previous value to $D_0$ (also in US-Dollar). Here, the total debt is just the value of all investments across the platform. Now assume that after one farming period has elapsed, the value of her investment is $p_1$. Furthermore, the system's total debt, i.e. the US-Dollar value of all investments together changed to $D_1$. The idea is that the system does not owe the investor her initial investment, but rather her initial proportion of the system's total debt, which is $D_0 p_0$. Hence, her actual personal debt $D_{Inv}$ is

$$
D_{Inv} = D_0 p_0 \cdot D_1
$$

In other words, the total debt is distributed among all investors according to their initial share of the total debt. In particular, everyone wins if $D_1 > D_0$, that is, the total debt increases, and everyone looses if $D_1 < D_0$. Furthermore, the investor's total gain G after one farming period is given by her personal debt minus her initial investment

$$
G = D_{Inv} - p_0 = p_0 \left( \frac{D_1}{D_0} - 1 \right)
$$

Let us quickly illustrate this equation before making the connection to the pool rate r. Assume the total debt has increased from D0​=1000 by 10% to D1​=1100. Plugging into the above equation for the gain G leads to G=p0​101​ and hence, the investor makes a gain of 10%. In order to see the relation to the *pool rate* r from the previous section, we rewrite the personal debt DInv​ in a somewhat artificial manner as

$$
D_{Inv} = p_0 \left( 1 + \left( \frac{D_1}{D_0} - 1 \right) \right)
$$

And hence, the pool rate r is given by

$$
r = \frac{D_1}{D_0} - 1
$$

It should come as no surprise that this leads to the pool rate r=0.1 for the above example. Let us now consider a slightly more comprehensive example.

**Example:**

| Step      | Investment 1 in \$                   | Investment 2 in \$                 | Investment 3 in \$               | Total Debt in \$ |
| --------- | ------------------------------------ | ---------------------------------- | -------------------------------- | ---------------- |
| sBTC      | 0                                    | 0                                  | 2                                | $D_0 = 150$      |
| sETH      | 100                                  | 48                                 | 0                                | $D_0 = 150$      |
| sBTC      | 0                                    | 0                                  | 4                                | $D_1 = 152$      |
| sETH      | 100                                  | 48                                 | 0                                | $D_1 = 152$      |
| $D_{Inv}$ | $100 \cdot \frac{152}{150} = 101,33$ | $48 \cdot \frac{152}{150} = 48,64$ | $2 \cdot \frac{152}{150} = 2,03$ |                  |
| $G$       | $100 \cdot \frac{2}{150} = 1,33$     | $48 \cdot \frac{2}{150} = 0,64$    | $2 \cdot \frac{2}{150} = 0,03$   |                  |

Consider a protocol with just two pools, namely sBTC and sETH, and three investors as shown in the first row. The system's total debt is the sum of the investments. Assume that after one farming period the ETH price miraculously remains the same, and the price of BTC doubles, leading to the balances shown in row 2. In the third row, the personal debt for each investor is computed using the above formula for $D_{Inv}$. In the last row, the corresponding total gains are computed. Although investor 3's strategy made a gain of 100%, the investor himself only made a gain of 1,5%, as he was the only one winning and his total gain is distributed among all investors. Furthermore, it is distributed according to the initial shares. As Investors 1 and 2 have far bigger initial shares, they get a large amount of Investment 3's gain, although their strategy did not win. Finally, we can easily compute the farming period's pool rate for this example, using the above formula

$$
r = \frac{152}{150} - 1 = 0,013\bar{3} = 1,\bar{3}\%
$$

## Estimation of Pool Rates from Total Rewards

Some platforms such as *Loopring* emit total system rewards, i.e. accumulated rewards distributed among all pools. We remark that, given a particular staking pool's balance D and the total reward R, an average pool rate r\~ can be estimated as follows

$$
\tilde{r} = \frac{R}{D}.
$$

## Fixed Reward Systems

In fixed reward systems as used by *Barnbridge*, a fixed (and predefined) reward $R$ is distributed among all investors in a pool after a given staking period. The reward is distributed according to an investor's share of the pool. More precisely, let again $D$ be the total staking pool's balance at the end of the staking period. Assume a particular investor has staked the amount $D_I$. Then the investor's reward $R_I$ is given by

$$
R_I = \frac{D_I}{D} \cdot R
$$

For instance, assume the reward is R=32000, the staking pool's balance at the end of the staking period of one week is given by D=200000000 and an investor invested DI​=400000 of an arbitrary currency. Then the reward is given by

$$
R_I = \frac{400000}{200000000} \cdot 32000 = 64.
$$

Here, the pool rate r is simply given by the quotient $r = \frac{D}{R}$, so in the above example $r = 0.00016$. We remark that there might be slight differences on how to implement these systems. Especially whether to allow deposits in the middle of a staking period and if so, how to distribute the reward among these "late" investors.


# Security Bounty Program
Source: https://www.diadata.org/docs/guides/resources/security-bounty-program

If you report security issues within our backend, smart contracts, and production operations, we offer a security bounty program. To be eligible for a bounty, be sure to follow these requirements:

1. Make sure you can describe the security issue you found in a concise and reproducible way.

2. Contact us first. If you use or publish the vulnerability you will not be eligible for a bounty payout. Our contact address is [security@diadata.org](mailto:security@diadata.org).

3. Give us time to assess and address the issue. Sometimes behaviour can be perceived as security issue.

We will grade severity of reported issues and use the CVSS scale as a guideline. The ultimate decision about the severity we consider to be achieved remains in our discretion.

|          |                  |
| -------- | ---------------- |
| Severity | Payout           |
| Low      | 500 - 2500 USDC  |
| Medium   | 2500 - 5000 USDC |
| High     | 5000 - 7500 USDC |

Payouts will be conducted in an established ERC20 stablecoin like USDC. Please make sure to be able to receive ERC20 tokens.


# Terms & Conditions
Source: https://www.diadata.org/docs/guides/resources/t-and-c



<CardGroup>
  <Card title="Contributor Covenant Code of Conduct" href="/resources/t-and-c/code_of_conduct" icon="angle-right" />

  <Card title="Licence Agreement" href="/resources/t-and-c/licence-agreement" icon="angle-right" />

  <Card title="Disclaimer" href="/resources/t-and-c/disclaimer" icon="angle-right" />
</CardGroup>


# Contributor Covenant Code of Conduct
Source: https://www.diadata.org/docs/guides/resources/t-and-c/code_of_conduct

We welcome every contributor who wants to add something to our project. If you want to submit a feature request or a bug report please submit an issue on our issue page. In case you want to add code, read the documentation about the area you want to contribute to and generate a pull request after you finished programming. We will then take a look at your contribution and eventually integrate it.

## Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone.

## Our Standards

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language

* Being respectful of differing viewpoints and experiences

* Gracefully accepting constructive criticism

* Focusing on what is best for the community

* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances

* Trolling, insulting/derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or electronic address, without explicit permission

* Other conduct which could reasonably be considered inappropriate in a professional setting

## Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

## Scope

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

## Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [coc@diadata.org](mailto:coc@diadata.org). The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

## Attribution


# Disclaimer
Source: https://www.diadata.org/docs/guides/resources/t-and-c/disclaimer

Important disclaimer information for visitors of DIA, outlining the boundaries and limitations of the content provided.

1. **General Information**: All content, including but not limited to texts, graphics, and services provided on this website, its linked platforms, applications, forums, blogs, social media, and other platforms associated with DIA (collectively referred to as the "Site"), are primarily sourced from third parties and are made available exclusively for general informational purposes.

2. **No Representations or Warranties:** DIA expressly disclaims all warranties, express or implied, related to the accuracy, completeness, security, or timeliness of the content and services. Nothing contained herein constitutes financial, legal, or any specialized advice. Users contemplating trading or other financial decisions should seek the counsel of a certified financial advisor. The Site does not constitute a solicitation, endorsement, or offer of any nature.

3. **'As Is' and 'As Available' Provision:** The Site, including all content and functionalities, is provided on an "AS IS" and "AS AVAILABLE" basis without any representation or endorsement. While DIA endeavors to ensure the seamless functioning of the Site, it does not warrant that the Site will be uninterrupted, timely, secure, or error-free, nor that defects, if any, will be corrected.

4. **Risk of Data Loss:** Users acknowledge that the data accessed or stored on our Site may be inadvertently lost, corrupted, or become temporarily inaccessible due to various factors. DIA shall not be held responsible for any loss, damage, or corruption of user data arising from technical failures, Internet disruptions, force majeure events, or other factors beyond or within our control.

5. **Exclusion of Implied Warranties:** To the fullest extent permissible under applicable law, all implied warranties, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, are hereby disclaimed. Some jurisdictions may prohibit the exclusion of certain warranties; thus, the above disclaimers may not apply to you in such jurisdictions.

6. **Limitation of Liability:** Under no circumstances, including negligence, shall DIA or its affiliates be liable for any indirect, special, incidental, punitive, exemplary, or consequential damages, including but not limited to loss of data, revenue, profits, or other economic advantage, arising out of or in any way connected with the use or performance of the Site or services, even if DIA had been previously advised of the possibility of such damages.

By accessing or using the Site, you hereby agree to be bound by the aforementioned terms and conditions. It is recommended to seek appropriate legal or professional advice when necessary.

This is a human-readable summary of (and not a substitute for) the [license](https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode). [Disclaimer](https://creativecommons.org/licenses/by-nc-sa/4.0/).

You are free to:

<CardGroup>
  <Card title="Share" icon="share">
    copy and redistribute the material in any medium or format
  </Card>

  <Card title="Adapt" icon="arrows-rotate">
    remix, transform, and build upon the material
  </Card>
</CardGroup>

The licensor cannot revoke these freedoms as long as you follow the license terms.

Under the following terms:

<CardGroup>
  <Card title="Attribution" icon="square-1">
    You must give [appropriate credit](https://creativecommons.org/licenses/by-nc-sa/4.0/), provide a link to the license, and [indicate if changes were made](https://creativecommons.org/licenses/by-nc-sa/4.0/). You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  </Card>

  <Card title="NonCommercial" icon="square-2">
    You may not use the material for [commercial purposes](https://creativecommons.org/licenses/by-nc-sa/4.0/).
  </Card>

  <Card title="ShareAlike" icon="square-3">
    If you remix, transform, or build upon the material, you must distribute your contributions under the [same license](https://creativecommons.org/licenses/by-nc-sa/4.0/) as the original.
  </Card>

  <Card title="No additional restrictions" icon="square-4">
    You may not apply legal terms or [technological measures](https://creativecommons.org/licenses/by-nc-sa/4.0/) that legally restrict others from doing anything the license permits.
  </Card>

  <Card title="Disclaimer" icon="square-5">
    The licensor provides the material as-is, without any guarantees or warranties. This means there's no promise about the material's quality, accuracy, or any other aspects.
  </Card>

  <Card title="No Liability" icon="square-6">
    The licensor won't be responsible for any kind of damages or costs that come from using the material, even if they know there's a risk.
  </Card>
</CardGroup>

Notices:

* You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable [exception or limitation](https://creativecommons.org/licenses/by-nc-sa/4.0/).

* No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as [publicity, privacy, or moral rights](https://creativecommons.org/licenses/by-nc-sa/4.0/) may limit how you use the material.


# Licence Agreement
Source: https://www.diadata.org/docs/guides/resources/t-and-c/licence-agreement

For the usage of DIA's data and services

<Frame>
  <img />
</Frame>

This is a human-readable summary of (and not a substitute for) the [license](https://creativecommons.org/licenses/by-nc-sa/4.0/legalcode). [Disclaimer](https://creativecommons.org/licenses/by-nc-sa/4.0/#).

## You are free to:

<CardGroup>
  <Card title="Share" icon="share">
    copy and redistribute the material in any medium or format
  </Card>

  <Card title="Adapt" icon="arrows-rotate">
    remix, transform, and build upon the material
  </Card>
</CardGroup>

The licensor cannot revoke these freedoms as long as you follow the license terms.

## Under the following terms:

<CardGroup>
  <Card title="Attribution" icon="square-1">
    You must give [appropriate credit](https://creativecommons.org/licenses/by-nc-sa/4.0/#), provide a link to the license, and [indicate if changes were made](https://creativecommons.org/licenses/by-nc-sa/4.0/#). You may do so in any reasonable manner, but not in any way that suggests the licensor endorses you or your use.
  </Card>

  <Card title="NonCommercial" icon="square-2">
    You may not use the material for [commercial purposes](https://creativecommons.org/licenses/by-nc-sa/4.0/#).
  </Card>

  <Card title="ShareAlike" icon="square-3">
    If you remix, transform, or build upon the material, you must distribute your contributions under the [same license](https://creativecommons.org/licenses/by-nc-sa/4.0/#) as the original.
  </Card>

  <Card title="No additional restrictions" icon="square-4">
    You may not apply legal terms or [technological measures](https://creativecommons.org/licenses/by-nc-sa/4.0/#) that legally restrict others from doing anything the license permits.
  </Card>
</CardGroup>

## Notices:

* You do not have to comply with the license for elements of the material in the public domain or where your use is permitted by an applicable [exception or limitation](https://creativecommons.org/licenses/by-nc-sa/4.0/#).

* No warranties are given. The license may not give you all of the permissions necessary for your intended use. For example, other rights such as [publicity, privacy, or moral rights](https://creativecommons.org/licenses/by-nc-sa/4.0/#) may limit how you use the material.


# null
Source: https://www.diadata.org/docs/home



<div>
  <div />

  <div />

  <div>
    <h1>
      DIA Oracles Docs
    </h1>

    <p>
      Build onchain with trustless oracles.
    </p>

    <div>
      <button type="button">
        <svg />

        Ask about DIA...
      </button>
    </div>
  </div>
</div>

<div>
  <h2>
    What is DIA
  </h2>

  <p>
    <strong>DIA is a trustless oracle provider that delivers data feeds for tokens,
    LSTs, RWAs, randomness, and more to any blockchain.</strong>
  </p>

  <p>
    Unlike traditional oracles that rely on opaque third-party data, DIA takes a
    novel approach, sourcing data directly from its origin. This ensures full
    transparency, complete customization, and support for any data type across
    ecosystems.
  </p>

  <p>
    With integrations with 100+ data sources, support for 60+ blockchains, and
    powering over 200 dApps, DIA continues to scale its network while empowering
    Web3 ecosystems to thrive.
  </p>
</div>

<div>
  <h2>
    Quickstart
  </h2>

  <CardGroup>
    <Card title="Fetch Price Data" icon="code" href="/guides/how-to-guides/fetch-price-data">
      Integrate token price feeds with Push or Pull oracles.
    </Card>

    <Card title="Generate Randomness" icon="dice-six" href="/guides/how-to-guides/generate-randomness">
      Add verifiable randomness to your smart contracts with xRandom.
    </Card>

    <Card title="Fund your DIA Oracle" icon="wallet" href="/guides/how-to-guides/fund-the-oracle">
      Learn how to fund DIA's gas wallet to enable oracle updates.
    </Card>

    <Card title="Migrate from Chainlink" icon="repeat" href="/guides/how-to-guides/migrate-to-dia#migrate-to-dia">
      Switch to DIA-compatible oracles with minimal code changes.
    </Card>
  </CardGroup>

  <h2>
    Use DIA Products
  </h2>

  <CardGroup>
    <Card title="Token Price Feeds" icon="chart-line" href="/dia-stack/data-products/token-price-feeds">
      Get on-chain price feeds for 20,000+ digital assets.
    </Card>

    <Card title="RWA Feeds" icon="building-columns" href="/dia-stack/data-products/rwa-price-feeds">
      Fetch data for stocks, FX rates, and other real-world assets.
    </Card>

    <Card title="Randomness" icon="dice-six" href="/dia-stack/data-products/verifiable-randomness">
      Integrate DIA xRandom for provably fair random numbers.
    </Card>

    <Card title="Proof of Reserve" icon="clipboard-check" href="/dia-stack/data-products/fundamental-feeds">
      Feeds for on/off-chain assets that account for the collateral ratio.
    </Card>
  </CardGroup>

  <h2>
    Dive into Stack
  </h2>

  <CardGroup>
    <Card title="How DIA Oracles Work" icon="gear" href="/dia-stack/how-it-works">
      Understand the architecture and components of DIA oracles.
    </Card>

    <Card title="Feeders (Sourcing Layer)" icon="database" href="/dia-stack/architecture/core-components/feeders">
      Learn how DIA collects data from various sources.
    </Card>

    <Card title="Lasernet (Aggregation Layer)" icon="calculator" href="/dia-stack/architecture/core-components/lasernet/overview">
      Explore how data is aggregated and validated.
    </Card>

    <Card title="Spectra (Messaging Layer)" icon="truck" href="/dia-stack/architecture/core-components/spectra">
      Discover how data is delivered across chains.
    </Card>

    <Card title="API Reference" icon="magnifying-glass-chart" href="/reference/apis">
      Access comprehensive API documentation.
    </Card>
  </CardGroup>

  <h2>
    Get Support
  </h2>

  <CardGroup>
    <Card title="Join Dev Discord" icon="Discord" href="https://discord.gg/RjHBcZ9mEH">
      Ask questions & get help from the DIA community.
    </Card>

    <Card title="Join Telegram" icon="Telegram" href="https://t.me/DIAdata_org">
      Connect with the DIA community on Telegram.
    </Card>

    <Card title="Request Oracle" icon="circle-plus" href="/guides/how-to-guides/request-a-custom-oracle">
      Request a custom oracle integration for your dApp or chain.
    </Card>
  </CardGroup>
</div>


# DIA APIs
Source: https://www.diadata.org/docs/reference/apis



## **Overview**

**Find the right data for your needs**

Show your users the most transparent data on the market with our API. Whether you're building a financial service, a portfolio management tool, a new media offering, or more, we have the most advanced and updated data on the market for your product.

**Backtest your strategies**

Use the most efficient and transparent crypto data to run simulations and backtest your trading or investing strategies. With crowd-aggregated hundreds of exchanges, you can be sure that you're getting the right picture every single time.

**Run Experiments**

Build your own models with our data, to further your interest or just for fun. With our flexible and powerful API, we provide you with a set of data that will help you draw insights and make conclusions.

## API Access

The DIA base url is `https://api.diadata.org/v1`. All API paths are sub-paths of this base URL.

## Performance

We apply the highest performance standards for all our API feeds.

* 99.9% uptime

* \<1 sec response times


# Commodities
Source: https://www.diadata.org/docs/reference/apis/commodities

GET https://api.diadata.org/v1/rwa/Commodities/{CommoditySymbol}
Returns the latest price of a commodity in USD.

## Path Parameter

<ParamField type="string">
  Commodity symbol e.g. XAU-USD (Gold)
</ParamField>

<Accordion title="Available commodities">
  1. XAU/USD (Gold)
  2. XAGG/USD (Silver)
  3. XG/USD (Copper)
</Accordion>

<ResponseExample>
  ```json Sample Response theme={"system"}
  {
    "Ticker": "XAU-USD",
    "Name": "Gold Spot / US Dollar",
    "Price": 2925.88989,
    "Timestamp": "2025-02-17T20:00:00Z"
  }
  ```
</ResponseExample>


# ETFs
Source: https://www.diadata.org/docs/reference/apis/etfs

GET https://api.diadata.org/v1/rwa/ETF/{ETFSymbol}
Returns the latest price of an ETF in USD.

## Path Parameter

<ParamField type="string">
  ETF symbol e.g. IVV (iShares Core S\&P 500 ETF)
</ParamField>

<Accordion title="Available ETFs">
  1. IVV (iShares Core S\&P 500 ETF)
  2. URTH (iShares MSCI World ETF)
  3. EEM (iShares MSCI Emerging Markets ETF)
</Accordion>

<ResponseExample>
  ```json Sample Response theme={"system"}
  {
    "Ticker": "IVV",
    "Name": "iShares Core S&P 500 ETF",
    "Price": 612.97,
    "Timestamp": "2025-02-18T14:30:00Z"
  }
  ```
</ResponseExample>

To request custom data feeds, you can always refer to the following section:

<Card title="Request a Custom Oracle" href="/request-a-custom-oracle" icon="angle-right" />


# Forex
Source: https://www.diadata.org/docs/reference/apis/forex

GET https://api.diadata.org/v1/rwa/Fiat/{FiatQuote}
Returns the latest available exchange rate for fiat currencies.

## Path Parameter

<ParamField type="string">
  Exchange pair, e.g. EUR-USD; GBP-USD
</ParamField>

<Accordion title="Available FX pairs">
  1. NGN/USD
  2. EUR/USD
  3. BRL/USD
  4. JPY/USD
  5. CHF/USD
  6. GBP/USD
</Accordion>

<ResponseExample>
  ```json Sample Response theme={"system"}
  {
    "Ticker": "EUR-USD",
    "Price": 1.04512317205083,
    "Timestamp": "2025-02-18T14:49:00Z"
  }
  ```
</ResponseExample>


# RWA Prices
Source: https://www.diadata.org/docs/reference/apis/rwa-prices

DIA currently offers a set of price feeds for a selection of traditional financial assets, delivered via RestAPI endpoints.

<Info>
  Data is refreshed every 1-min
</Info>


# Token Prices
Source: https://www.diadata.org/docs/reference/apis/token-prices

Test DIA's APIs dedicated to token prices.

You can learn more about the product [here](https://app.gitbook.com/o/-M1UhUdjMqTODILqXwkd/s/7BgHS2yasVJB3IUNwbdE/~/changes/1/data-products/token-price-feeds).

<CardGroup>
  <Card title="RestAPI" href="/reference/apis/token-prices/api-endpoints" icon="angle-right" />

  <Card title="GraphQL" href="/reference/apis/token-prices/graphql" icon="angle-right" />
</CardGroup>


# RestAPI
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints

The page includes a list of all available Token data endpoints on DIA network. To review the data sources and methodologies used for pricing, visit the [Data Sources](/reference/cryptocurrency-trading-data) page.



# Asset Chart Points
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/asset-chart-points

GET https://api.diadata.org/v1/assetChartPoints/{filter}/{blockchain}/{address}
Get asset details for all exchanges.

<Card title="Example" href="https://api.diadata.org/v1/assetChartPoints/MA120/Bitcoin/0x0000000000000000000000000000000000000000" icon="angle-right">
  [https://api.diadata.org/v1/assetChartPoints/MA120/Bitcoin/0x0000000000000000000000000000000000000000](https://api.diadata.org/v1/assetChartPoints/MA120/Bitcoin/0x0000000000000000000000000000000000000000)
</Card>

*Remark:* Careful! Successful responses can be rather large.

## Path Parameters

<ParamField type="integer">
  Unix timestamp setting the start of the return array
</ParamField>

<ParamField type="integer">
  Unix timestamp setting the end of the return array
</ParamField>

<ParamField type="string">
  Which filter should be applied (Available options: MA120, MEDIR120, VOL120 and
  MAIR120)
</ParamField>

<ParamField type="string">
  A valid blockchain from GET /v1/blockchains, e.g., Bitcoin
</ParamField>

<ParamField type="string">
  A valid asset address from GET /v1/token/:symbol, e.g.,
  0x000000000000000000000000000000000000000 for BTC
</ParamField>

## Query Parameters

<ParamField type="string">
  Which scale the graph points distance should have. Available options: 5m 30m
  1h 4h 1d 1w
</ParamField>

<ResponseExample>
  ```json 200 Successful retrieval of a chart points for an asset theme={"system"}
  {"DataPoints":[{"Series":[{"name":"filters","columns":["time","exchange","filter","symbol","value"],"values":[["2020-05-19T08:17:59Z",null,"MEDIR120","EOS",2.6236194301032314]]}],"Messages":null}]}
  ```
</ResponseExample>


# Asset Last Trades
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/asset-last-trades

GET https://api.diadata.org/v1/lastTradesAsset/{blockchain}/{address}
Get last trade timestamp for an asset.

Get last trade timestamp for an asset.

<Card title="Example" href="https://api.diadata.org/v1/lastTradesAsset/Bitcoin/0x0000000000000000000000000000000000000000" icon="angle-right">
  [https://api.diadata.org/v1/lastTradesAsset/Bitcoin/0x0000000000000000000000000000000000000000](https://api.diadata.org/v1/lastTradesAsset/Bitcoin/0x0000000000000000000000000000000000000000)
</Card>

## Path Parameters

<ParamField type="string">
  A valid blockchain from GET /v1/blockchains, e.g., Bitcoin.
</ParamField>

<ParamField type="string">
  A valid asset address from GET /v1/token/:symbol, e.g.,
  0x000000000000000000000000000000000000000 for BTC.
</ParamField>

<ResponseExample>
  ```json 200: OK Succesful retrieval of last trades for an asset theme={"system"}
  {
    // Response
  }
  ```
</ResponseExample>


# Blockchains
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/blockchains

GET https://api.diadata.org/v1/blockchains
Get a list of all available blockchains.

Get a list of all available blockchains.

<ResponseExample>
  ```json 200: OK theme={"system"}
  {
      // Response
  }
  ```
</ResponseExample>


# Centralized Exchange Pairs by Asset
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/centralized-exchange-pairs-by-asset

GET https://api.diadata.org/v1/pairsAssetCex/{blockchain}/{address}
Get all pairs on a centralized exchange for which DIA is collecting trades data at the moment. Include pairs across all exchanges involving the requested asset as either base- or quote token.

<Card title="Example" href="https://api.diadata.org/v1/pairsAssetCex/Shiden/0x0000000 000000000000000000000000000000000" icon="angle-right">
  [https://api.diadata.org/v1/pairsAssetCex/Shiden/0x0000000000000000000000000000000000000000](https://api.diadata.org/v1/pairsAssetCex/Shiden/0x0000000000000000000000000000000000000000)
</Card>

Use the query parameter verified in order to get either verified or unverified pairs.

<Card title="Example" href="https://api.diadata.org/v1/pairsAssetCex/Shiden/0x0000000000000000000000000000000000000000?verified=true" icon="angle-right">
  [https://api.diadata.org/v1/pairsAssetCex/Shiden/0x0000000000000000000000000000000000000000?verified=true](https://api.diadata.org/v1/pairsAssetCex/Shiden/0x0000000000000000000000000000000000000000?verified=true)
</Card>

## Path Parameters

<ParamField type="string">
  Name of the blockchain for the requested asset.
</ParamField>

<ParamField type="string">
  Address of the requested asset.
</ParamField>

## Query Parameters

<ParamField type="boolean">
  If set to true, only verified pairs are returned. If set to false, only
  unverified pairs are returned.
</ParamField>


# Centralized Exchange Pairs by Exchange
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/centralized-exchange-pairs-by-exchange

GET https://api.diadata.org/v1/pairsCex/{exchange}
Get all pairs on a given exchange for which DIA is collecting trades data at the moment.

Get all pairs on a given exchange for which DIA is collecting trades data at the moment.

<Card title="Example" href="https://api.diadata.org/v1/pairsCex/Kraken" icon="angle-right">
  [https://api.diadata.org/v1/pairsCex/Kraken](https://api.diadata.org/v1/pairsCex/Kraken)
</Card>

Use the query parameter verified in order to get either verified or unverified pairs.

<Card title="Example" href="https://api.diadata.org/v1/pairsCex/Kraken?verified=true" icon="angle-right">
  [https://api.diadata.org/v1/pairsCex/Kraken?verified=true](https://api.diadata.org/v1/pairsCex/Kraken?verified=true)
</Card>

## Path Parameters

<ParamField type="string">
  Name of the crypto exchange.
</ParamField>

## Query Parameters

<ParamField type="boolean">
  If set to true, only verified pairs are returned. If set to false, only
  unverified pairs are returned.
</ParamField>


# Decentralized Exchanges Pool Liquidity
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/decentralized-exchanges-pool-liquidity

GET https://api.diadata.org/v1/poolLiquidity/{blockchain}/{pool_address}
Get the latest state of a DEX pool's liquidity.

<Card title="Example" href="https://api.diadata.org/v1/poolLiquidity/Ethereum/0xB4e16d0168e52d35CaCD2c6185b44281Ec28C9Dc" icon="angle-right">
  [https://api.diadata.org/v1/poolLiquidity/Ethereum/0xB4e16d0168e52d35CaCD2c6185b44281Ec28C9Dc](https://api.diadata.org/v1/poolLiquidity/Ethereum/0xB4e16d0168e52d35CaCD2c6185b44281Ec28C9Dc)
</Card>

## Path Parameters

<ParamField type="string">
  Name of the blockchain of the requested pool.
</ParamField>

<ParamField type="string">
  Address of the requested pool.
</ParamField>

<ResponseExample>
  ```json 200: OK Successful retrieval of DEX pools. theme={"system"}
  {Exchange: "Uniswap", Blockchain: "Ethereum", Address: "0xB4e16d0168e52d35CaCD2c6185b44281Ec28C9Dc", Time: "0001-01-01T00:00:00Z", TotalLiquidityUSD: 97124191.13292821,
  Liquidity:
  { 0: {Asset: {Symbol: "WETH", Name: "Wrapped Ether", Address: "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2", Decimals: 18, Blockchain: "Ethereum"}, Volume: 34642.164578066426 }}
  {1: {Asset: {Symbol: "USDC", Name: "USD Coin", Address: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", Decimals: 6, Blockchain: "Ethereum"}, Volume: 50362947.314436}}
  }
  ```
</ResponseExample>


# DeFi Protocols Collateral Information
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/defi-protocols-collateral-information

GET https://api.diadata.org/v1/synthasset/{blockchain}/{protocol}
The endpoint provides information on the health factor of DeFi protocols.

It takes into consideration outstanding loans, contracts' balance and compares it to synthetic token issuance. This helps to make sure that all assets are fully collateralized.

<Card title="Example query" href="https://api.diadata.org/v1/synthasset/Ethereum/Aave-V2" icon="angle-right">
  [https://api.diadata.org/v1/synthasset/Ethereum/Aave-V2](https://api.diadata.org/v1/synthasset/Ethereum/Aave-V2)
</Card>

*Currently only Aave V2 and Aave V3 are supported on Ethereum and Avalanche blockchains.*

It is possible to receive collateral information for a single token by using token filter as in example below:

<Card title="https://api.diadata.org/v1/synthasset/Avalanche/Aave-V3?address=0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7" href="https://api.diadata.org/v1/synthasset/Avalanche/Aave-V3?address=0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7" icon="angle-right" />

To receive all asset updates data during the selected period use `starttime` and `endtime` filter parameters with timestamps as inputs. Here is an example:

<Card title="https://api.diadata.org/v1/synthasset/Avalanche/Aave-V3?address=0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7\&starttime=1664502770\&endtime=1664531570" href="https://api.diadata.org/v1/synthasset/Avalanche/Aave-V3?address=0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7\&starttime=1664502770\&endtime=1664531570" icon="angle-right" />

## Path Parameters

<ParamField type="string">
  Ethereum or Avalanche
</ParamField>

<ParamField type="string">
  Aave
</ParamField>

<ParamField type="string">
  Token contract address. You can use either underlying token address or
  synthetic token to receive the data
</ParamField>

<ParamField type="integer">
  Unix timestamp setting the start of the return array
</ParamField>

<ParamField type="integer">
  Unix timestamp setting the end of the return array
</ParamField>

<ResponseExample>
  ```json 200: OK theme={"system"}
  {
    // Response
  }
  ```
</ResponseExample>


# Exchange Chart Points
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/exchange-chart-points

GET https://api.diadata.org/v1/chartPoints/{filter}/{exchange}/{symbol}
Get chart points for an exchange.

<Card title="Example" href="https://api.diadata.org/v1/chartPoints/MEDIR120/Binance/BTC" icon="angle-right">
  [https://api.diadata.org/v1/chartPoints/MEDIR120/Binance/BTC](https://api.diadata.org/v1/chartPoints/MEDIR120/Binance/BTC)
</Card>

<Info>Successful responses can be rather large.</Info>

## Path Parameters

<ParamField type="string">
  Which filter should be applied (Available options: MA120, VOL120, MEDIR120 and
  MAIR120).
</ParamField>

<ParamField type="string">
  A valid exchange from GET /v1/exchanges, e.g., Binance
</ParamField>

<ParamField type="string">
  A valid symbol from GET /v1/coins, e.g., BTC.
</ParamField>

## Query Parameters

<ParamField type="string">
  Which scale the graph points distance should have. Available options: 5m 30m
  1h 4h 1d 1w.
</ParamField>

<ResponseExample>
  ```json 200 Successful retrieval of a chart point. theme={"system"}
  {"DataPoints":[{"Series":[{"name":"filters","columns":["time","exchange","filter","symbol","value"],"values":[["2020-05-19T08:02:09Z","GateIO","MEDIR120","EOS",2.6218717017500084]]}],"Messages":null}]}
  ```
</ResponseExample>


# Exchanges
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/exchanges

GET https://api.diadata.org/v1/exchanges
Get a list of all available crypto exchanges.

<ResponseExample>
  ```json 200 Successful retrieval of available exchanges. theme={"system"}
  ["KuCoin","Uniswap","Balancer","Maker","Gnosis","Curvefi","Binance","BitBay","Bitfinex","Bittrex","CoinBase","GateIO","HitBTC","Huobi","Kraken","LBank","OKEx","Quoine","Simex","ZB","Bancor","Loopring","SushiSwap","Dforce","0x","Kyber","Bitmax","PanCakeSwap","CREX24","STEX"]
  ```
</ResponseExample>


# Guest Quotation
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/guest-quotation

GET https://api.diadata.org/v1/foreignQuotation/{source}/{symbol}
Get the latest quotation for a token from a guest source.

<Card title="Example" href="https://api.diadata.org/v1/foreignQuotation/CoinMarketCap/BTC" icon="angle-right">
  [https://api.diadata.org/v1/foreignQuotation/CoinMarketCap/BTC](https://api.diadata.org/v1/foreignQuotation/CoinMarketCap/BTC)
</Card>

Use the query parameter time in order to get the latest quotation before the specified timestamp

<Card title="Example" href="https://api.diadata.org/v1/foreignQuotation/Coingecko/BTC?time=1647349656" icon="angle-right">
  [https://api.diadata.org/v1/foreignQuotation/Coingecko/BTC?time=1647349656](https://api.diadata.org/v1/foreignQuotation/Coingecko/BTC?time=1647349656)
</Card>

## Path Parameters

<ParamField type="string">
  Source of the quotation
</ParamField>

<ParamField type="string">
  Which symbol to get a quotation for, e.g. BTC
</ParamField>

## Query Parameters

<ParamField type="number">
  Unix timestamp.
</ParamField>

<ResponseExample>`json 200 `</ResponseExample>


# Guest Symbols
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/guest-symbols

GET https://api.diadata.org/v1/foreignSymbols/{source}
Get the list of available symbols along with their ITIN for guest quotations.

<Card title="Example" href="https://api.diadata.org/v1/foreignSymbols/Coingecko" icon="angle-right">
  [https://api.diadata.org/v1/foreignSymbols/Coingecko](https://api.diadata.org/v1/foreignSymbols/Coingecko)
</Card>

## Path Parameters

<ParamField type="string">
  Source of the quotation
</ParamField>

<ResponseExample>`json 200 `</ResponseExample>


# Quotable Assets
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/quotable-assets

GET https://api.diadata.org/v1/quotedAssets
Returns a list of assets available for quotations.

<Card title="Example" href="https://api.diadata.org/v1/quotedAssets" icon="angle-right">
  [https://api.diadata.org/v1/quotedAssets](https://api.diadata.org/v1/quotedAssets)
</Card>

Use the query parameter blockchain in order to obtain exclusively assets on the selected blockchain.

<Card title="Example" href="https://api.diadata.org/v1/quotedAssets?blockchain=Polygon" icon="angle-right">
  [https://api.diadata.org/v1/quotedAssets?blockchain=Polygon](https://api.diadata.org/v1/quotedAssets?blockchain=Polygon)
</Card>

## Query Parameters

<ParamField type="string">
  Name of the blockchain for the requested assets.
</ParamField>

<ResponseExample>
  ```json 200: OK Successful retrieval of quotable assets. theme={"system"}
  [{"Asset":{"Symbol":"WETH","Name":"Wrapped Ether","Address":"0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619","Decimals":18,"Blockchain":"Polygon"},"Volume":35305550.57803},{"Asset":{"Symbol":"WMATIC","Name":"Wrapped Matic","Address":"0x0d500B1d8E8eF31E21C99d1Db9A6444d3ADf1270","Decimals":18,"Blockchain":"Polygon"},"Volume":24233330.345671}]
  ```
</ResponseExample>


# Request Samples
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/request-samples

To simplify your DIA API integration journey, we created sample API calls for retrieving price data in the most widely used programming languages.

All examples make a call to DIA Asset Quotation API for Bitcoin price.

<AccordionGroup>
  <Accordion title="Shell">
    ### cURL

    ```bash theme={"system"}
    curl --request GET \
      --url https://api.diadata.org/v1/assetQuotation/Bitcoin/0x000000000000000000000000000000000000000 \
      --header 'Content-Type: application/json'
    ```

    ### HTTPie

    ```bash theme={"system"}
    http GET https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000 \
      Content-Type:application/json
    ```

    ### Wget

    ```bash theme={"system"}
    wget --quiet \
      --method GET \
      --header 'Content-Type: application/json' \
      --output-document \
      - https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000
    ```
  </Accordion>

  <Accordion title="JavaScript">
    ### Fetch

    ```js theme={"system"}
    fetch("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000", {
      "method": "GET",
      "headers": {
        "Content-Type": "application/json"
      }
    })
    .then(response => {
      console.log(response);
    })
    .catch(err => {
      console.error(err);
    });
    ```

    ### XMLHttpRequest

    ```js theme={"system"}
    const data = null;

    const xhr = new XMLHttpRequest();
    xhr.withCredentials = true;

    xhr.addEventListener("readystatechange", function () {
      if (this.readyState === this.DONE) {
        console.log(this.responseText);
      }
    });

    xhr.open("GET", "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000");
    xhr.setRequestHeader("Content-Type", "application/json");

    xhr.send(data);
    ```

    ### jQuery

    ```js theme={"system"}
    const settings = {
      "async": true,
      "crossDomain": true,
      "url": "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000",
      "method": "GET",
      "headers": {
        "Content-Type": "application/json"
      }
    };

    $.ajax(settings).done(function (response) {
      console.log(response);
    });
    ```

    ### Axios

    ```js theme={"system"}
    import axios from "axios";

    const options = {
      method: 'GET',
      url: 'https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000',
      headers: {'Content-Type': 'application/json'}
    };

    axios.request(options).then(function (response) {
      console.log(response.data);
    }).catch(function (error) {
      console.error(error);
    });
    ```
  </Accordion>

  <Accordion title="Node">
    ### Native

    ```js theme={"system"}
    const http = require("https");

    const options = {
      "method": "GET",
      "hostname": "api.diadata.org",
      "port": null,
      "path": "/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000",
      "headers": {
        "Content-Type": "application/json"
      }
    };

    const req = http.request(options, function (res) {
      const chunks = [];

      res.on("data", function (chunk) {
        chunks.push(chunk);
      });

      res.on("end", function () {
        const body = Buffer.concat(chunks);
        console.log(body.toString());
      });
    });

    req.end();
    ```

    ### Request

    ```js theme={"system"}
    const request = require('request');

    const options = {
      method: 'GET',
      url: 'https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000',
      headers: {'Content-Type': 'application/json'}
    };

    request(options, function (error, response, body) {
      if (error) throw new Error(error);

      console.log(body);
    });
    ```

    ### Unirest

    ```js theme={"system"}
    const unirest = require("unirest");

    const req = unirest("GET", "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000");

    req.headers({
      "Content-Type": "application/json"
    });

    req.end(function (res) {
      if (res.error) throw new Error(res.error);

      console.log(res.body);
    });
    ```

    ### Fetch

    ```js theme={"system"}
    const fetch = require('node-fetch');

    let url = 'https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000';

    let options = {method: 'GET', headers: {'Content-Type': 'application/json'}};

    fetch(url, options)
      .then(res => res.json())
      .then(json => console.log(json))
      .catch(err => console.error('error:' + err));
    ```

    ### Axios

    ```js theme={"system"}
    var axios = require("axios").default;

    var options = {
      method: 'GET',
      url: 'https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000',
      headers: {'Content-Type': 'application/json'}
    };

    axios.request(options).then(function (response) {
      console.log(response.data);
    }).catch(function (error) {
      console.error(error);
    });
    ```
  </Accordion>

  <Accordion title="Python">
    ### Python 3

    ```python theme={"system"}
    import http.client

    conn = http.client.HTTPSConnection("api.diadata.org")

    headers = { 'Content-Type': "application/json" }

    conn.request("GET", "/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000", headers=headers)

    res = conn.getresponse()
    data = res.read()

    print(data.decode("utf-8"))
    ```

    ### Requests

    ```python theme={"system"}
    import requests

    url = "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000"

    headers = {'Content-Type': 'application/json'}

    response = requests.request("GET", url, headers=headers)

    print(response.text)
    ```
  </Accordion>

  <Accordion title="Go">
    ```go theme={"system"}
    package main

    import (
    	"fmt"
    	"net/http"
    	"io/ioutil"
    )

    func main() {

    	url := "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000"

    	req, _ := http.NewRequest("GET", url, nil)

    	req.Header.Add("Content-Type", "application/json")

    	res, _ := http.DefaultClient.Do(req)

    	defer res.Body.Close()
    	body, _ := ioutil.ReadAll(res.Body)

    	fmt.Println(res)
    	fmt.Println(string(body))

    }
    ```
  </Accordion>

  <Accordion title="C">
    ```c theme={"system"}
    CURL *hnd = curl_easy_init();

    curl_easy_setopt(hnd, CURLOPT_CUSTOMREQUEST, "GET");
    curl_easy_setopt(hnd, CURLOPT_URL, "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000");

    struct curl_slist *headers = NULL;
    headers = curl_slist_append(headers, "Content-Type: application/json");
    curl_easy_setopt(hnd, CURLOPT_HTTPHEADER, headers);

    CURLcode ret = curl_easy_perform(hnd);
    ```
  </Accordion>

  <Accordion title="Obj-C">
    ```c theme={"system"}
    #import <Foundation/Foundation.h>

    NSDictionary *headers = @{ @"Content-Type": @"application/json" };

    NSMutableURLRequest *request = [NSMutableURLRequest requestWithURL:[NSURL URLWithString:@"https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000"]
                                                           cachePolicy:NSURLRequestUseProtocolCachePolicy
                                                       timeoutInterval:10.0];
    [request setHTTPMethod:@"GET"];
    [request setAllHTTPHeaderFields:headers];

    NSURLSession *session = [NSURLSession sharedSession];
    NSURLSessionDataTask *dataTask = [session dataTaskWithRequest:request
                                                completionHandler:^(NSData *data, NSURLResponse *response, NSError *error) {
                                                    if (error) {
                                                        NSLog(@"%@", error);
                                                    } else {
                                                        NSHTTPURLResponse *httpResponse = (NSHTTPURLResponse *) response;
                                                        NSLog(@"%@", httpResponse);
                                                    }
                                                }];
    [dataTask resume];
    ```
  </Accordion>

  <Accordion title="OCaml">
    ```ocaml theme={"system"}
    open Cohttp_lwt_unix
    open Cohttp
    open Lwt

    let uri = Uri.of_string "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000" in
    let headers = Header.add (Header.init ()) "Content-Type" "application/json" in

    Client.call ~headers `GET uri
    >>= fun (res, body_stream) ->
      (* Do stuff with the result *)
    ```
  </Accordion>

  <Accordion title="C#">
    ### HttpClient

    ```csharp theme={"system"}
    var client = new HttpClient();
    var request = new HttpRequestMessage
    {
        Method = HttpMethod.Get,
        RequestUri = new Uri("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000"),
        Headers =
        {
            { "Content-Type", "application/json" },
        },
    };
    using (var response = await client.SendAsync(request))
    {
        response.EnsureSuccessStatusCode();
        var body = await response.Content.ReadAsStringAsync();
        Console.WriteLine(body);
    }
    ```

    ### RestSharp

    ```csharp theme={"system"}
    var client = new RestClient("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000");
    var request = new RestRequest(Method.GET);
    request.AddHeader("Content-Type", "application/json");
    IRestResponse response = client.Execute(request);
    ```
  </Accordion>

  <Accordion title="Java">
    ### AsyncHttp

    ```java theme={"system"}
    AsyncHttpClient client = new DefaultAsyncHttpClient();
    client.prepare("GET", "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000")
      .setHeader("Content-Type", "application/json")
      .execute()
      .toCompletableFuture()
      .thenAccept(System.out::println)
      .join();

    client.close();
    ```

    ### NetHttp

    ```java theme={"system"}
    HttpRequest request = HttpRequest.newBuilder()
        .uri(URI.create("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000"))
        .header("Content-Type", "application/json")
        .method("GET", HttpRequest.BodyPublishers.noBody())
        .build();
    HttpResponse<String> response = HttpClient.newHttpClient().send(request, HttpResponse.BodyHandlers.ofString());
    System.out.println(response.body());
    ```

    ### OkHttp

    ```java theme={"system"}
    OkHttpClient client = new OkHttpClient();

    Request request = new Request.Builder()
      .url("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000")
      .get()
      .addHeader("Content-Type", "application/json")
      .build();

    Response response = client.newCall(request).execute();
    ```

    ### Unirest

    ```java theme={"system"}
    HttpResponse<String> response = Unirest.get("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000")
      .header("Content-Type", "application/json")
      .asString();
    ```
  </Accordion>

  <Accordion title="Http">
    ```bash theme={"system"}
    GET /v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000 HTTP/1.1
    Content-Type: application/json
    Host: api.diadata.org
    ```
  </Accordion>

  <Accordion title="Clojure">
    ```clojure theme={"system"}
    (require '[clj-http.client :as client])

    (client/get "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000" {:headers {:Content-Type "application/json"}})
    ```
  </Accordion>

  <Accordion title="Kotlin">
    ```kotlin theme={"system"}
    val client = OkHttpClient()

    val request = Request.Builder()
      .url("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000")
      .get()
      .addHeader("Content-Type", "application/json")
      .build()

    val response = client.newCall(request).execute()
    ```
  </Accordion>

  <Accordion title="PHP">
    ### pecl/http 1

    ```php theme={"system"}
    <?php

    $request = new HttpRequest();
    $request->setUrl('https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000');
    $request->setMethod(HTTP_METH_GET);

    $request->setHeaders([
      'Content-Type' => 'application/json'
    ]);

    try {
      $response = $request->send();

      echo $response->getBody();
    } catch (HttpException $ex) {
      echo $ex;
    }
    ```

    ### pecl/http 2

    ```php theme={"system"}
    <?php

    $client = new http\Client;
    $request = new http\Client\Request;

    $request->setRequestUrl('https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000');
    $request->setRequestMethod('GET');
    $request->setHeaders([
      'Content-Type' => 'application/json'
    ]);

    $client->enqueue($request)->send();
    $response = $client->getResponse();

    echo $response->getBody();
    ```

    ### cURL

    ```php theme={"system"}
    <?php

    $curl = curl_init();

    curl_setopt_array($curl, [
      CURLOPT_URL => "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000",
      CURLOPT_RETURNTRANSFER => true,
      CURLOPT_ENCODING => "",
      CURLOPT_MAXREDIRS => 10,
      CURLOPT_TIMEOUT => 30,
      CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
      CURLOPT_CUSTOMREQUEST => "GET",
      CURLOPT_HTTPHEADER => [
        "Content-Type: application/json"
      ],
    ]);

    $response = curl_exec($curl);
    $err = curl_error($curl);

    curl_close($curl);

    if ($err) {
      echo "cURL Error #:" . $err;
    } else {
      echo $response;
    }
    ```
  </Accordion>

  <Accordion title="Powershell">
    ### WebRequest

    ```powershell theme={"system"}
    $headers=@{}
    $headers.Add("Content-Type", "application/json")
    $response = Invoke-WebRequest -Uri 'https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000' -Method GET -Headers $headers
    ```

    ### RestMethod

    ```powershell theme={"system"}
    $headers=@{}
    $headers.Add("Content-Type", "application/json")
    $response = Invoke-RestMethod -Uri 'https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000' -Method GET -Headers $headers
    ```
  </Accordion>

  <Accordion title="R">
    ```r theme={"system"}
    library(httr)

    url <- "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000"

    response <- VERB("GET", url, add_headers(Content_Type = 'application/json'), content_type("application/octet-stream"))

    content(response, "text")
    ```
  </Accordion>

  <Accordion title="Ruby">
    ```ruby theme={"system"}
    require 'uri'
    require 'net/http'
    require 'openssl'

    url = URI("https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000")

    http = Net::HTTP.new(url.host, url.port)
    http.use_ssl = true
    http.verify_mode = OpenSSL::SSL::VERIFY_NONE

    request = Net::HTTP::Get.new(url)
    request["Content-Type"] = 'application/json'

    response = http.request(request)
    puts response.read_body
    ```
  </Accordion>

  <Accordion title="Swift">
    ```swift theme={"system"}
    import Foundation

    let headers = ["Content-Type": "application/json"]

    let request = NSMutableURLRequest(url: NSURL(string: "https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000")! as URL,
                                            cachePolicy: .useProtocolCachePolicy,
                                        timeoutInterval: 10.0)
    request.httpMethod = "GET"
    request.allHTTPHeaderFields = headers

    let session = URLSession.shared
    let dataTask = session.dataTask(with: request as URLRequest, completionHandler: { (data, response, error) -> Void in
      if (error != nil) {
        print(error)
      } else {
        let httpResponse = response as? HTTPURLResponse
        print(httpResponse)
      }
    })

    dataTask.resume()
    ```
  </Accordion>
</AccordionGroup>


# Slippage Calculation (for Uniswap V2 and its forks)
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/slippage-calculation-for-uniswap-v2-and-its-forks

GET https://api.diadata.org/v1/poolSlippage/{blockchain}/{pool_address}/{token1_address}/{pool_type}/{desired_slippage}
To predict the amount of tokens required to reach a specified slippage, you can use `Pool Slippage` endpoint. It works for any pool that exists on Uniswap V2 or any fork DEX on supported list of exchanges.

<Card title="Here is an exemplary API call" href="https://api.diadata.org/v1/poolSlippage/Ethereum/0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48/UniswapV2/100" icon="angle-right">
  [https://api.diadata.org/v1/poolSlippage/Ethereum/0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48/UniswapV2/100](https://api.diadata.org/v1/poolSlippage/Ethereum/0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48/UniswapV2/100)
</Card>

The logic is as follows:

Provide the address of the pool, select a token in which you wish to have slippage calculated (e.g. if selected ETH from ETH-USDC, it will show how much is ETH is required to move the price by selected amount) and determine the goal for price movement.

## Path Parameters

<ParamField type="string">
  Name of the blockchain of the requested pool (e.g. Ethereum, Moonbeam, etc.)
</ParamField>

<ParamField type="string">
  Address of the requested pool
</ParamField>

<ParamField type="string">
  Address of either of the tokens in the pool
</ParamField>

<ParamField type="string">
  Type of the pool (e.g. UniswapV2)
</ParamField>

<ParamField type="integer">
  Desired slippage in per mille (e.g. 100 will result in 10% slippage)
</ParamField>

<ResponseExample>
  ```json 200: OK theme={"system"}
  {
    // Response
  }
  ```
</ResponseExample>


# Token Price Quotation (by address)
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/token-price-quotation-by-address

GET https://api.diadata.org/v1/assetQuotation/{blockchain}/{asset}
Returns the quotation for a fully qualified asset (i.e. distinguished by blockchain and address). Quotations are obtained by filtering trades data with a Moving Average filter and Interquartile Range outlier detection (MAIR).

<Card title="Example" href="https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000" icon="angle-right">
  [https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000](https://api.diadata.org/v1/assetQuotation/Bitcoin/0x0000000000000000000000000000000000000000)
</Card>

## Path Parameters

<ParamField type="string">
  Name of the blockchain for requested asset
</ParamField>

<ParamField type="string">
  Address of the requested asset for this data
</ParamField>

<ResponseExample>
  ```json 200: OK Price information for a given asset theme={"system"}
  {
      "Symbol": "BTC",
      "Name": "Bitcoin",
      "Address": "0x0000000000000000000000000000000000000000",
      "Blockchain": "Bitcoin",
      "Price": 25703.376586196053,
      "PriceYesterday": 25815.29054321003,
      "VolumeYesterdayUSD": 1317774231.5192668,
      "Time": "2023-09-11T10:07:59.944Z",
      "Source": "diadata.org",
      "Signature": "0x8e0ffd0f2aac9306a6605e82f87856859b0666f1e600c9247b2935bfe52ded71061aa0c04e83dde4b6272a3057b5b93d9395ed5d8e1f033d1b25b04e73e1680101"
  }
  ```
</ResponseExample>


# Token Price Quotation (by symbol)
Source: https://www.diadata.org/docs/reference/apis/token-prices/api-endpoints/token-price-quotation-by-symbol

GET https://api.diadata.org/v1/quotation/{symbol}
Get most recent information on the currency corresponding to symbol. Quotations are obtained by filtering trades data with a Moving Average filter and Interquartile Range outlier detection (MAIR).

<Info>
  this endpoint is intended for testing purposes only; if multiple assets with
  the same symbol exists, data for the highest volume generating asset will be
  returned\*
</Info>

<Card title="Example" href="https://api.diadata.org/v1/quotation/BTC" icon="angle-right">
  [https://api.diadata.org/v1/quotation/BTC](https://api.diadata.org/v1/quotation/BTC)
</Card>

## Path Parameters

<ParamField type="string">
  Which symbol to get a quotation for, e.g., BTC.
</ParamField>

<ResponseExample>
  ```json 200: OK Price information for a given symbol theme={"system"}
  {
      "Symbol": "BTC",
      "Name": "Bitcoin",
      "Address": "0x0000000000000000000000000000000000000000",
      "Blockchain": "Bitcoin",
      "Price": 25692.061459484863,
      "PriceYesterday": 25825.253617593764,
      "VolumeYesterdayUSD": 1323023983.1804218,
      "Time": "2023-09-11T10:15:59.299Z",
      "Source": "diadata.org"
  }
  ```
</ResponseExample>


# GraphQL
Source: https://www.diadata.org/docs/reference/apis/token-prices/graphql

DIA made API data easily accessible through GraphQL endpoint.

You can use the following link to send GraphQL requests:

[`https://api.diadata.org/graphql/query`](https://api.diadata.org/graphql/query)

Also you can use a dedicated front-end to try out queries:

[`https://api.diadata.org/graphql/`](https://api.diadata.org/graphql/)

Currently only tokens price feed data is available on GraphQL.

Example of schema that can be used for quoting data:

<CodeGroup>
  ```bash Sample Schema theme={"system"}
  query  {
       GetFeed(
        Filter: "mair",
        BlockSizeSeconds: 480,
        BlockShiftSeconds: 480,
        StartTime: 1690449575,
        EndTime: 1690535975,
        FeedSelection: [
          {
            Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
            Blockchain:"Ethereum",
            Exchangepairs:[],
          },
        ],
      )
    {
      Name
      Time
      Value
      Pools
      Pairs
    }
  }
  ```
</CodeGroup>

The schema will return the moving average price of ETH calculated every 5min (300 sec) by counting 2min trade blocks.

## Query parameters rundown

| Parameter           | Description                                                                                                                                                                                                |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `filter`            | Select trades processing methodology (e.g. `VWAP`, `MAIR`, find out all available filters here)                                                                                                            |
| `BlockSizeSeconds`  | Determine the window for trades inclusion in seconds (e.g. `120` will include all trades into price calculation that happened during the last 2 minutes)                                                   |
| `BlockShiftSeconds` | Determine the frequency of price updates in seconds during the selected timeframe (e.g. `600` will return price for every 5min during the selected period)                                                 |
| `StartTime`         | The start time of the preferred period for price calculation in timestamp format (e.g. `1655084380` will start calculating price from 13.06.2022 01:39:40 GMT time)                                        |
| `EndTime`           | The end time of the preferred period for price calculation in timestamp format (e.g. `1655090649` will calculate price until 13.06.2022 03:24:09 GMT time)                                                 |
| `FeedSelection`     | This is the main module of the query which is responsible for parametrizing asset(s) for which the price data should be retrieved. Available parameters for `FeedSelection` are described in detail below. |

### `FeedSelection` filtering options

There are a number of ways to filter out exchanges with DIA's GraphQL endpoints.

First of all, you should define the desired asset. DIA uses blockchain-address asset identification methodology. You can search for available assets and find out blockchain/address information in the [DIA APP asset explorer](https://www.diadata.org/app/price/).

Here's an example how to define FeedSelection query to return a price for a given range with all sources included:

```json theme={"system"}
FeedSelection: [
        {
          Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
          Blockchain:"Ethereum",
          Exchangepairs:[],
        },
      ]
```

There are number of ways to filter desired sources from the entire sources library for a given asset. We'll go over examples of these filters.

To select specific exchanges you can use the following format:

```json theme={"system"}
FeedSelection: [
        {
          Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
          Blockchain:"Ethereum",
          Exchangepairs:[{Exchange:"CoinBase"},{Exchange:"UniswapV3"}],
        },
      ]
```

It is also possible to select specific pairs from a given exchange. The query would look as follows:

```json theme={"system"}
FeedSelection: [
        {
          Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
          Blockchain:"Ethereum",
          Exchangepairs:[
            {
              Exchange: "CoinBase",
              Pairs:["DAI-USD"],
            },
            {
              Exchange: "UniswapV3",
              Pairs:["0x60594a405d53811d3BC4766596EFD80fd545A270","0x6f48ECa74B38d2936B02ab603FF4e36A6C0E3A77"],
            },
       ]
```

Another filtering option is to include sources based on available liquidity in the pool. For example if you select a liquidity threshold of $5 000 000, the response will calculate the price of an asset only by including liquidity pools from DEXes which have higher than $5 000 000 liquidity. The query looks as follows:

```json theme={"system"}
FeedSelection: [
          {
          Address: "0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599",
          Blockchain:"Ethereum",
          LiquidityThreshold:5000000.0
          Exchangepairs: [],
          },
       ]
```

It is also possible to merge pairs selection with `LiquidityThreshold`, which would result in such query:

```json theme={"system"}
FeedSelection: [
        {
          Address: "0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599",
          Blockchain:"Ethereum",
          Exchangepairs:[
            {
              Exchange: "CoinBase",
              Pairs:["DAI-USD"],
            },
          ]
        },
        {
          Address: "0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599",
          Blockchain:"Ethereum",
          LiquidityThreshold:5000000.0
          Exchangepairs: [],
        },
      ],
```

One more option is to use two different assets to calculate one unified price. It might be useful for cross-chain assets, e.g. DAI on ETH mainnet & DAI on Arbitrum One. The query which can be used for such cases would look as follows:

```json theme={"system"}
FeedSelection: [
        {
          Address: "0x2260FAC5E5542a773Aa44fBCfeDf7C193bc2C599",
          Blockchain:"Ethereum",
          Exchangepairs:[]
        },
        {
          Address: "0xda10009cbd5d07dd0cecc66161fc93d7c9000da1",
          Blockchain:"Arbitrum",
          Exchangepairs:[]
        },
      ],
```

## Response fields

In the table below you can find the description of response fields:

| Field      | Description                                                                                         |
| ---------- | --------------------------------------------------------------------------------------------------- |
| Time       | Time at which the value was generated                                                               |
| Value      | Price of an asset at a give time                                                                    |
| Pools      | Pools which had a trade during the block time period and were involved in the price calculation     |
| Pairs      | CEX pairs which had a trade during the block time period and were involved in the price calculation |
| Blockchain | Blockchain of an asset                                                                              |
| Address    | Address of an asset                                                                                 |


# Request Samples
Source: https://www.diadata.org/docs/reference/apis/token-prices/graphql/request-samples

You can find examples of how to query the endpoint in different programming languages below:

<AccordionGroup>
  <Accordion title="Python">
    ```python theme={"system"}
    import requests
    import json

    url = "https://api.diadata.org/graphql/query"

    query = """
    {
    GetFeed(
          Filter: "mair",
          BlockSizeSeconds: 480,
          BlockShiftSeconds: 480,
          StartTime: 1690449575,
          EndTime: 1690535975,
          FeedSelection: [
            {
              Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
              Blockchain:"Ethereum",
              Exchangepairs:[],
            },
          ],
        )
      {
        Name
        Time
        Value
        Pools
        Pairs
      }
    }
    """

    headers = {
        "Content-Type": "application/json"
    }

    data = {
        "query": query
    }

    response = requests.post(url, headers=headers, data=json.dumps(data))

    if response.status_code == 200:
        # Print the response content
        print(response.json())
    else:
        print("Request failed with status code:", response.status_code)
    ```
  </Accordion>

  <Accordion title="GO">
    ```go theme={"system"}
    package main

    import (
    	"bytes"
    	"encoding/json"
    	"fmt"
    	"net/http"
    )

    func main() {
    	url := "https://api.diadata.org/graphql/query"

    	query := `
    		GetFeed(
          			Filter: "mair",
          			BlockSizeSeconds: 480,
          			BlockShiftSeconds: 480,
          			StartTime: 1690449575,
          			EndTime: 1690535975,
          			FeedSelection: [
            		{
              		Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
              		Blockchain:"Ethereum",
              		Exchangepairs:[],
            		},
          		],
        	)
      			{
       			Name
       			Time
        			Value
        			Pools
        			Pairs
      			}
    		}
    	`
    	requestBody, err := json.Marshal(map[string]string{
    		"query": query,
    	})
    	if err != nil {
    		fmt.Println("Failed to create request body:", err)
    		return
    	}

    	response, err := http.Post(url, "application/json", bytes.NewBuffer(requestBody))
    	if err != nil {
    		fmt.Println("Request failed:", err)
    		return
    	}
    	defer response.Body.Close()

    	if response.StatusCode == http.StatusOK {
    		var data map[string]interface{}
    		err = json.NewDecoder(response.Body).Decode(&data)
    		if err != nil {
    			fmt.Println("Failed to decode response JSON:", err)
    			return
    		}

    		fmt.Println(data)
    	} else {
    		fmt.Println("Request failed with status code:", response.StatusCode)
    	}
    }
    ```
  </Accordion>

  <Accordion title="JavaScript">
    ```javascript theme={"system"}
    const axios = require('axios');

    const url = 'https://api.diadata.org/graphql/query';

    const query = `
      {
        GetFeed(
          Filter: "mair",
          BlockSizeSeconds: 480,
          BlockShiftSeconds: 480,
          StartTime: 1690449575,
          EndTime: 1690535975,
          FeedSelection: [
            {
              Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
              Blockchain:"Ethereum",
              Exchangepairs:[],
            },
          ],
        )
      {
        Name
        Time
        Value
        Pools
        Pairs
      }
    }  }
    `;

    const data = {
      query: query
    };

    axios.post(url, data)
      .then(response => {
        console.log(response.data);
      })
      .catch(error => {
        console.error('Request failed:', error.message);
      });
    ```
  </Accordion>

  <Accordion title="Node">
    ```javascript theme={"system"}
    const fetch = require('node-fetch');

    const url = 'https://api.diadata.org/graphql/query';

    const query = `
      {
    GetFeed(
          Filter: "mair",
          BlockSizeSeconds: 480,
          BlockShiftSeconds: 480,
          StartTime: 1690449575,
          EndTime: 1690535975,
          FeedSelection: [
            {
              Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
              Blockchain:"Ethereum",
              Exchangepairs:[],
            },
          ],
        )
      {
        Name
        Time
        Value
        Pools
        Pairs
      }
    }
    `;

    const data = JSON.stringify({ query });

    fetch(url, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: data
    })
      .then(response => response.json())
      .then(data => {
        console.log(data);
      })
      .catch(error => {
        console.error('Request failed:', error);
      });
    ```
  </Accordion>

  <Accordion title="Rust">
    ```rust theme={"system"}
    use reqwest;
    use serde_json::json;

    #[tokio::main]
    async fn main() -> Result<(), Box<dyn std::error::Error>> {
        let url = "https://api.diadata.org/graphql/query";

        let query = r#"
            {
                {
    GetFeed(
          Filter: "mair",
          BlockSizeSeconds: 480,
          BlockShiftSeconds: 480,
          StartTime: 1690449575,
          EndTime: 1690535975,
          FeedSelection: [
            {
              Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
              Blockchain:"Ethereum",
              Exchangepairs:[],
            },
          ],
        )
      {
        Name
        Time
        Value
        Pools
        Pairs
      }
    }
        "#;

        let data = json!({
            "query": query,
        });

        let client = reqwest::Client::new();
        let response = client
            .post(url)
            .json(&data)
            .send()
            .await?;

        if response.status().is_success() {
            let body = response.text().await?;
            println!("{}", body);
        } else {
            println!("Request failed with status code: {}", response.status());
        }

        Ok(())
    }
    ```
  </Accordion>

  <Accordion title="PHP">
    ```php theme={"system"}
    <?php

    $url = 'https://api.diadata.org/graphql/query';

    $query = '
      {
    GetFeed(
          Filter: "mair",
          BlockSizeSeconds: 480,
          BlockShiftSeconds: 480,
          StartTime: 1690449575,
          EndTime: 1690535975,
          FeedSelection: [
            {
              Address: "0x6B175474E89094C44Da98b954EedeAC495271d0F",
              Blockchain:"Ethereum",
              Exchangepairs:[],
            },
          ],
        )
      {
        Name
        Time
        Value
        Pools
        Pairs
      }
    }
    ';

    $data = array(
        'query' => $query
    );

    $options = array(
        CURLOPT_URL => $url,
        CURLOPT_POST => true,
        CURLOPT_POSTFIELDS => json_encode($data),
        CURLOPT_HTTPHEADER => array(
            'Content-Type: application/json'
        ),
        CURLOPT_RETURNTRANSFER => true
    );

    $ch = curl_init();

    curl_setopt_array($ch, $options);

    $response = curl_exec($ch);

    if (curl_errno($ch)) {
        echo 'Request failed with error: ' . curl_error($ch);
    } else {
        echo $response;
    }

    curl_close($ch);
    ?>
    ```
  </Accordion>
</AccordionGroup>