diff --git a/docs/data-tables/spellbook/top-tables/dex.trades.md b/docs/data-tables/spellbook/top-tables/dex.trades.md index d6dbc002..ec390fbb 100644 --- a/docs/data-tables/spellbook/top-tables/dex.trades.md +++ b/docs/data-tables/spellbook/top-tables/dex.trades.md @@ -13,29 +13,90 @@ This table standardizes and normalizes the trading data across virtually all rel The scripts that generate the table dex.trades can be found in this [public github](https://github.com/duneanalytics/spellbook/tree/main/models/dex) repo. +## Indexed Chains And Platforms + + + ## Column Data -| Column name | Data type | Description | -| - | :-: | - | -| `block_time` | _timestamptz_ | The timestamp of the block that included this transaction | -| `token_a_symbol` | _varchar_ | The symbol of one of the two tokens that got traded | -| `token_b_symbol` | _varchar_ | The symbol of one of the two tokens that got traded | -| `token_a_amount` | _numeric_ | The amount of token A that got traded | -| `token_b_amount` | _numeric_ | The amount of token B that got traded | -| `project` | _varchar_ | The dex on which this trade was executed | -| `version` | _varchar_ | Which version of the dex got used? | -| `blockchain` | _varchar_ | Which blockchain did this occur on | -| `taker` | _varbinary_ | Which contract called the dex contract? | -| `maker` | _varbinary_ | In some special cases there actually is a counter party to transactions, this party will get displayed here if applicable | -| `token_a_amount_raw` | _numeric_ | The raw amount of token A that got traded | -| `token_b_amount_raw` | _numeric_ | The raw amount of token B that got traded | -| `amount_usd` | _numeric_ | The USD value of this trade | -| `token_a_address` | _varbinary_ | The ERC-20 token contract address of token A | -| `token_b_address` | _varbinary_ | The ERC-20 token contract address of token B | -| `exchange_contract_address` | _varbinary_ | The address of the decentralized exchange contract that made this trade possible | -| `tx_hash` | _varbinary_ | The hash of the transaction that contained this trade | -| `tx_from` | _varbinary_ | Which address initiated this transaction? | -| `tx_to` | _varbinary_ | What was the first smart contract that got called during this tx? | -| `trace_address` | _ARRAY_ | Which position in the graph tree does the execution of the trade have? | -| `evt_index` | _integer_ | This logs index position in the block (cumulative amount of logs ordered by execution) | -| `trade_id` | _integer_ | Just for database magic | +| Column Name | Data Type | Description | +|-------------------------|-------------------|----------------------------------------------------------------------- | +| `amount_usd` | _double_ | The USD value of this trade | +| `block_date` | _timestamp_ | The truncated timestamp of the block including this transaction | +| `block_time` | _timestamp_ | The timestamp of the block including this transaction | +| `blockchain` | _varchar_ | The blockchain where this transaction was broadcasted | +| `evt_index` | _int_ | This log's index position in the block (cumulative amount of logs ordered by execution) | +| `maker` | _varbinary_ | In some special cases, the counterparty to transactions (if applicable) | +| `project` | _varchar_ | The decentralized exchange (DEX) on which this trade was executed | +| `project_contract_address` | _varbinary_ | The contract address of the project or DEX | +| `taker` | _varbinary_ | The contract that called the DEX contract | +| `token_bought_address` | _varbinary_ | The address of the token bought during this trade | +| `token_bought_amount` | _double_ | The amount of the token bought during this trade | +| `token_bought_amount_raw` | _decimal(38,0)_ | The raw amount of the token bought during this trade | +| `token_bought_symbol` | _varchar_ | The symbol of the token bought | +| `token_pair` | _varchar_ | The trading pair of tokens involved in this trade | +| `token_sold_address` | _varbinary_ | The address of the token sold during this trade | +| `token_sold_amount` | _double_ | The amount of the token sold during this trade | +| `token_sold_amount_raw` | _decimal(38,0)_ | The raw amount of the token sold during this trade | +| `token_sold_symbol` | _varchar_ | The symbol of the token sold | +| `trace_address` | _varchar_ | The position in the execution graph tree for this trade | +| `tx_from` | _varbinary_ | The address that initiated this transaction | +| `tx_hash` | _varbinary_ | The hash of the transaction containing this trade | +| `tx_to` | _varbinary_ | The address of the first smart contract called during this transaction | +| `version` | _varchar_ | The version of the DEX used for this trade | + +#### Get all transactions of USDC swaps in the past 24 hours + +```sql +select * from dex.trades +where (token_bought_address = 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 +OR token_sold_address = 0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48) +AND blockchain = 'ethereum' +AND block_time >= NOW() - interval '24' hour +``` + + + + +#### Get top 100 uniswap pairs' volume from uniswap in the past 3 days + +```sql +select token_pair, + SUM(amount_usd) as total_volume +from dex.trades +WHERE blockchain = 'ethereum' +AND project = 'uniswap' +AND block_time >= NOW() - interval '3' day +AND token_pair IS NOT NULL +GROUP BY 1 +ORDER BY 2 DESC -- order by total_volume +limit 100 -- 100 rows +``` + + + + +#### Get top 100 traders' volume of erc20 token using dex.trades + +```sql +-- top traders trading wBTC in the past 7 days +SELECT tx_from as address, + SUM(amount_usd) as total_volume, + SUM(CASE WHEN "token_bought_address" = 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 THEN 1 END) as buy_count, + SUM(CASE WHEN "token_sold_address" = 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 THEN 1 END) as sell_count, + SUM(CASE WHEN "token_bought_address" = 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 THEN amount_usd END) as total_buy_volume, + SUM(CASE WHEN "token_sold_address" = 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 THEN amount_usd END) as total_sell_volume +FROM dex.trades +WHERE ("token_bought_address" = 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599 OR "token_sold_address" = 0x2260fac5e5542a773aa44fbcfedf7c193bc2c599) +AND blockchain = 'ethereum' +AND block_time >= NOW() - interval '7' day +GROUP BY 1 +ORDER BY 2 DESC +limit 100 +``` + + + + + + diff --git a/docs/data-tables/spellbook/top-tables/labels.md b/docs/data-tables/spellbook/top-tables/labels.md index 0beeece7..faa1ba23 100644 --- a/docs/data-tables/spellbook/top-tables/labels.md +++ b/docs/data-tables/spellbook/top-tables/labels.md @@ -69,21 +69,93 @@ Note that there might be a few minutes delay from adding the label on [dune.com] ## The labels table -Labels are stored in the new `labels.labels` table which has the following schema: - -| Column name | Data type | Description | -| - | :-: | - | -| `id` | _int_ | incrementing integer | -| `address` | _varbinary_ | The address of a contract or wallet this label describes | -| `name` | _varchar_ | label name | -| `blockchain` | _varchar_ | the blockchain the label is meant for | -| `author` | _varchar_ | The username of the user who created this label | -| `source` | _varchar_ | The source of this label, autopopulated by Dune | -| `updated_at` | _timestamptz_ | The last time this label was changed | -| `label_type` | _varchar_ | The type of label, defined in the readme | -| `model_name` | _varchar_ | The name of the label model (filename) | +Labels are stored in the new `labels.all` table which has the following schema: + +| Column name | Data type | Description | +|---------------|---------------|-------------------------------------------------------| +| `address` | _varbinary_ | The address of a contract or wallet this label describes | +| `category` | _varchar_ | The category of the label (e.g., dex/contracts/institution) | +| `blockchain` | _varchar_ | The blockchain of the address where the label is given | +| `contributor` | _varchar_ | The name of the contributor that created the label | +| `name` | _varchar_ | The name of the label | +| `source` | _varchar_ | The source reference of the label | +| `label_type` | _varchar_ | The type of label (e.g., persona/usage/identifier) | +| `model_name` | _varchar_ | The name of the model used to create the label | +| `created_at` | _timestamp_ | The time when the label was created | +| `updated_at` | _timestamp_ | The time when the label was last updated | ## Using labels -!!! warning - this section is currently under construction, stay tuned! \ No newline at end of file +#### Identifying CRV Holders Using Labels + +```sql +SELECT address, + ens, + ARRAY_AGG(DISTINCT name) as label_list, + symbol, + contract_address, + balance +FROM ( +SELECT address, + symbol, + name as ens, + contract_address, + SUM(amount) as balance +FROM ( +SELECT tr."from" AS address, + symbol, + contract_address, + -(tr.value/POW(10,decimals)) AS amount +FROM erc20_ethereum.evt_transfer tr JOIN tokens.erc20 USING (contract_address) +WHERE "from" != 0x0000000000000000000000000000000000000000 -- exclude mint/burn addresses +AND contract_address = 0xD533a949740bb3306d119CC777fa900bA034cd52 -- contract_address of the erc20 token +UNION ALL +SELECT tr."to" AS address, + symbol, + contract_address, + (tr.value/POW(10,decimals)) AS amount +FROM erc20_ethereum.evt_transfer tr JOIN tokens.erc20 USING (contract_address) + WHERE "to" != 0x0000000000000000000000000000000000000000 -- exclude mint/burn addresses + AND contract_address = 0xD533a949740bb3306d119CC777fa900bA034cd52 -- contract_address of the erc20 token + ) x LEFT JOIN ens.reverse_latest USING (address) + GROUP BY 1,2,3,4 + HAVING SUM(amount) > 0.1 -- having more than 0.1 balance + ) p LEFT JOIN labels.all USING (address) + GROUP BY 1,2,4,5,6 + ORDER BY 6 DESC +``` + + + +#### Using addresses of labels.contract_deployers_ethereum to find the top 100 deployers + +```sql +SELECT COUNT(*) as contracts_deployed, + SUM(COUNT(*)) OVER (ORDER BY block_time) as contracts_over_time +from ethereum.creation_traces +WHERE "from" IN (SELECT distinct address FROM labels.contract_deployers_ethereum) +AND block_time >= NOW() - interval '7' day +GROUP BY 1 +ORDER BY 2 DESC +``` + + + +#### Using smart_dex_traders label to find tokens traded by traders + +```sql +SELECT COALESCE(token_bought_symbol,CAST(token_bought_address AS VARCHAR)) as token_traded, + COUNT(DISTINCT tx_from) as address_count, + ARRAY_AGG(tx_from) as address_list, + SUM(amount_usd) as total_volume +FROM dex.trades +WHERE tx_from IN (select from_hex(address) from labels.smart_dex_traders) +AND token_bought_address != 0x0000000000000000000000000000000000000000 +AND block_time >= NOW() - interval '14' day +GROUP BY 1 +HAVING SUM(amount_usd) >= 100000 +ORDER BY 4 DESC +``` + + + diff --git a/docs/data-tables/spellbook/top-tables/nft.trades.md b/docs/data-tables/spellbook/top-tables/nft.trades.md index d109bf6f..5ff69717 100644 --- a/docs/data-tables/spellbook/top-tables/nft.trades.md +++ b/docs/data-tables/spellbook/top-tables/nft.trades.md @@ -9,14 +9,42 @@ The culmination of this is a dataset which makes it extremely easy to query for You can find the specifications for nft.trades on our [Spellbook documentation](https://dune.com/spellbook#!/model/model.spellbook.nft_trades). -So far we have indexed the data of the following platforms: +## Indexed Chain And Projects -- OpenSea -- Rarible -- SuperRare -- CryptoPunks (They get traded in their own contracts) -- Foundation -- LooksRare + + + +## Column Data + +| Column Name | Data Type | Description | +|-------------------------|-------------------|----------------------------------------------------------| +| `nft_contract_address` | _varbinary_ | The contract address of the NFT | +| `number_of_items` | _decimal(38,0)_ | The number of NFT items in this trade | +| `project` | _varchar_ | The platform where the NFT is traded | +| `project_contract_address` | _varbinary_ | The contract address of platform | +| `seller` | _varbinary_ | The seller's address of the NFT transaction | +| `token_id` | _varchar_ | The ID of the NFT token | +| `token_standard` | _varchar_ | The standard of the NFT token (ERC-721 / ERC-1155) | +| `trade_category` | _varchar_ | The category of the NFT trade (e.g., Buy/Sell/Auction) | +| `trade_type` | _varchar_ | The type of the NFT trade (e.g., Single Item Trade/Bundle Trade) | +| `tx_from` | _varbinary_ | The address that initiated the transaction | +| `tx_hash` | _varbinary_ | The hash of the NFT transaction | +| `tx_to` | _varbinary_ | The destination address of the NFT transaction | +| `unique_trade_id` | _varchar_ | A unique identifier for the NFT trade | +| `version` | _varchar_ | The version of the platform | +| `aggregator_address` | _varbinary_ | The address of the aggregator | +| `aggregator_name` | _varchar_ | The name of the aggregator | +| `amount_original` | _double_ | The original amount of currency in the trade | +| `amount_raw` | _decimal(38,0)_ | The raw amount of currency in the trade | +| `amount_usd` | _double_ | The USD value of the trade | +| `block_number` | _double_ | The block number of the NFT transaction | +| `block_time` | _timestamp_ | The timestamp of the block of the NFT transaction | +| `blockchain` | _varchar_ | The blockchain of the NFT transaction | +| `buyer` | _varbinary_ | The buyer's address in the NFT trade | +| `collection` | _varchar_ | The NFT collection name | +| `currency_contract` | _varbinary_ | The contract address of the currency used in the trade | +| `currency_symbol` | _varchar_ | The symbol of the currency used in the trade | +| `evt_type` | _varchar_ | The type of event associated with the NFT transaction | ## How it works @@ -52,110 +80,71 @@ In the most recent version of `nft.trades`, information about the amount and per Royalty fees are going to the creator, and Platform fees are collected by the NFT platform. Note that royalty fees cannot always be retrieved, and are set to null by default. -## Examples - -### Queries - -#### All trades for a given NFT - -**_SQL_** +#### Trading price for a given NFT in the past 7 days ```sql +-- get trade details of specific NFT collection (y00ts on polygon) select * from nft.trades - -where nft_contract_address = '\xb47e3cd837ddf8e4c57f05d70ab865de6e193bbb' --this is the cryptopunks address +where nft_contract_address = 0x670fd103b1a08628e9557cd66b87ded841115190 +AND block_time >= NOW() - interval '7' day ``` -**_Results_** + -![type:video](https://dune.com/embeds/146090/288199/bc835020-f730-4348-b749-abd94277b0f7) -#### Trades in the last 24 hour on a given platform - -**_SQL_** +#### Top collection in terms of volume traded in the last 72 hour on a given platform ```sql -select date_trunc('day', block_time), usd_amount, nft_contract_address, token_id from nft.trades - -where platform = 'OpenSea' --only shows trades on given Platform - -and block_time > now() - interval '24hours' +SELECT ROW_NUMBER() OVER (ORDER BY total_volume DESC) as ranking, + * +FROM ( +SELECT COALESCE(collection,CAST(nft_contract_address AS VARCHAR)) as collection, -- using coalesce here will get you the nft_contract_address + blockchain, -- instead of null if collection name does not exist + SUM(amount_usd) as total_volume +FROM nft.trades +where project = 'opensea' --only shows trades on Opensea +and block_time > now() - interval '72' hour +GROUP BY 1,2 +ORDER BY 3 DESC +limit 100 +) ``` -**_Results_** - -![type:video](https://dune.com/embeds/1622909/2690008/ce6aa75e-b94c-4dcf-a1f0-020d2cb5fa9b) + -#### Platform volumes in the last year - -**_SQL_** +#### Platform daily and cumulative volume over time in the last year ```sql -select sum(usd_amount), - date_trunc('day', block_time) as day, - platform +select date_trunc('day', block_time) as day, + project, + sum(amount_usd) as daily_project_amount_usd, + sum(sum(amount_usd)) OVER (PARTITION BY project ORDER BY date_trunc('day',block_time)) as project_cumulative_volume_usd from nft.trades -where block_time > now() - interval '365 days' -group by platform, day +where block_time > now() - interval '365' day +group by 1,2 +ORDER BY 1 DESC,4 DESC ``` + -**_Results_** + -![type:video](https://dune.com/embeds/146160/288002/cc990e4d-21e8-43a7-9bc3-2357a72be7b0) ### Dashboards #### That utilize parameters
-- [NFT by @0xBoxer](https://dune.com/0xBoxer/NFT) -- [NFT Sales Overview by Project by @rantum](https://dune.com/rantum/NFT-Sales-Overview-by-Project) +- [NFT Business metrics by @0datawolf](https://dune.com/0xdatawolf/nft-business-metrics) +- [NFT Custom Project @sealaunch](https://dune.com/sealaunch/abc)
#### That look across the entire Ecosystem
-- [NFT Collection Dashboard by @rantum](https://dune.com/rantum/NFT-Collection-Dashboard) -- [NFT by @sealaunch](https://dune.com/sealaunch/NFT) +- [NFT market overview by @hildobby](https://dune.com/hildobby/NFTs) +- [NFT Top Collections by @sealaunch](https://dune.com/sealaunch/NFT-Top-Collections)
-## Column Data - -| Column name | Data type | Description | -| - | :-: | - | -| `block_time` | _timestamp with time zone_ | When was this trade executed | -| `block_time` | _varchar_ | NFT project name (e.g. "the dudes") | -| `nft_token_id` | _varchar_ | The token_id that was traded (e.g. 235) | -| `erc_standard` | _varchar_ | The Token Standard of the traded token `ERC-721` or `ERC-1155` | -| `platform` | _varchar_ | Which Platform the trade was executed on | -| `platform_version` | _varchar_ | Which version of this platform was utilized? | -| `trade_type` | _varchar_ | "Single Item Sale" or "Bundle Sale" | -| `number_of_items` | _integer_ | How many NFTs were included in this trade | -| `category` | _varchar_ | Was this an auction or a direct sale | -| `evt_type` | _varchar_ | Currently not in use, default 'Trade' | -| `aggregator` | _varchar_ | Was this trade made using an aggregator (Yes : Name of aggregator, No : Null) | -| `usd_amount` | _numeric_ | USD value of the trade at time of execution | -| `seller` | _varbinary_ | Seller of NFTs | -| `buyer` | _varbinary_ | Buyer of NFTs | -| `royalty_fees_percent` | _numeric_ | Royalty fees going to the creator (in %) | -| `original_royalty_fees` | _numeric_ | Royalty fees in the currency used for this trade | -| `usd_royalty_fees` | _numeric_ | USD value of royalty fees at time of execution | -| `platform_fees_percent` | _numeric_ | Platform fees (in %) | -| `original_platform_fees` | _numeric_ | Platform fees in the currency used for this trade | -| `usd_platform_fees` | _numeric_ | USD value of platform fees at time of execution | -| `original_currency` | _varchar_ | The Currency used for this trade | -| `original_currency_contract` | _varbinary_ | The ERC-20 address of the currency used in this trade (does not work with raw ETH) | -| `currency_contract` | _varbinary_ | The corrected currency contract | -| `nft_contract_address` | _varbinary_ | The contract address of the NFT traded | -| `exchange_contract_address` | _varbinary_ | The platform contract that facilitated this trade | -| `tx_hash` | _varbinary_ | The hash of this transaction | -| `block_number` | _integer_ | The block_number that this trade was done in | -| `tx_from` | _varbinary_ | Initiated this transaction | -| `tx_to` | _varbinary_ | Received this transaction | -| `trace_address` | _ARRAY_ | n/a | -| `evt_index` | _integer_ | Event index | -| `trade_id` | _integer_ | n/a | - ## Ser, my platform is not indexed The SQL code that processes the data for every market place is open source and available in our [github repository](https://github.com/duneanalytics/spellbook/tree/master/ethereum/nft/trades). Everyone can review the code, make pull requests and submit code to add more marketplaces. diff --git a/docs/data-tables/spellbook/top-tables/prices.md b/docs/data-tables/spellbook/top-tables/prices.md index 1c85bc51..fe57f774 100644 --- a/docs/data-tables/spellbook/top-tables/prices.md +++ b/docs/data-tables/spellbook/top-tables/prices.md @@ -2,74 +2,120 @@ title: prices description: These tables allow you to get the price of almost all relevant erc20 tokens. --- -We pull price data from the [coinpaprika](https://coinpaprika.com) API. +The price feeds are derived from [Coinpaprika](https://coinpaprika.com/)'s API. The price is the volume-weighted price based on real-time market data, translated to USD. -The Price is the volume-weighted price based on real-time market data, translated to USD. ## prices.usd -This table supports a range of erc20.tokens. - ### adding a token to price tracking -If the token you desire is not listed in here, please make a pull request to our [GitHub repository](https://github.com/duneanalytics/spellbook/blob/main/models/prices/prices_tokens.sql). (For V1 Engine, you can also use the decentralized price feed **dex.view_token_prices.**) +If the token has yet to be listed in here, please make a pull request to our [GitHub repository](https://github.com/duneanalytics/spellbook/blob/main/models/prices/prices_tokens.sql)(Make sure that the token is active on Coinpaprika!). + +| Column Name | Data Type | Description | +|-------------------|---------------|-------------------------------------------------------------| +| `contract_address`| `varbinary` | The contract address of the ERC20 token | +| `blockchain` | `varchar` | The blockchain associated with the ERC20 token | +| `decimals` | `int` | The number of decimal places for the token's value | +| `minute` | `timestamp` | The resolution of this data table in minutes | +| `price` | `double` | The price of the asset in any given minute | +| `symbol` | `varchar` | The identifier of the asset (ticker) | -| Column name | Data type | Description | -| - | :-: | - | -| `contract_address`| _varbinary_ |string the contract address of the erc20 token | -| `symbol` | _varchar_ |the identifier of the asset (ticker, cashtag) | -| `price` | _bigint_ | The price of the asset in any given minute | -| `minute` | _timestampz_ | The resolution for this table is by minute | Note that `WETH` can be used for ETH price as it trades at virtually the same price. +```sql +-- getting the token price for WETH for the past 30 days +select * from prices.usd +where contract_address = 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 +and blockchain = 'ethereum' +and minute >= NOW() - interval '7' day +``` + + + +#### Getting the latest token price + +Just as the table name suggest, this table contains the latest price available, derived from prices.usd + +```sql +-- getting the latest price for 4 tokens +select * from prices.usd_latest +where blockchain = 'ethereum' +and symbol IN ('WETH','WBTC','USDC','USDT') +``` + + + + + ## How we get prices from DEXs We created a table that creates price feeds based on decentralized exchange trading data. This table covers much more assets than `prices.usd`, since it covers all assets that are traded on any of the decentralized exchanges that are indexed in `dex.trades`. **Please keep in mind that this script can generate wrong prices in rare cases.** -This table is very resource intensive and can therefore only be updated every few hours, please keep that in mind when utilizing it. **** Also the resolution is only hourly, so if you need minutely prices do refer to [`prices.usd`](prices.md). +The logic of how this table works can be accessed in our [public github](https://github.com/duneanalytics/spellbook/blob/main/models/dex/dex_prices.sql) repo. + +As there could be potential inaccuracy of prices derived from dex.trades due to low liquidity/high slippage trades. Hence, it is recommended to use [`prices.usd`](prices.md),which prices are sourced directly from Coinpaprika API. -This table currently only exists for Ethereum on our old database architecture. +## How Dex.prices work? -The logic of how this table works can be accessed in our [public github](https://github.com/duneanalytics/spellbook/tree/master/ethereum/prices) repo. +For example, there is a liquidity pool with the token pair $WBTC/ETH -This script generates median hourly prices based on data from decentralized exchanges found in `dex.trades`. It will assign asset prices based on a trading pair which has a pricefeed in `prices.usd`. + Assuming the following: -Let's take the $SPELL/ETH Pool for example. + - $ETH price is contained in `prices.usd` -* $ETH price is contained in `prices.usd` -* $SPELL price is not contained in `prices.usd` + - $WBTC price is not contained in `prices.usd` -In order to get the $SPELL price, the script will dynamically calculate the price of $SPELL based on the price of $ETH that was exchanged for it. +In order to get the $WBTC price, the script will dynamically calculate the price of $WBTC based on the price of $ETH that was exchanged for it. -e.g. 5 $ETH were exchanged for 1,086,083 $SPELL. +e.g. 10 $ETH were exchanged for 0.69 $WBTC. Dex.trades will assign a `usd_amount` to this trade based on the $ETH price data in `prices.usd`. -That `usd_amount` is $23,498. +That `usd_amount` is $17,000. -`5 * price of ETH (4.699,6) = $23,498` +`10 * price of ETH ($1,700) = $17,000` -Calculating the price of $SPELL is now as simple as dividing the amount of tokens exchanged with the `usd_amount` recorded in `dex.trades`. +Calculating the price of $WBTC is now as simple as dividing the amount of tokens exchanged with the `usd_amount` recorded in `dex.trades`. -`$23,498/1,086,083 ≈ $0,02163` +`$17,000 /0.69 ≈ $24,637.68` -We now have successfully calculated the price of 1 $SPELL. +We now have successfully calculated the price of 1 $WBTC. In order to correct for extreme outliers and in order for this table to be performant the script then aggregates all recorded data into one `median_price` per hour. +#### Get daily average price using dex.prices + +```sql +-- get daily average price of weth from dex.prices +select date_trunc('day',hour) as date, + contract_address, + AVG(median_price) as avg_price +from dex.prices +WHERE blockchain = 'ethereum' +AND contract_address = 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 +AND hour >= NOW() - interval '3' day +GROUP BY 1,2 +ORDER BY 1 DESC +``` + + + ### Known issues In rare cases this script will generate price feeds that are based on illiquid pairs and therefore report wrong data. This happens when all liquid trading pools of this token do not have a price feed in `prices.usd`. -An example of this would be $PLAY, a metaverse index from PieDAO. The liquid trading pair for this asset is $PLAY/$DOUGH. The "correct" price of $PLAY is represented in this pool, but the combination of `dex.trades` and `prices.prices_from_dex_data` are not able to pick up this price. +An example of this would be $PLAY, a metaverse index from PieDAO. The liquid trading pair for this asset is $PLAY/$DOUGH. The "correct" price of $PLAY is represented in this pool, but the combination of `dex.trades` and `dex.prices` are not able to pick up this price. -Instead, `dex.trades` will only have a `usd_amount` for illiquid pairs of this asset. In this case, the $PLAY/$ETH pool has trades once in a while and these will have a `usd_amount` in `dex.trades`. The liquidity of the $PLAY/$ETH pool is very low and it pretty much only consists of arbitrage trades. Therefore, the resulting pricefeed in `prices.prices_from_dex_data` is faulty since it depends on the `usd_amount` in `dex.trades`. +Instead, `dex.trades` will only have a `usd_amount` for illiquid pairs of this asset. In this case, the $PLAY/$ETH pool has trades once in a while and these will have a `usd_amount` in `dex.trades`. The liquidity of the $PLAY/$ETH pool is very low and it pretty much only consists of arbitrage trades. Therefore, the resulting pricefeed in `dex.prices` is faulty since it depends on the `usd_amount` in `dex.trades`. -In order to check for this, you should manually verify the results of `prices.prices_from_dex_data` in order to make sure arbitrage trades do not disturb the price feed constructed. A simple way of validating that the script is working with the right pools is checking the `sample_size` column. If the number seems suspiciously low, the script probably doesn't pick up the right price. +In order to check for this, you should manually verify the results of `dex.prices` in order to make sure arbitrage trades do not disturb the price feed constructed. A simple way of validating that the script is working with the right pools is checking the `sample_size` column. If the number seems suspiciously low, the script probably doesn't pick up the right price. In cases like this, you have to manually construct a price feed. -We are always looking to improve this table, if you have any ideas or comments don't hesitate to open a PR or contact us in our Discord. \ No newline at end of file +We are always looking to improve this table, if you have any ideas or comments don't hesitate to open a PR or contact us in our Discord. + + + diff --git a/docs/data-tables/spellbook/top-tables/tokens.md b/docs/data-tables/spellbook/top-tables/tokens.md index b9bf45d3..e0f3c7da 100644 --- a/docs/data-tables/spellbook/top-tables/tokens.md +++ b/docs/data-tables/spellbook/top-tables/tokens.md @@ -9,15 +9,166 @@ You'll likely be working with tokens that are fungible (erc20) and nonfungible ( 1. [**`tokens.erc20`**](https://spellbook-docs.dune.com/#!/model/model.spellbook.tokens_erc20): contains useful information such as the token `symbol` and the `decimals` for any given `contract_address`, the latter of which is needed to get the actual amount from raw amounts in onchain data. +| Column Name | Data Type | Description | +|-------------------|-------------|--------------------------------------------------------| +| `blockchain` | _varchar_ | The blockchain associated with the ERC20 token | +| `contract_address`| _varbinary_ | The contract address of the ERC20 token | +| `decimals` | _int_ | The number of decimal places for the token's value | +| `symbol` | _varchar_ | The identifier of the asset (ticker) | + + +```sql +-- querying using ethereum's weth contract_address +select * from tokens.erc20 +WHERE contract_address = 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 +``` + +| Blockchain | Contract Address | Symbol | Decimals | +|------------|-------------------------------------------|--------|---------- | +| Ethereum | 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 | WETH | 18 | + 2. [**`tokens.nft`**](https://spellbook-docs.dune.com/#!/model/model.spellbook.tokens_nft): contains the collection `name` and `symbol` for any given `contract_address`. These tables are usually joined on `contract_address` at the end of a query to make everything more human readable. +```sql +-- querying using bayc contract +select * from tokens.nft +where contract_address = 0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d +``` + +| Blockchain | Contract Address | Name | Symbol | Token Standard | +|------------|-------------------------------------------|---------------------|--------|---------------- | +| Ethereum | 0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d | Bored Ape Yacht Club | BAYC | ERC721 | + ## Transfer tables: -1. [**`erc20_ethereum.evt_Transfer`**](https://spellbook-docs.dune.com/#!/model/model.spellbook.transfers_ethereum_erc20): all transfer events for every erc20 token. You can find how to get erc20 balances, mints, and burns using [this guide](https://www.youtube.com/watch?v=LT_PB-Fso3M). +1. [**`erc20_ethereum.evt_Transfer`**](https://spellbook-docs.dune.com/#!/model/model.spellbook.transfers_ethereum_erc20): all transfer events for every erc20 token. + +| Column Name | Data Type | Description | +|--------------------|------------------|---------------------------------------------------| +| `contract_address` | _varbinary_ | The contract address. | +| `from` | _varbinary_ | The sender's address. | +| `value` | _uint256_ | The value of the transaction. | +| `evt_block_number` | _bigint_ | The block number of the event. | +| `evt_block_time` | _timestamp_ | The timestamp of the event's block. | +| `evt_index` | _bigint_ | The index of the event within the block. | +| `evt_tx_hash` | _varbinary_ | The transaction hash of the event. | + +#### Get the total inflow and outflow of USDT token from an address in the past 3 days + +```sql +SELECT CASE WHEN "from" = 0xdfd5293d8e347dfe59e90efd55b2956a1343963d THEN 'Outflow' ELSE 'Inflow' END AS token_flow, + SUM(value/POW(10,decimals)) as total_amount +FROM erc20_ethereum.evt_transfer a JOIN tokens.erc20 b ON a.contract_address = b.contract_address +WHERE a.contract_address = 0xdac17f958d2ee523a2206206994597c13d831ec7 +AND ("from" = 0xdfd5293d8e347dfe59e90efd55b2956a1343963d OR "to" = 0xdfd5293d8e347dfe59e90efd55b2956a1343963d) +AND evt_block_time >= NOW() - interval '3' day +GROUP BY 1 +``` + + + +#### Get all holders with their ens and balances of an erc20 token contract -2. [**`nft.transfers`**](https://spellbook-docs.dune.com/#!/model/model.spellbook.nft_transfers): all transfer events for every erc721 or erc1155 token. You can learn how to leverage this to find nft balances, transfers, and mints in [this guide](https://web3datadegens.substack.com/p/web3-sql-weekly-3-finding-all-nfts) +```sql +SELECT address, + symbol, + ARRAY_AGG(distinct name) as ens, + SUM(amount) as balance +FROM ( +SELECT tr."from" AS address, + symbol, + contract_address, + -(tr.value/POW(10,decimals)) AS amount +FROM erc20_ethereum.evt_transfer tr JOIN tokens.erc20 USING (contract_address) +WHERE "from" != 0x0000000000000000000000000000000000000000 -- exclude mint/burn addresses +AND contract_address = 0x046eee2cc3188071c02bfc1745a6b17c656e3f3d -- contract_address of the erc20 token +-- AND evt_block_time <= TIMESTAMP '2023-01-01' -- you can use this to get snapshot data +UNION ALL +SELECT tr."to" AS address, + symbol, + contract_address, + (tr.value/POW(10,decimals)) AS amount +FROM erc20_ethereum.evt_transfer tr JOIN tokens.erc20 USING (contract_address) + WHERE "to" != 0x0000000000000000000000000000000000000000 -- exclude mint/burn addresses + AND contract_address = 0x046eee2cc3188071c02bfc1745a6b17c656e3f3d -- contract_address of the erc20 token +-- AND evt_block_time <= TIMESTAMP '2023-01-01' -- you can use this to get snapshot data + ) x LEFT JOIN labels.ens USING (address) + GROUP BY 1,2 + HAVING SUM(amount) > 0.1 -- having more than 0.1 balance + ORDER BY 4 DESC +``` + + If you're looking for how to calculate native token balances like ethereum (ETH) balances then check out [this guide](https://web3datadegens.substack.com/p/web3-sql-weekly-1-how-to-calculate) +You can find how to get erc20 balances, mints, and burns using [this guide](https://www.youtube.com/watch?v=LT_PB-Fso3M). + +2. [**`nft.transfers`**](https://spellbook-docs.dune.com/#!/model/model.spellbook.nft_transfers): all transfer events for every erc721 or erc1155 token. + +| Column Name | Data Type | Description | +|-------------------|-------------|---------------------------------------------------| +| `contract_address`| _varbinary_ | The contract address | +| `from` | _varbinary_ | The sender's address | +| `to` | _varbinary_ | The recipient's address | +| `tokenId` | _uint256_ | The token ID of the transaction | +| `evt_block_number`| _bigint_ | The block number of the event | +| `evt_block_time` | _timestamp_ | The timestamp of the event's block | +| `evt_index` | _bigint_ | The index of the event within the block | +| `evt_tx_hash` | _varbinary_ | The transaction hash of the event | + +#### Get all erc721 token transfers to an addresses in the past 30 days + +```sql +SELECT date_trunc('day',evt_block_time) as date, + name, + COUNT(*) as transfer_count +FROM erc721_ethereum.evt_transfer LEFT JOIN labels.contracts on to = address +where to = 0xdb5485c85bd95f38f9def0ca85499ef67dc581c0 +AND evt_block_time >= NOW() - interval '30' day +GROUP BY 1,2 +order by 1 desc +``` + + + +#### Get all holders with their ens,labels and balances of an erc721 token contract + +```sql +SELECT z.name, + contract_address, + address, + a.name as ens_name, + ARRAY_AGG(DISTINCT b.name) as labels_list, + nft_list, + number_of_nft_held, + total_nft_supply +FROM ( +SELECT contract_address, + to as address, + ARRAY_AGG(tokenId) as nft_list, + COUNT(*) as number_of_nft_held, + SUM(COUNT(*)) OVER () as total_nft_supply +FROM ( +select contract_address, + to, + tokenId, + ROW_NUMBER() OVER (PARTITION BY contract_address,tokenId ORDER BY evt_block_time DESC,evt_index DESC) as rn +from erc721_ethereum.evt_transfer +where contract_address = 0xBC4CA0EdA7647A8aB7C2061c2E118A18a936f13D +) x +WHERE rn = 1 +GROUP BY 1,2 +) p +LEFT JOIN tokens.nft z USING (contract_address) +LEFT JOIN ens.reverse_latest a USING (address) +LEFT JOIN labels.addresses b USING (address) +GROUP BY 1,2,3,4,6,7,8 +ORDER BY 7 DESC +``` + + + +You can learn how to leverage this to find nft balances, transfers, and mints in [this guide](https://web3datadegens.substack.com/p/web3-sql-weekly-3-finding-all-nfts) \ No newline at end of file