Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent blockchain names on volume endpoints for DEXes and Derivatives #1768

Open
JoaoVasques opened this issue Oct 11, 2024 · 0 comments

Comments

@JoaoVasques
Copy link
Contributor

JoaoVasques commented Oct 11, 2024

Context

I am using the folllowing endpoints to pull data for volume

  1. DEXes - https://api.llama.fi/overview/dexs?excludeTotalDataChart=true&excludeTotalDataChartBreakdown=true&dataType=dailyVolume
  2. Derivatives - https://api.llama.fi/overview/derivatives?excludeTotalDataChart=true&excludeTotalDataChartBreakdown=true

Problem

Inside each protocol that contains the volume data there are two fields I am using. One is chains to get the list of available blockchains, the other is breakdown24h. I have noticed that some names in chains don't have a direct mapping (even using lower casing) to their counterparts in breakdown24h. The following image shows and example for the opBNB chain

Screenshot 2024-10-10 at 19 00 29

I have also detect some additional inconsistencies that I am sharing in the following mapping

    mapping = {
        "opBNB": "op_bnb",
        "Gnosis": "xdai",
        "ZKsync Era": "era",
        "Cronos zkEVM": "cronos_zkevm",
        "Polygon zkEVM": "polygon zkevm",
        "X Layer": "xlayer",
        "Avalanche": "avax",
        "ZetaChain": "zeta",
    }

Questions

  1. Why does this inconsistency exists?
  2. Is there any endpoint that I can use to resolve them?

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant