📄 Chain Integration Process
This page lacks a description under H1.
1. Retrieve New Chains Batch
Leadership and the Business Development (BD) team initiate chain integration requests based on strategic opportunities and the goals of ongoing projects
2. Submission and Approval
Ensure that
- The chains and related dAPIs have been submitted and approved through the #chain-integration-request channel.
- The chain mainnet will support OEV service by confirming that its gas token is viable. A chain mainnet for which OEV won't be supported should not be integrated.
- Only testnets whose mainnets meet the above integration requirements are added to the pipeline.
3. Confirm Infrastructure Details
Confirm the chain's infrastructure details (e.g., chainID, block explorer, deployer wallet funding) with Bedirhan and Hayrettin. Add the chains (and their related metadata) by order of priority to the list in the Csur sheet, to be planned through the integration pipeline. Also, add the related dAPIs required in the dAPIs needed related cells and add these dAPIs to the list in the dAPIs Nodary sheet.
4. Schedule Chains for Survey
When the survey batch reaches the top of the list, decide with the integration team when the chains should be surveyed and add the Csur batch to the GH issues batches sheet with the relevant planned date. A Csur batch should typically not exceed 5 chains, and it is recommended to pick the top 5 chains from the list by order of priority.
5. Preliminary Issue Creation for Chains Repo
Reach out to Hayrettin (about 2 days in advance of the Csur checklist date) for him to create an issue in the tasks repo from this issue template set-up-chains-for-csur.md in order to add the new chains and their metadata to api3dao/contracts/tree/main/data/chains and to deploy key contracts on these chains.
6. Create Csur Issue
When the above issue is completed and the Csur batch date is confirmed at the integration call, create the Csur issue in the data-feeds repo and move it to TODO. The chains names should be added in the Csur issue description by alphabetical order and using the exact chain aliases as the chains repo.
7. Update Csur and Cint Lists
When the Csur issue is completed, remove the chains from the Csur sheet list and transfer them to the bottom of the list in the Cint sheet with the related metadata about the chains and survey start date.
8. Survey and Integration Planning
Wait for the standard survey time to lapse (15 days for mainnets and 7 days for testnets). If urgent, go directly to step 9 below and hardcode the prices during integration as needed. Note that if needed, the survey time can be skipped by about a day without hardcoding requirements.
9. Integration of Surveyed Chains
For chains that have been surveyed through a Csur and need to be integrated into the market, ensure that the chains have completed their survey time. Pick up 5 chains by order of priority from the top of the list in the Cint tab. Coordinate with the integration team to establish a timeline for the new chain integrations. This alignment should happen either during the integration call or via the team group chat. Create a Cint issue for the batch of chains and add them in the description by alphabetical order and using the exact chain aliases as the chains repo.
10. Verification and Final Steps
Once the Cint issue is completed, verify that the chains are displayed on the market: Buy a test subscription and verify that the oracle updates occur correctly for the purchased subscriptions. A standard test subscription of USDT/USD with 5% threshold can be purchased so that the Api3 team can verify that it updates correctly. Once the subscriptions have updated, the related chains rows can be deleted from the Cint sheet. Inform the team that the chains have been integrated
Regular Weekly Housekeeping Tasks
- Daily checks of the Integration Pipeline worksheet for management and planning of integrations.