Create SCHEMA_AMM (with vault) #48
Conversation
| | pair_index | The index of the token in the smart contract (one row for each pair). | number | | ||
| | pair_address | The contract address of the pair. | string | | ||
| | pair_symbol | The symbol of the pair. | string | | ||
| | pair_liquidity | The liquidity available for trading for the pair (24h rolling average, in tokens). | string | |
There was a problem hiding this comment.
eg if this is a BTC/USD pair, will it be :
base index 0
quote index 1
pair_liquidity - liquidity available for each token?
for other verticals, we just use the amount on the daily / hourly snapshot (00:59:59 or 23:59:59), and we date_trunc the timestamp . probably easier if they are doing it on sql?
There was a problem hiding this comment.
datatype for pair_liquidity and pair_liquidity_usd is wrong
There was a problem hiding this comment.
yeah liquidity for each
| | liquidation_fees_usd | The total liquidation fees accrued for each pair (24h rolling average, in USD). | number | | ||
| | funding_rate | The funding rate for each pair at the time of the snapshot, as a percentage. | number | | ||
| | open_fees_usd | The total open fees accrued for each pair (24h rolling average, in USD). | number | | ||
| | close_fees_usd | The total close fees accrued for each pair (24h rolling average, in USD). | number | |
There was a problem hiding this comment.
whats the difference between this and the same columns in the vault schema?
There was a problem hiding this comment.
here's my thinking, if we are tracking a few pairs and not all of them in the vault, we might end up underestimating the total
There was a problem hiding this comment.
vault_fees are toal fees accrued by the protocol.
those fees can only be calculated at the pair level
in the vault, it's usd values, not fees.
There was a problem hiding this comment.
ideally we want to get all token amount and usd amount as optional. in case if token price is missing we can still use our internal price table
| | tvl | Total Value Locked at snapshot, in tokens (one entry for each token in the vault). | number | | ||
| | tvl_usd | Total Value Locked at snapshot (TOTAL of all tokens, in USD). | number | |
There was a problem hiding this comment.
tvl - is this the token amount ? if so maybe lets name it token_amount and token_amount_usd?
also token_address is missing
There was a problem hiding this comment.
I find token_amount rather confusing compared to tvl.
I don't think we need any token_address at the vault level, just the vault address, don't we?
There was a problem hiding this comment.
using sudo as an example here
their SLP is one vault, so shouldnt there be token address to identify the correct asset?
There was a problem hiding this comment.
indeed, i'll add it.
| | amount_useful_usd | The amount of liquid tokens supplied in USD. | number | | ||
| | liquidated_amount | The amount of tokens liquidated from the LP (when the taker has positive PnL if a position is closed), decimal normalized. | number | | ||
| | liquidated_amount_usd | The amount liquidated, in USD. | number | | ||
| | total_lp_fees_usd | Total fees generated for the LP at the time of snapshot (in USD). | number | |
There was a problem hiding this comment.
total_lp_fees_usd - is this the amount of fee that is earned by the individual LP provider?
There was a problem hiding this comment.
yes, it's in the LP snapshot, so for each LP
There was a problem hiding this comment.
this field seems difficult to calculate here, but we can leave it here and wait for team's feedback
No description provided.