fix: Incorrect token liquidity tracking and old social links for Morphex / BMX #11336
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NOTE
Please enable "Allow edits by maintainers" while putting up the PR.
package-lock.json
file as part of your changes, we use lockfileVersion 2, and most use v1 and using that messes up our CIName (to be shown on DefiLlama): https://defillama.com/protocol/bmx
Twitter Link: Please update our twitter link to https://x.com/MorphexBMX
List of audit links if any:
Website Link: https://www.bmx.trade/
Logo (High resolution, will be shown with rounded borders):
Current TVL:
Treasury Addresses (if the protocol has treasury): 0xE02Fb5C70aF32F80Aa7F9E8775FE7F12550348ec (Base)
Chain: Base, Mode
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.): Chainlink, Pyth, API3
Implementation Details: Briefly describe how the oracle is integrated into your project: Pricefeeds
Documentation/Proof: Provide links to documentation or any other resources that verify the oracle's usage: Chainlink and Pyth were previously submitted as oracles for BMX, there is no Chainlink on Mode so we went with API3. https://docs.morphex.trade/oracles
forkedFrom (Does your project originate from another project): We have 2 trading engines / UIs:
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):
Additional request: Currently, there are 4 different protocol versions lumped under "Morphex":
Morphex was our original deployment on Fantom and BNB Chain with the MPX token. BMX was deployed with a new token (BMX) due to tokenomics changes, and Freestyle is a product released under BMX. BMX is currently live on Base and Mode, with Optimism coming soon.
Would it be possible to separate Morphex and BMX as groupings, as it confuses our users too much with all of the differences between those protocols. It would be great to have something like this:
Classic is what we now call our GMX-v1 deployment (with spot+margin trading), Freestyle is intent-based. With the current grouping for everything (Morphex + BMX + Freestyle), the "BMX" tab is what would be the "Classic" tab. Just to reiterate, Classic and Freestyle should be under the grouping "BMX".
Additionally, I've submitted feedback directly through the site but it hasn't been fixed yet - the liquidity links for our token BMX are the wrong ones, they are showing for MPX on Fantom. Can this also please be fixed? https://www.coingecko.com/en/coins/bmx