📄 Pipeline for Chains, dAPIs, and Providers Api3 Market operations
This document is now maintained as a dynamic Google Sheet to provide real-time updates on the chains and dAPIs we plan to survey, integrate, deprecate, and retire. The live list allows us to prioritize our efforts effectively and track new blockchain projects and dAPIs; Integration Pipeline.
Lists of Chains
Chains to Survey
In the chains to survey list available on the Csur candidates sheet, chains are ordered by priority based on their potential and relevance to our goals. This list is live and will be updated as new chains emerge and as our focus shifts based on new projects' needs.
Chains to Integrate
Following surveys, chains that meet our criteria for integration are prioritized in the chains to integrate list available on the Cint candidates sheet.
Chains to Deprecate
Integrated chains that meet our criteria for deprecation are prioritized in the chains to deprecate list available on the Cdep candidates sheet.
Chains to Retire
- Deprecated chains that meet our criteria for retirement are prioritized in the chains to retire list available on the Cret candidates sheet.
- Chains are retired only after all active subscriptions have expired and active users are notified.
Workflow for Chain Management
- The Csur candidates sheet maintains a list of chains to be surveyed in the listed order of priority.
- The Cint candidates sheet maintains a list of chains to be integrated in the listed order of priority.
- We typically should have only one active checklist at a time, whether it is a chains-related checklist or a dAPIs-related checklist.
- When we complete a checklist (e.g.,
CsurorCint), we decide if we will survey or integrate chains next. - We then pick a maximum of 5 chains from the top of the respective list, create an issue with it just in time, and move it to In Progress.
- The Cdep candidates sheet maintains a list of chains to be deprecated in the listed order of priority.
- The Cret candidates sheet maintains a list of chains to be retired in the listed order of priority.
Lists of dAPIs
dAPIs to be added to Nodary
- In the dAPIs to be added to Nodary list available on the dAPIs Nodary sheet, dAPIs' names are ordered by priority based on their potential and relevance to our goals.
- Nodary support is a mandatory step before any dAPI is integrated
- This list is live and will be updated as new dAPIs candidates emerge and as our focus shifts based on new projects' needs.
dAPIs to be supported by other Providers
The list of dAPIs to be supported by other providers is available on the dAPIs Providers sheet. dAPIs are ordered by priority based on their potential and relevance to our goals. This list is live and will be updated as new dAPIs candidates emerge and as our focus shifts based on new projects' needs.
dAPIs to Survey
In the dAPIs to survey list available on the Dsur candidates sheet, dAPIs are ordered by priority based on their potential and relevance to our goals. This list is live and will be updated as new dAPIs candidates emerge and as our focus shifts based on new projects' needs.
dAPIs to Integrate
Following surveys, dAPIs that meet our criteria for integration are prioritized in the dAPIs to integrate list available on the Dint candidates sheet.
dAPIs to be integrated by other Providers
dAPIs supported by providers other than Nodary need to be integrated into Providers' airnode-feeds. These dAPIs are tracked and prioritized in the Fint sheet. This is a mandatory step for dAPIs reconfiguration.
dAPIs to Reconfigure
Integrated dAPIs that need to be reconfigured are prioritized in the dAPIs to reconfigure list available on the Dre candidates sheet.
dAPIs to Deprecate
- Integrated dAPIs that meet our criteria for deprecation are prioritized in the dAPIs to deprecate list available on the Ddep candidates sheet.
- dAPIs scheduled for retirements (see when should a dapi be retired) are first deprecated, often to prevent new subscriptions while existing subscriptions expire.
dAPIs to Retire
- Deprecated dAPIs that meet our criteria for retirement are prioritized in the dAPIs to retire list available on the Dret candidates sheet.
- dAPIs are retired only after all active subscriptions across chains have expired and active users are notified.
Workflow for dAPIs Management
- The dAPIs Nodary sheet maintains a list of dAPIs to be added by Nodary in the listed order of priority.
- The dAPIs Providers sheet maintains a list of dAPIs to be supported by other providers.
- The Dsur candidates sheet maintains a list of dAPIs to be surveyed in the listed order of priority.
- The Dint candidates sheet maintains a list of dAPIs to be integrated in the listed order of priority.
- We typically should have only one active checklist at a time, whether it is a chains-related checklist or a dAPIs-related checklist.
- When we complete a checklist (e.g.,
DsurorDint), we decide if we will survey or integrate dAPIs next. - The Fint sheet maintains a list of dAPIs that need to be integrated into Providers' airnode-feeds.
- The Dre candidates sheet maintains a list of integrated dAPIs that need to be reconfigured.
- We then pick a maximum of 5 dAPIs from the top of the respective list, create an issue with it just in time, and move it to In Progress.
- The Ddep candidates sheet maintains a list of dAPIs to be deprecated in the listed order of priority.
- The Dret candidates sheet maintains a list of dAPIs to be retired in the listed order of priority.
Planning and Stats sheets
Upcoming operations
The GH Issue batches sheet is our central hub for planning and tracking operations across chains, dAPIs, and providers. To streamline our delivery pipeline and coordinate team efforts, we group related operations into combined GitHub issues. This sheet is also used to log relevant context, flag potential blockers, and view all upcoming operations sorted chronologically by their target date.
Operations follow-up actions
Some operations require temporary configurations that must be reverted in a later operation. For example, if a chain or dAPI uses hardcoded pricing because its survey was skipped before integration, that pricing should be removed once the normal survey period has passed. These follow-up tasks are tracked in the Follow-up GH issues sheet. To reduce operational burden, these actions are aligned with upcoming operations so they are not overlooked.
Operations Stats
We track our core operational metrics in the Stats sheet. This document provides a comprehensive list and tally of all integrated and retired chains, dAPIs, and providers across monthly, quarterly, and annual timeframes. For historical data from last year, please refer to the Stats 2025 sheet.
Contribution Guidelines
- The lists of chains and dAPIs are currently maintained by the TM team based on recommendations and priorities defined by the leadership.
- If you wish to discuss or suggest the integration of new projects, please liaise with the TM or Leadership directly.
- To contribute to this list, the steps are typically as follows:
- Identify New blockchain projects or assets: Keep an eye on new projects, technologies, and narratives in the blockchain space.
- Add to the List: Liaise with the TM and Leadership, and if a new blockchain and/or crypto assets align with our integration criteria, suggest adding it to the lists.
- Review: Regularly review the lists to ensure they are up-to-date and to prioritize integration based on relevance and feasibility.
Notes
- The TM team is responsible for editing and maintaining the live lists of chains and dAPIs.
- The lists are for internal documentation purposes only and should be regularly updated by the assigned individuals or teams.
- Any chain that is planned for integration should have its corresponding native currency added to the list of dAPIs to integrate.
- The Google Sheet should only be updated by authorized TM team members to ensure data integrity and accuracy.
- The credibility and viability of chains and dAPIs must be thoroughly vetted before they can be added to our survey or integration lists.