Introduction to CDRs
DIA CDRs are designed to provide an open process for dApps to request custom data feeds while providing full public transparency on the specific implementation of the oracle, including sources, methodologies and other specifications.

What is a CDR?

CDRs (Custom Delivery Requests) are mechanisms for dApps to publicly request custom data feeds from DIA. CDRs allow any market actor to independently request any data feeds with fully customized specifications regarding sources and methodologies, as well as to update the delivery requests further down the line.
Additionally, the DIA CDRs enable dApps ingesting DIA data feeds to offer full transparency to their users on how the data they leverage to power the application is being built. All DIA CDRs will be processed and stored in the DIA DAO Forum and they will be free and open for anybody to access.

How to submit a CDR?

CDRs can be submitted in the DIA DAO Forum by opening a new topic under the CDRs category. When doing so, a template will load on-screen that users will need to fill in and submit. Here is an overview of what it entails:
CDR #001: Protocol Name, Product Type

dApp introduction

Overview of the protocol

Feed usage

A quick introduction to the data type and the use case it will enable:
  • Data type: Price feed / Index / other
  • Use case: Lending and borrowing / Stablecoin / Gaming / other

Specifications

Technical details to build the data feed. Consisting of:
  • Delivery method: off-chain (signed API) / on-chain (network, mainnet/testnet)
  • Update mechanism: e.g. block-based / deviation-based / time-based / other
  • Methodology: e.g. MA / MAIR / MEDIR / VWAP / VWAPIR / other
  • Frequency: e.g. 10s / 20s / 60s / 120s / 5m / other
  • Sources (by chain/version): e.g UniSwap V2 β€” ETH
  • Pairs: e.g BTC/USD

Other relevant information

Any other data feed related parameters that are not listed above.
Find out step-by-step process in the following page: