📄 dAPI integration Process

1. Request Initiation: Leadership and the Business Development (BD) team initiate dAPI integration requests based on strategic opportunities and the goals of ongoing projects.

2. Eliminate Ambiguity: Include a link to the asset from an exchange platform to eliminate any ambiguity about the requested feed.

3. Ensure Sufficient Information: Provide detailed information in the request, especially for exchange rates. This should include:

   • Exact name to be listed on the Market (e.g., X/Y Exchange Rate).
   • Confirm the category of the requested feed
   • A link to the contract function(s) to call. (for exchange Rate)
   • Instructions on how the rate/value should be calculated. (For exchange Rate)

4. Verify Asset Names: Confirm the correct name of each asset in the requested pairs.

5. Approval: Ensure Ugur approves the listing before proceeding.

6. Request Nodary Support:

   • Request that the feed is supported by Nodary using the nodary-add-feed template
   • Convey any urgency related to it.

   The Nodary support requests can be tracked in the dAPIs Nodary sheet

7. Assess Provider Support: Simultaneously to the Nodary support request, start assessing Provider Support for the feed using the MockFint template. This involves:

   • Identifying providers that support the feed.
   • Requesting support from providers that do not yet support it.

   The Providers support assessment requests can be tracked in the dAPIs Providers sheet

8. Nodary and Provider Support: Once Nodary supports the feeds and they have been assessed for provider support, the feeds are included into provider mock deployments and are ready to be surveyed. The feeds ready for survey can be tracked in the Dsur sheet

9. Schedule Fints:

• After completing the provider support assessment, schedule Fints (see fint) to allow providers to redeploy their airnode-feeds with the newly supported feeds.
• This Fint is required before the feed is listed with providers that support it.
• The current setup schedules a round of Fints with providers monthly.
• Ensure as many feeds as possible are being surveyed before the next Fints round to maximize efficiency.

The feeds scheduled for fint can be tracked in the Fint sheet

11. Survey Period:

    • The feeds are surveyed for 15 days before they can be listed (see dint). A minimum of 13 days of survey is acceptable.
    • If the survey period is less than 13 days, it is considered skipped and will require to be hardcoded in config.json.
    • When this happens, a task to recalculate the feed price should be scheduled for a time (preferably during a checklist Pricing MT step) after the initially intended survey period is completed (e.g., if 10 days of survey were skipped, the price should be recalculated after 10 days).

    The feeds being survey and awaiting to be integrated can be tracked in the Dint sheet.

---

Owner: Prenaam