Skip to content

Remove Exponent Fees - Inaccurate data#5669

Draft
valentinmadrid wants to merge 1 commit intoDefiLlama:masterfrom
valentinmadrid:master
Draft

Remove Exponent Fees - Inaccurate data#5669
valentinmadrid wants to merge 1 commit intoDefiLlama:masterfrom
valentinmadrid:master

Conversation

@valentinmadrid
Copy link
Copy Markdown

@valentinmadrid valentinmadrid commented Jan 20, 2026

NOTE

Please enable "Allow edits by maintainers" while putting up the PR.


  • If you would like to add a tvl adapter please submit the PR here.
  1. Once your adapter has been merged, it takes time to show on the UI. If more than 24 hours have passed, please let us know in Discord.
  2. Please fill the form below only if the PR is for listing a new protocol else it can be ignored/replaced with reason/details about the PR
  3. For updating listing info It is a different repo, you can find your listing in this file: https://github.com/DefiLlama/defillama-server/blob/master/defi/src/protocols/data4.ts, you can edit it there and put up a PR
  4. Do not edit/push package.json/package-lock.json file as part of your changes
  5. No need to go to our discord/other channel and announce that you've created a PR, we monitor all PRs and will review it asap

Name (to be shown on DefiLlama):

Exponent

--

Thanks for adding the fee tracker to the Exponent DefiLlama page.

We noticed that the current fee data isn't quite correct. Since we want the numbers on DefiLlama to be accurate and reliable, we're working on tooling to make fee parsing clearer on our end, and we'll open a PR once that's ready.

It would also be great to have a direct way to communicate (Slack/Telegram) to coordinate more easily, do you have a standard process for that?

Best, Valentin.

Summary by CodeRabbit

  • Chores
    • Removed Exponent fee data adapter

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Jan 20, 2026

📝 Walkthrough

Walkthrough

The entire fees/exponent/index.ts module was removed, eliminating the Exponent protocol fee adapter that previously aggregated daily fees and revenue data from Solana-based Exponent markets and vaults using treasury account balance computations and SY token unwrapping.

Changes

Cohort / File(s) Summary
Module Removal
fees/exponent/index.ts
Entire file deleted (−191 lines). Removes adapter with Exponent market/vault fee orchestration, including helpers for token account data retrieval, SY token mapping, balance unwrapping, and SimpleAdapter export.

Possibly related PRs

  • Exponent fees #5188: Introduced the fees/exponent/index.ts module and SimpleAdapter export that this PR removes.

Poem

🐰 A module takes its final bow,
Exponent fees must leave us now,
No more treasuries to explore,
SY tokens unwrapped no more. 🌙

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The PR description includes repository guidelines but lacks specific details about why the data is inaccurate and the expected resolution timeline. Provide more specific details about the inaccuracy, the tooling being developed, and the expected timeline for the follow-up PR with corrected fee parsing.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change—removal of the Exponent Fees adapter due to inaccurate data.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@noateden
Copy link
Copy Markdown
Contributor

hello, can you share how data is inaccurate? we will fix it

@noateden noateden self-assigned this Jan 28, 2026
@noateden noateden marked this pull request as draft January 28, 2026 08:51
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.

2 participants