Update reservoir protocol assets

[eukadish]

NOTE

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

---

1. If you would like to add a volume/fees/revenue adapter please submit the PR here.

2. 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.

3. Sorry, We no longer accept fetch adapter for new projects, we prefer the tvl to computed from blockchain data, if you have trouble with creating a the adapter, please hop onto our discord, we are happy to assist you.

4. For updating listing info It is a different repo, you can find your listing in this file, you can edit it there and put up a PR

5. Please do not add new npm dependencies, do not edit/push pnpm-lock.yaml file as part of your changes

---

(Needs to be filled only for new listings)

Name (to be shown on DefiLlama):

Twitter Link:

List of audit links if any:

Website Link:

Logo (High resolution, will be shown with rounded borders):

Current TVL:

Treasury Addresses (if the protocol has treasury)

Chain:

Coingecko ID (so your TVL can appear on Coingecko, leave empty if not listed): (https://api.coingecko.com/api/v3/coins/list)

Coinmarketcap ID (so your TVL can appear on Coinmarketcap, leave empty if not listed): (https://api.coinmarketcap.com/data-api/v3/map/all?listing_status=active,inactive,untracked&start=1&limit=10000)

Short Description (to be shown on DefiLlama):

Token address and ticker if any:

Category (full list at https://defillama.com/categories) *Please choose only one:

Oracle Provider(s): Specify the oracle(s) used (e.g., Chainlink, Band, API3, TWAP, etc.):

Implementation Details: Briefly describe how the oracle is integrated into your project:

Documentation/Proof: Provide links to documentation or any other resources that verify the oracle's usage:

forkedFrom (Does your project originate from another project):

methodology (what is being counted as tvl, how is tvl being calculated):

Github org/user (Optional, if your code is open source, we can track activity):

Does this project have a referral program?

Summary by CodeRabbit

• New Features

  • Extended protocol support to additional blockchains with new chain integrations.

• Chores

  • Updated and expanded token/owner configurations across multiple supported blockchains to improve tracking coverage
  • Simplified TVL calculation mechanism for improved stability and reliability
  • Enhanced supported token pair listings to include additional stablecoins and protocol tokens

[coderabbitai]

📝 Walkthrough

Walkthrough

This change removes dynamic Reservoir reserves caching and replaces it with static configuration. The Ethereum setup is substantially updated with modified fund addresses and an expanded set of token/owner pairs across multiple protocols. Configuration is extended to support three new chains (bsc, monad, hyperliquid) and includes token/owner mappings for previously empty chains (mantle, optimism), plus updates to existing multi-chain configurations.

Changes

Cohort / File(s)	Summary
Caching mechanism removal projects/reservoir-protocol/index.js	Removed the getConfig cached fetch of Reservoir reserves that dynamically populated tokensAndOwners with [token, owner] pairs and associated console logging. tvl now relies entirely on static config[api.chain] data.
Ethereum configuration overhaul projects/reservoir-protocol/index.js	Updated Ethereum funds list (removed 2 addresses, added 1 Gauntlet USDC Prime address). Substantially reworked Ethereum tokensAndOwners with new stablecoins (USDC, USDT, USD1, PYUSD, RLUSD, GHO) and extensive protocol-specific entries (Aave, Cap, Ethena, Euler, Fluid, Morpho, Pendle, Hyperithm, IPOR, Stargate, Sky-Spark, Uniswap v4).
New chain support expansion projects/reservoir-protocol/index.js	Added configuration for three new chains (bsc, monad, hyperliquid) with non-empty tokensAndOwners arrays. Populated previously empty entries for mantle and optimism with token/owner pairs.
Multi-chain updates projects/reservoir-protocol/index.js	Modified tokensAndOwners for arbitrum, base, and plasma by adding new token/owner pairs and updating comments/labels on existing entries.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Poem

A rabbit hops through tokens bright,
Static chains replace dynamic flight,
From Ethereum's grand display,
New blockchains join the fray—
Bsc, Monad, Hyperliquid's might! 🐰✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title 'Update reservoir protocol assets' clearly and concisely summarizes the main change: updating asset configurations for the Reservoir Protocol adapter.
Description check	✅ Passed	The pull request description is the standard template filled with repository guidelines and contributor instructions, but contains no new listing information specific to this update (all optional fields are left blank as expected for an update PR).
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 unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  196.70 M
plasma                    10.02 M
mantle                    2.01 M
berachain                 1.00
bsc                       0.00
arbitrum                  0.00
optimism                  0.00
monad                     0.00
base                      0.00
wc                        0.00
hyperliquid               0.00

total                    208.73 M 

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@projects/reservoir-protocol/index.js`:
- Around line 34-100: The Reservoir adapter is missing the doublecounted flag so
these listed receipt/strategy positions are being treated as unique TVL; update
the adapter's exported config (the adapter object in index.js that contains the
token pairs array and chain config for Ethereum) to include doublecounted: true
(set it alongside other adapter-level properties for the Reservoir adapter), and
ensure the same flag is applied for the additional sections covering lines
~103-194 where similar external positions are listed.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: ed1df717-0fa3-4ee6-b902-1bbe3324b624

📥 Commits

Reviewing files that changed from the base of the PR and between 1f67a4b and 0543b2d.

📒 Files selected for processing (1)

• projects/reservoir-protocol/index.js

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Mark this adapter as doublecounted.

These additions are mostly external receipt/strategy positions (Aave, Euler, Fluid, Morpho, Pendle, Stargate, etc.), so their underlying capital is already counted in the source protocols. Without doublecounted: true, Reservoir will be reported as additive unique TVL instead of layered exposure.

Suggested fix

 Object.keys(config).forEach(chain => {
-  module.exports[chain] = { tvl }
+  module.exports[chain] = { tvl, doublecounted: true }
 })

Based on learnings: the GRVT and Royco adapters mark balances as doublecounted: true when they include assets already tracked in external protocols.

Also applies to: 103-194

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@projects/reservoir-protocol/index.js` around lines 34 - 100, The Reservoir
adapter is missing the doublecounted flag so these listed receipt/strategy
positions are being treated as unique TVL; update the adapter's exported config
(the adapter object in index.js that contains the token pairs array and chain
config for Ethereum) to include doublecounted: true (set it alongside other
adapter-level properties for the Reservoir adapter), and ensure the same flag is
applied for the additional sections covering lines ~103-194 where similar
external positions are listed.