-
Notifications
You must be signed in to change notification settings - Fork 5k
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
feat: add otsea protocol #10633
feat: add otsea protocol #10633
Conversation
The adapter at projects/otsea exports TVL:
|
The adapter at projects/otsea exports TVL:
|
return async (api) => { | ||
// locked in sell orders (ETH amount on sell orders) | ||
let graphQLClient = new GraphQLClient(endpoint); | ||
let query = gql` |
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.
Where is the ETH in the sell orders held?
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.
We have buy/sell orders on markets.
Buy orders means the request of buying the target token with ETH, so users lock ETH. we calculate locked ETH for buy orders by fetching the ETH balance of our market contract.
Sell orders means the request of selling the token. so users lock the target token and suggest the required ETH amount. We calculate the sum of required ETH amount for sell orders by using our graphql endpoints.
Totally, locked assets = locked ETH (buy orders) + required ETH (sell orders)
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.
is it possible to count the token opposed to the required ETH? If not, could you add a 'misrepresentedTokens: true' property to your adapter exports?
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.
Added 'misrepresentedTokens: true' property to exports
The adapter at projects/otsea exports TVL:
|
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):
OTSea
Twitter Link:
https://x.com/otseaerc20
List of audit links if any:
https://dedaub.com/audits/otsea/otsea-dec-18-2023/
https://raw.githubusercontent.com/peckshield/publications/master/audit_reports/PeckShield-Audit-Report-OTSea-v1.0.pdf
Website Link:
https://otsea.io/
Logo (High resolution, will be shown with rounded borders):
Current TVL:
Treasury Addresses (if the protocol has treasury)
Chain:
Ethereum, Base, Blast
Coingecko ID (so your TVL can appear on Coingecko, leave empty if not listed): (https://api.coingecko.com/api/v3/coins/list)
otsea
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)
28349
Short Description (to be shown on DefiLlama):
OTSea is a leading OTC trading platform on web3 that provides users with a reliable and user friendly solution for trading crypto assets peer-to-peer.
Token address and ticker if any:
N/A
Category (full list at https://defillama.com/categories) *Please choose only one:
Dexes
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:
N/A
forkedFrom (Does your project originate from another project):
Not a fork
methodology (what is being counted as tvl, how is tvl being calculated):
We are calculating tvl by fetching the locked assets with otsea graphql endpoints.