Added EOS xSat EVM adapter

[nsjames]

Name (to be shown on DefiLlama):

EOS XSAT EVM

Twitter Link:

https://x.com/exsatnetwork

Website Link:

https://exsat.network/

Logo (High resolution, will be shown with rounded borders):

Current TVL:

$27.45m

Chain:

EOS

Coingecko ID (so your TVL can appear on Coingecko, leave empty if not listed):

eos

Coinmarketcap ID (so your TVL can appear on Coinmarketcap, leave empty if not listed):

1765

Short Description (to be shown on DefiLlama):

The amount of BTC that has been bridged over to the EOS network via the xSat BTC EVM.

Token address and ticker if any:

btc.xsat
BTC

Category (full list at https://defillama.com/categories) *Please choose only one:

15 Cross Chain

methodology (what is being counted as tvl, how is tvl being calculated):

EOS ExSAT EVM TVL is achieved by querying the total available supply from the [btc.xsat] account. This supply fluctuates as users deposit and withdraw funds from the ExSAT EVM.

Github org/user (Optional, if your code is open source, we can track activity):

https://github.com/exsat-network/contract-of-consensus

[llamatester]

The adapter at projects/eos-exsat-evm exports TVL:

eos                       27.42 M

total                    27.42 M 

[nsjames]

Please let me know if there is any additional information that needs to be provided, or if I need to add anything to the icons or server repos.

Thanks!

[g1nt0ki]

@nsjames thanks for the PR, can you instead return a list of btc addresses with at least 0.001 BTC and compute tvl using sumTokens method, also, can you place the address fetcher code here: https://github.com/seancheen/DefiLlama-Adapters/blob/pr/seancheen/12406/projects/helper/bitcoin-book/fetchers.js#L9

the adapter code would be something like this: https://github.com/seancheen/DefiLlama-Adapters/blob/pr/seancheen/12406/projects/lombard/index.js#L13

[g1nt0ki]

.

[llamatester]

The adapter at projects/eos-exsat-evm exports TVL:

eos                       26.82 M

total                    26.82 M 

[nsjames]

@g1nt0ki thanks for the info

I see there's already another implementation of the exsat bridge calculation in fetchers however it's attributing the TVL to bitcoin via the exsat adapter. It would be preferable to display that TVL on EOS instead as that is where those BTC effectively are now.

I've modified the adapter to use that same code to attribute the TVL to EOS, but am unsure how you'd like to handle this.

[g1nt0ki]

hi @nsjames for bridge protocols, we count the tokens deposited on the source chain, so counting bitcoin on bitcoin chain is the correct approach.

I would also like to mention that, these bridge tvl would not be counted towards either source or destination chain tvl. #435