Introducing DIA CDRs — Custom Delivery Requests
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.
Overview
Oracles secure smart contracts which in turn lock hundreds of millions of dollars of capital. As a critical layer in the Web3 value stack, oracles require both high standards of quality in terms of technological implementation, as well as transparency about what specifically is implemented.
In order to evaluate how smart contracts function it is not only critical that the developers of a project receive a feed that reliably delivers what they demand, but that all stakeholders have insight into the specifications of a data feed.
DIA is an open-source oracle platform and a DAO. As such, it is intended to leverage decentralised and autonomous processes to deliver its product and services. This approach promotes public and transparent processes both for sourcing as well as requesting and delivering data feeds, which naturally adds a layer of public scrutiny and validation to the data feeds being delivered.
Today, in an effort to push further the decentralisation of DIA’s product delivery, DIA announces a new DAO module: ‘Custom Delivery Requests’, or, ‘CDRs’.
What is a ‘Custom Delivery Request’?
CDRs 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: Asset price feed / NFT Floor price / 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.
Resources
In order to complete all specifications and parameters of the DIA CDRs, users can access the DIA Platform’s available resources via the links below:
Create a CDR for your Smart Contract now
Are you a developer building a dApp and need a custom-made trusted oracle? Head over to the DIA DAO Forum and request your data feed by creating a DIA CDR.
