Skip to content

Conversation

@PumpBase-Launchpad
Copy link

NOTE

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


  • If you would like to add a volume/fees/revenue 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): PumpBase
Twitter Link: https://x.com/PumpBase_HQ
List of audit links if any: https://spywolf.co/audits/Pumpbase_0x19798E390E69a36814B25BbBC7e75530E8a0A101.pdf
Website Link: https://pumpbase.site/
Logo (High resolution, will be shown with rounded borders): https://drive.google.com/file/d/1oLZ02FE5fzwTXiZ1fMKU9FYXc0RtlTiP/view?usp=sharing
Current TVL: 243.3k
Treasury Addresses (if the protocol has treasury)
Chain: Base 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): PumpBase makes it effortless for anyone to create, trade, and grow onchain tokens. Every token launched through PumpBase follows a fair-launch model, ensuring equal access for all users — no insider allocations, no pre-mines, and no unfair advantages.
Token address and ticker if any:
Category (full list at https://defillama.com/categories) *Please choose only one: Launchpad
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): Counts ETH and tokens locked in bonding curves. ETH reserves are calculated by subtracting the fake initial liquidity (1.5 ETH) from the total reserves.
Github org/user (Optional, if your code is open source, we can track activity): https://github.com/PumpBase-Launchpad

@waynebruce0x
Copy link
Collaborator

Please only count base tokens in bonding curves and not the tokens minted

@waynebruce0x waynebruce0x self-assigned this Oct 21, 2025
@llamabutler
Copy link

Error while running adapter at :

Please revert changes to package.json / package-lock.json

@PumpBase-Launchpad
Copy link
Author

PumpBase-Launchpad commented Oct 21, 2025

Please only count base tokens in bonding curves and not the tokens minted

Could you please tell me the meaning of “base tokens”?
My project is a token launchpad that uses bonding curves before the tokens graduate.
So, I thought the TVL should represent the total balance of all bonding curves.
Each minted token has its own bonding curve pool, so I summed the balances of all the minted tokens’ bonding curves.

@PumpBase-Launchpad
Copy link
Author

Error while running adapter at :

Please revert changes to package.json / package-lock.json

I have updated pull request.

@waynebruce0x
Copy link
Collaborator

By base token I mean ETH, USDT etc, tokens that exist before the bonding curve is initialised. The minted tokens should not be counted here

@PumpBase-Launchpad
Copy link
Author

By base token I mean ETH, USDT etc, tokens that exist before the bonding curve is initialised. The minted tokens should not be counted here

I’ve already done that.
I've only summed the Eth balance.

@waynebruce0x
Copy link
Collaborator

Where is the ETH? The reserveEth value seems to generally be higher than the ETH balance of the bonding curve contract

@llamabutler
Copy link

The adapter at projects/PumpBase exports TVL:

base                      233.29 k

total                    233.29 k 

@PumpBase-Launchpad
Copy link
Author

Where is the ETH? The reserveEth value seems to generally be higher than the ETH balance of the bonding curve contract

No, It's not higher.
Could you please check it again?
The aggregated ETH balance across all bonding curves is currently between 60 and 65 ETH,
which corresponds to an approximate value of 230k–250k.
I’ve tested it, and the calculations are accurate.

@llamabutler
Copy link

The adapter at projects/PumpBase exports TVL:

base                      242.82 k

total                    242.82 k 

@waynebruce0x
Copy link
Collaborator

https://basescan.org/address/0x26e8e25624553e0DAF3BF73351635F7d65BF9A48#code

reserveEth is 2.6658559
balance ETH is 1.0098403

@PumpBase-Launchpad
Copy link
Author

https://basescan.org/address/0x26e8e25624553e0DAF3BF73351635F7d65BF9A48#code

reserveEth is 2.6658559 balance ETH is 1.0098403

Sir, I think there might be some mistakes here.
I’d like to explain my methodology for calculating the total TVL again.
When I calculated the TVL, I removed the fake initial liquidity (1.5 ETH) from the reserved ETH.
I already mentioned it in my script.
"methodology (what is being counted as tvl, how is tvl being calculated): Counts ETH and tokens locked in bonding curves. ETH reserves are calculated by subtracting the fake initial liquidity (1.5 ETH) from the total reserves."

@waynebruce0x
Copy link
Collaborator

I see - but there is still a discrepancy, the difference isnt 1.5 - I'm just trying to work out what the source of this difference is. Why dont we count the ETH balance of each bonding curve instead of using the reserveEth() method?

@PumpBase-Launchpad
Copy link
Author

I see - but there is still a discrepancy, the difference isnt 1.5 - I'm just trying to work out what the source of this difference is. Why dont we count the ETH balance of each bonding curve instead of using the reserveEth() method?

Sir, there is no difference between the actual balance of the bonding curve and reserveEth - 1.5 ETH.
As you can see in the verified code, they are the same.
Could you please check the verified code again?
You can view the contract code here.
https://basescan.org/address/0x26e8e25624553e0DAF3BF73351635F7d65BF9A48#code

@waynebruce0x
Copy link
Collaborator

Screenshot

I dont understand why this doesnt equal 0.9682968?

@PumpBase-Launchpad
Copy link
Author

I dont understand why this doesnt equal 0.9682968?

Since the token is currently being traded, I believe BaseScan cannot update the ETH balance in real time.
Please check other bonding curves, such as this one: https://basescan.org/address/0x26e60a483e722998e5d4ffd69a6ffdb2a298ff91.

image

@PumpBase-Launchpad
Copy link
Author

Sir, I swear there is no problem with the script.

image

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