-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Prom chain integration and token details #14106
Conversation
Replaced the factory address in savmswap for Prometeus and added "prom" to the supported chains list. Implemented token mappings for PROM and associated assets across Prom, Ethereum, and BSC. These updates improve chain support and token balance accuracy.
Could you take a look at the conflicts please? |
Error while running adapter at projects/savmswap:
|
Replaced the old factory address with the new one in the uniTvlExport function. This ensures the TVL calculation uses the correct and updated address.
Error while running adapter at projects/savmswap:
|
Included 'prom' in the `ibcChains` array to ensure compatibility with IBC-related functionality. This update enhances the mapping logic for improved chain support.
Error while running adapter at projects/savmswap:
|
@waynebruce0x how Can I fix this test? |
Removed an extra comment misplacement in the BSC mapping section for better readability. The change does not affect functionality or data structure.
The adapter at projects/savmswap exports TVL:
|
module.exports = uniTvlExport('prom', '0x3B73a7eDc9dfE4847a20BcCfEf6Eb1c90439f5C9') //factory address |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we track both the prom and svm deployments here? It will be more complete and better for our historical data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes
What should I change?
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):
Prom
Twitter Link:
https://x.com/prom_io
List of audit links if any:
Website Link:
https://prom.io/
Logo (High resolution, will be shown with rounded borders):
https://assets-cdn.trustwallet.com/blockchains/ethereum/assets/0xfc82bb4ba86045Af6F327323a46E80412b91b27d/logo.png
Current TVL:
Treasury Addresses (if the protocol has treasury)
Chain:
prom
Coingecko ID (so your TVL can appear on Coingecko, leave empty if not listed): (https://api.coingecko.com/api/v3/coins/list)
https://www.coingecko.com/en/coins/prom
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)
https://coinmarketcap.com/currencies/prom/
Short Description (to be shown on DefiLlama):
Lastly, update the project’s configuration file to add your new blockchain as a valid supported chain. If we don´t track any protocol on your blockchain, we can not add it. So make sure to add the new chain under a current project or add a new adapter to track the project on your blockchain
Token address and ticker if any:
0xfc82bb4ba86045af6f327323a46e80412b91b27d prom
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):
https://github.com/prom-io