Reservoir protocol

[eukadish]

NOTE

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

---

• If you would like to add a volume adapter please submit the PR here.
• If you would like to add a liquidations adapter, please refer to this readme document for details.

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. 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.
3. 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
4. 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/data2.ts, you can edit it there and put up a PR
5. Do not edit/push package-lock.json file as part of your changes, we use lockfileVersion 2, and most use v1 and using that messes up our CI
6. No need to go to our discord and announce that you've created a PR, we monitor all PRs and will review it asap

---

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):

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  137.94 M

total                    137.94 M 

[bosswissam]

I am not sure why the tests are failing, do we need to define an rpc for bera?

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  134.92 M
berachain                 15.00 M

total                    149.92 M 

[bosswissam]

I am not sure why the tests are failing, do we need to define an rpc for bera?

Resolved

[bosswissam]

the tests are not failing?

@0xngmi They're passing now.

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  134.99 M
berachain                 15.00 M

total                    149.99 M 

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  134.98 M
berachain                 15.00 M

total                    149.98 M 

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  135.42 M
berachain                 23.84 M

total                    159.26 M 

[bosswissam]

I rewrote the adapter but I now realize I could leverage sumTokens or sumTokens2 but unfortunately I cannot find good docs at https://docs.llama.fi/list-your-project/how-to-write-an-sdk-adapter#line-4-input-parameter. Would be great if you can point me to a decent overview of the api reference.

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  136.59 M
berachain                 23.84 M

total                    160.43 M 

[llamabutler]

The adapter at projects/reservoir-protocol exports TVL:

ethereum                  136.68 M
berachain                 23.84 M

total                    160.52 M 

[bosswissam]

I rewrote the adapter but I now realize I could leverage sumTokens or sumTokens2 but unfortunately I cannot find good docs at https://docs.llama.fi/list-your-project/how-to-write-an-sdk-adapter#line-4-input-parameter. Would be great if you can point me to a decent overview of the api reference.

Figured it out but honestly the docs are very limited. If there's a comprehensive reference somewhere please point me to it

[waynebruce0x]

please export any TVL from ruSD-XXXX LPs as pool2 and exclude them from the main tvl export

[bosswissam]

@waynebruce0x This is not different than our core TVL. Instead of USDC being deployed into morpho for example, it's being bridged to Berachain and deployed into a liquidity.

pool2 makes no sense for this. This is our core TVL on Berachain. We are simply trying to denote our TVL on Berachain vs Mainnet.

[waynebruce0x]

Are we counting the collateral backing these bridged tokens?

[bosswissam]

@waynebruce0x

We're not double-counting if that's what you're asking.

USDC is deposited in our PSM, and once we bridge it to Berachain it's not counted on Mainnet anymore. Right now we are only counting USDC in our asset adapters (missing one) on Mainnet.

[waynebruce0x]

We should count the USDC in the PSM instead of the rUSD supply

[bosswissam]

This is the protocol minting more rUSD backed by USDC to get exposure into this asset. Please merge this as it aligns with how the protocol generates yield

[waynebruce0x]

how do you mean to get exposure into this asset? can you explain a bit more

[noateden]

hi @bosswissam can you give more info about your USDC PSM? otherwise, we can not merge this

[noateden]

get USDC backing for rUSD on berachain instead of rUSD supply