ZEROBASE adaptor for DeFiLama

[asilbek-0311]

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

Twitter Link: x.com/zerobasezk

List of audit links if any:

PeckShield Audit Report: https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-ZeroBase-Vault-v1.0.pdf
Salus Audit Report: https://github.com/Salusec/Salus-audit/blob/main/2024/ZeroBase_report_2024-12-24.pdf

Website Link: https://app.zerobase.pro/

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

Current TVL: 36M

Treasury Addresses (if the protocol has treasury)

Chain:

ethereum, avax, bsc, arbitrum, polygon, base, optimism

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

ZEROBASE introduces the first zk-powered staking product on stablecoins.

Token address and ticker if any:

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

Basis trading

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

For each chain: call getTVL(token) on its vault and sum per‐token amounts.

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

[llamabutler]

The adapter at projects/ZEROBASE exports TVL:

bsc                       8.17 M
arbitrum                  4.60 M
base                      1.22 M
polygon                   778.98 k
ethereum                  774.56 k
avax                      72.64 k
optimism                  45.18 k

total                    15.66 M 

[Define101]

@asilbek-0311 Hello.
This fits under the basis trading category.
Could you please confirm which custodian you are currently using? Additionally, we would appreciate it if you could share details of all the wallets involved in the process. Our assumption is that there may be commingled wallets as well as a final destination wallet, which makes it difficult for us to independently verify the flow of funds

[Define101]

The wallets for all this chains

[asilbek-0311]

Thank you for your prompt response! Here are my answers to your questions, one by one:

We use Ceffu as our custodian.

Since Ceffu does not support deposits on L2s such as Arbitrum, Optimism, and BASE, we use ZEROBASE’s Binance account as an intermediate account and hot wallet/buffer pool. The process is as follows: users stake their funds into the following vault contracts:

ETH
Vault Contract: 0x9eF52D8953d184840F2c69096B7b3A7dA7093685

AVAX-C
Vault Address: 0xC3e9006559cB209a987e99257986aA5Ce324F829

BSC, ARB, Polygon, OP, BASE
Vault Contract: 0xCc5Df5C68d8c991035B6A437D4e00A99875228E4

Once funds on each chain reach a certain threshold, they are transferred to the ZEROBASE Binance address (multi-chain):
0xd038213a84a86348d000929c115528ae9ddc1158

Then, they are moved to the Ceffu address:
BEP20: 0x1ea0f3315a80dc736788ff0f6d2fe1912ec4a85d

Previously used aggregation addresses (now deprecated):

TRC20: TQrfy2ty4t17SAZTb5WTLRrDPPrRoo4Aw3

BEP20: 0x430743877a540234f527e2d547d744a18124920a

Fund aggregation logic:
Since we support multiple chains, all addresses are active and used accordingly.

Regarding the parsed data being smaller than 36M:
ZEROBASE underwent a contract upgrade from V1 to V2, during which some whale users did not receive LP Token allocations. We will address this issue soon, but for now, please proceed based on the data currently available.

[asilbek-0311]

Hello @Define101
is the information sufficient

[llamabutler]

The adapter at projects/ZEROBASE exports TVL:

bsc                       8.15 M
arbitrum                  4.58 M
base                      1.22 M
ethereum                  778.80 k
polygon                   739.02 k
avax                      72.69 k
optimism                  35.33 k

total                    15.58 M 

[0xpeluche]

All good, I refactored the code a bit, thanks for the PR!