Add TradingStrategy.ai

[miohtama]

Internal PR to see what CI says

[llamatester]

The adapter at projects/trading-strategy exports TVL:

polygon                   13.28 k
ethereum                  0
bsc                       0
base                      0
arbitrum                  0

total                    13.28 k 

[g1nt0ki]

hi, your app has two issues, the open strategies are enzyme contracts, which we already count as part of enzyme tvl

And the hot wallets being hot wallets, we cant include as tvl. So, I am not sure if we can list you :(

[g1nt0ki]

this can be reduced to

const { getConfig } = require('../helper/cache')

const chains = ["ethereum", "polygon", "base", "bsc", "arbitrum"]

chains.forEach(chain => {
  module.exports[chain] = {
    tvl: async (api) => {
      const { strategies } = await getConfig('trading-strategy', 'https://tradingstrategy.ai/strategies/tvl')
      const vaults = Object.values(strategies).filter(strat => strat.chain_id === api.chainId && strat.asset_management_mode === 'enzyme').map(i => i.address)
      const tokens = await api.multiCall({ abi: 'address[]:getTrackedAssets', calls: vaults })
      return api.sumTokens({ ownerTokens: tokens.map((t, i) => [t, vaults[i]])})
    }
  }
})

[miohtama]

Thank you for getting back @g1nt0ki.

What if I exclude our vaults from Enzyme adapter? I can speak with Enzyme about this, as we are in good terms.

We can also label them Trading Strategy + Enzyme.

There are couple of other digital asset management protocols who have a similar set up and wish we can find a solution for this.

[miohtama]

@g1nt0ki ping here - please see the question above

[g1nt0ki]

hi @miohtama sorry for the delayed response. Trying to understand the product a bit more, how does TradingStrategy UI interact with emzyme contracts, directly? or you have deployed your own contracts, that act as proxy/controller?

[miohtama]

Thank you for your response @g1nt0ki

• We use Enzyme vaults
• You can interact the same vaults through Enzyme frontend and TradingStrategy.ai frontend
• Vaults that are Trading Strategy enabled have a special configuration on Enzyme - it is an extensible protocol after all
• The per-vault customisations and configuration changes enabled to have oracle-based asset manager (instead of "human" asset managers that's Enzyme default)
• There are our own contracts deployed, but they are set as guard and asset manager roles in Enzyme vaults, the core Comproller and Vault contracts are still Enzyme defaults (they are immutable, they cannot be changed in fact)

Hope this helps.

Also I believe you might run into similar questions with Uniswap v4, as multiple protocols are building on the top of its hooks.

[g1nt0ki]

hi @miohtama

Sorry, we cant show tvl in that case. But do you charge some fees? if so, we can pull and show the revenue/fee metric.

Checked with the team, same will be applicable to the teams building on top of uni v4.