Skip to main content

📄 dAPI Management Merkle Tree Signing Checklist Steps

TODO

This page could benefit from a description under H1 here. OR in frontMatter.description then display in whole or in part, example: {frontmatter.description} And further more you can proceed to ...

ℹī¸ In case you encounter an issue while pushing signatures or pulling the most recent changes, it is advised to restart the checklist steps from the beginning (i.e. Reclone the repo ...)

  • Identify the correct PR: Identified the correct PR related to the MT update (e.g., Dint-2024-05-17).

  • Checkout the PR locally: Clone or switch to the correct branch (e.g., git clone --depth 1 -b Dint-2024-05-17 https://github.com/api3dao/data-feeds.git or git checkout Dint-2024-05-17).

  • Run the dapi-management FE locally: Navigate to packages/dapi-management and execute pnpm frontend:prod

  • Access the dAPI Management menu on the dapi-management FE and connect your relevant signing wallet address as recorded in dapi-management/data/dapi-management-merkle-tree-root/hash-signers.json.

  • Review FE Data: Ensure all displayed data is accurate:

    • Check for warning signs (e.g., deviations in API values) and investigate the tooltips for issues details.
    • Address any warnings by investigating and correcting issues, such as replacing API providers or fixing airnode feeds. Remove problematic dAPIs or providers as needed.
    • Cross-verify all dAPI values with external sources for accuracy (e.g., compare AAPL/USD values with actual market rates).
    • Ensure all listed API providers are up-to-date and relevant.
    • Examine tree diffs to understand the changes you're signing, with a focus on the most recent modifications. Access raw data if necessary.
    • Ensure additional notes (e.g. reconfiguration of some dAPIs in dapis.json) present in the issue description or in the comments, that are relevant to the dAPI management MT are addressed.

  • CI Checks Before Signing: Pull the latest PR updates to avoid signature conflicts. Check CI status, CI might fail due to missing signatures. If CI fails for reasons other than missing signatures, investigate and resolve before signing.

  • Sign and Confirm CI:

    • Hash signers: click "sign root" and sign with your wallet.
    • Delegates: click "sign root as delegate", choose the hash signer's name you're delegate for from the dropdown, and sign with your wallet.
    • Commit and push your signature to the PR and ensure CI tests pass.
Owner: UNKNOWN
Last updated on by Warren Anderson