Skip to content

Conversation

internalmsg
Copy link

@internalmsg internalmsg commented Sep 15, 2025

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): Syntropia
Twitter Link: https://x.com/syntropia_ai
List of audit links if any:
Website Link: https://syntropia.ai/
Logo (High resolution, will be shown with rounded borders):
telegram-cloud-document-2-5316750607107780269
Current TVL: 1,300,000 USDC
Treasury Addresses (if the protocol has treasury)
Chain: Ethereum
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): Capture the best risk adjusted yield on stablecoins across DeFi protocols while maintaining full transparency
Token address and ticker if any:
Category (full list at https://defillama.com/categories) *Please choose only one: Yield Aggregator
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
Copy link

The adapter at projects/syntropia exports TVL:

ethereum                  1.36 M

total                    1.36 M 

const { get } = require("../helper/http");
const ADDRESSES = require("../helper/coreAssets.json");

async function tvl(api) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please use our SDK and on chain methods to calculate TVL, opposed to a proprietary API

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @waynebruce0x,

We're using our API in this case since it's a wrapper over the basic DeBank API.

Right now, it returns the total TVL from our single USDC vault:
https://debank.com/profile/0x3daB62f33E7032bD33C532808092D033887EB456

The vault contains various underlying assets, so it might be difficult to compute TVL using only on-chain methods - especially considering that the assets are frequently redistributed.

What would you suggest in this case?

@waynebruce0x waynebruce0x self-assigned this Sep 15, 2025
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