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

shadow: add legacy fees and volume #2410

Merged
merged 1 commit into from
Feb 12, 2025
Merged

Conversation

morazzela
Copy link
Contributor

No description provided.

@llamabutler
Copy link

The shadow-exchange.ts adapter exports:

> [email protected] test
> ts-node --transpile-only cli/testAdapter.ts protocols shadow-exchange.ts

🦙 Running SHADOW-EXCHANGE.TS adapter 🦙
---------------------------------------------------
GRAPH_API_KEY env variable is not set, using the default api key
Start Date:	Tue, 11 Feb 2025 00:49:29 GMT
End Date:	Wed, 12 Feb 2025 00:49:29 GMT
---------------------------------------------------

ClientError: auth error: payment required for subsequent requests for this API key: {"response":{"errors":[{"message":"auth error: payment required for subsequent requests for this API key"}],"status":200,"headers":{}},"request":{"query":"\n      {\n        clPoolDayDatas(where:{startOfDay: 1739318400}) {\n          startOfDay\n          volumeUSD\n          feesUSD\n        }\n        legacyPoolDayDatas(where:{startOfDay: 1739318400}) {\n          startOfDay\n          volumeUSD\n          feesUSD\n        }\n      }\n  "}}
    at /home/runner/work/dimension-adapters/dimension-adapters/node_modules/graphql-request/src/index.ts:498:11
    at step (/home/runner/work/dimension-adapters/dimension-adapters/node_modules/graphql-request/dist/index.js:67:23)
    at Object.next (/home/runner/work/dimension-adapters/dimension-adapters/node_modules/graphql-request/dist/index.js:48:53)
    at fulfilled (/home/runner/work/dimension-adapters/dimension-adapters/node_modules/graphql-request/dist/index.js:39:58)
    at processTicksAndRejections (node:internal/process/task_queues:95:5) {
  response: {
    errors: [ [Object] ],
    status: 200,
    headers: Headers { [Symbol(map)]: [Object: null prototype] }
  },
  request: {
    query: '\n' +
      '      {\n' +
      '        clPoolDayDatas(where:{startOfDay: 1739318400}) {\n' +
      '          startOfDay\n' +
      '          volumeUSD\n' +
      '          feesUSD\n' +
      '        }\n' +
      '        legacyPoolDayDatas(where:{startOfDay: 1739318400}) {\n' +
      '          startOfDay\n' +
      '          volumeUSD\n' +
      '          feesUSD\n' +
      '        }\n' +
      '      }\n' +
      '  ',
    variables: undefined
  },
  chain: 'sonic'
}

@dtmkeng dtmkeng merged commit bb6a95d into DefiLlama:master Feb 12, 2025
2 checks passed
@morazzela
Copy link
Contributor Author

@dtmkeng
do i have to make a different folder to separate Shadow V2 and Shadow Legacy revenues?

@dtmkeng
Copy link
Contributor

dtmkeng commented Feb 12, 2025

yes, you should create new one for Legacy and CLMM

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

Successfully merging this pull request may close these issues.

3 participants