diff --git a/api-reference/dex/endpoint/dex_ohlc.mdx b/api-reference/dex/endpoint/dex_ohlc.mdx index a3aab533..7f59561f 100644 --- a/api-reference/dex/endpoint/dex_ohlc.mdx +++ b/api-reference/dex/endpoint/dex_ohlc.mdx @@ -4,7 +4,7 @@ openapi: 'GET /v1/dex/ohlc/{token}/{chain}' --- -- You must pass in `token` address in all lower cased string +- You must pass in `token` address in all lowercase string - Query can be found [here](https://dune.com/queries/3582296) - Chains included are: all [EVM chains on Dune](/data-catalog/evm/overview) - Scheduled to update every 30 minutes @@ -24,10 +24,10 @@ openapi: 'GET /v1/dex/ohlc/{token}/{chain}' | period | Date of the pricing data | string | | token_contract_address| Token's blockchain contract address | string | | token_symbol | Token symbol | string | -| blockchain | Blockchain where the token is deployed on | string | +| blockchain | Blockchain where the token is deployed | string | | median_price | The median trading price of the token for the period | double | -| high_price | The highest trading price of the token during the period, calculated by taking the 99th percentile of day's trades if there are more than 1000 trades for the token on that day, else 95th percentile to account for edge cases | double | -| low_price | The lowest trading price of the token during the period, calculated by taking the 1st percentile of day's trades if there are more than 1000 trades for the token on that day, else 5th percentile to account for edge cases | double | +| high_price | The highest trading price of the token during the period, calculated by taking the 99th percentile of the day's trades if there are more than 1000 trades for the token on that day, else 95th percentile to account for edge cases | double | +| low_price | The lowest trading price of the token during the period, calculated by taking the 1st percentile of the day's trades if there are more than 1000 trades for the token on that day, else 5th percentile to account for edge cases | double | | opening_price | The price of the token at the start of the period, calculated by taking the first 10 trades of the day | double | | closing_price | The price of the token at the end of the period, calculated by taking the last 10 trades of the day | double | | sample_size | The number of trades sampled to calculate the prices | int | diff --git a/api-reference/dex/endpoint/dex_pair.mdx b/api-reference/dex/endpoint/dex_pair.mdx index 36ef7f6e..fb5eedb8 100644 --- a/api-reference/dex/endpoint/dex_pair.mdx +++ b/api-reference/dex/endpoint/dex_pair.mdx @@ -32,4 +32,4 @@ openapi: 'GET /v1/dex/pairs/{chain}' | thirty_day_volume | 30-day USD trading volume for the token pair across all pools on all DEXes | double | | all_time_volume | Total USD trading volume for the token pair since inception across all pools on all DEXes | double | | usd_liquidity | Current USD liquidity available in all pools for the token pair on all DEXes | double | -| seven_day_volume_liquidity_ratio| 7-day trading volume to liquidity ratio for the token pair across all pools on all DEXes | double | +| seven_day_volume_liquidity_ratio| 7-day trading volume to liquidity ratio for the token pair across all pools on all DEXes | double | diff --git a/api-reference/eigenlayer/endpoint/avs_metadata.mdx b/api-reference/eigenlayer/endpoint/avs_metadata.mdx index 89ddc013..eac55f92 100644 --- a/api-reference/eigenlayer/endpoint/avs_metadata.mdx +++ b/api-reference/eigenlayer/endpoint/avs_metadata.mdx @@ -5,7 +5,7 @@ openapi: 'GET /v1/eigenlayer/avs-metadata' - Query powering this endpoint can be found [here](https://dune.com/queries/3682939) -- Scheduled to update daily (_AVS registration happen once every few days normally_) +- Scheduled to update daily (_AVS registrations happen once every few days normally_) diff --git a/api-reference/eigenlayer/endpoint/avs_metrics.mdx b/api-reference/eigenlayer/endpoint/avs_metrics.mdx index c4e66731..60fb0035 100644 --- a/api-reference/eigenlayer/endpoint/avs_metrics.mdx +++ b/api-reference/eigenlayer/endpoint/avs_metrics.mdx @@ -16,7 +16,7 @@ openapi: 'GET /v1/eigenlayer/avs-stats' | ------------------------- | ------------------------------------------------------------------- | ---------- | | avs_name | Name of the Actively Validated Service (AVS) | string | | avs_contract_address | Ethereum contract address of the AVS | string | -| num_operators | Number of operators resgistered to the AVS | integer | +| num_operators | Number of operators registered to the AVS | integer | | total_TVL | Total value locked across all strategies in the AVS | double | | num_stakers | Number of stakers currently staking to the AVS (via operators) | integer | | cbETH_TVL | Total value locked in cbETH strategy in the AVS | double | diff --git a/api-reference/eigenlayer/endpoint/operator_metadata.mdx b/api-reference/eigenlayer/endpoint/operator_metadata.mdx index 339d1740..58714c08 100644 --- a/api-reference/eigenlayer/endpoint/operator_metadata.mdx +++ b/api-reference/eigenlayer/endpoint/operator_metadata.mdx @@ -5,7 +5,7 @@ openapi: 'GET /v1/eigenlayer/operator-metadata' - Query powering this endpoint can be found [here](https://dune.com/queries/3685760) -- Scheduled to update 15 minutes +- Scheduled to update every 15 minutes - Apply [filters](../../executions/filtering) like WHERE, IN, AND/OR upon results - Use a combination of `sort_by` and `limit` to grab a subset of results, see [pagination](../../executions/pagination) and [sorting](../../executions/sorting) for more info diff --git a/api-reference/eigenlayer/endpoint/operator_metrics.mdx b/api-reference/eigenlayer/endpoint/operator_metrics.mdx index 6647dc39..ea6ee917 100644 --- a/api-reference/eigenlayer/endpoint/operator_metrics.mdx +++ b/api-reference/eigenlayer/endpoint/operator_metrics.mdx @@ -5,7 +5,7 @@ openapi: 'GET /v1/eigenlayer/operator-stats' - Query powering this endpoint can be found [here](https://dune.com/queries/3685928) -- Scheduled to update 15 minutes +- Scheduled to update every 15 minutes - Apply [filters](../../executions/filtering) like WHERE, IN, AND/OR upon results - Use a combination of `sort_by` and `limit` to grab a subset of results, see [pagination](../../executions/pagination) and [sorting](../../executions/sorting) for more info @@ -31,4 +31,4 @@ openapi: 'GET /v1/eigenlayer/operator-stats' | lsETH_TVL | Total value locked in lsETH strategy in the operator | double | | mETH_TVL | Total value locked in mETH strategy in the operator | double | | beacon_chain_ETH_TVL | Total value locked in Beacon Chain ETH strategy in the operator | double | -| EIGEN_TVL | Total value locked in EIGEN strategy in the AVS | double | +| EIGEN_TVL | Total value locked in EIGEN strategy in the operator | double | diff --git a/api-reference/eigenlayer/endpoint/operator_to_avs_mapping.mdx b/api-reference/eigenlayer/endpoint/operator_to_avs_mapping.mdx index 93c8f0bf..24903c8a 100644 --- a/api-reference/eigenlayer/endpoint/operator_to_avs_mapping.mdx +++ b/api-reference/eigenlayer/endpoint/operator_to_avs_mapping.mdx @@ -5,7 +5,7 @@ openapi: 'GET /v1/eigenlayer/operator-to-avs-mapping' - Query powering this endpoint can be found [here](https://dune.com/queries/3685583) -- Scheduled to update 15 minutes +- Scheduled to update every 15 minutes - Apply [filters](../../executions/filtering) like WHERE, IN, AND/OR upon results - Use a combination of `sort_by` and `limit` to grab a subset of results, see [pagination](../../executions/pagination) and [sorting](../../executions/sorting) for more info diff --git a/api-reference/eigenlayer/introduction.mdx b/api-reference/eigenlayer/introduction.mdx index ab29d780..887f82e1 100644 --- a/api-reference/eigenlayer/introduction.mdx +++ b/api-reference/eigenlayer/introduction.mdx @@ -6,7 +6,7 @@ Leverage Dune's API for direct access to [EigenLayer](https://www.eigenlayer.xyz - **JSON Format**: All endpoints deliver JSON-formatted data for straightforward integration. - **Instant Access**: Begin immediately by [creating a free account](https://dune.com/auth/register) and [obtain an API key](.././overview/authentication). -- **Expansive Data Ecosystem**: Enhance your projects by connecting with an extensive range of on-chain and off-chain data, from [Farcaster](.././farcaster/introduction) to [DEX](../dex/endpoint/dex_pair.mdx) and more. Build alongside with our vibrant community. +- **Expansive Data Ecosystem**: Enhance your projects by connecting with an extensive range of on-chain and off-chain data, from [Farcaster](.././farcaster/introduction) to [DEX](../dex/endpoint/dex_pair.mdx) and more. Build alongside our vibrant community. diff --git a/api-reference/evm/endpoint/contracts.mdx b/api-reference/evm/endpoint/contracts.mdx index 319cba4a..9e9ec289 100644 --- a/api-reference/evm/endpoint/contracts.mdx +++ b/api-reference/evm/endpoint/contracts.mdx @@ -12,7 +12,7 @@ openapi: 'GET /v1/trends/evm/contracts/{chain}' # Use Cases - Feed into a CRM of developers and projects based on contract popularity -- Build an explorer page of top trending contracts, with basic metadata to support. +- Build an explorer page of top trending contracts with basic metadata support. - Track trending contracts by value and type (user facing, contract facing, token, router, safes, etc.) # Column Descriptions @@ -26,7 +26,7 @@ openapi: 'GET /v1/trends/evm/contracts/{chain}' | contract_name | Name of the contract | string | | created_time | Time when the contract was created | string | | deployed_days_ago | Number of days since deployment | integer | -| token_standard | Standard of the token (ERC20,ERC721,ERC1155) if applicable | string | +| token_standard | Standard of the token (ERC20, ERC721, ERC1155) if applicable | string | | usd_value_received | Value received in USD in ETH and ERC20 tokens in last 30 days | integer | | transaction_calls | Number of transaction calls (top level transactions) in last 30 days | integer | | unique_callers | Number of unique callers (tx from) in last 30 days | integer | diff --git a/api-reference/executions/endpoint/cancel-execution.mdx b/api-reference/executions/endpoint/cancel-execution.mdx index a31c35a5..bb15bd6d 100644 --- a/api-reference/executions/endpoint/cancel-execution.mdx +++ b/api-reference/executions/endpoint/cancel-execution.mdx @@ -5,7 +5,7 @@ openapi: 'POST /v1/execution/{execution_id}/cancel' You must pass the `execution_id` obtained from making an [execute query](/api-reference/executions/endpoint/execute-query) POST request. -Result returns a boolean for whether the execution is successfully canceled. +The result returns a boolean for whether the execution is successfully canceled. diff --git a/api-reference/executions/endpoint/execute-query.mdx b/api-reference/executions/endpoint/execute-query.mdx index 991ed391..398b54f5 100644 --- a/api-reference/executions/endpoint/execute-query.mdx +++ b/api-reference/executions/endpoint/execute-query.mdx @@ -4,7 +4,7 @@ openapi: 'POST /v1/query/{query_id}/execute' --- - If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly executes and fetches result in one function call, like below: + If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly execute and fetch result in one function call, like below: Use `run_query` to get result in JSON, `run_query_csv` to get result in CSV format, diff --git a/api-reference/executions/endpoint/get-execution-result-csv.mdx b/api-reference/executions/endpoint/get-execution-result-csv.mdx index 615d39e7..a3893bbb 100644 --- a/api-reference/executions/endpoint/get-execution-result-csv.mdx +++ b/api-reference/executions/endpoint/get-execution-result-csv.mdx @@ -20,7 +20,7 @@ Result returns the status, metadata, and query results (in CSV) from a query exe - If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly executes and fetches result in one function call, like below: + If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly execute and fetch result in one function call, like below: ``` python Python SDK diff --git a/api-reference/executions/endpoint/get-execution-status.mdx b/api-reference/executions/endpoint/get-execution-status.mdx index b020b17b..f778f081 100644 --- a/api-reference/executions/endpoint/get-execution-status.mdx +++ b/api-reference/executions/endpoint/get-execution-status.mdx @@ -17,7 +17,7 @@ Once an execution is triggered, it can be in one of the following states: - `QUERY_STATE_COMPLETED`: The query execution completed successfully. You can retrieve the query result for this execution_id. - `QUERY_STATE_CANCELED`: The query execution was canceled by the user. - `QUERY_STATE_EXPIRED`: The query execution expired, and the result is no longer available. -- `QUERY_STATE_COMPLETED_PARTIAL`: The query execution was successful, but the result was truncated because it was too large. To receive the truncated result, set the `allow_partial_results` flag to `true` in the API request to fetch result. +- `QUERY_STATE_COMPLETED_PARTIAL`: The query execution was successful, but the result was truncated because it was too large. To receive the truncated result, set the `allow_partial_results` flag to `true` in the API request to fetch the result. diff --git a/api-reference/executions/endpoint/get-query-result-csv.mdx b/api-reference/executions/endpoint/get-query-result-csv.mdx index 2f69dd06..f1cbf0a0 100644 --- a/api-reference/executions/endpoint/get-query-result-csv.mdx +++ b/api-reference/executions/endpoint/get-query-result-csv.mdx @@ -20,7 +20,7 @@ The query specified must either be public or a query you have ownership of (you - If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly executes and fetches result in one function call, like below: + If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly execute and fetch result in one function call, like below: ``` python Python SDK @@ -39,7 +39,7 @@ The query specified must either be public or a query you have ownership of (you ``` Use `run_query` to get result in JSON, `run_query_csv` to get result in CSV format, - and `run_query_dataframe` to get result in Pandas dataframe + and `run_query_dataframe` to get result in Pandas dataframe. ``` result = dune.run_query( diff --git a/api-reference/executions/endpoint/get-query-result.mdx b/api-reference/executions/endpoint/get-query-result.mdx index fc95146b..e35bc203 100644 --- a/api-reference/executions/endpoint/get-query-result.mdx +++ b/api-reference/executions/endpoint/get-query-result.mdx @@ -20,7 +20,7 @@ The query specified must either be public or a query you have ownership of (you - If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly executes and fetches result in one function call, like below: + If you are using the [Python SDK](https://github.com/duneanalytics/dune-client/tree/d2195b2a9577e2dcae5d2600cb3eddce20987f38), you can directly execute and fetch result in one function call, like below: ``` python Python SDK diff --git a/api-reference/executions/execution-object.mdx b/api-reference/executions/execution-object.mdx index 6272d895..de47865e 100644 --- a/api-reference/executions/execution-object.mdx +++ b/api-reference/executions/execution-object.mdx @@ -59,7 +59,7 @@ Below is an overview of each endpoint, providing a high-level understanding of t |--------------------------|-----------------------------------|-----------------------------------------------------------------------------------------------| | [Cancel Execution](./endpoint/cancel-execution) | `POST /v1/execution/{execution_id}/cancel` | Cancels an ongoing query execution. Requires the `execution_id`. Returns a success boolean. | | [Execute Query](./endpoint/execute-query) | `POST /v1/query/{query_id}/execute` | Triggers an execution based on the `query_id`. Returns a `execution_id`. | -| [Get Execution Status](./endpoint/get-execution-status) | `GET /v1/execution/{execution_id}/status` | Provides the status of a query execution give an `execution_id`. | +| [Get Execution Status](./endpoint/get-execution-status) | `GET /v1/execution/{execution_id}/status` | Provides the status of a query execution given an `execution_id`. | | [Get Execution Result in CSV](./endpoint/get-execution-result-csv) | `GET /v1/execution/{execution_id}/results/csv` | Retrieves the status, metadata, and results in CSV format. Includes data retention and limit information. | | [Get Execution Result](./endpoint/get-execution-result) | `GET /v1/execution/{execution_id}/results` | Fetches the execution status, metadata, and results in JSON format. Similar data handling as CSV endpoint. | | [Get Latest Query Result in CSV](./endpoint/get-query-result-csv) | `GET /v1/query/{query_id}/results/csv` | Returns the latest results of a query in CSV format, irrespective of the execution method. Queries must be public or owned. | diff --git a/api-reference/executions/filtering.mdx b/api-reference/executions/filtering.mdx index 21459151..9c9f3d4d 100644 --- a/api-reference/executions/filtering.mdx +++ b/api-reference/executions/filtering.mdx @@ -20,7 +20,7 @@ Filtering can be effectively used in conjunction with [pagination](./pagination) from dune_client.client import DuneClient from dune_client.query import QueryBase - os.chdir("") + os.chdir("") # load .env file dotenv.load_dotenv(".env") @@ -112,7 +112,7 @@ Filtering can be effectively used in conjunction with [pagination](./pagination) // Create query parameters params := url.Values{} - params.Set("limit", 10) + params.Set("limit", "10") params.Set("filters", "block_time > '2024-03-01'") params.Set("columns", "tx_from,tx_to,tx_hash,amount_usd") params.Set("sort_by", "amount_usd desc, block_time") diff --git a/api-reference/executions/pagination.mdx b/api-reference/executions/pagination.mdx index 84932cae..8925a7ea 100644 --- a/api-reference/executions/pagination.mdx +++ b/api-reference/executions/pagination.mdx @@ -30,7 +30,7 @@ Pagination can be effectively combined with [filtering](./filtering) and [sortin from dune_client.client import DuneClient from dune_client.query import QueryBase - os.chdir("") + os.chdir("") # load .env file dotenv.load_dotenv(".env") @@ -126,7 +126,7 @@ Pagination can be effectively combined with [filtering](./filtering) and [sortin // Create query parameters params := url.Values{} - params.Set("limit", 1000) + params.Set("limit", "1000") // Add parameters to URL fullURL := fmt.Sprintf("%s?%s", url, params.Encode()) diff --git a/api-reference/executions/sampling.mdx b/api-reference/executions/sampling.mdx index 233f1860..7086d264 100644 --- a/api-reference/executions/sampling.mdx +++ b/api-reference/executions/sampling.mdx @@ -18,7 +18,7 @@ Our API supports sampling on all `/results` endpoints to provide a uniform sampl from dune_client.client import DuneClient from dune_client.query import QueryBase - os.chdir("") + os.chdir("") # load .env file dotenv.load_dotenv(".env") diff --git a/api-reference/executions/sorting.mdx b/api-reference/executions/sorting.mdx index 83f065c9..bb17d998 100644 --- a/api-reference/executions/sorting.mdx +++ b/api-reference/executions/sorting.mdx @@ -20,7 +20,7 @@ Sorting can be effectively combined with [pagination](./pagination), [filtering] from dune_client.client import DuneClient from dune_client.query import QueryBase - os.chdir("") + os.chdir("") # load .env file dotenv.load_dotenv(".env") diff --git a/api-reference/farcaster/endpoint/farcaster_channels.mdx b/api-reference/farcaster/endpoint/farcaster_channels.mdx index 68302f9e..1a3fe2ae 100644 --- a/api-reference/farcaster/endpoint/farcaster_channels.mdx +++ b/api-reference/farcaster/endpoint/farcaster_channels.mdx @@ -28,8 +28,8 @@ openapi: 'GET /v1/farcaster/trends/channels' | influential_casters | top casters by engagement in channel| array(string) | | top_domains | top domains in casts in channel | array(string) | | top_casters | top casters by number of casts in channel | array(string) | -| casters | number of casts in channels in the last week | integer | -| wow_cast | week over week change in number of casts | integer | +| casters | number of casters in channels in the last week | integer | +| wow_casters | week over week change in number of casters | integer | | got_casts | number of casts in channels in the last week | integer | | wow_cast | week over week change in number of casts | integer | | engagement | engagement on channel casts in the last week | integer | diff --git a/api-reference/farcaster/endpoint/farcaster_memecoins.mdx b/api-reference/farcaster/endpoint/farcaster_memecoins.mdx index 93ba897f..8f1e0608 100644 --- a/api-reference/farcaster/endpoint/farcaster_memecoins.mdx +++ b/api-reference/farcaster/endpoint/farcaster_memecoins.mdx @@ -21,13 +21,13 @@ Learn more about the score and methodology [in this article](https://read.crypto | Column | Description | Type | | --------------------- | --------------------------------------------------------------------- | ------- | | word_raw | Ticker symbol of the token | string | -| related_symbol | any symbol or word that is related to the token (i.e. the degen hat or higher arrow) | string | +| related_symbol | Any symbol or word that is related to the token (i.e. the degen hat or higher arrow) | string | | token_contract_address| Contract address of the token | string | | blockchain | Blockchain on which the token is deployed | string | | deployed_days_ago | Number of days since the token was deployed | integer | | social_score | Social score of the token | integer | | financial_score | Financial score of the token | integer | -| meme_category | category of meme based off of social and financial score values | string | +| meme_category | Category of meme based off of social and financial score values | string | | casters | Number of users who have casted the token ticker | integer | | casters_wow | Change in the number of casters week over week | integer | | percent_recipient_casters | Percentage of casters this week that have received the token before | integer | diff --git a/api-reference/farcaster/endpoint/farcaster_users.mdx b/api-reference/farcaster/endpoint/farcaster_users.mdx index 2890cf52..e8022c00 100644 --- a/api-reference/farcaster/endpoint/farcaster_users.mdx +++ b/api-reference/farcaster/endpoint/farcaster_users.mdx @@ -20,22 +20,22 @@ openapi: 'GET /v1/farcaster/trends/users' | Column | Description | Type | | --------------------- | ------------------------------------- | ---------- | -| fid_active_tier_name | name of farcaster tier this week | string | -| fid_active_tier | farcaster user tier this week | integer | -| fid_active_tier_last | farcaster user tier last week | integer | -| fid | farcaster user id | integer | -| fname | farcaster username of user | string | +| fid_active_tier_name | name of Farcaster tier this week | string | +| fid_active_tier | Farcaster user tier this week | integer | +| fid_active_tier_last | Farcaster user tier last week | integer | +| fid | Farcaster user id | integer | +| fname | Farcaster username of user | string | | account_age | age of account in days | integer | -| channels | number of casted in channels in the last week | integer | -| top_channels | top casted in channels | array(string)| -| top_domains | top casted domains | array(string)| +| channels | number of channels cast in during the last week | integer | +| top_channels | top channels cast in | array(string)| +| top_domains | top domains cast | array(string)| | top_engagers | top cast engagers | array(string)| | followers | total number of followers | integer | | wow_followers | week over week change in number of followers | integer | | casts | number of casts in the last week | integer | | wow_casts | week over week change in number of casts | integer | | engagement | engagement on user casts in the last week | integer | -| wow_engage | week over week change in number of engage | integer | +| wow_engage | week over week change in number of engagements | integer | | total_transactions | total number of wallet transactions | integer | | trading_volume_usd | total NFT and DEX trading volume (USD)| integer | | contracts_deployed | total number of deployed contracts | integer | diff --git a/api-reference/farcaster/introduction.mdx b/api-reference/farcaster/introduction.mdx index 31192224..a74a0838 100644 --- a/api-reference/farcaster/introduction.mdx +++ b/api-reference/farcaster/introduction.mdx @@ -2,7 +2,7 @@ title: "Dune Farcaster Endpoints" --- -While you can create/use any query as an API endpoint, we've defined three popular queries as custom endpoints (so you don't need to worry about executions or editing SQL). You should use these endpoints to provide better data to inform your algorithims, recomendations, or UI elements. +While you can create/use any query as an API endpoint, we've defined three popular queries as custom endpoints (so you don't need to worry about executions or editing SQL). You should use these endpoints to provide better data to inform your algorithms, recommendations, or UI elements. -- This endpoint will create a new matview if none exists for the gven query ID, or update an existing one if the query ID matches. +- This endpoint will create a new matview if none exists for the given query ID, or update an existing one if the query ID matches. - It will fail to create a matview with the same name as an existing one, but for a different query ID - The name of the matview is just the last part of the matview, not including `dune..` and must be prefixed with `result_` - The `cron_expression` parameter must be passed in as a valid 5 section cron expression. [See here](https://crontab.guru/) for how to write them. diff --git a/api-reference/materialized-views/delete.mdx b/api-reference/materialized-views/delete.mdx index 213c51ea..c1e998c7 100644 --- a/api-reference/materialized-views/delete.mdx +++ b/api-reference/materialized-views/delete.mdx @@ -5,5 +5,5 @@ openapi: 'DELETE /v1/materialized-views/{name}' -- The name must be the full name qualifier for the matview, i.e. `dune..` +- The name must be the full name qualifier for the materialized view, i.e. `dune..` diff --git a/api-reference/materialized-views/get.mdx b/api-reference/materialized-views/get.mdx index b3dab28f..e4513587 100644 --- a/api-reference/materialized-views/get.mdx +++ b/api-reference/materialized-views/get.mdx @@ -5,5 +5,5 @@ openapi: 'GET /v1/materialized-views/{name}' -- The name must be the full name qualifier for the matview, i.e. `dune..` +- The name must be the full name qualifier for the materialized view, i.e. `dune..` diff --git a/api-reference/overview/billing.mdx b/api-reference/overview/billing.mdx index a0800ac3..a7ee2af8 100644 --- a/api-reference/overview/billing.mdx +++ b/api-reference/overview/billing.mdx @@ -3,7 +3,7 @@ title: 'Billing' icon: "file-invoice-dollar" --- -Pricing for API is charged along two dimensions. All details can be found at [dune.com/pricing](https://dune.com/pricing) +Pricing for the API is charged along two dimensions. All details can be found at [dune.com/pricing](https://dune.com/pricing) If your execution fails, then no credits are charged. If you execute a query but never pull the results, you are only charged for the execution. @@ -17,7 +17,7 @@ If your execution fails, then no credits are charged. If you execute a query but | Queries Endpoint | Available on Plus and Premium | | Webhooks (Alerts) | 1 on Free

5 on Plus

50 on Premium | -A datapoint applies to query results after the query is run, and can in most cases be thought of `rows * columns` with an additional limit of 100 avg bytes per cell in a set of results. This can be expressed as: +A datapoint applies to query results after the query is run, and can in most cases be thought of as `rows * columns` with an additional limit of 100 avg bytes per cell in a set of results. This can be expressed as: $$ Credits = \frac{Datapoints}{1000} = \frac{\max(\text{rows} * \text{columns}, \lceil \frac{\text{totalbytes}}{100} \rceil)}{1000} diff --git a/api-reference/overview/faq.mdx b/api-reference/overview/faq.mdx index 76168712..e443fae7 100644 --- a/api-reference/overview/faq.mdx +++ b/api-reference/overview/faq.mdx @@ -9,7 +9,7 @@ There are no major performance differences within a specific performance tier wh The Dune API gives you programmatic access to the capabilities and data sets that can already be accessed from the Dune web app. The same queries and results exist in the web app, even if created/executed from the API (and vice versa). -#### What are Sim APIs and how do they differ from the Dune API? +#### What are Sim APIs and how do they differ from the Dune API? Sim APIs, formerly Echo, are a separate, developer-focused product by Dune, providing realtime access to EVM and SVM blockchain data. They are designed for building apps like realtime wallets and AI agents. @@ -64,7 +64,7 @@ Yes! The results storage period can be found on the API response on the “expires_at” field in the execution status and results body. -#### How do I import Dune data into a google sheet? +#### How do I import Dune data into a Google sheet? -Use "Import Data" to import your CSV results into a google sheet using "api_key" as a param. (We advise against doing this any public document where your API key can be viewed and compromised.) +Use "Import Data" to import your CSV results into a Google sheet using "api_key" as a param. (We advise against doing this in any public document where your API key can be viewed and compromised.) `=importData("https://api.dune.com/api/v1/query/{{query_id}}/results/csv?api_key={{api_key}}")`. Then, [schedule a query execution](https://dune.com/docs/app/query-editor/query-scheduler/?h=scheduling) to have your results regularly updated on a set schedule. \ No newline at end of file diff --git a/api-reference/overview/introduction.mdx b/api-reference/overview/introduction.mdx index 93d51e82..6f66fce9 100644 --- a/api-reference/overview/introduction.mdx +++ b/api-reference/overview/introduction.mdx @@ -35,13 +35,14 @@ They offer improved performance and a broader set of features for developers. ## Custom Endpoints - - Create and manage API endpoints from Dune queries directly on the web app, enabling data consumption via custom URLs with scheduled query execution. - + + + Create and manage API endpoints from Dune queries directly on the web app, enabling data consumption via custom URLs with scheduled query execution. + ## SQL Endpoints They help you manage and execute queries, as well as fetch data from these queries. diff --git a/api-reference/overview/rate-limits.mdx b/api-reference/overview/rate-limits.mdx index 3533d785..751038e3 100644 --- a/api-reference/overview/rate-limits.mdx +++ b/api-reference/overview/rate-limits.mdx @@ -44,4 +44,4 @@ For example, on the Free plan, you have a low limit of 15 requests per minute an **Data Return Limit** -Dune internally has a maximum query result size limit (which currently is 8GB, but subject to increase in the future). If your query yields more than 8GB of data, the result will be truncated in storage. In such cases, pulling the result data (using pagination) but without specifying `allow_partial_results` set to true will trigger an error message: "error": "Partial Result, please request with 'allows_partial_results=true'". If you wish to retrieve partial results, you can pass the parameter `allow_partial_results=true`. But please make sure you indeed want to fetch the truncated result. +Dune internally has a maximum query result size limit (which currently is 8GB, but subject to increase in the future). If your query yields more than 8GB of data, the result will be truncated in storage. In such cases, pulling the result data (using pagination) but without specifying `allow_partial_results` set to true will trigger an error message: "error": "Partial Result, please request with 'allow_partial_results=true'". If you wish to retrieve partial results, you can pass the parameter `allow_partial_results=true`. But please make sure you indeed want to fetch the truncated result. diff --git a/api-reference/overview/sdks.mdx b/api-reference/overview/sdks.mdx index d06fbd94..19ff58cc 100644 --- a/api-reference/overview/sdks.mdx +++ b/api-reference/overview/sdks.mdx @@ -7,7 +7,7 @@ icon: "sd-cards" We currently support a [Python SDK](https://github.com/duneanalytics/dune-client) for working with our API. You'll find `Python SDK` snippets on all endpoint pages, if you want to go deeper into the code then check out [these files](https://github.com/duneanalytics/dune-client/tree/main/dune_client/api). -To still the SDK, run the following command in your terminal: +To install the SDK, run the following command in your terminal: ```bash pip install dune-client @@ -49,7 +49,7 @@ results_df = dune.run_query_dataframe(query) ## Typescript -We have a community client from that can be [found here](https://www.npmjs.com/package/@duneanalytics/client-sdk). +We have a community client that can be [found here](https://www.npmjs.com/package/@duneanalytics/client-sdk). To install, run this command @@ -66,7 +66,7 @@ const { DUNE_API_KEY } = process.env; const client = new DuneClient(DUNE_API_KEY ?? ""); const queryID = 1215383; const params = { - query_parameters = [ + query_parameters: [ QueryParameter.text("TextField", "Plain Text"), QueryParameter.number("NumberField", 3.1415926535), QueryParameter.date("DateField", "2022-05-04 00:00:00"), diff --git a/api-reference/overview/troubleshooting.mdx b/api-reference/overview/troubleshooting.mdx index 8bd2db59..3799bc9a 100644 --- a/api-reference/overview/troubleshooting.mdx +++ b/api-reference/overview/troubleshooting.mdx @@ -17,7 +17,7 @@ Dune uses conventional HTTP response codes to indicate the success or failure of | 429 | Too Many Requests | Too many requests hit the API too quickly (rate limited). | | 500 | Server Errors | Generic internal server error. | -For specific error code information, please refer to each of the endpoint itself. Here we list some common errors and suggest possible solution: +For specific error code information, please refer to each of the endpoints themselves. Here we list some common errors and suggest possible solutions: #### Invalid API key ```json @@ -34,7 +34,7 @@ You did not input a valid API key. You can go generate a new key and make sure y "error": "not found: Query not found or private" } ``` -When you perform an action to a private query your API key doesn't have access to, you will get this error. If you indeed own this query, please check the context of the API key and the query owner are the same. +When you perform an action on a private query your API key doesn't have access to, you will get this error. If you indeed own this query, please check that the context of the API key and the query owner are the same. #### Credit limit error diff --git a/api-reference/projects/endpoint/linea_lxp.mdx b/api-reference/projects/endpoint/linea_lxp.mdx index f0d3791f..81899368 100644 --- a/api-reference/projects/endpoint/linea_lxp.mdx +++ b/api-reference/projects/endpoint/linea_lxp.mdx @@ -15,7 +15,7 @@ openapi: 'GET /v1/points/linea/lxp' | Column | Description | Type | | ----------------------- | ------------------------------------------------------- | --------------- | -| wallet | User wallet which hold LXP points | string | +| wallet | User wallet which holds LXP points | string | | current_lxp | Current [Linea Voyage LXP](https://docs.linea.build/use-mainnet/linea-xp) balance | double | | num_quests | Number of quests completed by the user to obtain LXP | integer | | on_farcaster | Indicates if the wallet is connected to a Farcaster account | boolean | @@ -24,7 +24,7 @@ openapi: 'GET /v1/points/linea/lxp' | connected_wallets | List of wallet addresses connected to the user | array(string)| | L14D_active_tier | The active tier of the connected wallet user over the last 14 days. Possible values are "vip", "influencer", "star", "active", "npc", and "not active" | string | | top_channels | Top 3 channels where connected wallet user is active | array(string) | -| top_domains | Top 3 domains frequented casted by the connected wallet user | array(string) | +| top_domains | Top 3 domains frequently casted by the connected wallet user | array(string) | | top_engagers | Top 3 users who engage with this connected wallet user | array(string) | | num_followers | Number of followers the connected wallet user has on Farcaster | integer | | num_onchain_txns | Number of on-chain transactions performed by the connected wallet user | integer | diff --git a/api-reference/projects/introduction.mdx b/api-reference/projects/introduction.mdx index b6936169..e7e994c4 100644 --- a/api-reference/projects/introduction.mdx +++ b/api-reference/projects/introduction.mdx @@ -16,7 +16,7 @@ Utilize Dune's dedicated APIs to access specific project, protocol, or topic dat icon="road-bridge" href="/api-reference/projects/endpoint/linea_lxp" > - Get LXP balance for wallet, along with social and onchain behavior stats + Get LXP balance for wallet, along with social and on-chain behavior stats diff --git a/api-reference/queries/endpoint/archive.mdx b/api-reference/queries/endpoint/archive.mdx index 542dfd0a..52823f9e 100644 --- a/api-reference/queries/endpoint/archive.mdx +++ b/api-reference/queries/endpoint/archive.mdx @@ -14,7 +14,7 @@ To access Query endpoints, an [Analyst plan](https://dune.com/pricing) or higher ```bash cURL -curl --request GET \ +curl --request POST \ --url https://api.dune.com/api/v1/query/{queryId}/archive \ --header 'X-DUNE-API-KEY: ' ``` @@ -37,14 +37,14 @@ url = "https://api.dune.com/api/v1/query/{queryId}/archive" headers = {"X-DUNE-API-KEY": ""} -response = requests.request("GET", url, headers=headers) +response = requests.request("POST", url, headers=headers) print(response.text) ``` ```javascript JavaScript -const options = {method: 'GET', headers: {'X-DUNE-API-KEY': ''}}; +const options = {method: 'POST', headers: {'X-DUNE-API-KEY': ''}}; fetch('https://api.dune.com/api/v1/query/{queryId}/archive', options) .then(response => response.json()) @@ -65,7 +65,7 @@ func main() { url := "https://api.dune.com/api/v1/query/{queryId}/archive" - req, _ := http.NewRequest("GET", url, nil) + req, _ := http.NewRequest("POST", url, nil) req.Header.Add("X-DUNE-API-KEY", "") @@ -92,7 +92,7 @@ curl_setopt_array($curl, [ CURLOPT_MAXREDIRS => 10, CURLOPT_TIMEOUT => 30, CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1, - CURLOPT_CUSTOMREQUEST => "GET", + CURLOPT_CUSTOMREQUEST => "POST", CURLOPT_HTTPHEADER => [ "X-DUNE-API-KEY: " ], @@ -111,7 +111,7 @@ if ($err) { ``` ```java Java -HttpResponse response = Unirest.get("https://api.dune.com/api/v1/query/{queryId}/archive") +HttpResponse response = Unirest.post("https://api.dune.com/api/v1/query/{queryId}/archive") .header("X-DUNE-API-KEY", "") .asString(); ``` diff --git a/api-reference/queries/endpoint/create.mdx b/api-reference/queries/endpoint/create.mdx index f6bf6c0a..69d66c7e 100644 --- a/api-reference/queries/endpoint/create.mdx +++ b/api-reference/queries/endpoint/create.mdx @@ -129,7 +129,7 @@ import ( "fmt" "strings" "net/http" - "io/ioutil" + "io" ) func main() { @@ -146,7 +146,7 @@ func main() { res, _ := http.DefaultClient.Do(req) defer res.Body.Close() - body, _ := ioutil.ReadAll(res.Body) + body, _ := io.ReadAll(res.Body) fmt.Println(res) fmt.Println(string(body)) diff --git a/api-reference/queries/endpoint/private.mdx b/api-reference/queries/endpoint/private.mdx index 36d53289..4225ffd2 100644 --- a/api-reference/queries/endpoint/private.mdx +++ b/api-reference/queries/endpoint/private.mdx @@ -1,6 +1,6 @@ --- title: 'Private Query' -openapi: 'POST /v1/query/{queryId}/private' +openapi: 'GET /v1/query/{queryId}/private' --- diff --git a/api-reference/queries/endpoint/query-object.mdx b/api-reference/queries/endpoint/query-object.mdx index 20774b4b..21e3e3dc 100644 --- a/api-reference/queries/endpoint/query-object.mdx +++ b/api-reference/queries/endpoint/query-object.mdx @@ -3,7 +3,7 @@ title: 'Overview' icon: "star" --- -These query management endspoints help you programmatically create and manage Dune SQL queries via the API, ideal for integration with GitHub or other CI/CD pipelines. +These query management endpoints help you programmatically create and manage Dune SQL queries via the API, ideal for integration with GitHub or other CI/CD pipelines. ### Queries @@ -15,7 +15,7 @@ Each query comes with fields you can edit such as: - `query_sql`: the raw sql text - `params`: parameters within the query, using the `{{ foo }}` syntax. See the section below for more details. - `is_private`: boolean for if query is private or not. Private queries cannot be found or queried by others. -- `archived`: boolean for if query is archived or not. Archived queries cannot run or edited by anyone. +- `archived`: boolean for if query is archived or not. Archived queries cannot be run or edited by anyone. ### Query Parameters @@ -35,7 +35,7 @@ For passing these parameters through the API request body, you can use the follo "baz": "2020-12-01T01:20:30Z" } ``` -Where "foo", "bar", and "baz" are three params in a query. If you leave one out, it goes with the default param valiue. +Where "foo", "bar", and "baz" are three params in a query. If you leave one out, it goes with the default param value. For Queries endpoints, you'll need to define the type and more: diff --git a/api-reference/queries/endpoint/unarchive.mdx b/api-reference/queries/endpoint/unarchive.mdx index 75fbef93..b580a070 100644 --- a/api-reference/queries/endpoint/unarchive.mdx +++ b/api-reference/queries/endpoint/unarchive.mdx @@ -14,7 +14,7 @@ In Dune context, delete action is replaced by archive as deletion of queries is ```bash cURL -curl --request GET \ +curl --request POST \ --url https://api.dune.com/api/v1/query/{queryId}/unarchive \ --header 'X-DUNE-API-KEY: ' ``` @@ -37,14 +37,14 @@ url = "https://api.dune.com/api/v1/query/{queryId}/unarchive" headers = {"X-DUNE-API-KEY": ""} -response = requests.request("GET", url, headers=headers) +response = requests.request("POST", url, headers=headers) print(response.text) ``` ```javascript JavaScript -const options = {method: 'GET', headers: {'X-DUNE-API-KEY': ''}}; +const options = {method: 'POST', headers: {'X-DUNE-API-KEY': ''}}; fetch('https://api.dune.com/api/v1/query/{queryId}/unarchive', options) .then(response => response.json()) @@ -65,7 +65,7 @@ func main() { url := "https://api.dune.com/api/v1/query/{queryId}/unarchive" - req, _ := http.NewRequest("GET", url, nil) + req, _ := http.NewRequest("POST", url, nil) req.Header.Add("X-DUNE-API-KEY", "") @@ -92,7 +92,7 @@ curl_setopt_array($curl, [ CURLOPT_MAXREDIRS => 10, CURLOPT_TIMEOUT => 30, CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1, - CURLOPT_CUSTOMREQUEST => "GET", + CURLOPT_CUSTOMREQUEST => "POST", CURLOPT_HTTPHEADER => [ "X-DUNE-API-KEY: " ], @@ -111,7 +111,7 @@ if ($err) { ``` ```java Java -HttpResponse response = Unirest.get("https://api.dune.com/api/v1/query/{queryId}/unarchive") +HttpResponse response = Unirest.post("https://api.dune.com/api/v1/query/{queryId}/unarchive") .header("X-DUNE-API-KEY", "") .asString(); ``` diff --git a/api-reference/queries/endpoint/unprivate.mdx b/api-reference/queries/endpoint/unprivate.mdx index 6e7ccdb0..11f6b74c 100644 --- a/api-reference/queries/endpoint/unprivate.mdx +++ b/api-reference/queries/endpoint/unprivate.mdx @@ -10,7 +10,7 @@ To access Query endpoints, an [Analyst plan](https://dune.com/pricing) or higher ```bash cURL -curl --request GET \ +curl --request POST \ --url https://api.dune.com/api/v1/query/{queryId}/unprivate \ --header 'X-DUNE-API-KEY: ' ``` @@ -33,14 +33,14 @@ url = "https://api.dune.com/api/v1/query/{queryId}/unprivate" headers = {"X-DUNE-API-KEY": ""} -response = requests.request("GET", url, headers=headers) +response = requests.request("POST", url, headers=headers) print(response.text) ``` ```javascript JavaScript -const options = {method: 'GET', headers: {'X-DUNE-API-KEY': ''}}; +const options = {method: 'POST', headers: {'X-DUNE-API-KEY': ''}}; fetch('https://api.dune.com/api/v1/query/{queryId}/unprivate', options) .then(response => response.json()) @@ -61,7 +61,7 @@ func main() { url := "https://api.dune.com/api/v1/query/{queryId}/unprivate" - req, _ := http.NewRequest("GET", url, nil) + req, _ := http.NewRequest("POST", url, nil) req.Header.Add("X-DUNE-API-KEY", "") @@ -88,7 +88,7 @@ curl_setopt_array($curl, [ CURLOPT_MAXREDIRS => 10, CURLOPT_TIMEOUT => 30, CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1, - CURLOPT_CUSTOMREQUEST => "GET", + CURLOPT_CUSTOMREQUEST => "POST", CURLOPT_HTTPHEADER => [ "X-DUNE-API-KEY: " ], @@ -107,7 +107,7 @@ if ($err) { ``` ```java Java -HttpResponse response = Unirest.get("https://api.dune.com/api/v1/query/{queryId}/unprivate") +HttpResponse response = Unirest.post("https://api.dune.com/api/v1/query/{queryId}/unprivate") .header("X-DUNE-API-KEY", "") .asString(); ``` diff --git a/api-reference/queries/endpoint/update.mdx b/api-reference/queries/endpoint/update.mdx index 99b11bf4..4e2c1f4c 100644 --- a/api-reference/queries/endpoint/update.mdx +++ b/api-reference/queries/endpoint/update.mdx @@ -35,14 +35,14 @@ query = dune.update_query( ) ``` -```python Python +```bash cURL curl --request PATCH \ --url https://api.dune.com/api/v1/query/{queryId} \ --header 'Content-Type: application/json' \ --header 'X-DUNE-API-KEY: ' \ --data '{ "query_id": 1252207, - "query_sql": "{{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}" + "query_sql": "SELECT * FROM {{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}" }' ``` @@ -50,7 +50,7 @@ curl --request PATCH \ const options = { method: 'PATCH', headers: {'X-DUNE-API-KEY': '', 'Content-Type': 'application/json'}, - body: '{"query_id":1252207,"query_sql":"{{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}"}' + body: '{"query_id":1252207,"query_sql":"SELECT * FROM {{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}"}' }; fetch('https://api.dune.com/api/v1/query/{queryId}', options) @@ -73,7 +73,7 @@ func main() { url := "https://api.dune.com/api/v1/query/{queryId}" - payload := strings.NewReader("{\n \"query_id\": 1252207,\n ,\n \"query_sql\": \"{{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}\"}") + payload := strings.NewReader("{\n \"query_id\": 1252207,\n \"query_sql\": \"SELECT * FROM {{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}\"}") req, _ := http.NewRequest("PATCH", url, payload) @@ -104,7 +104,7 @@ curl_setopt_array($curl, [ CURLOPT_TIMEOUT => 30, CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1, CURLOPT_CUSTOMREQUEST => "PATCH", - CURLOPT_POSTFIELDS => "{\n \"query_id\": 1252207,\n \"query_sql\": \"{{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}\"}", + CURLOPT_POSTFIELDS => "{\n \"query_id\": 1252207,\n \"query_sql\": \"SELECT * FROM {{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}\"}", CURLOPT_HTTPHEADER => [ "Content-Type: application/json", "X-DUNE-API-KEY: " @@ -127,7 +127,7 @@ if ($err) { HttpResponse response = Unirest.patch("https://api.dune.com/api/v1/query/{queryId}") .header("X-DUNE-API-KEY", "") .header("Content-Type", "application/json") - .body("{\n \"query_id\": 1252207,\n \"query_sql\": \"{{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}\"}") + .body("{\n \"query_id\": 1252207,\n \"query_sql\": \"SELECT * FROM {{blockchain}}.transactions WHERE to = {{address}} AND block_number > {{blocknumber}}\"}") .asString(); ``` diff --git a/api-reference/quickstart/queries-eg.mdx b/api-reference/quickstart/queries-eg.mdx index 9578e41c..d59c31f6 100644 --- a/api-reference/quickstart/queries-eg.mdx +++ b/api-reference/quickstart/queries-eg.mdx @@ -6,7 +6,7 @@ In this quickstart, we will walk through how to turn any dashboard (or set of qu ### Prerequisites - Python environment set up (check out [Anaconda Navigator](https://docs.continuum.io/free/navigator/) if you want somewhere to start.) -- Have a Dune API key from the team/user who's queries you want to manage (to obtain one [follow the steps here](../overview/authentication#generate-an-api-key)) +- Have a Dune API key from the team/user whose queries you want to manage (to obtain one [follow the steps here](../overview/authentication#generate-an-api-key)) ### Set up a new repo from the GitHub template diff --git a/api-reference/quickstart/results-eg.mdx b/api-reference/quickstart/results-eg.mdx index 1d113cd1..a005a65c 100644 --- a/api-reference/quickstart/results-eg.mdx +++ b/api-reference/quickstart/results-eg.mdx @@ -97,27 +97,27 @@ You can choose to either get the latest query result without triggering an execu ```python - query_result = dune.get_latest_result(3373921) # get latest result in json format - # query_result = dune.get_latest_result_dataframe(3373921) # get latest result in Pandas dataframe format - ``` + query_result = dune.get_latest_result(3373921) # get latest result in json format + # query_result = dune.get_latest_result_dataframe(3373921) # get latest result in Pandas dataframe format + ``` - - ```python - query = QueryBase( - query_id=3373921, - - # uncomment and change the parameter values if needed - # params=[ - # QueryParameter.text_type(name="contract", value="0x6B175474E89094C44Da98b954EedeAC495271d0F"), # default is DAI - # QueryParameter.text_type(name="owner", value="owner"), # default using vitalik.eth's wallet - # ], - ) + + ```python + query = QueryBase( + query_id=3373921, + + # uncomment and change the parameter values if needed + # params=[ + # QueryParameter.text_type(name="contract", value="0x6B175474E89094C44Da98b954EedeAC495271d0F"), # default is DAI + # QueryParameter.text_type(name="owner", value="owner"), # default using vitalik.eth's wallet + # ], + ) query_result = dune.run_query_dataframe( - query=query - # , ping_frequency = 10 # uncomment to change the seconds between checking execution status, default is 1 second - # , performance="large" # uncomment to run query on large engine, default is medium - # , batch_size = 5_000 # uncomment to change the maximum number of rows to retrieve per batch of results, default is 32_000 + query=query + # , ping_frequency = 10 # uncomment to change the seconds between checking execution status, default is 1 second + # , performance="large" # uncomment to run query on large engine, default is medium + # , batch_size = 5_000 # uncomment to change the maximum number of rows to retrieve per batch of results, default is 32_000 ) # Note: to get the result in csv format, call run_query_csv(); for json format, call run_query(). @@ -164,10 +164,10 @@ You can choose to either get the latest query result without triggering an execu ) query_result = dune.run_query_dataframe( - query=query - # , ping_frequency = 10 # uncomment to change the seconds between checking execution status, default is 1 second - # , performance="large" # uncomment to run query on large engine, default is medium - # , batch_size = 5_000 # uncomment to change the maximum number of rows to retrieve per batch of results, default is 32_000 + query=query + # , ping_frequency = 10 # uncomment to change the seconds between checking execution status, default is 1 second + # , performance="large" # uncomment to run query on large engine, default is medium + # , batch_size = 5_000 # uncomment to change the maximum number of rows to retrieve per batch of results, default is 32_000 ) # Note: to get the result in csv format, call run_query_csv(); for json format, call run_query(). diff --git a/api-reference/quickstart/tables-eg.mdx b/api-reference/quickstart/tables-eg.mdx index 80c73f0e..90d92735 100644 --- a/api-reference/quickstart/tables-eg.mdx +++ b/api-reference/quickstart/tables-eg.mdx @@ -16,7 +16,7 @@ DUNE_API_KEY= ### Upload the CSV -Follow below steps to upload your CSV. Please make sure to modify paths to your .env file and to your CSV file. +Follow the below steps to upload your CSV. Please make sure to modify paths to your .env file and to your CSV file. ```python import dotenv, os @@ -45,7 +45,7 @@ with open(csv_file_path) as open_file: Once the upload is successful, you will see the data show up under [Your Data](https://dune.com/queries?category=uploaded_data) in the Data Explorer. -You can query your uploaded table under the name `dune..dataset_`. For example, here I defined the table name to be "cereal_table" and my team name is "dune", so to access the uploaded table we will do `select * from dune.dune.dataset_cereal_table` +You can query your uploaded table under the name `dune..dataset_
`. For example, here I defined the table name to be "cereal_table" and my team name is "dune", so to access the uploaded table we will do `select * from dune.dune.dataset_cereal_table`. diff --git a/api-reference/tables/endpoint/clear.mdx b/api-reference/tables/endpoint/clear.mdx index f69fa440..1c342cd4 100644 --- a/api-reference/tables/endpoint/clear.mdx +++ b/api-reference/tables/endpoint/clear.mdx @@ -23,7 +23,7 @@ headers = { "X-DUNE-API-KEY": "" } -response = requests.request("POST", url, data=data, headers=headers) +response = requests.request("POST", url, headers=headers) ``` \ No newline at end of file diff --git a/api-reference/tables/endpoint/create.mdx b/api-reference/tables/endpoint/create.mdx index f703269d..811ebebf 100644 --- a/api-reference/tables/endpoint/create.mdx +++ b/api-reference/tables/endpoint/create.mdx @@ -13,7 +13,7 @@ The resulting table will be empty, and can be inserted into with the [/insert en ## Schema -You need to define the schema of your data by providing `schema` array of columns in the request. Each column has three parameters: +You need to define the schema of your data by providing a `schema` array of columns in the request. Each column has three parameters: **name**: the name of the field @@ -61,7 +61,7 @@ table = dune.create_table( ```typescript TS SDK import { DuneClient, ColumnType } from "@duneanalytics/client-sdk"; -client = new DuneClient(process.env.DUNE_API_KEY!); +const client = new DuneClient(process.env.DUNE_API_KEY!); const result = await client.table.create({ namespace: "my_user", table_name: "interest_rates", diff --git a/api-reference/tables/endpoint/insert.mdx b/api-reference/tables/endpoint/insert.mdx index 67ca83c6..50b9450e 100644 --- a/api-reference/tables/endpoint/insert.mdx +++ b/api-reference/tables/endpoint/insert.mdx @@ -7,7 +7,7 @@ To be able to insert into a table, it must have been created with the [/create e - The data in the files must conform to the schema, and must use the same column names as the schema. -- One successful `/insert` request consumes 1 credits. +- One successful `/insert` request consumes 1 credit. - The maximum request size is 1.2GB @@ -19,7 +19,7 @@ A status code of 200 means that the data in the request was successfully inserte If you get any other status code, you can safely retry your request after addressing the issue that the error message indicated. ## Concurrent requests -A limited number of concurrent insertion requests per table is supported. However, there will be a slight performance penalty as we serialize the writes behind the scenes to ensure data integrity. Larger number of concurrent requests per table may result in an increased number of failures. Therefore, we recommend managing your requests within a 5-10 threshold to maintain optimal performance. +A limited number of concurrent insertion requests per table is supported. However, there will be a slight performance penalty as we serialize the writes behind the scenes to ensure data integrity. A larger number of concurrent requests per table may result in an increased number of failures. Therefore, we recommend managing your requests within a 5-10 threshold to maintain optimal performance. ## Supported filetypes ### CSV files (`Content-Type: text/csv`) @@ -32,7 +32,7 @@ Each line must have keys that match the column names of the table. ## Data types DuneSQL supports a variety of types which are not natively supported in many data exchange formats. Here we provide guidance on how to work with such types. ### Varbinary values -When uploading varbinary data using JSON or CSV formats, you need to convert the binary data into a textual representation. Reason being, JSON or CSV don't natively support binary values. There are many ways to transform binary data to a textual representation. We support **hexadecimal** and **base64** encodings. +When uploading varbinary data using JSON or CSV formats, you need to convert the binary data into a textual representation. The reason being, JSON or CSV don't natively support binary values. There are many ways to transform binary data to a textual representation. We support **hexadecimal** and **base64** encodings. #### base64 Base64 is a binary-to-text encoding scheme that transforms binary data into a sequence of characters. All characters are taken from a set of 64 characters. @@ -40,7 +40,7 @@ Base64 is a binary-to-text encoding scheme that transforms binary data into a se Example: `{"varbinary_column":"SGVsbG8gd29ybGQK"}` #### hexadecimal -In the hexadecimal representation input data should contain an even number of characters in the range `[0-9a-fA-F]` always prefixed with `0x`. +In the hexadecimal representation, input data should contain an even number of characters in the range `[0-9a-fA-F]` always prefixed with `0x`. Example: `{"varbinary_column":"0x92b7d1031988c7af"}` @@ -74,7 +74,7 @@ with open("./interest_rates.csv", "rb") as data: import * as fs from "fs/promises"; import { DuneClient, ContentType } from "@duneanalytics/client-sdk"; -client = new DuneClient(process.env.DUNE_API_KEY!); +const client = new DuneClient(process.env.DUNE_API_KEY!); const data = await fs.readFile("./sample_table_insert.csv"); // Or JSON // const data: Buffer = await fs.readFile("./sample_table_insert.json"); diff --git a/api-reference/tables/endpoint/upload.mdx b/api-reference/tables/endpoint/upload.mdx index 6d629495..49ae0085 100644 --- a/api-reference/tables/endpoint/upload.mdx +++ b/api-reference/tables/endpoint/upload.mdx @@ -16,7 +16,7 @@ For working with uploads, keep in mind that: - File has to be < 200 MB - Column names in the table can't start with a special character or digits. - Private uploads require a Premium subscription. -- If you upload to an existing table name, it will delete the old data and overwite it with your new data. Appends are only supported for the `/create`, `/insert` endpoints. +- If you upload to an existing table name, it will delete the old data and overwrite it with your new data. Appends are only supported for the `/create`, `/insert` endpoints. - To delete an upload table, you must go to `user settings (dune.com) -> data -> delete`. If you have larger datasets you want to upload, please [contact us here](https://docs.google.com/forms/d/e/1FAIpQLSekx61WzIh-MII18zRj1G98aJeLM7U0VEBqaa6pVk_DQ7lq6Q/viewform) diff --git a/api-reference/webhooks/webhook.mdx b/api-reference/webhooks/webhook.mdx index cb2281d5..cd031dfa 100644 --- a/api-reference/webhooks/webhook.mdx +++ b/api-reference/webhooks/webhook.mdx @@ -5,7 +5,7 @@ icon: "webhook" iconType: "solid" --- -You can send Dune data to a webhook by going to any query your own, and pressing the "schedule" button to the left of "Run" in the editor. You'll the popup below, where you can paste in a webhook url and receive data on a scheduled interval. +You can send Dune data to a webhook by going to any query you own, and pressing the "schedule" button to the left of "Run" in the editor. You'll see the popup below, where you can paste in a webhook url and receive data on a scheduled interval. A good use case for this is sending data to a Slack webhook, which you can [learn to do here](https://api.slack.com/messaging/webhooks). @@ -54,7 +54,7 @@ Here is an example schema sent to the webhook from this [Jupiter swap fees query } ``` -You'll need to GET query the `data_uri` with your api key to get the results data. This is the same as passing the `execution_id` into [get execution result](/api-reference/executions/endpoint/get-execution-result). +You'll need to query the `data_uri` with your api key to get the results data. This is the same as passing the `execution_id` into [get execution result](/api-reference/executions/endpoint/get-execution-result). diff --git a/catalyst/overview.mdx b/catalyst/overview.mdx index 6c2d5c49..22572ecf 100644 --- a/catalyst/overview.mdx +++ b/catalyst/overview.mdx @@ -82,7 +82,7 @@ For EVM-based chains, Dune provides a fully-managed, white-glove service approac - Implementation: address of proxy contract (if proxy) **Example Chains** -To get a feel of how data on Dune looks for this integration route, check out examples like [Ethereum](/data-catalog/evm/ethereum/overview), [Base](/data-catalog/evm/base/overview), or [Polygon](/data-catalog/evm/polygon/overview). +To get a feel for how data on Dune looks for this integration route, check out examples like [Ethereum](/data-catalog/evm/ethereum/overview), [Base](/data-catalog/evm/base/overview), or [Polygon](/data-catalog/evm/polygon/overview). --- @@ -96,7 +96,7 @@ For non-EVM chains supporting RPC calls, Dune provides an integration method via - **Node Indexing**: The chain should have a node provider capable of making relevant RPC calls (e.g., `getBlock`, `getTransaction`, or chain-specific alternatives). **Example Chains** -To get a feel of how data on Dune looks for this integration route, check out [Solana](/data-catalog/solana/overview), [Bitcoin](/data-catalog/bitcoin/overview), or [Aptos](/data-catalog/aptos/overview). +To get a feel for how data on Dune looks for this integration route, check out [Solana](/data-catalog/solana/overview), [Bitcoin](/data-catalog/bitcoin/overview), or [Aptos](/data-catalog/aptos/overview). --- diff --git a/data-catalog/bitcoin/overview.mdx b/data-catalog/bitcoin/overview.mdx index 524e91de..64aef3b8 100644 --- a/data-catalog/bitcoin/overview.mdx +++ b/data-catalog/bitcoin/overview.mdx @@ -7,13 +7,13 @@ description: Bitcoin is the first and most well-known blockchain. -Bitcoin uses a UTXO transaction model, and has a heavy focus on signatures and scripts for "locking" and "unlocking" tokens. They are also most well known for being tied to a 21 million token supply, and halvenings. +Bitcoin uses a UTXO transaction model, and has a heavy focus on signatures and scripts for "locking" and "unlocking" tokens. It is also most well known for being tied to a 21 million token supply, and halvenings. ## Data Available diff --git a/data-catalog/bitcoin/transactions.mdx b/data-catalog/bitcoin/transactions.mdx index 9fc740d4..f90501aa 100644 --- a/data-catalog/bitcoin/transactions.mdx +++ b/data-catalog/bitcoin/transactions.mdx @@ -22,7 +22,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ### Struct definitions -Within several of these columns is a data type of STRUCT which allows for representing nested hierarchical data and has key-value pairs. It's similar to a dictionary in python and can be used to group fields together to make them more accessible. +Within several of these columns is a data type of STRUCT which allows for representing nested hierarchical data and has key-value pairs. It's similar to a dictionary in Python and can be used to group fields together to make them more accessible. Note that you can work with these columns with the syntax `input[1].witness_data[2]` or `input[3].script_pub_key.address` depending on lengths of arrays within each value. It is an `array(row(map))` type, and while it looks like just an array in the returned table - it is more than that! diff --git a/data-catalog/bring-your-own-data.mdx b/data-catalog/bring-your-own-data.mdx index 9d5cc477..5a640b3a 100644 --- a/data-catalog/bring-your-own-data.mdx +++ b/data-catalog/bring-your-own-data.mdx @@ -50,7 +50,7 @@ A few examples of data we already have in this category are: - [**Reservoir**](https://reservoir.api) provides enriched and cleaned NFT trading data - etc... - The Criteria for adding data in this category is that it should be relevant to the web3 ecosystem and should be of high quality. + The criteria for adding data in this category is that it should be relevant to the web3 ecosystem and should be of high quality. diff --git a/data-catalog/community/farcaster/casts.mdx b/data-catalog/community/farcaster/casts.mdx index f25e7563..34b63060 100644 --- a/data-catalog/community/farcaster/casts.mdx +++ b/data-catalog/community/farcaster/casts.mdx @@ -16,7 +16,7 @@ This table contains all casts on the Farcaster protocol | fid | bigint | User ID of user on Farcaster protocol | | hash | bytea | Hash of the cast | | parent\_hash | bytea | Hash of the cast that this cast is a reply to | -| parent\_fid | bigint | FID of author or parent_hash | +| parent\_fid | bigint | FID of author of parent_hash | | parent\_url | varchar | Posting channel for the cast; can be null | | text | text | Text of the cast | | embeds | jsonb | Attachments inside the cast e.g. images, links, etc. | diff --git a/data-catalog/community/farcaster/fids.mdx b/data-catalog/community/farcaster/fids.mdx index eef00d24..60b7d726 100644 --- a/data-catalog/community/farcaster/fids.mdx +++ b/data-catalog/community/farcaster/fids.mdx @@ -8,7 +8,7 @@ This table contains all User IDs for Farcaster users | **Column name** | **Type** | **Description** | | --------------------- | ------------------------------- | -------------------------------------------------------- | -| fid | bigint | User ID of user on Farcaster protocol | +| fid | bigint | User ID of user on the Farcaster protocol | | created\_at | timestamp without timezone | Timestamp of row creation | | updated\_at | timestamp without timezone | Timestamp of last update | -| custody\_address | bytea | Address that stores user profile on the protocol | +| custody\_address | bytea | Address that stores the user profile on the protocol | diff --git a/data-catalog/community/farcaster/fnames.mdx b/data-catalog/community/farcaster/fnames.mdx index 448166c3..8ae058f6 100644 --- a/data-catalog/community/farcaster/fnames.mdx +++ b/data-catalog/community/farcaster/fnames.mdx @@ -8,11 +8,11 @@ This table contains usernames associated with FIDs on the Farcaster protocol. | **Column name** | **Type** | **Description** | | --------------- | -------------------------- | ----------------------------------------------- | -| fname | varchar | Fname of the given user | +| fname | varchar | Farcaster name of the given user | | created_at | timestamp without timezone | Timestamp of creation within database | | updated_at | timestamp without timezone | Timestamp of update within database | | deleted_at | timestamp without timezone | Timestamp of deletion on Farcaster protocol | | timestamp | timestamp without timezone | Timestamp of creation on Farcaster protocol | | fid | bigint | User ID of user on Farcaster protocol | -| custody_address | varbinary | Address that stores the FC profile for the user | +| custody_address | varbinary | Address that stores the Farcaster profile for the user | | expires_at | timestamp without timezone | Timestamp when username expires for the user | diff --git a/data-catalog/community/farcaster/links.mdx b/data-catalog/community/farcaster/links.mdx index 0a42d1ae..6cb369d5 100644 --- a/data-catalog/community/farcaster/links.mdx +++ b/data-catalog/community/farcaster/links.mdx @@ -14,6 +14,6 @@ This table contains data about follower and following relationships on the Farca | deleted\_at | timestamp without timezone | Timestamp of deletion on Farcaster protocol | | timestamp | timestamp without timezone | Timestamp of creation on Farcaster protocol | | fid | bigint | User ID of user on Farcaster protocol | -| target\_fid | bigint | FID of the user who is link target | +| target\_fid | bigint | FID of the user who is the link target | | hash | bytea | Link hash on the protocol | | type | text | Link type, usually this is a “follow” | diff --git a/data-catalog/community/farcaster/overview.mdx b/data-catalog/community/farcaster/overview.mdx index 42624075..3b40d6ec 100644 --- a/data-catalog/community/farcaster/overview.mdx +++ b/data-catalog/community/farcaster/overview.mdx @@ -50,6 +50,6 @@ Neynar is the development platform for web3 social protocols. Neynar makes Farca Farcaster user's profile data and their connected addresses. - Warpcast power badge users lists by fid + Warpcast power badge user lists by fid diff --git a/data-catalog/community/farcaster/power_badge.mdx b/data-catalog/community/farcaster/power_badge.mdx index 891e52e1..47d8a450 100644 --- a/data-catalog/community/farcaster/power_badge.mdx +++ b/data-catalog/community/farcaster/power_badge.mdx @@ -4,9 +4,9 @@ title: Power Badge Fids ## **dune.neynar.dataset_farcaster_warpcast_power_users** -This table contains all power badge users on the Warpcast. Read more [about power badges](https://warpcast.notion.site/Power-Badge-d81fea2e953e4dafae7c85295ffaf3ae) and the [power badge API](https://docs.farcaster.xyz/reference/warpcast/api#get-all-power-badge-users). +This table contains all power badge users on Warpcast. Read more [about power badges](https://warpcast.notion.site/Power-Badge-d81fea2e953e4dafae7c85295ffaf3ae) and the [power badge API](https://docs.farcaster.xyz/reference/warpcast/api#get-all-power-badge-users). -This is a Warpcast specific concept, this is NOT stored on the farcaster protocol itself. The table only contains the current power badge fids, not historical. +This is a Warpcast specific concept, this is NOT stored on the Farcaster protocol itself. The table only contains the current power badge fids, not historical. | **Column name** | **Type** | **Description** | | ------------------------ | ------------------------------- | -------------------------------------------------------------- | diff --git a/data-catalog/community/farcaster/profile_with_addresses.mdx b/data-catalog/community/farcaster/profile_with_addresses.mdx index 261ba7c7..35277bc5 100644 --- a/data-catalog/community/farcaster/profile_with_addresses.mdx +++ b/data-catalog/community/farcaster/profile_with_addresses.mdx @@ -4,11 +4,11 @@ title: Profile with addresses ## **dune.neynar.dataset_farcaster_profile_with_addresses** -This table contains farcaster user's profile data and their connected addresses +This table contains Farcaster user's profile data and their connected addresses | Column name | type | description | | --- | --- | --- | -| fid | bigint | User ID of farcaster user | +| fid | bigint | User ID of Farcaster user | | fname | text | Username | | display_name | text | Display name of user | | avatar_url | text | Link to profile picture | diff --git a/data-catalog/community/farcaster/signers.mdx b/data-catalog/community/farcaster/signers.mdx index 880b64cb..789fb445 100644 --- a/data-catalog/community/farcaster/signers.mdx +++ b/data-catalog/community/farcaster/signers.mdx @@ -14,5 +14,5 @@ This table contains data about signers associated with users on the Farcaster pr | deleted\_at | timestamp without timezone | Timestamp of deletion on Farcaster protocol | | timestamp | timestamp without timezone | Timestamp of creation on Farcaster protocol | | fid | bigint | User ID of user on Farcaster protocol | -| hash | bytea | Hash of creating signer on the protocol | +| hash | bytea | Hash of created signer on the protocol | | signer | bytea | Signer created by user | diff --git a/data-catalog/community/farcaster/user_data.mdx b/data-catalog/community/farcaster/user_data.mdx index 68c8e51a..5c74223f 100644 --- a/data-catalog/community/farcaster/user_data.mdx +++ b/data-catalog/community/farcaster/user_data.mdx @@ -7,7 +7,7 @@ title: User Data This table contains data about the user information on the Farcaster protocol. It can be joined with `fname` or `fid` for additional details. | **Column name** | **Type** | **Description** | -|-----------------------|------------------------------------|-------------------------------------------------------- | +|-----------------------|------------------------------------|----------------------------------------------------------------------------------------------------------------------| | id | bigint | Row id | | created\_at | timestamp without timezone | Timestamp of creation within database | | updated\_at | timestamp without timezone | Timestamp of update within database | diff --git a/data-catalog/community/farcaster/verifications.mdx b/data-catalog/community/farcaster/verifications.mdx index c3af0723..d8d652cf 100644 --- a/data-catalog/community/farcaster/verifications.mdx +++ b/data-catalog/community/farcaster/verifications.mdx @@ -9,9 +9,9 @@ This table contains data about the Ethereum wallet addresses connected to Farcas | **Column name** | **Type** | **Description** | |-----------------------|------------------------------------|--------------------------------------------------------------------------| | id | bigint | Row id | -| created\_at | timestamp without timezone | Timestamp of creation within database | -| updated\_at | timestamp without timezone | Timestamp of update within database | -| deleted\_at | timestamp without timezone | Timestamp of deletion on Farcaster protocol | +| created_at | timestamp without timezone | Timestamp of creation within database | +| updated_at | timestamp without timezone | Timestamp of update within database | +| deleted_at | timestamp without timezone | Timestamp of deletion on Farcaster protocol | | timestamp | timestamp without timezone | Timestamp of creation on Farcaster protocol | | fid | bigint | User ID of user on Farcaster protocol | | hash | bytea | Hash of connecting address to profile on protocol | diff --git a/data-catalog/community/flashbots/mempool-dumpster.mdx b/data-catalog/community/flashbots/mempool-dumpster.mdx index ee2a9d50..7e3b7684 100644 --- a/data-catalog/community/flashbots/mempool-dumpster.mdx +++ b/data-catalog/community/flashbots/mempool-dumpster.mdx @@ -13,15 +13,15 @@ This table captures detailed transaction data from the Ethereum mempool. It incl | Column Name | Description | Data Type | | ----------------------------- | ------------------------------------------------------------------------------------------------------ | --------- | | `to` | The recipient address of the transaction. | varchar | -| `from` | The sender address of the transaction. | Varchar | -| `hash` | The unique transaction hash. | Varchar | +| `from` | The sender address of the transaction. | varchar | +| `hash` | The unique transaction hash. | varchar | | `nonce` | The nonce of the transaction, a counter of the sender's transactions. | Integer | | `value` | The value transferred in the transaction, in wei. | BigInt | | `gas` | The gas limit set for the transaction. | Integer | | `gas_price` | The gas price set for the transaction, in wei. | BigInt | | `data_size` | The size of the data payload in the transaction, in bytes. | Integer | -| `data_4bytes` | The first four bytes of the transaction data, typically the method identifier in a contract call. | Varchar | -| `sources` | The sources that captured the transaction data. | Varchar | +| `data_4bytes` | The first four bytes of the transaction data, typically the method identifier in a contract call. | varchar | +| `sources` | The sources that captured the transaction data. | varchar | | `chain_id` | The identifier for the blockchain network (e.g., 1 for Ethereum Mainnet). | Integer | | `gas_fee_cap` | The maximum amount of gas fee the sender is willing to pay (EIP-1559). | BigInt | | `gas_tip_cap` | The maximum tip the sender is willing to pay miners (EIP-1559). | BigInt | diff --git a/data-catalog/community/ghostlogs/overview.mdx b/data-catalog/community/ghostlogs/overview.mdx index ab4109bc..f8aae8b8 100644 --- a/data-catalog/community/ghostlogs/overview.mdx +++ b/data-catalog/community/ghostlogs/overview.mdx @@ -8,8 +8,7 @@ description: Define and emit custom gasless events, replay historical transactio # GhostLogs [GhostLogs](https://ghostlogs.xyz) - add and emit gasless events from Smart Contracts. -GhostLogs is a tool that allows you to define and emit custom gasless events from Smart Contracts. Using these additonal events, you can replay historical transactions and automatically upload the data to Dune. This way, you can modify any deployed contract to emit gasless events and then export those logs to Dune tables. After that you'll be able to query and join with other native -tables to create dashboards. +GhostLogs is a tool that allows you to define and emit custom gasless events from Smart Contracts. Using these additional events, you can replay historical transactions and automatically upload the data to Dune. This way, you can modify any deployed contract to emit gasless events and then export those logs to Dune tables. After that you'll be able to query and join with other native tables to create dashboards. ## What are gasless events? @@ -29,7 +28,7 @@ Since anyone can replay transactions on a local fork and emit whatever events th To use GhostLogs data on Dune, you need to create an account on GhostLogs and follow the steps to export the data to Dune. You can find the detailed steps in the [documentation](https://docs.ghostlogs.xyz/ghostlogs/integrations/dune). -The data will be uploaded to Dune on your behalf by ghostlogs and you can query it like any other table. +The data will be uploaded to Dune on your behalf by GhostLogs and you can query it like any other table. e.g. ```sql diff --git a/data-catalog/community/lens/namespace-handle-link.mdx b/data-catalog/community/lens/namespace-handle-link.mdx index f3dd4bae..7e8c60f8 100644 --- a/data-catalog/community/lens/namespace-handle-link.mdx +++ b/data-catalog/community/lens/namespace-handle-link.mdx @@ -1,7 +1,7 @@ --- -title: dune.lens.handle_link +title: dune.lens.namespace_handle_link sidebarTitle: "Handle Links" -description: Description of the dune.lens.handle_link table on Dune +description: Description of the dune.lens.namespace_handle_link table on Dune --- ## Table description @@ -12,4 +12,4 @@ You link your handle to your profile and this holds the reference of the link. import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/community/lens/namespace-handle.mdx b/data-catalog/community/lens/namespace-handle.mdx index 7030de73..2ba66456 100644 --- a/data-catalog/community/lens/namespace-handle.mdx +++ b/data-catalog/community/lens/namespace-handle.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.namespace_handle table on Dune ## Table description -This holds the handle information note handles and profiles are 2 different NFTs. A handle has its own ID. +This holds the handle information. Note that handles and profiles are 2 different NFTs. A handle has its own ID. ## Table Sample diff --git a/data-catalog/community/lens/overview.mdx b/data-catalog/community/lens/overview.mdx index 05c248e9..4911c851 100644 --- a/data-catalog/community/lens/overview.mdx +++ b/data-catalog/community/lens/overview.mdx @@ -2,7 +2,7 @@ title: Lens data sidebarTitle: "Lens Overview" icon: "star" -description: Lens.xyz data on dune +description: Lens.xyz data on Dune --- # Lens Protocol diff --git a/data-catalog/community/lens/profile-follow-module-record.mdx b/data-catalog/community/lens/profile-follow-module-record.mdx index 7f2ec3d1..b5825fc1 100644 --- a/data-catalog/community/lens/profile-follow-module-record.mdx +++ b/data-catalog/community/lens/profile-follow-module-record.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.profile_follow_module_record table on ## Table description -This holds any follow module which has been redeemed by another profile aka 0x01 pays to follow 0x02. +This holds any follow module which has been redeemed by another profile i.e. 0x01 pays to follow 0x02. ## Table Sample diff --git a/data-catalog/community/lens/profile-follower.mdx b/data-catalog/community/lens/profile-follower.mdx index d1f47b59..a6cf49f7 100644 --- a/data-catalog/community/lens/profile-follower.mdx +++ b/data-catalog/community/lens/profile-follower.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.profile_follower table on Dune ## Table description -This holds who follows who. +This table holds information about who follows whom. ## Table Sample diff --git a/data-catalog/community/lens/profile-metadata.mdx b/data-catalog/community/lens/profile-metadata.mdx index ead3f674..21c81c8c 100644 --- a/data-catalog/community/lens/profile-metadata.mdx +++ b/data-catalog/community/lens/profile-metadata.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.profile_metadata table on Dune ## Table description -This holds the profile metadata again If it does not pass metadata standards, it goes into the metadata_failed table. This holds stuff like name, bio etc. +This holds the profile metadata. If it does not pass metadata standards, it goes into the metadata_failed table. This holds stuff like name, bio, etc. ## Table Sample diff --git a/data-catalog/community/lens/publication-metadata.mdx b/data-catalog/community/lens/publication-metadata.mdx index 4ce11511..51b4906d 100644 --- a/data-catalog/community/lens/publication-metadata.mdx +++ b/data-catalog/community/lens/publication-metadata.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.publication_metadata table on Dune ## Table description -This holds the publication content/metadata in. +This holds the publication content/metadata. ## Table Sample diff --git a/data-catalog/community/lens/publication-open-action-module-acted-multirecipient.mdx b/data-catalog/community/lens/publication-open-action-module-acted-multirecipient.mdx index 1fb5b68e..045c23f4 100644 --- a/data-catalog/community/lens/publication-open-action-module-acted-multirecipient.mdx +++ b/data-catalog/community/lens/publication-open-action-module-acted-multirecipient.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.publication_open_action_module_multire ## Table description -This holds a line for each recipient who gets paid out by the multi-collect module. +This holds a line for each recipient who gets paid out by the multi-recipient module. ## Table Sample diff --git a/data-catalog/community/lens/publication-open-action-module-acted-recorded.mdx b/data-catalog/community/lens/publication-open-action-module-acted-recorded.mdx index abb15392..df21fcfd 100644 --- a/data-catalog/community/lens/publication-open-action-module-acted-recorded.mdx +++ b/data-catalog/community/lens/publication-open-action-module-acted-recorded.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.publication_open_action_module_acted_r ## Table description -This holds which profiles have acted on that publication (collects are a part of an act). +This holds which profiles have acted on that publication (collects are a part of an action). ## Table Sample diff --git a/data-catalog/community/lens/publication-reaction.mdx b/data-catalog/community/lens/publication-reaction.mdx index ba6a0a4f..b77c1d78 100644 --- a/data-catalog/community/lens/publication-reaction.mdx +++ b/data-catalog/community/lens/publication-reaction.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.publication_reaction table on Dune ## Table description -This holds the reaction type and who did. +This holds the reaction type and who reacted. ## Table Sample diff --git a/data-catalog/community/lens/publication-record.mdx b/data-catalog/community/lens/publication-record.mdx index 360b7bf7..4d5dec6c 100644 --- a/data-catalog/community/lens/publication-record.mdx +++ b/data-catalog/community/lens/publication-record.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.publication_record table on Dune ## Table description -This holds all the SUCCESSFUL publication records, including Momoka publications; it also has a MIRROR|QUOTE|COMMENT|POST publication type, but the rest of the cols should explain itself. The definition of success to us is if it follows the metadata standard. +This holds all the SUCCESSFUL publication records, including Momoka publications; it also has a MIRROR|QUOTE|COMMENT|POST publication type, but the rest of the columns should explain itself. The definition of success to us is if it follows the metadata standard. ## Table Sample diff --git a/data-catalog/community/lens/publication-reference-module.mdx b/data-catalog/community/lens/publication-reference-module.mdx index 86c25a6e..ba4c3aa5 100644 --- a/data-catalog/community/lens/publication-reference-module.mdx +++ b/data-catalog/community/lens/publication-reference-module.mdx @@ -6,7 +6,7 @@ description: Description of the dune.lens.publication_reference_module table on ## Table description -This holds any reference modules which have been attached to a publication. +This holds any reference modules that have been attached to a publication. ## Table Sample diff --git a/data-catalog/community/reservoir/asks.mdx b/data-catalog/community/reservoir/asks.mdx index bb8e8a0c..bee23988 100644 --- a/data-catalog/community/reservoir/asks.mdx +++ b/data-catalog/community/reservoir/asks.mdx @@ -36,7 +36,7 @@ Query examples can be found here: | nonce | string | The order nonce of the maker | | source | string | Source of the listing (e.g. opensea.io) | | fee\_bps | bigint | Listing fee | -| expiration | bigint | Associated transaction hash | +| expiration | bigint | Listing expiration time | | raw\_data | string | Raw order data (format will vary per source) | | created\_at | timestamp | Timestamp the listing was created | | updated\_at | timestamp | Timestamp the listing was updated | diff --git a/data-catalog/community/reservoir/attribute-keys.mdx b/data-catalog/community/reservoir/attribute-keys.mdx index ba731f7f..d8f3f5ce 100644 --- a/data-catalog/community/reservoir/attribute-keys.mdx +++ b/data-catalog/community/reservoir/attribute-keys.mdx @@ -16,6 +16,6 @@ Query examples can be found here: | collection\_id | string | Associated collection id | | key | string | The name of the attribute | | kind | string | Value type (string, number, date, range) | -| rank | string | Sort order | +| rank | number | Sort order | | created\_at | timestamp | Timestamp the attribute key was created | | updated\_at | timestamp | Timestamp the attribute key was updated | diff --git a/data-catalog/community/reservoir/attributes.mdx b/data-catalog/community/reservoir/attributes.mdx index b5550613..27e7342a 100644 --- a/data-catalog/community/reservoir/attributes.mdx +++ b/data-catalog/community/reservoir/attributes.mdx @@ -20,7 +20,7 @@ Query examples can be found here: | token\_count | bigint | Amount of tokens that have the attribute | | on\_sale\_count | bigint | Amount of tokens that have the attribute which are on sale | | floor\_sell\_value | decimal | Current floor ask price | -| sell\_updated\_at | timestamp | Timestamp the floor sale was last updated | +| sell\_updated\_at | timestamp | Timestamp the floor ask was last updated | | collection\_id | string | Associated collection id | | kind | string | Value type (string, number, date, range) | | key | string | Associated key name | diff --git a/data-catalog/community/reservoir/bid-events.mdx b/data-catalog/community/reservoir/bid-events.mdx index 6dbef2e9..7db3cff5 100644 --- a/data-catalog/community/reservoir/bid-events.mdx +++ b/data-catalog/community/reservoir/bid-events.mdx @@ -21,7 +21,7 @@ This table contains records with information about each bid change. | quantity\_remaining | bigint | Associated bid tokens remaining | | valid\_from | bigint | Associated bid validity start | | valid\_until | bigint | Associated bid validity expiration | -| source | string | Source of the order (e.g. opensea.io) | +| source | string | Source of the order (e.g. opensea.io) | | tx\_hash | string | Associated transaction hash | | tx\_timestamp | bigint | Associated transaction timestamp | | created\_at | timestamp | Timestamp the event was recorded | diff --git a/data-catalog/community/reservoir/bids.mdx b/data-catalog/community/reservoir/bids.mdx index 7d0cdaaf..1fa422b7 100644 --- a/data-catalog/community/reservoir/bids.mdx +++ b/data-catalog/community/reservoir/bids.mdx @@ -21,7 +21,7 @@ This table contains records with information about each bid. | currency\_address | string | Currency address | | currency\_symbol | string | Currency symbol | | currency\_price | string | Currency price | -| quantity | bigint | Amount of tokens that is listed | +| quantity | bigint | Amount of tokens that are listed | | quantity\_filled | bigint | Amount of tokens that was filled | | quantity\_remaining | bigint | Amount of tokens remaining | | valid\_from | bigint | Listing start time | @@ -29,7 +29,7 @@ This table contains records with information about each bid. | nonce | bigint | The order nonce of the maker | | source | string | Source of the listing (e.g. opensea.io) | | fee\_bps | bigint | Listing fee | -| expiration | bigint | Associated transaction hash | +| expiration | bigint | Expiration timestamp | | raw\_data | string | Raw order data (format will vary per source) | | created\_at | timestamp | Timestamp the listing was created | | updated\_at | timestamp | Timestamp the listing was updated | diff --git a/data-catalog/community/reservoir/collection-floor-ask-events.mdx b/data-catalog/community/reservoir/collection-floor-ask-events.mdx index 77156379..ef58486d 100644 --- a/data-catalog/community/reservoir/collection-floor-ask-events.mdx +++ b/data-catalog/community/reservoir/collection-floor-ask-events.mdx @@ -22,7 +22,7 @@ Query examples can be found here: | order\_id | string | Associated ask id | | maker | string | Associated ask maker wallet address | | price | decimal | Associated ask price (native currency) | -| previous\_price | decimal | previous floor ask price (native currency) | +| previous\_price | decimal | Previous floor ask price (native currency) | | valid\_until | bigint | Associated ask validity expiration | | source | string | Source of the order (e.g. opensea.io) | | tx\_hash | string | Associated transaction hash | diff --git a/data-catalog/community/reservoir/collection-top-bid-events.mdx b/data-catalog/community/reservoir/collection-top-bid-events.mdx index 91babdf2..58623d73 100644 --- a/data-catalog/community/reservoir/collection-top-bid-events.mdx +++ b/data-catalog/community/reservoir/collection-top-bid-events.mdx @@ -16,7 +16,7 @@ This table contains records with information about each collection top bid chang | order\_id | string | Associated bid id | | maker | string | Associated bid maker wallet address | | price | string | Associated bid price (native currency) | -| previous\_price | decimal | previous top bid price (native currency) | +| previous\_price | decimal | Previous top bid price (native currency) | | valid\_until | bigint | Associated bid validity expiration | | source | string | Source of the order (e.g. opensea.io) | | tx\_hash | string | Associated transaction hash | diff --git a/data-catalog/community/reservoir/collections.mdx b/data-catalog/community/reservoir/collections.mdx index d0410cc0..404f6531 100644 --- a/data-catalog/community/reservoir/collections.mdx +++ b/data-catalog/community/reservoir/collections.mdx @@ -18,7 +18,7 @@ Query examples can be found here: | slug | string | Collection slug | | name | string | Collection name | | description | string | Collection description | -| token\_count | bigint | Id of the token in the collection | +| token\_count | bigint | Number of tokens in the collection | | contract | string | Contract address | | day1\_rank | bigint | Ranking in the previous day | | day7\_rank | bigint | Ranking in the previous 7 days | @@ -31,7 +31,7 @@ Query examples can be found here: | day1\_volume\_change | double | Trade volume change in the previous day | | day7\_volume\_change | double | Trade volume change in the previous 7 days | | day30\_volume\_change | double | Trade volume change in the previous 30 days | -| floor\ask\_value | decimal | Current floor sale price (native currency) | +| floor\_ask\_value | decimal | Current floor ask price (native currency) | | day1\_floor\_sale\_value | decimal | Floor sale price in the previous day | | day7\_floor\_sale\_value | decimal | Floor sale price 7 days ago | | day30\_floor\_sale\_value | decimal | Floor sale price 30 days ago | @@ -39,4 +39,4 @@ Query examples can be found here: | day7\_floor\_sale\_change | double | Floor sale price change from 7 days ago | | day30\_floor\_sale\_change | double | Floor sale price change from 30 days ago | | created\_at | timestamp | Timestamp the collection was created | -| updated\_at | timestamp | Timestamp the collection was updated | | +| updated\_at | timestamp | Timestamp the collection was updated | diff --git a/data-catalog/community/reservoir/overview.mdx b/data-catalog/community/reservoir/overview.mdx index e9f9340f..d6c11b8a 100644 --- a/data-catalog/community/reservoir/overview.mdx +++ b/data-catalog/community/reservoir/overview.mdx @@ -2,7 +2,7 @@ title: Reservoir NFT trading data sidebarTitle: "Overview" icon: "star" -description: "Reservoir makes Open-source NFT trading infrastructure enabling the next generation of NFT products." +description: "Reservoir makes open-source NFT trading infrastructure enabling the next generation of NFT products." --- # Reservoir diff --git a/data-catalog/community/reservoir/sales.mdx b/data-catalog/community/reservoir/sales.mdx index 3f96a975..4fa331a1 100644 --- a/data-catalog/community/reservoir/sales.mdx +++ b/data-catalog/community/reservoir/sales.mdx @@ -30,7 +30,7 @@ Query examples can be found here: | currency\_price | decimal | Sale price | | amount | string | Amount of tokens sold | | fill\_source | string | Where the order was filled | -| aggregator\_source | string | aggregator source (e.g. reservoir) | +| aggregator\_source | string | Aggregator source (e.g. reservoir) | | wash\_trading\_score | int | Internal wash trading score (based on past sales) | | is\_primary | boolean | Is paid mint? | | tx\_hash | string | Associated transaction hash | @@ -38,4 +38,4 @@ Query examples can be found here: | tx\_batch\_index | int | Associated transaction batch index | | tx\_timestamp | bigint | Associated transaction timestamp | | created\_at | timestamp | Timestamp the sale was recorded | -| updated\_at | timestamp | Timestamp the sale was updated | | +| updated\_at | timestamp | Timestamp the sale was updated | diff --git a/data-catalog/community/reservoir/token-attributes.mdx b/data-catalog/community/reservoir/token-attributes.mdx index 06a1ef1d..1d6af64c 100644 --- a/data-catalog/community/reservoir/token-attributes.mdx +++ b/data-catalog/community/reservoir/token-attributes.mdx @@ -20,4 +20,4 @@ Query examples can be found here: | key | string | Attribute name | | value | string | Attribute value | | created\_at | timestamp | Timestamp the token attribute was created | -| updated\_at | timestamp | Timestamp the token attribute was updated | | +| updated\_at | timestamp | Timestamp the token attribute was updated | diff --git a/data-catalog/community/reservoir/token-floor-ask-events.mdx b/data-catalog/community/reservoir/token-floor-ask-events.mdx index c4afb212..54a6e8ed 100644 --- a/data-catalog/community/reservoir/token-floor-ask-events.mdx +++ b/data-catalog/community/reservoir/token-floor-ask-events.mdx @@ -21,7 +21,7 @@ Query examples can be found here: | order\_id | string | Associated Ask id | | maker | string | Associated Ask maker wallet address | | price | decimal | Associated ask price (native currency) | -| previous\_price | decimal | Associated ask price (native currency) | +| previous\_price | decimal | Previous associated ask price (native currency) | | nonce | string | The order nonce of the maker | | valid\_from | bigint | Associated ask validity start | | valid\_until | bigint | Associated ask validity expiration | diff --git a/data-catalog/community/reservoir/tokens.mdx b/data-catalog/community/reservoir/tokens.mdx index 065f72fd..3d9782f9 100644 --- a/data-catalog/community/reservoir/tokens.mdx +++ b/data-catalog/community/reservoir/tokens.mdx @@ -24,10 +24,10 @@ Query examples can be found here: | floor\_ask\_id | string | Floor ask id | | floor\_ask\_value | bigint | Floor ask value | | floor\_ask\_maker | string | Floor ask maker wallet address | -| floor\_ask\_valid\_from | bigint | Floor ask Listing start time | -| floor\_ask\_valid\_to | bigint | Floor ask Listing end time | +| floor\_ask\_valid\_from | bigint | Floor ask listing start time | +| floor\_ask\_valid\_to | bigint | Floor ask listing end time | | floor\_ask\_source | string | Floor ask source (e.g. opensea.io) | -| last\_sale\_value | bigint | Associated transaction timestamp | -| last\_sale\_timestamp | bigint | Associated transaction timestamp | +| last\_sale\_value | bigint | Last sale value | +| last\_sale\_timestamp | bigint | Last sale timestamp | | created\_at | timestamp | Timestamp the token was created | | updated\_at | timestamp | Timestamp the token was updated | | diff --git a/data-catalog/curated/dex-trades/evm/dex-aggregator-trades.mdx b/data-catalog/curated/dex-trades/evm/dex-aggregator-trades.mdx index dd8c0f8a..b5f539cf 100644 --- a/data-catalog/curated/dex-trades/evm/dex-aggregator-trades.mdx +++ b/data-catalog/curated/dex-trades/evm/dex-aggregator-trades.mdx @@ -24,7 +24,7 @@ The `dex_aggregator.trades` table captures high-level trade data executed via de Users can expect the `dex_aggregator.trades` table to provide a high-level view of DEX trades facilitated by aggregators. This table simplifies trade records by showing a single entry for trades that may involve multiple DEXs and liquidity pools. For instance, a user might initiate a trade to swap USDC for PEPE via a DEX aggregator. The aggregator might route this trade through several liquidity pools such as WETH-USDC and WETH-PEPE, but `dex_aggregator.trades` will record it as a single USDC -> PEPE trade. -Complimentary to `dex_aggregator.trades` is the `dex.trades` table, where detailed trade executions are recorded. This table captures the granular steps of each trade, including interactions with different liquidity pools. The volume routed through aggregators is also recorded in the `dex.trades` table. One row in `dex_aggregator.trades` corresponds to one or more rows in `dex.trades`, providing a comprehensive view of the detailed execution path that aggregated trades take. +Complementary to `dex_aggregator.trades` is the `dex.trades` table, where detailed trade executions are recorded. This table captures the granular steps of each trade, including interactions with different liquidity pools. The volume routed through aggregators is also recorded in the `dex.trades` table. One row in `dex_aggregator.trades` corresponds to one or more rows in `dex.trades`, providing a comprehensive view of the detailed execution path that aggregated trades take. ## Coverage diff --git a/data-catalog/curated/dex-trades/evm/dex-sandwiched.mdx b/data-catalog/curated/dex-trades/evm/dex-sandwiched.mdx index af072d7b..6c48a1f4 100644 --- a/data-catalog/curated/dex-trades/evm/dex-sandwiched.mdx +++ b/data-catalog/curated/dex-trades/evm/dex-sandwiched.mdx @@ -1,5 +1,5 @@ --- -title: dex.sandwiched +title: dex.sandwiches sidebarTitle: "Sandwich Victims" icon: "crosshairs" description: "The `dex.sandwiched` table captures detailed data on the victim trades of sandwich attacks in decentralized exchanges (DEXs), recording transactions that have been sandwiched across various EVM networks." diff --git a/data-catalog/curated/dex-trades/evm/dex-sandwiches.mdx b/data-catalog/curated/dex-trades/evm/dex-sandwiches.mdx index 54ef960d..a10c095f 100644 --- a/data-catalog/curated/dex-trades/evm/dex-sandwiches.mdx +++ b/data-catalog/curated/dex-trades/evm/dex-sandwiches.mdx @@ -15,11 +15,13 @@ The `dex.sandwiches` table provides an in-depth view of the outer trades in sand However, this table also captures more complex sandwich attack patterns. For example: +``` bot1: ETH>USDC victim1: USDC>ETH bot1: USDC>ETH victim2: ETH>USDC bot1: ETH>USDC +``` In this scenario, the bot executes trades on both sides of the liquidity pool, sandwiching multiple victim trades in a single sequence. diff --git a/data-catalog/curated/dex-trades/evm/dex-trades.mdx b/data-catalog/curated/dex-trades/evm/dex-trades.mdx index 486ea7ed..9b954963 100644 --- a/data-catalog/curated/dex-trades/evm/dex-trades.mdx +++ b/data-catalog/curated/dex-trades/evm/dex-trades.mdx @@ -2,7 +2,7 @@ title: dex.trades sidebarTitle: "DEX Trades" icon: "handshake" -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols and blockchains." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols and blockchains." --- import { DuneEmbed } from '/snippets/dune-embed.mdx' @@ -17,13 +17,13 @@ import { DuneEmbed } from '/snippets/dune-embed.mdx' ## Table Description -The `dex.trades` table captures detailed data on trades executed via decentralized exchanges (DEXs). This table captures all raw trade events that happen across all liqudity pools. It provides a comprehensive view of the entire trade execution process, detailing the specific paths and liquidity sources utilized. +The `dex.trades` table captures detailed data on trades executed via decentralized exchanges (DEXs). This table captures all raw trade events that happen across all liquidity pools. It provides a comprehensive view of the entire trade execution process, detailing the specific paths and liquidity sources utilized. ## Functional Overview -The `dex.trades` table provides an in-depth view of trades on decentralized exchanges like uniswap or curve. This table includes entries for each segment of a trade that passes through different liquidity pools, as well as single-step trades. For example, a user may initiate a trade to swap USDC for PEPE. If this trade is executed through multiple liquidity pools, such as USDC-WETH and WETH-PEPE, the `dex.trades` table will record each segment of the trade as a separate entry. Conversely, a single-step trade, such as directly swapping USDC for ETH, will be recorded as a single entry. +The `dex.trades` table provides an in-depth view of trades on decentralized exchanges like Uniswap or Curve. This table includes entries for each segment of a trade that passes through different liquidity pools, as well as single-step trades. For example, a user may initiate a trade to swap USDC for PEPE. If this trade is executed through multiple liquidity pools, such as USDC-WETH and WETH-PEPE, the `dex.trades` table will record each segment of the trade as a separate entry. Conversely, a single-step trade, such as directly swapping USDC for ETH, will be recorded as a single entry. This detailed approach allows for granular analysis of trade execution paths, enabling users to: @@ -34,7 +34,7 @@ This detailed approach allows for granular analysis of trade execution paths, en By providing comprehensive trade details, the `dex.trades` table supports advanced analytics and research into DEX trading behavior and liquidity management. -Complimentary tables include `dex_aggregator.trades`, in which trade-intents that are routed through aggregators are recorded. The volume routed through aggregators is also recorded in the dex.trades table, one row in dex_aggregator trades corresponds to one or more rows in dex.trades. +Complementary tables include `dex_aggregator.trades`, in which trade-intents that are routed through aggregators are recorded. The volume routed through aggregators is also recorded in the dex.trades table, one row in dex_aggregator trades corresponds to one or more rows in dex.trades. ## Coverage diff --git a/data-catalog/curated/dex-trades/overview.mdx b/data-catalog/curated/dex-trades/overview.mdx index b7bbf678..23df1b3b 100644 --- a/data-catalog/curated/dex-trades/overview.mdx +++ b/data-catalog/curated/dex-trades/overview.mdx @@ -20,11 +20,11 @@ Our DEX data covers multiple blockchain ecosystems: - Individual trades across DEX protocols like Uniswap, Sushiswap, Curve and more + Individual trades across DEX protocols like Uniswap, SushiSwap, Curve and more - Trades routed through aggregators like 1inch, 0x Protocol, ParaSwap + Trades routed through aggregators like 1Inch, 0x Protocol, ParaSwap diff --git a/data-catalog/curated/dex-trades/solana/jupiter-aggregator-trades.mdx b/data-catalog/curated/dex-trades/solana/jupiter-aggregator-trades.mdx index 6656dcca..33a0c517 100644 --- a/data-catalog/curated/dex-trades/solana/jupiter-aggregator-trades.mdx +++ b/data-catalog/curated/dex-trades/solana/jupiter-aggregator-trades.mdx @@ -1,7 +1,7 @@ --- title: jupiter_solana.aggregator_swaps sidebarTitle: "Jupiter Aggregator Swaps" -icon : "layer-group" +icon: "layer-group" description: "The `jupiter_solana.aggregator_swaps` table captures data on trades executed through the Jupiter aggregator on Solana." --- diff --git a/data-catalog/curated/dex-trades/solana/overview.mdx b/data-catalog/curated/dex-trades/solana/overview.mdx index 320456f5..ecb0d901 100644 --- a/data-catalog/curated/dex-trades/solana/overview.mdx +++ b/data-catalog/curated/dex-trades/solana/overview.mdx @@ -48,7 +48,7 @@ SELECT project, COUNT(*) as num_trades, SUM(amount_usd) as volume_usd -FROM dex_solana.trades +FROM solana.dex_trades WHERE block_time >= NOW() - INTERVAL '30' day GROUP BY 1, 2 ORDER BY 1 DESC, 4 DESC diff --git a/data-catalog/curated/dex-trades/solana/solana-dex-trades.mdx b/data-catalog/curated/dex-trades/solana/solana-dex-trades.mdx index 35a44fde..e3d4f687 100644 --- a/data-catalog/curated/dex-trades/solana/solana-dex-trades.mdx +++ b/data-catalog/curated/dex-trades/solana/solana-dex-trades.mdx @@ -45,7 +45,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ## Examples -The following query demonstrates how to use the dex_solana.trades table to calculate the total volume of trades on a weekly basis for Solana DEXs. +The following query demonstrates how to use the `dex_solana.trades` table to calculate the total volume of trades on a weekly basis for Solana DEXs. ```sql SELECT diff --git a/data-catalog/curated/labels/address-labels.mdx b/data-catalog/curated/labels/address-labels.mdx index c31975b0..afccb065 100644 --- a/data-catalog/curated/labels/address-labels.mdx +++ b/data-catalog/curated/labels/address-labels.mdx @@ -27,7 +27,7 @@ Here are all the distinct category values available in the `labels.addresses` ta | `blockchain` | The blockchain network where the address is located (e.g., Ethereum, Binance Chain).| | `address` | The blockchain address being labeled. | | `name` | Descriptive name or label for the address. | -| `category` | The category that best describes the address' role (e.g., dex, wallet). | +| `category` | The category that best describes the address's role (e.g., dex, wallet). | | `contributor` | The Dune user who contributed the data. | | `source` | The source or methodology used to gather or verify the information. | | `created_at` | The date when the label record was first created. | diff --git a/data-catalog/curated/labels/owner-addresses.mdx b/data-catalog/curated/labels/owner-addresses.mdx index 5ac31ef7..d9d60ed7 100644 --- a/data-catalog/curated/labels/owner-addresses.mdx +++ b/data-catalog/curated/labels/owner-addresses.mdx @@ -27,7 +27,7 @@ The `labels.owner_addresses` table on Dune provides detailed data on blockchain | `eoa` | Indicates if the address is an Externally Owned Account (EOA) (this field is often not used). | | `factory_contract` | Indicates if the address belongs to a factory contract that deploys other contracts. | | `source` | Reference to the data source providing the information (this field is often not used). | -| `indentifying_transaction` | Transaction ID that can be used to identify the ownership (this field is often not used). | +| `identifying_transaction` | Transaction ID that can be used to identify the ownership (this field is often not used). | | `algorithm_name` | Algorithm associated with the address for cryptographic operations (this field is often not used).| | `source_website` | Website URL providing the data about the address (this field is often not used). | | `source_evidence` | Any evidence supporting the data provided (this field is often not used). | diff --git a/data-catalog/curated/labels/owner-details.mdx b/data-catalog/curated/labels/owner-details.mdx index 8c7a5c82..85294cf0 100644 --- a/data-catalog/curated/labels/owner-details.mdx +++ b/data-catalog/curated/labels/owner-details.mdx @@ -10,7 +10,7 @@ The `labels.owner_details` table on Dune provides essential information about va Data in this table is sourced from community contributions and official documentation, offering a comprehensive overview of the entities' activities, categories, and online presence. Analysts can leverage this data to track the latest developments, partnerships, and projects associated with specific entities. - You can find addresses assocaited with the account owners and custody owners in the `labels.owner_addresses` table. + You can find addresses associated with the account owners and custody owners in the `labels.owner_addresses` table. ## Column Descriptions diff --git a/data-catalog/curated/nft-trades/evm/nft-trades.mdx b/data-catalog/curated/nft-trades/evm/nft-trades.mdx index 2daf78ec..0d3d9782 100644 --- a/data-catalog/curated/nft-trades/evm/nft-trades.mdx +++ b/data-catalog/curated/nft-trades/evm/nft-trades.mdx @@ -17,7 +17,7 @@ The nft.trades table serves as an essential tool for delving into the NFT market ## Coverage -The `nft.trades` table is maintained by Dune and its community of contributors. We try to make sure that the data is as accurate and up-to-date as possible. However, Dune does not guarantee the accuracy or completeness of the data provided. The table covers the following decentralized exchanges and their versions: +The `nft.trades` table is maintained by Dune and its community of contributors. We try to make sure that the data is as accurate and up-to-date as possible. However, Dune does not guarantee the accuracy or completeness of the data provided. The table covers the following marketplaces and their versions:
diff --git a/data-catalog/curated/nft-trades/evm/nft-wash-trades.mdx b/data-catalog/curated/nft-trades/evm/nft-wash-trades.mdx index a463b205..471f321a 100644 --- a/data-catalog/curated/nft-trades/evm/nft-wash-trades.mdx +++ b/data-catalog/curated/nft-trades/evm/nft-wash-trades.mdx @@ -2,7 +2,7 @@ title: nft.wash_trades sidebarTitle: "NFT Wash Trades" icon: "washing-machine" -description: Dataset for identifying and analyzing potential wash trading activities in NFT transactions across various marketplaces and blockchains +description: Dataset for identifying and analyzing potential wash trading activities in NFT transactions across various marketplaces and blockchains --- import { DuneEmbed } from "/snippets/dune-embed.mdx"; diff --git a/data-catalog/curated/nft-trades/solana/solana-nft-transfers.mdx b/data-catalog/curated/nft-trades/solana/solana-nft-transfers.mdx index 808d8590..ee11b157 100644 --- a/data-catalog/curated/nft-trades/solana/solana-nft-transfers.mdx +++ b/data-catalog/curated/nft-trades/solana/solana-nft-transfers.mdx @@ -8,8 +8,8 @@ icon: "hexagon-vertical-nft" The `tokens_solana.nft` table contains NFT transfer events for tokens on the Solana blockchain indexed on Dune. This dataset encompasses transfer events for various Solana NFT standards. - Some Solana NFTs may have non-standard transfer mechanisms and might not be included in the transfers table. - You can check the logic for the transfers table [here](https://github.com/duneanalytics/spellbook/blob/main/dbt_subprojects/solana/models/tokens/solana/tokens_solana_nft.sql). + Some Solana NFTs may have non-standard transfer mechanisms and might not be included in the transfer table. + You can check the logic for the transfer table [here](https://github.com/duneanalytics/spellbook/blob/main/dbt_subprojects/solana/models/tokens/solana/tokens_solana_nft.sql). ### Utility diff --git a/data-catalog/curated/overview.mdx b/data-catalog/curated/overview.mdx index ba8aeace..56a87410 100644 --- a/data-catalog/curated/overview.mdx +++ b/data-catalog/curated/overview.mdx @@ -2,7 +2,7 @@ title: "Curated Data Overview" sidebarTitle: "Overview" icon: "star" -description: "Curated data Tables are the easiest way to gain insights on Dune" +description: "Curated data tables are the easiest way to gain insights on Dune" --- import { DuneEmbed } from '/snippets/dune-embed.mdx'; @@ -50,13 +50,13 @@ Here is a non-exhaustive list of some of the curated data tables available in Sp
-## Benefits of curated data Tables +## Benefits of Curated Data Tables Curated data tables provide several benefits: -- **Simplified Queries**: curated data tables make it easier to query and analyze blockchain data by providing a high-level view of the data. +- **Simplified Queries**: Curated data tables make it easier to query and analyze blockchain data by providing a high-level view of the data. - **Cross-Chain Analysis**: Consistent data models enable easy comparison between different blockchain networks. -- **Consistent Data Models**: The curated data tables follow a consistent data model, making it easier to combine data from different sources. +- **Consistent Data Models**: The curated data tables follow consistent data models, making it easier to combine data from different sources. - **Community Contributions**: The curated data tables are maintained by the Dune community, so anyone can contribute to them and improve the data quality. ## Resources diff --git a/data-catalog/curated/prices/overview.mdx b/data-catalog/curated/prices/overview.mdx index 8b64c255..8e530090 100644 --- a/data-catalog/curated/prices/overview.mdx +++ b/data-catalog/curated/prices/overview.mdx @@ -53,7 +53,7 @@ The price system works in multiple layers: - 900,000 unique tokens - 40+ blockchains -- new tokens are automatically added when they exceed a $10k volume threshold +- New tokens are automatically added when they exceed a $10k volume threshold import { DuneEmbed } from '/snippets/dune-embed.mdx' @@ -117,15 +117,14 @@ For details on how Dune processes DEX trade data to derive accurate token prices - Excludes trades with less than $10,000 USD in total volume - Takes the median price from each minute to reduce outlier impact - Calculates USD prices using our trusted token prices as reference - - Uses forward-filling to handle periods without valid trades, with time limits - - 30 days for daily prices - - 7 days for hourly prices - - 2 days for minute prices + - Uses forward-filling to handle periods without valid trades, with time limits: + - 30 days for daily prices + - 7 days for hourly prices + - 2 days for minute prices ## Usage Examples Here are some examples of how to use the prices tables. - ### Basic query to get the latest ETH price: ```sql SELECT price diff --git a/data-catalog/curated/prices/prices_day.mdx b/data-catalog/curated/prices/prices_day.mdx index 847fb87b..39306c5f 100644 --- a/data-catalog/curated/prices/prices_day.mdx +++ b/data-catalog/curated/prices/prices_day.mdx @@ -99,4 +99,4 @@ ORDER BY timestamp - Native tokens (like ETH, BNB) are assigned fixed addresses for consistency - For native tokens, use `dune.blockchains` table to get the standardized address for each blockchain - The same token may have different prices on different blockchains due to bridging inefficiencies -- Always use `contract_address` and `blockchain` for precise token identification, never use `symbol` for joins or filters \ No newline at end of file +- Always use `contract_address` and `blockchain` for precise token identification; never use `symbol` for joins or filters \ No newline at end of file diff --git a/data-catalog/curated/prices/prices_hour.mdx b/data-catalog/curated/prices/prices_hour.mdx index fe903ee6..b5c9ac55 100644 --- a/data-catalog/curated/prices/prices_hour.mdx +++ b/data-catalog/curated/prices/prices_hour.mdx @@ -17,7 +17,7 @@ The `prices.hour` table provides hourly token price data across all supported bl | blockchain | varchar | Blockchain identifier (e.g., 'ethereum', 'arbitrum') | | contract_address | varbinary | Token contract address (fixed address for native tokens) | | symbol | varchar | Token symbol (e.g., 'ETH', 'USDC') | -| timestamp | timestamp | Hour timestamp (00:00, 01:00, etc. UTC of each hour) | +| timestamp | timestamp | Hour timestamp (00:00, 01:00, etc. in UTC for each hour) | | price | double | Token price in USD | | decimals | int | Token decimals | | volume | double | Trading volume in USD (from price source) | @@ -31,7 +31,7 @@ The hourly prices are built through these steps: 1. Collect sparse price observations from different sources 2. Group by hour, taking the most recent price observation per hour 3. Fill missing hours with the previous hour's price (forward filling) -4. Set a 7-day (168 hour) expiration for forward filling to avoid stale data +4. Set a 7-day (168-hour) expiration for forward filling to avoid stale data ## Usage @@ -43,7 +43,7 @@ The `prices.hour` table is updated hourly based on the upstream data pipeline. A ## Usage Examples -Here are some examples of how to use the prices tables. +Here are some examples of how to use the hourly prices table. ### Get hourly ETH prices for the last day: ```sql diff --git a/data-catalog/curated/prices/prices_latest.mdx b/data-catalog/curated/prices/prices_latest.mdx index 7f6fdae3..1a5bc5e9 100644 --- a/data-catalog/curated/prices/prices_latest.mdx +++ b/data-catalog/curated/prices/prices_latest.mdx @@ -90,7 +90,7 @@ FROM dune.blockchains b JOIN prices.latest p ON p.blockchain = b.name AND p.contract_address = b.token_address -WHERE b.name IN ('ethereum', 'arbitrum', 'optimism', 'polygon','gnosis','solana') +WHERE b.name IN ('ethereum', 'arbitrum', 'optimism', 'polygon', 'gnosis', 'solana') ``` ## Data Quality Notes diff --git a/data-catalog/curated/prices/prices_usd.mdx b/data-catalog/curated/prices/prices_usd.mdx index bd20d3f9..7bcb8686 100644 --- a/data-catalog/curated/prices/prices_usd.mdx +++ b/data-catalog/curated/prices/prices_usd.mdx @@ -43,7 +43,7 @@ WHERE blockchain = 'ethereum' AND contract_address = 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 -- WETH AND timestamp >= DATE '2023-01-01' -ORDER BY timestamp asc +ORDER BY timestamp ASC ``` ## Legacy Table Structure diff --git a/data-catalog/curated/token-transfers/evm/balances.mdx b/data-catalog/curated/token-transfers/evm/balances.mdx index fc99bd15..d79cce1f 100644 --- a/data-catalog/curated/token-transfers/evm/balances.mdx +++ b/data-catalog/curated/token-transfers/evm/balances.mdx @@ -52,16 +52,16 @@ Balances are available for the following EVM-compatible networks: ### Balance Calculation Methodology -Our approach to storing balances is the following: We store token balances for each address. This process involves querying the blockchain for the balance of each address at the end of the day. The balance is then stored in the `tokens_.balances` table, which is updated . For the balance to be queried, the address must have appeared in any of the following tables: +Our approach to storing balances is the following: We store token balances for each address. This process involves querying the blockchain for the balance of each address at the end of the day. The balance is then stored in the `tokens_.balances` table, which is updated daily. For the balance to be queried, the address must have appeared in any of the following tables: - **For native currencies**: Transactions and traces ``to``/``from`` addresses, Ethereum-specific withdrawals, and block mining/validator activities. -- **For ERC20**: Analysis is based on token transfer events detailed in the [tokens_ethereum_base_transfers](https://github.com/duneanalytics/spellbook/blob/main/models/_sector/tokens/ethereum/tokens_ethereum_base_transfers.sql). The address balance is updated based on the `to`/`from` addresses in the transfer events. If the token is a non-standard ERC20 token, the balance might not be updated until we detect a standard ERC20 transfer event. Known issues currently include ERC4626 tokens and rebasing tokens like stETH or $ampleforth. We are working on improving the range of balance changes that we detect. +- **For ERC20**: Analysis is based on token transfer events detailed in the [tokens_ethereum_base_transfers](https://github.com/duneanalytics/spellbook/blob/main/models/_sector/tokens/ethereum/tokens_ethereum_base_transfers.sql). The address balance is updated based on the `to`/`from` addresses in the transfer events. If the token is a non-standard ERC20 token, the balance might not be updated until we detect a standard ERC20 transfer event. Known issues currently include ERC4626 tokens and rebasing tokens like stETH or Ampleforth. We are working on improving the range of balance changes that we detect. - **For ERC721 and ERC1155**: Inspection of NFT transfer activities via the [nft_ethereum_transfers](https://github.com/duneanalytics/spellbook/blob/main/models/_sector/nft/transfers/chains/nft_ethereum_transfers.sql), focusing on the `to`/`from` addresses. These dependencies on transfer and NFT event tables introduce a delay to balance updates, contingent on the latency inherent in the Spellbook's processing. This also means that if an address has not been involved in any of the above activities, its balance will not be updated. -This might be the case for non-standard erc20 contracts that do not emit the `Transfer` event, or for addresses that have not been involved in any transactions or NFT transfers. If there is a specific token that does not emit the `Transfer` event, but has a different event for token transfers, please let us know and we will see if we can include it in our balance calculations. +This might be the case for non-standard ERC20 contracts that do not emit the `Transfer` event, or for addresses that have not been involved in any transactions or NFT transfers. If there is a specific token that does not emit the `Transfer` event, but has a different event for token transfers, please let us know and we will see if we can include it in our balance calculations. ### Granular balances @@ -81,7 +81,7 @@ The `tokens_.balances` table adds a new row every time a balance changes #### Querying for the latest fungible Token Balances for a specific Address -This query will return the latest fungible token balances for the specified address. Fungible tokens refer to erc20 and native tokens. Please keep in mind that the balance table lags behind the real state by approximately 2 hours. +This query will return the latest fungible token balances for the specified address. Fungible tokens refer to ERC20 and native tokens. Please keep in mind that the balance table lags behind the real state by approximately 2 hours. ```sql select @@ -103,7 +103,7 @@ order by balance_usd desc #### Querying for daily fungible Token Balances for a specific Address -This query will return the daily fungible token balances for the specified address over time. Fungible tokens refer to erc20 and native tokens. +This query will return the daily fungible token balances for the specified address over time. Fungible tokens refer to ERC20 and native tokens. ```sql select diff --git a/data-catalog/curated/token-transfers/evm/token-transfers.mdx b/data-catalog/curated/token-transfers/evm/token-transfers.mdx index f9f8f292..58023dd6 100644 --- a/data-catalog/curated/token-transfers/evm/token-transfers.mdx +++ b/data-catalog/curated/token-transfers/evm/token-transfers.mdx @@ -17,7 +17,7 @@ The `tokens.transfers` table contains token transfer events across ERC20 tokens - Gas used transfers - Some erc20 tokens and native currencies have non-standard ways of being transferred and might not be included in the transfers table. + Some ERC20 tokens and native currencies have non-standard ways of being transferred and might not be included in the transfers table. You can check the logic for the transfers table [here](https://github.com/duneanalytics/spellbook/tree/main/dbt_subprojects/tokens/models/transfers_and_balances). The level of detail of the transfers table will vary by chain. @@ -81,7 +81,7 @@ LIMIT 100 This query calculates the daily transfer volume for a specific ERC20 token. -Please be aware that token volumes are not necessarily indicative of anything. These metric can be misleading if the token is not well-known or if there are a lot of small transfers. Token transfers can be mints, burns, transfers, flashloans and anything in between, trying to read into the data can lead to misleading results. +Please be aware that token volumes are not necessarily indicative of anything. These metrics can be misleading if the token is not well-known or if there are a lot of small transfers. Token transfers can be mints, burns, transfers, flash loans and anything in between, trying to read into the data can lead to misleading results. ```sql SELECT diff --git a/data-catalog/curated/token-transfers/evm/tokens-metadata.mdx b/data-catalog/curated/token-transfers/evm/tokens-metadata.mdx index 920c204d..99c0daac 100644 --- a/data-catalog/curated/token-transfers/evm/tokens-metadata.mdx +++ b/data-catalog/curated/token-transfers/evm/tokens-metadata.mdx @@ -25,7 +25,7 @@ New tokens meeting these criteria are added to the table within approximately 1 We use [Sim API](https://docs.sim.dune.com/evm/token-info) to retrieve token metadata for all qualifying contracts. For chains not supported on Sim API, we fall back to [DefinedFi](https://docs.defined.fi/reference/token) as our metadata provider. -Native tokens are also included in this dataset, using metadata info from `dune.blockchains`. +Native tokens are also included in this dataset, using metadata information from `dune.blockchains`. ### Utility diff --git a/data-catalog/curated/token-transfers/solana/overview.mdx b/data-catalog/curated/token-transfers/solana/overview.mdx index 7cf144d4..393b21a5 100644 --- a/data-catalog/curated/token-transfers/solana/overview.mdx +++ b/data-catalog/curated/token-transfers/solana/overview.mdx @@ -19,7 +19,7 @@ Blockchain networks have become popular platforms for creating, managing, and tr - Transfer events for Solana NFTs + Transfer events for Solana NFTs diff --git a/data-catalog/curated/token-transfers/solana/solana-token-transfers.mdx b/data-catalog/curated/token-transfers/solana/solana-token-transfers.mdx index 32c0cc47..3cb326bc 100644 --- a/data-catalog/curated/token-transfers/solana/solana-token-transfers.mdx +++ b/data-catalog/curated/token-transfers/solana/solana-token-transfers.mdx @@ -9,7 +9,7 @@ The `tokens_solana.transfers` table contains token transfer events for tokens on - SPL token transfers - token2022 token transfers -- native SOL transfers (excluding staking related transfers) +- native SOL transfers (excluding staking-related transfers) diff --git a/data-catalog/data-freshness.mdx b/data-catalog/data-freshness.mdx index 1762400f..a720f44b 100644 --- a/data-catalog/data-freshness.mdx +++ b/data-catalog/data-freshness.mdx @@ -34,7 +34,7 @@ You can find the data freshness of the decoded data in the table below. -# Curated Data +## Curated Data Curated data tables on Dune are tables like `dex.trades` or `nft.trades` that are derived from raw and decoded data. They take away the complexity of working with raw or even decoded data and are ready to be used for analysis. The data pipelines are defined and documented in this [GitHub repo](https://github.com/duneanalytics/spellbook). @@ -44,7 +44,7 @@ Curated tables are usually scheduled to run once every hour. The runtime of the -# Community Data +## Community Data Several notable 3rd party data providers are uploading their data into Dune. These data providers have their own update schedules and are not controlled by Dune. The data freshness of these providers can be found in the table below. diff --git a/data-catalog/dune-index/gas-fees.mdx b/data-catalog/dune-index/gas-fees.mdx index 966e4776..4c89f0ca 100644 --- a/data-catalog/dune-index/gas-fees.mdx +++ b/data-catalog/dune-index/gas-fees.mdx @@ -1,6 +1,6 @@ --- -title: Transactions Fees -sidebarTitle: "Transactions Fees" +title: Transaction Fees +sidebarTitle: "Transaction Fees" icon: "gas-pump" description: Understanding transaction fees and their relationship to transaction costs in blockchain networks --- @@ -231,8 +231,11 @@ For EVM networks, we have developed a unified model to calculate transaction fee provides a straightforward way to calculate transaction fees. Tron also subsidizes the fees for transactions, so the fee paid is not necessarily the actual cost of the transaction. We are correcting for this in the - `metrics.gas_fees_daily` table, but not in gas.fees yet. ```sql tx_fee_raw = - gas_used * gas_price ``` + `metrics.gas_fees_daily` table, but not in gas.fees yet. + + ```sql + tx_fee_raw = gas_used * gas_price + ``` @@ -281,7 +284,7 @@ For EVM networks, we have developed a unified model to calculate transaction fee ### Non-EVM Networks -For non-EVM networks we haven't yet found a consistent way to model the fee structure, so we are not yet able to provide a unified model for non-EVM networks. However all the data is included in the `metrics.gas_fees_daily` table. +For non-EVM networks we haven't yet found a consistent way to model the fee structure, so we are not yet able to provide a unified model for non-EVM networks. However, all the data is included in the `metrics.gas_fees_daily` table. #### Solana @@ -312,7 +315,7 @@ Solana has two "types" of transactions: _transactions_ and _votes_. We track the -We consider both `gas_solana.tx_fees` and `gas_solana.vote_fees` when calculating the total transaction fees for solana in `metrics.gas_fees_daily`. +We consider both `gas_solana.tx_fees` and `gas_solana.vote_fees` when calculating the total transaction fees for Solana in `metrics.gas_fees_daily`. #### Bitcoin diff --git a/data-catalog/dune-index/introduction.mdx b/data-catalog/dune-index/introduction.mdx index 335604b9..155ddb69 100644 --- a/data-catalog/dune-index/introduction.mdx +++ b/data-catalog/dune-index/introduction.mdx @@ -21,7 +21,7 @@ The Dune Index aggregates three fundamental metrics, each normalized to a baseli - Measures real demand for blockspace + Measures real demand for block space Tracks genuine value movement @@ -35,7 +35,7 @@ The Dune Index aggregates three fundamental metrics, each normalized to a baseli These metrics were carefully chosen to provide a comprehensive view of blockchain usage. Transaction fees demonstrate users' willingness to pay for block space, serving as a market-driven indicator of demand. Net transfers capture actual economic activity while filtering out artificial volume. Transaction count provides context about the breadth of network usage. -Together, these metrics create a robust framework that resists artificial inflation and captures different aspects of blockchain utility. +Together, these metrics create a robust framework that resists artificial inflation and captures different aspects of blockchain utility. diff --git a/data-catalog/evm/abstract/curated-data/dex/dex-trades.mdx b/data-catalog/evm/abstract/curated-data/dex/dex-trades.mdx index a1e98a3f..aeca0a9e 100644 --- a/data-catalog/evm/abstract/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/abstract/curated-data/dex/dex-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex.trades on abstract +title: dex.trades on Abstract sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on abstract." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Abstract." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; diff --git a/data-catalog/evm/abstract/curated-data/nft/nft-trades.mdx b/data-catalog/evm/abstract/curated-data/nft/nft-trades.mdx index e1171843..5ee79f46 100644 --- a/data-catalog/evm/abstract/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/abstract/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/abstract/decoded/contracts.mdx b/data-catalog/evm/abstract/decoded/contracts.mdx index c8d4d639..1b741cc8 100644 --- a/data-catalog/evm/abstract/decoded/contracts.mdx +++ b/data-catalog/evm/abstract/decoded/contracts.mdx @@ -1,7 +1,7 @@ --- -title: abstract.contracts +title: Abstract Contracts sidebarTitle: "Decoded Contracts" -description: Description of the abstract.contracts table on Dune +description: Description of the Abstract contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; diff --git a/data-catalog/evm/abstract/raw/transactions.mdx b/data-catalog/evm/abstract/raw/transactions.mdx index 2811048c..e8dd2142 100644 --- a/data-catalog/evm/abstract/raw/transactions.mdx +++ b/data-catalog/evm/abstract/raw/transactions.mdx @@ -8,5 +8,4 @@ import { TransactionsSnippet } from '/snippets/evm/raw/transactions-snippet.mdx' import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file diff --git a/data-catalog/evm/apechain/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/apechain/curated-data/dex/dex-aggregator-trades.mdx index f52eb8e1..aaec2932 100644 --- a/data-catalog/evm/apechain/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/apechain/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for apechain import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/apechain/curated-data/dex/dex-trades.mdx b/data-catalog/evm/apechain/curated-data/dex/dex-trades.mdx index 0f83bf39..f2af8010 100644 --- a/data-catalog/evm/apechain/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/apechain/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/apechain/curated-data/nft/nft-trades.mdx b/data-catalog/evm/apechain/curated-data/nft/nft-trades.mdx index db1a4813..357a06de 100644 --- a/data-catalog/evm/apechain/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/apechain/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/apechain/decoded/overview.mdx b/data-catalog/evm/apechain/decoded/overview.mdx index f9417b51..3d7502bf 100644 --- a/data-catalog/evm/apechain/decoded/overview.mdx +++ b/data-catalog/evm/apechain/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/apechain/raw/logs.mdx b/data-catalog/evm/apechain/raw/logs.mdx index 03957fb9..3260428e 100644 --- a/data-catalog/evm/apechain/raw/logs.mdx +++ b/data-catalog/evm/apechain/raw/logs.mdx @@ -5,8 +5,6 @@ description: Description of the apechain.logs table on Dune --- import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-aggregator-trades.mdx index 04163844..99797198 100644 --- a/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for Arbitrum Nova import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-trades.mdx b/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-trades.mdx index b44ec5e2..a1a95a63 100644 --- a/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/arbitrum-nova/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/arbitrum-nova/curated-data/nft/nft-trades.mdx b/data-catalog/evm/arbitrum-nova/curated-data/nft/nft-trades.mdx index e9ef2ebc..ba09fc67 100644 --- a/data-catalog/evm/arbitrum-nova/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/arbitrum-nova/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on nova +title: NFT.trades on Nova sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on nova." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Nova." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/arbitrum-nova/decoded/contracts.mdx b/data-catalog/evm/arbitrum-nova/decoded/contracts.mdx index 5b362bd0..7203e2b0 100644 --- a/data-catalog/evm/arbitrum-nova/decoded/contracts.mdx +++ b/data-catalog/evm/arbitrum-nova/decoded/contracts.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Decoded Contracts" description: Description of the nova.contracts table on Dune --- -import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; +import { ContractsSnippet } from "/snippets/evm/decoded/contracts-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/arbitrum-nova/decoded/overview.mdx b/data-catalog/evm/arbitrum-nova/decoded/overview.mdx index 455a6663..0cc0ec0d 100644 --- a/data-catalog/evm/arbitrum-nova/decoded/overview.mdx +++ b/data-catalog/evm/arbitrum-nova/decoded/overview.mdx @@ -1,6 +1,6 @@ --- -title: Arbitrum One Decoded Overview -description: Simplifying Arbitrum One smart contract analysis through human-readable tables. +title: Arbitrum Nova Decoded Overview +description: Simplifying Arbitrum Nova smart contract analysis through human-readable tables. icon: "star" --- diff --git a/data-catalog/evm/arbitrum-nova/decoded/traces-decoded.mdx b/data-catalog/evm/arbitrum-nova/decoded/traces-decoded.mdx index 2af0e035..07913883 100644 --- a/data-catalog/evm/arbitrum-nova/decoded/traces-decoded.mdx +++ b/data-catalog/evm/arbitrum-nova/decoded/traces-decoded.mdx @@ -1,6 +1,6 @@ --- title: nova.traces_decoded -sidebarTitle: "traces_decoded" +sidebarTitle: "Decoded Traces" description: Description of the nova.traces_decoded table on Dune --- diff --git a/data-catalog/evm/arbitrum-nova/overview.mdx b/data-catalog/evm/arbitrum-nova/overview.mdx index d04d3dc7..780eb208 100644 --- a/data-catalog/evm/arbitrum-nova/overview.mdx +++ b/data-catalog/evm/arbitrum-nova/overview.mdx @@ -1,5 +1,5 @@ --- -title: Arbitrum One Overview +title: Arbitrum Nova Overview icon: "star" sidebarTitle: "Overview" description: Arbitrum Nova data on Dune @@ -31,7 +31,7 @@ Ether (ETH) is the primary utility token on Arbitrum Nova, used for paying trans - + The official page for Arbitrum Nova (an AnyTrust chain), offering comprehensive details on the platform, its architecture, and resources for developers @@ -43,7 +43,7 @@ Ether (ETH) is the primary utility token on Arbitrum Nova, used for paying trans Insights into smart contract interactions through event logs - Information on blocks processed on Arbitrum One, reflecting network activity and capacity + Information on blocks processed on Arbitrum Nova, reflecting network activity and capacity Detailed data on transactions, showcasing efficiency and operational execution diff --git a/data-catalog/evm/arbitrum-nova/raw/blocks.mdx b/data-catalog/evm/arbitrum-nova/raw/blocks.mdx index 048759a0..cbbdf684 100644 --- a/data-catalog/evm/arbitrum-nova/raw/blocks.mdx +++ b/data-catalog/evm/arbitrum-nova/raw/blocks.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Blocks" description: Description of the nova.blocks table on Dune --- -import { BlockSnippet } from '/snippets/evm/raw/blocks-snippet.mdx'; +import { BlockSnippet } from "/snippets/evm/raw/blocks-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/arbitrum-nova/raw/logs.mdx b/data-catalog/evm/arbitrum-nova/raw/logs.mdx index 0601dd12..37384460 100644 --- a/data-catalog/evm/arbitrum-nova/raw/logs.mdx +++ b/data-catalog/evm/arbitrum-nova/raw/logs.mdx @@ -5,8 +5,8 @@ description: Description of the nova.logs table on Dune --- import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; +import { ColumnDescriptions } from '/snippets/column-descriptions.mdx'; +import { TableSample } from '/snippets/table-sample.mdx'; \ No newline at end of file diff --git a/data-catalog/evm/arbitrum/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/arbitrum/curated-data/dex/dex-aggregator-trades.mdx index 3e3b1048..bf46ff24 100644 --- a/data-catalog/evm/arbitrum/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/arbitrum/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for Arbitrum import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/arbitrum/curated-data/dex/dex-trades.mdx b/data-catalog/evm/arbitrum/curated-data/dex/dex-trades.mdx index 566d7224..7ca6ce4e 100644 --- a/data-catalog/evm/arbitrum/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/arbitrum/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/arbitrum/curated-data/nft/nft-trades.mdx b/data-catalog/evm/arbitrum/curated-data/nft/nft-trades.mdx index de9a2e85..4dd46dc2 100644 --- a/data-catalog/evm/arbitrum/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/arbitrum/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on arbitrum +title: NFT.trades on Arbitrum sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on arbitrum." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Arbitrum." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/arbitrum/decoded/contracts.mdx b/data-catalog/evm/arbitrum/decoded/contracts.mdx index f73d60e0..b89f20fa 100644 --- a/data-catalog/evm/arbitrum/decoded/contracts.mdx +++ b/data-catalog/evm/arbitrum/decoded/contracts.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Decoded Contracts" description: Description of the arbitrum.contracts table on Dune --- -import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; +import { ContractsSnippet } from "/snippets/evm/decoded/contracts-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/arbitrum/decoded/overview.mdx b/data-catalog/evm/arbitrum/decoded/overview.mdx index 551363b6..5635516c 100644 --- a/data-catalog/evm/arbitrum/decoded/overview.mdx +++ b/data-catalog/evm/arbitrum/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/arbitrum/overview.mdx b/data-catalog/evm/arbitrum/overview.mdx index 0b0cea50..4ba70554 100644 --- a/data-catalog/evm/arbitrum/overview.mdx +++ b/data-catalog/evm/arbitrum/overview.mdx @@ -31,7 +31,7 @@ Dune provides extensive datasets for Arbitrum One, covering various aspects such Detailed data on transactions, showcasing efficiency and operational execution - + Decoded transaction information for enhanced analysis and understanding of smart contract executions diff --git a/data-catalog/evm/avalanche/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/avalanche/curated-data/dex/dex-aggregator-trades.mdx index a9cad1ba..dec09754 100644 --- a/data-catalog/evm/avalanche/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/avalanche/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for avalanche import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/avalanche/curated-data/dex/dex-trades.mdx b/data-catalog/evm/avalanche/curated-data/dex/dex-trades.mdx index d41bbd03..a08ecab0 100644 --- a/data-catalog/evm/avalanche/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/avalanche/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/avalanche/curated-data/nft/nft-trades.mdx b/data-catalog/evm/avalanche/curated-data/nft/nft-trades.mdx index b9e9c2f9..929bc166 100644 --- a/data-catalog/evm/avalanche/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/avalanche/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on avalanche +title: NFT Trades on Avalanche sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on avalanche." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Avalanche." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/avalanche/decoded/overview.mdx b/data-catalog/evm/avalanche/decoded/overview.mdx index 5c517d1c..fb445c84 100644 --- a/data-catalog/evm/avalanche/decoded/overview.mdx +++ b/data-catalog/evm/avalanche/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/avalanche/overview.mdx b/data-catalog/evm/avalanche/overview.mdx index a26ff50b..74fd96df 100644 --- a/data-catalog/evm/avalanche/overview.mdx +++ b/data-catalog/evm/avalanche/overview.mdx @@ -9,12 +9,12 @@ Avalanche C-Chain is a Layer 1 blockchain that functions as part of the Avalanch The core innovation of Avalanche C-Chain is its consensus mechanism, which combines classical consensus and Nakamoto consensus techniques to deliver rapid transaction finality and robust security. This design allows the C-Chain to process transactions faster and at lower costs compared to traditional blockchain networks. -$Avax is used as the primary utility token on the Avalanche C-Chain for transaction fees. However, the unique aspects of Avalanche's architecture provide enhanced scalability, making it a popular choice for developers seeking efficient and cost-effective blockchain solutions. +AVAX is used as the primary utility token on the Avalanche C-Chain for transaction fees. However, the unique aspects of Avalanche's architecture provide enhanced scalability, making it a popular choice for developers seeking efficient and cost-effective blockchain solutions. Dune provides extensive datasets for Avalanche C-Chain, offering detailed insights into transactions, smart contract interactions, and overall network health. - + The official documentation for Avalanche C-Chain, with detailed guides on its technology, architecture, and developer resources @@ -31,7 +31,7 @@ Dune provides extensive datasets for Avalanche C-Chain, offering detailed insigh Transaction details that highlight the efficiency and speed of the Avalanche C-Chain - + Decoded transaction data for easier analysis and deeper understanding of contract executions diff --git a/data-catalog/evm/b3/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/b3/curated-data/dex/dex-aggregator-trades.mdx index 59b4c8fb..a6ffbf4c 100644 --- a/data-catalog/evm/b3/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/b3/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for b3 import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/b3/curated-data/dex/dex-trades.mdx b/data-catalog/evm/b3/curated-data/dex/dex-trades.mdx index 3edbaf2d..1c2f660c 100644 --- a/data-catalog/evm/b3/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/b3/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/b3/curated-data/nft/nft-trades.mdx b/data-catalog/evm/b3/curated-data/nft/nft-trades.mdx index 7a7038f1..2fa7e738 100644 --- a/data-catalog/evm/b3/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/b3/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/b3/decoded/overview.mdx b/data-catalog/evm/b3/decoded/overview.mdx index feef55cf..9da97fd5 100644 --- a/data-catalog/evm/b3/decoded/overview.mdx +++ b/data-catalog/evm/b3/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/b3/overview.mdx b/data-catalog/evm/b3/overview.mdx index 2fd4b451..f72aad90 100644 --- a/data-catalog/evm/b3/overview.mdx +++ b/data-catalog/evm/b3/overview.mdx @@ -29,15 +29,15 @@ As a secure, low-cost Layer 2 incubated by Coinbase, Base provides the ideal fou - Detailed event logs from smart contracts, providing insights into interactions within the b3 network. + Detailed event logs from smart contracts, providing insights into interactions within the B3 network. - Information on blocks, illustrating the operational capacity and activity levels on b3. + Information on blocks, illustrating the operational capacity and activity levels on B3. - Extensive transaction data, showcasing the efficiency and execution of operations on b3. + Extensive transaction data, showcasing the efficiency and execution of operations on B3. - + Enhanced transaction data decoded for better analysis and understanding of contract executions. diff --git a/data-catalog/evm/base/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/base/curated-data/dex/dex-aggregator-trades.mdx index 30612e13..a66bd127 100644 --- a/data-catalog/evm/base/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/base/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for base import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/base/curated-data/dex/dex-trades.mdx b/data-catalog/evm/base/curated-data/dex/dex-trades.mdx index 6adca5e3..4153601c 100644 --- a/data-catalog/evm/base/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/base/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/base/curated-data/nft/nft-trades.mdx b/data-catalog/evm/base/curated-data/nft/nft-trades.mdx index 7dec5220..64eaf0e7 100644 --- a/data-catalog/evm/base/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/base/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on base +title: NFT.trades on Base sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on base." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Base." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/base/decoded/contracts.mdx b/data-catalog/evm/base/decoded/contracts.mdx index 1c4bcc20..4142e5ae 100644 --- a/data-catalog/evm/base/decoded/contracts.mdx +++ b/data-catalog/evm/base/decoded/contracts.mdx @@ -5,8 +5,6 @@ description: Description of the base.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/base/decoded/traces-decoded.mdx b/data-catalog/evm/base/decoded/traces-decoded.mdx index 6c7167a7..bdd84ff3 100644 --- a/data-catalog/evm/base/decoded/traces-decoded.mdx +++ b/data-catalog/evm/base/decoded/traces-decoded.mdx @@ -1,7 +1,7 @@ --- title: base.traces_decoded sidebarTitle: "Decoded Traces" -description: Description of the base.traces_decoded table on Dune +description: A description of the base.traces_decoded table on Dune --- import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; diff --git a/data-catalog/evm/base/overview.mdx b/data-catalog/evm/base/overview.mdx index cb139e2d..4d31bb05 100644 --- a/data-catalog/evm/base/overview.mdx +++ b/data-catalog/evm/base/overview.mdx @@ -36,7 +36,7 @@ Base leverages Coinbase's robust infrastructure to offer decentralized apps enha Extensive transaction data, showcasing the efficiency and execution of operations on Base. - + Enhanced transaction data decoded for better analysis and understanding of contract executions. diff --git a/data-catalog/evm/beacon/blocks.mdx b/data-catalog/evm/beacon/blocks.mdx index 56784e54..83c925ec 100644 --- a/data-catalog/evm/beacon/blocks.mdx +++ b/data-catalog/evm/beacon/blocks.mdx @@ -5,7 +5,7 @@ description: Description of the beacon.blocks table on Dune --- ## Table Description -Stores information about blocks in the Ethereum 2.0 Beacon Chain, including the block proposer, block metadata, and the blob sidecar associated with the block. +Stores information about blocks in the Ethereum 2.0 Beacon Chain, including the block proposer, block metadata, and associated blob sidecars. ## Column Descriptions | **Column** | **Type** | **Description** | diff --git a/data-catalog/evm/beacon/deposits.mdx b/data-catalog/evm/beacon/deposits.mdx index 677725cf..09f255e9 100644 --- a/data-catalog/evm/beacon/deposits.mdx +++ b/data-catalog/evm/beacon/deposits.mdx @@ -18,7 +18,7 @@ Stores deposit data for validators joining the Beacon network. This table is par | **pubkey** | binary | BLS public key of the validator making the deposit. | | **signature** | binary | BLS signature verifying the deposit data. | | **withdrawal_credentials** | binary | Credentials specifying the withdrawal address or conditions. | -| **proof** | binary | Merkle proof demonstrating the inclusion of the deposit in the Ethereum 1.0 deposit contract. | +| **proof** | binary | Merkle proof demonstrating the inclusion of the deposit in the Ethereum 1.0 deposit contract. | ## Table Sample diff --git a/data-catalog/evm/beacon/epoch-summaries.mdx b/data-catalog/evm/beacon/epoch-summaries.mdx index 2c5aa0a6..ead99a93 100644 --- a/data-catalog/evm/beacon/epoch-summaries.mdx +++ b/data-catalog/evm/beacon/epoch-summaries.mdx @@ -32,8 +32,8 @@ This table is indexed from Lido. Stores summary data for each epoch on the Beaco | **exiting_validators** | bigint | Number of validators exiting during the epoch. | | **canonical_blocks** | bigint | Number of canonical blocks in the epoch. | | **withdrawals** | bigint | Number of withdrawals processed during the epoch. | -| **updated_at** | timestamp | Last time the record was updated | -| **ingested_at** | timestamp | Time when the record was ingested | +| **updated_at** | timestamp | Last time the record was updated. | +| **ingested_at** | timestamp | Time when the record was ingested. | ## Table Sample diff --git a/data-catalog/evm/beacon/operators.mdx b/data-catalog/evm/beacon/operators.mdx index af1aa92f..dada1267 100644 --- a/data-catalog/evm/beacon/operators.mdx +++ b/data-catalog/evm/beacon/operators.mdx @@ -14,8 +14,8 @@ This table is indexed from Lido. Stores information about staking operators on t | **operator_name** | varchar | Name of the staking operator. | | **module_id** | bigint | Identifier linking the operator to a specific staking module or service. | | **public_key** | varbinary | Operator's public key used for cryptographic operations. | -| **updated_at** | timestamp | Last time the record was updated | -| **ingested_at** | timestamp | Time when the record was ingested | +| **updated_at** | timestamp | Last time the record was updated. | +| **ingested_at** | timestamp | Time when the record was ingested. | diff --git a/data-catalog/evm/beacon/raw.mdx b/data-catalog/evm/beacon/raw.mdx index 39cd3ef5..0d9320ab 100644 --- a/data-catalog/evm/beacon/raw.mdx +++ b/data-catalog/evm/beacon/raw.mdx @@ -1,7 +1,7 @@ --- -title: beacon.raw +title: ethereum_beacon.raw sidebarTitle: "Raw" -description: Description of the beacon.raw table on Dune +description: Description of the ethereum_beacon.raw table on Dune --- ## Table Description diff --git a/data-catalog/evm/beacon/validator-day-summaries.mdx b/data-catalog/evm/beacon/validator-day-summaries.mdx index 483295ad..d47c95ee 100644 --- a/data-catalog/evm/beacon/validator-day-summaries.mdx +++ b/data-catalog/evm/beacon/validator-day-summaries.mdx @@ -31,7 +31,7 @@ This table is indexed from Lido. Stores daily summaries of validator activity on | **sync_committee_messages** | bigint | Number of sync committee messages signed by the validator during the period. | | **sync_committee_messages_included**| bigint | Number of the validator's sync committee messages that were included in the chain during the period. | | **withdrawals** | bigint | Number of withdrawals made by the validator during the period. | -| **updated_at** | timestamp | Last time the record was updated | +| **updated_at** | timestamp | Last time the record was updated. | | **ingested_at** | timestamp | Time when the record was ingested | diff --git a/data-catalog/evm/beacon/validators.mdx b/data-catalog/evm/beacon/validators.mdx index 8469a342..22433f76 100644 --- a/data-catalog/evm/beacon/validators.mdx +++ b/data-catalog/evm/beacon/validators.mdx @@ -5,7 +5,7 @@ description: Description of the beacon.validators table on Dune --- ## Table Description -Stores data about withdrawals initiated by validators on the Beacon network. This table is partitioned by block_date. +Stores data about validators on the Beacon network. This table is partitioned by block_date. ## Column Descriptions | **Column** | **Type** | **Description** | @@ -27,4 +27,4 @@ Stores data about withdrawals initiated by validators on the Beacon network. Thi import { TableSample } from "/snippets/table-sample.mdx"; - + diff --git a/data-catalog/evm/beacon/withdrawals.mdx b/data-catalog/evm/beacon/withdrawals.mdx index 7b766a7e..d9459b6d 100644 --- a/data-catalog/evm/beacon/withdrawals.mdx +++ b/data-catalog/evm/beacon/withdrawals.mdx @@ -14,7 +14,7 @@ Stores data about withdrawals initiated by validators on the Beacon network. Thi | **block_slot** | long | Slot number within the epoch when the block containing the withdrawal was proposed. | | **block_time** | timestamp | Timestamp when the block containing the withdrawal was included in the chain. | | **block_date** | date | Date corresponding to the block_time. | -| **address** | binary | Execution layer (Eth1) address receiving the withdrawn ETH. | +| **address** | binary | Execution layer (ETH1) address receiving the withdrawn ETH. | | **amount** | long | Amount of ETH withdrawn, specified in Gwei. | | **index** | long | Unique identifier for the withdrawal operation. | | **validator_index** | long | Index of the validator initiating the withdrawal. | diff --git a/data-catalog/evm/berachain/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/berachain/curated-data/dex/dex-aggregator-trades.mdx index a89e8532..8842397a 100644 --- a/data-catalog/evm/berachain/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/berachain/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for berachain import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/berachain/curated-data/dex/dex-trades.mdx b/data-catalog/evm/berachain/curated-data/dex/dex-trades.mdx index 8781a30a..bfda8dc1 100644 --- a/data-catalog/evm/berachain/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/berachain/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/berachain/curated-data/nft/nft-trades.mdx b/data-catalog/evm/berachain/curated-data/nft/nft-trades.mdx index 046b6012..9efebad3 100644 --- a/data-catalog/evm/berachain/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/berachain/curated-data/nft/nft-trades.mdx @@ -7,6 +7,6 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/berachain/decoded/logs-decoded.mdx b/data-catalog/evm/berachain/decoded/logs-decoded.mdx index 9b10aed0..d96df4a5 100644 --- a/data-catalog/evm/berachain/decoded/logs-decoded.mdx +++ b/data-catalog/evm/berachain/decoded/logs-decoded.mdx @@ -8,7 +8,7 @@ description: Description of the berachain.logs_decoded table on Dune The `logs_decoded` table contains decoded logs from Berachain transactions. The table matches `topic0` to the event signature and the corresponding event name. The table does not contain the full event data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Event Logs](/data-catalog/evm/berachain/decoded/event-logs). -This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. +This table is great for gaining a high-level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. ## Column Descriptions diff --git a/data-catalog/evm/berachain/decoded/traces-decoded.mdx b/data-catalog/evm/berachain/decoded/traces-decoded.mdx index 19198023..9d08684a 100644 --- a/data-catalog/evm/berachain/decoded/traces-decoded.mdx +++ b/data-catalog/evm/berachain/decoded/traces-decoded.mdx @@ -6,7 +6,7 @@ description: Description of the berachain.traces_decoded table on Dune ## Table Description -The `traces_decoded` table contains decoded traces from Berachain transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/berachain/decoded/traces-decoded). +The `traces_decoded` table contains decoded traces from Berachain transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/berachain/decoded/call-tables). This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. diff --git a/data-catalog/evm/berachain/overview.mdx b/data-catalog/evm/berachain/overview.mdx index 0bfb300a..7da640a3 100644 --- a/data-catalog/evm/berachain/overview.mdx +++ b/data-catalog/evm/berachain/overview.mdx @@ -13,7 +13,7 @@ Berachain's execution layer is identical to the Ethereum Virtual Machine (EVM) r **Proof-of-Liquidity (PoL):** Berachain introduces a novel consensus mechanism that radically changes L1 economics, prioritizing users and applications over validator rewards. Network incentives go towards enriching ecosystem liquidity, contributing to: - Efficient trading -- Price stability +- Price stability - Chain security - Network/user growth diff --git a/data-catalog/evm/berachain/raw/creation-traces.mdx b/data-catalog/evm/berachain/raw/creation-traces.mdx index 0c13d719..828d74df 100644 --- a/data-catalog/evm/berachain/raw/creation-traces.mdx +++ b/data-catalog/evm/berachain/raw/creation-traces.mdx @@ -20,4 +20,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/berachain/raw/logs.mdx b/data-catalog/evm/berachain/raw/logs.mdx index 0218d67b..4ac0bcc4 100644 --- a/data-catalog/evm/berachain/raw/logs.mdx +++ b/data-catalog/evm/berachain/raw/logs.mdx @@ -7,7 +7,7 @@ description: Description of the berachain.logs table on Dune ## Table Description The `logs` table represents the logs generated by the Ethereum Virtual Machine (EVM) when a contract is executed on Berachain. As an EVM-identical chain, Berachain maintains complete compatibility with Ethereum's logging system while benefiting from its unique PoL consensus mechanism. Logs consist of: -- topic list: a list of 0 to 4 32-byte data topics +- Topic list: a list of 0 to 4 32-byte data topics - data: contains non-indexed data ## Column Descriptions diff --git a/data-catalog/evm/berachain/raw/traces.mdx b/data-catalog/evm/berachain/raw/traces.mdx index 1693f5a6..8839f2e9 100644 --- a/data-catalog/evm/berachain/raw/traces.mdx +++ b/data-catalog/evm/berachain/raw/traces.mdx @@ -6,7 +6,7 @@ description: Description of the berachain.traces table on Dune ## Table Description -The `traces` table contains the traces of the transactions executed on the Ethereum Virtual Machine (EVM). It includes the traces of the transaction and the traces of the internal transactions. Traces are the result of the execution of the transaction and are used to debug and understand the execution of the transaction. They are also known as `internal transactions` and can be used to understand the execution of a transaction. +The `traces` table contains the traces of transactions executed on the Ethereum Virtual Machine (EVM). It includes the traces of the transaction and the traces of internal transactions. Traces are the result of transaction execution and are used to debug and understand transaction execution. They are also known as `internal transactions` and can be used to understand the execution of a transaction. This is the raw version of this table, for decoded transaction calls, see the [call tables](/data-catalog/evm/berachain/decoded/call-tables) section. diff --git a/data-catalog/evm/blast/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/blast/curated-data/dex/dex-aggregator-trades.mdx index 7b7a36ca..28fdd5c1 100644 --- a/data-catalog/evm/blast/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/blast/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for blast import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/blast/curated-data/dex/dex-trades.mdx b/data-catalog/evm/blast/curated-data/dex/dex-trades.mdx index 065a7230..53822da2 100644 --- a/data-catalog/evm/blast/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/blast/curated-data/dex/dex-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex.trades on blast +title: dex.trades on Blast sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on blast." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Blast." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; diff --git a/data-catalog/evm/blast/curated-data/nft/nft-trades.mdx b/data-catalog/evm/blast/curated-data/nft/nft-trades.mdx index b3c88d8d..0324fca8 100644 --- a/data-catalog/evm/blast/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/blast/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on blast +title: NFT.trades on Blast sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on blast." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Blast." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/blast/decoded/contracts.mdx b/data-catalog/evm/blast/decoded/contracts.mdx index b83cc405..f9999c40 100644 --- a/data-catalog/evm/blast/decoded/contracts.mdx +++ b/data-catalog/evm/blast/decoded/contracts.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Decoded Contracts" description: Description of the blast.contracts table on Dune --- -import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; +import { ContractsSnippet } from "/snippets/evm/decoded/contracts-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/blast/overview.mdx b/data-catalog/evm/blast/overview.mdx index 36bd5a7a..4dbc7d2a 100644 --- a/data-catalog/evm/blast/overview.mdx +++ b/data-catalog/evm/blast/overview.mdx @@ -17,7 +17,7 @@ Blast is an Ethereum Layer 2 (L2) that natively provides yield for ETH and stabl - **T-Bill Yield:** Users who bridge stablecoins receive USDB, Blast's auto-rebasing stablecoin. The yield for USDB comes from MakerDAO's on-chain T-Bill protocol. USDB can be redeemed for DAI when bridging back to Ethereum. In the future, the Blast community will have the power to supplement, or even fully replace, MakerDAO with Blast-native solutions or other third-party protocols. -- **Gas Revenue Sharing:** Other L2s keep revenue from gas fees for themselves. Blast gives net gas revenue back to Dapps programmatically. Dapps developers can keep this revenue for themselves or use it to subsidize gas fees for users. +- **Gas Revenue Sharing:** Other L2s keep revenue from gas fees for themselves. Blast gives net gas revenue back to dApps programmatically. dApps developers can keep this revenue for themselves or use it to subsidize gas fees for users. diff --git a/data-catalog/evm/bnb/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/bnb/curated-data/dex/dex-aggregator-trades.mdx index 73b60caf..9fab7c6b 100644 --- a/data-catalog/evm/bnb/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/bnb/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for bnb import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/bnb/curated-data/dex/dex-trades.mdx b/data-catalog/evm/bnb/curated-data/dex/dex-trades.mdx index 711a98e3..66d19314 100644 --- a/data-catalog/evm/bnb/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/bnb/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/bnb/curated-data/nft/nft-trades.mdx b/data-catalog/evm/bnb/curated-data/nft/nft-trades.mdx index 40c1c450..53d02a67 100644 --- a/data-catalog/evm/bnb/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/bnb/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/bnb/decoded/contracts.mdx b/data-catalog/evm/bnb/decoded/contracts.mdx index 1c4bcc20..af84d840 100644 --- a/data-catalog/evm/bnb/decoded/contracts.mdx +++ b/data-catalog/evm/bnb/decoded/contracts.mdx @@ -1,7 +1,7 @@ --- -title: base.contracts +title: bnb.contracts sidebarTitle: "Decoded Contracts" -description: Description of the base.contracts table on Dune +description: Description of the bnb.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/bnb/decoded/event-logs.mdx b/data-catalog/evm/bnb/decoded/event-logs.mdx index b508fb2d..1cd25a33 100644 --- a/data-catalog/evm/bnb/decoded/event-logs.mdx +++ b/data-catalog/evm/bnb/decoded/event-logs.mdx @@ -1,6 +1,6 @@ --- -title: Event Logs - Bnb -description: Smart contracts on Bnb emit event logs when certain predefined actions are completed. +title: Event Logs - BNB +description: Smart contracts on BNB emit event logs when certain predefined actions are completed. --- import EventLogs from '/snippets/evm/decoded/event-logs-snippet.mdx' diff --git a/data-catalog/evm/bnb/decoded/logs-decoded.mdx b/data-catalog/evm/bnb/decoded/logs-decoded.mdx index da692b78..df3e9a19 100644 --- a/data-catalog/evm/bnb/decoded/logs-decoded.mdx +++ b/data-catalog/evm/bnb/decoded/logs-decoded.mdx @@ -1,7 +1,7 @@ --- -title: base.logs_decoded +title: bnb.logs_decoded sidebarTitle: "Decoded Logs" -description: Description of the base.logs_decoded table on Dune +description: Description of the bnb.logs_decoded table on Dune --- import { LogsDecodedSnippet } from '/snippets/evm/decoded/logs-decoded-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/bnb/decoded/overview.mdx b/data-catalog/evm/bnb/decoded/overview.mdx index bf7b9d1f..a0392be7 100644 --- a/data-catalog/evm/bnb/decoded/overview.mdx +++ b/data-catalog/evm/bnb/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/bnb/decoded/traces-decoded.mdx b/data-catalog/evm/bnb/decoded/traces-decoded.mdx index 6c7167a7..6ab81f8e 100644 --- a/data-catalog/evm/bnb/decoded/traces-decoded.mdx +++ b/data-catalog/evm/bnb/decoded/traces-decoded.mdx @@ -1,7 +1,7 @@ --- -title: base.traces_decoded +title: bnb.traces_decoded sidebarTitle: "Decoded Traces" -description: Description of the base.traces_decoded table on Dune +description: Description of the bnb.traces_decoded table on Dune --- import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/bnb/overview.mdx b/data-catalog/evm/bnb/overview.mdx index 8f0c2240..c3f9abf6 100644 --- a/data-catalog/evm/bnb/overview.mdx +++ b/data-catalog/evm/bnb/overview.mdx @@ -36,7 +36,7 @@ BNB Chain benefits from the strong community support and the extensive ecosystem Detailed information on transactions, illustrating operational efficiency and execution on the network. - + Decoded transaction data for easier analysis and better understanding of smart contract executions. diff --git a/data-catalog/evm/bob/overview.mdx b/data-catalog/evm/bob/overview.mdx index bace30fc..188e4d6d 100644 --- a/data-catalog/evm/bob/overview.mdx +++ b/data-catalog/evm/bob/overview.mdx @@ -59,6 +59,6 @@ BOB’s hybrid L2 design will be launched in multiple stages: Extensive transaction data, showcasing the efficiency and execution of operations on BOB. - Enhanced transaction data, including internal transactions invoked by top level transactions. + Enhanced transaction data, including internal transactions invoked by top-level transactions. diff --git a/data-catalog/evm/boba/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/boba/curated-data/dex/dex-aggregator-trades.mdx index 23242c2b..91365a49 100644 --- a/data-catalog/evm/boba/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/boba/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for boba import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/boba/curated-data/dex/dex-trades.mdx b/data-catalog/evm/boba/curated-data/dex/dex-trades.mdx index 9bba0a79..c1e11da7 100644 --- a/data-catalog/evm/boba/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/boba/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/boba/curated-data/nft/nft-trades.mdx b/data-catalog/evm/boba/curated-data/nft/nft-trades.mdx index 2bf7129b..4b8d75c5 100644 --- a/data-catalog/evm/boba/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/boba/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on boba +title: NFT.trades on Boba sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on boba." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Boba." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/boba/decoded/overview.mdx b/data-catalog/evm/boba/decoded/overview.mdx index 833f88f9..4a670f2a 100644 --- a/data-catalog/evm/boba/decoded/overview.mdx +++ b/data-catalog/evm/boba/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/boba/raw/logs.mdx b/data-catalog/evm/boba/raw/logs.mdx index 12cb5bf1..e971185a 100644 --- a/data-catalog/evm/boba/raw/logs.mdx +++ b/data-catalog/evm/boba/raw/logs.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Logs" description: Description of the boba.logs table on Dune --- -import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; +import { LogsSnippet } from "/snippets/evm/raw/logs-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/celo/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/celo/curated-data/dex/dex-aggregator-trades.mdx index 0741856a..3976f317 100644 --- a/data-catalog/evm/celo/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/celo/curated-data/dex/dex-aggregator-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex_aggregator.trades on celo +title: dex_aggregator.trades on Celo sidebarTitle: Aggregator Trades -description: Description of the Dex Aggregator Trades table for celo +description: Description of the DEX Aggregator Trades table for Celo --- import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; diff --git a/data-catalog/evm/celo/curated-data/dex/dex-trades.mdx b/data-catalog/evm/celo/curated-data/dex/dex-trades.mdx index 205ce214..96636176 100644 --- a/data-catalog/evm/celo/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/celo/curated-data/dex/dex-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex.trades on celo +title: dex.trades on Celo sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on celo." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Celo." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; diff --git a/data-catalog/evm/celo/curated-data/nft/nft-trades.mdx b/data-catalog/evm/celo/curated-data/nft/nft-trades.mdx index 8b4fc889..c8be4d1a 100644 --- a/data-catalog/evm/celo/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/celo/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on celo +title: NFT.trades on Celo sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on celo." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Celo." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/celo/decoded/overview.mdx b/data-catalog/evm/celo/decoded/overview.mdx index 757b040a..5ebd0f18 100644 --- a/data-catalog/evm/celo/decoded/overview.mdx +++ b/data-catalog/evm/celo/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/celo/decoded/traces-decoded.mdx b/data-catalog/evm/celo/decoded/traces-decoded.mdx index 0cc06431..161586ca 100644 --- a/data-catalog/evm/celo/decoded/traces-decoded.mdx +++ b/data-catalog/evm/celo/decoded/traces-decoded.mdx @@ -1,7 +1,7 @@ --- -title: v.traces_decoded +title: celo.traces_decoded sidebarTitle: "Decoded Traces" -description: Description of the ethereum.traces_decoded table on Dune +description: Description of the celo.traces_decoded table on Dune --- import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/celo/overview.mdx b/data-catalog/evm/celo/overview.mdx index 4438db14..d6b7f32b 100644 --- a/data-catalog/evm/celo/overview.mdx +++ b/data-catalog/evm/celo/overview.mdx @@ -36,7 +36,7 @@ Celo extends the reach of DeFi applications by enabling a suite of decentralized Extensive transaction data, showcasing the efficiency and user engagement across the network. - + Decoded transaction data for better analysis and understanding of contract executions on Celo. diff --git a/data-catalog/evm/corn/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/corn/curated-data/dex/dex-aggregator-trades.mdx index 7526f246..9c484e54 100644 --- a/data-catalog/evm/corn/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/corn/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for corn import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/corn/curated-data/dex/dex-trades.mdx b/data-catalog/evm/corn/curated-data/dex/dex-trades.mdx index 1dc7d374..1be45a74 100644 --- a/data-catalog/evm/corn/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/corn/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/corn/curated-data/nft/nft-trades.mdx b/data-catalog/evm/corn/curated-data/nft/nft-trades.mdx index 7c2d9326..4bb9c42f 100644 --- a/data-catalog/evm/corn/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/corn/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/corn/raw/traces.mdx b/data-catalog/evm/corn/raw/traces.mdx index 937473da..c7817835 100644 --- a/data-catalog/evm/corn/raw/traces.mdx +++ b/data-catalog/evm/corn/raw/traces.mdx @@ -5,8 +5,6 @@ description: Description of the corn.traces table on Dune --- import { TracesSnippet } from '/snippets/evm/raw/traces-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/degen/overview.mdx b/data-catalog/evm/degen/overview.mdx index 81105e2d..0ca7358b 100644 --- a/data-catalog/evm/degen/overview.mdx +++ b/data-catalog/evm/degen/overview.mdx @@ -7,7 +7,7 @@ description: degen data on Dune Degen, an ERC-20 token launched in January 2024, has reshaped the Farcaster ecosystem by enabling Casters to reward others with DEGEN for posting quality content. Our points system recognizes unique posts and comments, effectively bridging the gap between online contributions and real-world value. -Degen has launched a layer3 solution that settles transactions on the base network. This solution is designed to provide a more efficient and scalable way to settle transactions related to $degen. +Degen has launched a layer 3 solution that settles transactions on the Base network. This solution is designed to provide a more efficient and scalable way to settle transactions related to $DEGEN. Degen Chain uses Arbitrum Orbit for rollups, Base for transaction settlements, and Arbitrum AnyTrust for data availability. diff --git a/data-catalog/evm/ethereum/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/ethereum/curated-data/dex/dex-aggregator-trades.mdx index 5fcb78cf..055bd605 100644 --- a/data-catalog/evm/ethereum/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/ethereum/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for ethereum import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ethereum/curated-data/dex/dex-trades.mdx b/data-catalog/evm/ethereum/curated-data/dex/dex-trades.mdx index 0b80917a..b18c7c7c 100644 --- a/data-catalog/evm/ethereum/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/ethereum/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ethereum/curated-data/nft/nft-trades.mdx b/data-catalog/evm/ethereum/curated-data/nft/nft-trades.mdx index 7a0fedd1..7fe8c9af 100644 --- a/data-catalog/evm/ethereum/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/ethereum/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on ethereum +title: NFT Trades on Ethereum sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on ethereum." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Ethereum." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/ethereum/decoded/call-tables.mdx b/data-catalog/evm/ethereum/decoded/call-tables.mdx index 8978e210..87730e28 100644 --- a/data-catalog/evm/ethereum/decoded/call-tables.mdx +++ b/data-catalog/evm/ethereum/decoded/call-tables.mdx @@ -54,7 +54,7 @@ However, if one of these functions is invoked by another smart contract in the c In short: **State data stored in the memory of a smart contract is not available on Dune!** -A good example of this is the function `decimals` of the [erc20 token contract](https://etherscan.io/token/0x1f9840a85d5af5bf1d1762f925bdaddc4201f984#readContract) `Uni` which is a `constant` state variable that is able to be accessed through an automatically created "[getter function](https://docs.soliditylang.org/en/v0.7.4/contracts.html#getter-functions)". Should a smart contract invoke this function in the context of transaction, this message call will be recorded in the Dune table [`uniswap_ethereum.UNI_call_decimals"`](https://dune.com/queries/741354). +A good example of this is the function `decimals` of the [ERC20 token contract](https://etherscan.io/token/0x1f9840a85d5af5bf1d1762f925bdaddc4201f984#readContract) `Uni` which is a `constant` state variable that is able to be accessed through an automatically created "[getter function](https://docs.soliditylang.org/en/v0.7.4/contracts.html#getter-functions)". Should a smart contract invoke this function in the context of a transaction, this message call will be recorded in the Dune table [`uniswap_ethereum.UNI_call_decimals`](https://dune.com/queries/741354). This is in contrast to anyone calling this function locally using web3.py/web3.js or using the Etherscan frontend to access this state. These local calls are not recorded in Dune. diff --git a/data-catalog/evm/ethereum/decoded/event-logs.mdx b/data-catalog/evm/ethereum/decoded/event-logs.mdx index 18ebf375..ceba3def 100644 --- a/data-catalog/evm/ethereum/decoded/event-logs.mdx +++ b/data-catalog/evm/ethereum/decoded/event-logs.mdx @@ -47,7 +47,7 @@ Let's take the [uniswap v3 factory](https://etherscan.io/address/0x1f98431c8ad98 ## Multiple Instances -If there is multiple instances of a contract we will collect all event logs across all instances of this smart contract in one table. For example, all uniswap v3 pool `swap` events (on ethereum) are stored in the table: `uniswap_v3_ethereum.Pair_evt_Swap` +If there are multiple instances of a contract we will collect all event logs across all instances of this smart contract in one table. For example, all uniswap v3 pool `swap` events (on ethereum) are stored in the table: `uniswap_v3_ethereum.Pair_evt_Swap` The column `contract_address` indicates as to which smart contract emitted this event. diff --git a/data-catalog/evm/ethereum/decoded/logs-decoded.mdx b/data-catalog/evm/ethereum/decoded/logs-decoded.mdx index 96177fe0..23e97fd3 100644 --- a/data-catalog/evm/ethereum/decoded/logs-decoded.mdx +++ b/data-catalog/evm/ethereum/decoded/logs-decoded.mdx @@ -8,7 +8,7 @@ description: Description of the ethereum.logs_decoded table on Dune The `logs_decoded` table contains decoded logs from Ethereum transactions. The table matches `topic0` to the event signature and the corresponding event name. The table does not contain the full event data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Event Logs](/data-catalog/evm/ethereum/decoded/event-logs). -This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. +This table is great for gaining a high-level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. ## Column Descriptions diff --git a/data-catalog/evm/ethereum/decoded/overview.mdx b/data-catalog/evm/ethereum/decoded/overview.mdx index 393a3de1..d1554ec5 100644 --- a/data-catalog/evm/ethereum/decoded/overview.mdx +++ b/data-catalog/evm/ethereum/decoded/overview.mdx @@ -37,7 +37,7 @@ Dune's decoded data approach offers several benefits: ## Which contracts have decoded data? -Contract submission on Dune are driven by the community. Usually the odds are good that the contract you are looking at is already decoded, but esepecially for new projects or new contracts, it might be that the contract is not decoded yet. In those cases you can submit the contract to be decoded. Decoding usually takes about 24 hours, in special cases it might take longer. +Contract submissions on Dune are driven by the community. Usually the odds are good that the contract you are looking at is already decoded, but especially for new projects or new contracts, it might be that the contract is not decoded yet. In those cases you can submit the contract to be decoded. Decoding usually takes about 24 hours, in special cases it might take longer. You can check if contracts are already decoded by querying [`[blockchain].contracts`](/data-catalog/evm/ethereum/decoded/contracts) tables, the [data explorer](/web-app/query-editor/data-explorer) or use [this dashboard](https://dune.com/dune/is-my-contract-decoded-yet-v2). @@ -108,7 +108,7 @@ WHERE evt_tx_hash = 0x2bb7c8283b782355875fa37d05e4bd962519ea294678a3dcf2fdffbbd0 How exactly does this work? -Since we know which event we are looking at here, we can simply convert the encoded bytecode to decoded data by decoding the bytecode according to it's datatype. +Since we know which event we are looking at here, we can simply convert the encoded bytecode to decoded data by decoding the bytecode according to its datatype. The structure for the `Transfer` event log of an ERC20 token will always be: @@ -139,6 +139,6 @@ It's not always easy for a human to understand what exactly is going on in these If you are not able to make sense of the data by just searching the tables, it usually helps to look at single transactions using the transaction hash and Etherscan. -Furthermore, actually going into the smart contracts code (our favorite way to do this is [DethCode](https://etherscan.deth.net)) to read the comments or the actual logic can help to understand the smart contract's emitted data. +Furthermore, actually going into the smart contract's code (our favorite way to do this is [DethCode](https://etherscan.deth.net)) to read the comments or the actual logic can help to understand the smart contract's emitted data. If that also doesn't lead to satisfactory results, scouring the relevant docs and GitHub of the project can lead you to the desired answers. Furthermore, talking to the developers and core community of a project can also help you to get an understanding of the smart contracts. diff --git a/data-catalog/evm/ethereum/decoded/traces-decoded.mdx b/data-catalog/evm/ethereum/decoded/traces-decoded.mdx index 58a25e02..943551cc 100644 --- a/data-catalog/evm/ethereum/decoded/traces-decoded.mdx +++ b/data-catalog/evm/ethereum/decoded/traces-decoded.mdx @@ -6,7 +6,7 @@ description: Description of the ethereum.traces_decoded table on Dune ## Table Description -The `traces_decoded` table contains decoded traces from Ethereum transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/ethereum/decoded/traces-decoded). +The `traces_decoded` table contains decoded traces from Ethereum transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/ethereum/decoded/call-tables). This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. diff --git a/data-catalog/evm/ethereum/overview.mdx b/data-catalog/evm/ethereum/overview.mdx index 3bc5d0c0..3e173f2f 100644 --- a/data-catalog/evm/ethereum/overview.mdx +++ b/data-catalog/evm/ethereum/overview.mdx @@ -34,7 +34,7 @@ Ethereum's use of smart contracts automates enforcement, management, performance Detailed information on transactions, underscoring the high throughput and complexity of operations on Ethereum. - + Decoded transaction data, facilitating easier analysis and deeper understanding of smart contract operations. diff --git a/data-catalog/evm/ethereum/raw/blocks.mdx b/data-catalog/evm/ethereum/raw/blocks.mdx index 446c5811..e10fed2b 100644 --- a/data-catalog/evm/ethereum/raw/blocks.mdx +++ b/data-catalog/evm/ethereum/raw/blocks.mdx @@ -43,7 +43,7 @@ LIMIT 10 ```sql SELECT date_trunc('day', time) AS day, - count(distinct number) + count(*) FROM ethereum.blocks GROUP BY diff --git a/data-catalog/evm/ethereum/raw/creation-traces.mdx b/data-catalog/evm/ethereum/raw/creation-traces.mdx index b295aa8e..e4de32e7 100644 --- a/data-catalog/evm/ethereum/raw/creation-traces.mdx +++ b/data-catalog/evm/ethereum/raw/creation-traces.mdx @@ -28,14 +28,14 @@ import { TableSample } from "/snippets/table-sample.mdx"; ```sql select * from ethereum.creation_traces -where contract_address = 0x06012c8cf97bead5deae237070f9587f8e7a266d +where contract_address = '0x06012c8cf97bead5deae237070f9587f8e7a266d' ``` ### Show the creation of smart contracts by a specific creator ```sql select * from ethereum.creation_traces -where "from" = 0x0d4a11d5eeaac28ec3f61d100da81f6a1b65c9d6 +where "from" = '0x0d4a11d5eeaac28ec3f61d100da81f6a1b65c9d6' ``` ### Show the creation of smart contracts in the last 10 days diff --git a/data-catalog/evm/ethereum/raw/logs.mdx b/data-catalog/evm/ethereum/raw/logs.mdx index a5cc194e..665e68ca 100644 --- a/data-catalog/evm/ethereum/raw/logs.mdx +++ b/data-catalog/evm/ethereum/raw/logs.mdx @@ -5,7 +5,7 @@ description: Description of the ethereum.logs table on Dune --- ## Table Description -The `logs` table represents the logs generated by the Ethereum Virtual Machine (EVM) when a contract is executed. Logs are a way to store data on the blockchain. Logs originate from events that occur during the execution of a smart contract. A log consists of: +The `logs` table represents the logs generated by the Ethereum Virtual Machine (EVM) when a contract is executed. Logs are a way to store data on the blockchain. Logs originate from events that occur during the execution of a smart contract. A log consists of: - topic list: a list of 0 to 4 32-byte data topics. `Topic0` is the hash of the signature of the event (indexed), and the remaining topics are indexed parameters of the event. - data: contains non-indexed data. diff --git a/data-catalog/evm/ethereum/raw/traces.mdx b/data-catalog/evm/ethereum/raw/traces.mdx index 1a3e9bf2..a15dcd3f 100644 --- a/data-catalog/evm/ethereum/raw/traces.mdx +++ b/data-catalog/evm/ethereum/raw/traces.mdx @@ -6,7 +6,7 @@ description: Description of the ethereum.traces table on Dune ## Table Description -The `traces` table contains the traces of the transactions executed on the Ethereum Virtual Machine (EVM). It includes the traces of the transaction and the traces of the internal transactions. Traces are the result of the execution of the transaction and are used to debug and understand the execution of the transaction. They are also known as `internal transactions` and are can be used to understand the execution of a transaction. +The `traces` table contains the traces of the transactions executed on the Ethereum Virtual Machine (EVM). It includes the traces of the transaction and the traces of the internal transactions. Traces are the result of the execution of the transaction and are used to debug and understand the execution of the transaction. They are also known as `internal transactions` and can be used to understand the execution of a transaction. This is the raw version of this table, for decoded transaction calls, see the [call tables](/data-catalog/evm/ethereum/decoded/call-tables) section. diff --git a/data-catalog/evm/ethereum/raw/transactions.mdx b/data-catalog/evm/ethereum/raw/transactions.mdx index ccf23ac1..4f523d3b 100644 --- a/data-catalog/evm/ethereum/raw/transactions.mdx +++ b/data-catalog/evm/ethereum/raw/transactions.mdx @@ -30,7 +30,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ```sql select * -from ethereum.transactions where "from" = 0x50A1b5c358F8D34F0d35aA2f10742c46054E247e +from ethereum.transactions where "from" = '0x50A1b5c358F8D34F0d35aA2f10742c46054E247e' ``` ### Count the number of transactions per block diff --git a/data-catalog/evm/ethereum/raw/withdrawals.mdx b/data-catalog/evm/ethereum/raw/withdrawals.mdx index 954e1599..f2f76da1 100644 --- a/data-catalog/evm/ethereum/raw/withdrawals.mdx +++ b/data-catalog/evm/ethereum/raw/withdrawals.mdx @@ -44,7 +44,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ```sql select date_trunc('day', block_time) as dt, -sum(AMOUNT)/1e9 as withdraw_amount +sum(amount)/1e9 as withdraw_amount from ethereum.withdrawals group by 1 ``` diff --git a/data-catalog/evm/fantom/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/fantom/curated-data/dex/dex-aggregator-trades.mdx index 5e1a0d7b..81417cfe 100644 --- a/data-catalog/evm/fantom/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/fantom/curated-data/dex/dex-aggregator-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex_aggregator.trades on fantom +title: dex_aggregator.trades on Fantom sidebarTitle: Aggregator Trades -description: Description of the Dex Aggregator Trades table for fantom +description: Description of the Dex Aggregator Trades table for Fantom --- import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; diff --git a/data-catalog/evm/fantom/curated-data/dex/dex-trades.mdx b/data-catalog/evm/fantom/curated-data/dex/dex-trades.mdx index aceaa61e..02068232 100644 --- a/data-catalog/evm/fantom/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/fantom/curated-data/dex/dex-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex.trades on fantom +title: dex.trades on Fantom sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on fantom." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Fantom." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; diff --git a/data-catalog/evm/fantom/curated-data/nft/nft-trades.mdx b/data-catalog/evm/fantom/curated-data/nft/nft-trades.mdx index cdd027b5..952550d4 100644 --- a/data-catalog/evm/fantom/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/fantom/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on fantom +title: NFT.trades on Fantom sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on fantom." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Fantom." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/fantom/overview.mdx b/data-catalog/evm/fantom/overview.mdx index dd9ea662..0e284a39 100644 --- a/data-catalog/evm/fantom/overview.mdx +++ b/data-catalog/evm/fantom/overview.mdx @@ -36,7 +36,7 @@ Fantom supports a growing ecosystem of decentralized finance (DeFi) applications Extensive transaction data, highlighting the efficiency and speed of operations across the Fantom network. - + Decoded transaction information for enhanced analysis and understanding of smart contract executions. diff --git a/data-catalog/evm/flare/curated-data/dex/dex-trades.mdx b/data-catalog/evm/flare/curated-data/dex/dex-trades.mdx index 371a6951..2b1e9ee8 100644 --- a/data-catalog/evm/flare/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/flare/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/flare/curated-data/nft/nft-trades.mdx b/data-catalog/evm/flare/curated-data/nft/nft-trades.mdx index 6dae2754..b81c923e 100644 --- a/data-catalog/evm/flare/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/flare/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on flare +title: NFT Trades on Flare sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on flare." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Flare." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/flare/decoded/overview.mdx b/data-catalog/evm/flare/decoded/overview.mdx index af5379cd..0a683adc 100644 --- a/data-catalog/evm/flare/decoded/overview.mdx +++ b/data-catalog/evm/flare/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/flare/overview.mdx b/data-catalog/evm/flare/overview.mdx index 9b7ee899..a6b81a98 100644 --- a/data-catalog/evm/flare/overview.mdx +++ b/data-catalog/evm/flare/overview.mdx @@ -22,7 +22,7 @@ Infrastructure providers on Flare serve a dual role as validators and data provi ### **Developing on Flare** Developers interested in building on Flare can find comprehensive resources and guides at the Flare Developer Hub. This hub provides tools, documentation, and support to help developers create, test, and deploy their applications on Flare’s network. -## Flare Networks and chains +## Flare Networks and Chains Flare encompasses several networks, each designed for specific functions and stages of development: diff --git a/data-catalog/evm/flare/raw/logs.mdx b/data-catalog/evm/flare/raw/logs.mdx index 391587fe..ffc44664 100644 --- a/data-catalog/evm/flare/raw/logs.mdx +++ b/data-catalog/evm/flare/raw/logs.mdx @@ -8,5 +8,4 @@ import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file diff --git a/data-catalog/evm/gnosis/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/gnosis/curated-data/dex/dex-aggregator-trades.mdx index e77e0378..46c6d47d 100644 --- a/data-catalog/evm/gnosis/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/gnosis/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for gnosis import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/gnosis/curated-data/dex/dex-trades.mdx b/data-catalog/evm/gnosis/curated-data/dex/dex-trades.mdx index d68f63d8..26311328 100644 --- a/data-catalog/evm/gnosis/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/gnosis/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/gnosis/curated-data/nft/nft-trades.mdx b/data-catalog/evm/gnosis/curated-data/nft/nft-trades.mdx index d2555e6b..0b1babc3 100644 --- a/data-catalog/evm/gnosis/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/gnosis/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on gnosis +title: NFT Trades on Gnosis sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on gnosis." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Gnosis." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/gnosis/overview.mdx b/data-catalog/evm/gnosis/overview.mdx index b98350ec..fbbc98d5 100644 --- a/data-catalog/evm/gnosis/overview.mdx +++ b/data-catalog/evm/gnosis/overview.mdx @@ -5,7 +5,7 @@ sidebarTitle: "Overview" description: Gnosis Chain data on Dune --- -Gnosis Chain is a Layer 2 scaling solution designed for Ethereum, focusing on creating a low-cost, high-efficiency platform for decentralized applications (dApps). Formerly known as xDai Chain, Gnosis Chain emphasizes predictability in transaction costs, which are paid in the native stablecoin, xDAI. +Gnosis Chain is a Layer 2 scaling solution designed for Ethereum, focusing on creating a low-cost, high-efficiency platform for decentralized applications (dApps). Formerly known as xDai Chain, Gnosis Chain emphasizes predictability in transaction costs, which are paid in the native stablecoin, xDai. This platform uses a unique consensus mechanism called POSDAO, which is a Proof of Stake system that provides enhanced security and scalability while supporting environmental sustainability. Gnosis Chain is compatible with Ethereum, allowing Ethereum assets and projects to transition smoothly without the need for code changes. diff --git a/data-catalog/evm/hemi/curated-data/dex/dex-trades.mdx b/data-catalog/evm/hemi/curated-data/dex/dex-trades.mdx index f1c7216a..85b9cf6f 100644 --- a/data-catalog/evm/hemi/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/hemi/curated-data/dex/dex-trades.mdx @@ -8,6 +8,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ink/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/ink/curated-data/dex/dex-aggregator-trades.mdx index 3ed13ff4..abc8094b 100644 --- a/data-catalog/evm/ink/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/ink/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for ink import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ink/curated-data/dex/dex-trades.mdx b/data-catalog/evm/ink/curated-data/dex/dex-trades.mdx index fa7c50fe..cc6a23dc 100644 --- a/data-catalog/evm/ink/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/ink/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ink/curated-data/nft/nft-trades.mdx b/data-catalog/evm/ink/curated-data/nft/nft-trades.mdx index 44857788..ec11bcf8 100644 --- a/data-catalog/evm/ink/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/ink/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/ink/decoded/call-tables.mdx b/data-catalog/evm/ink/decoded/call-tables.mdx index aaaa40e1..0102c8d6 100644 --- a/data-catalog/evm/ink/decoded/call-tables.mdx +++ b/data-catalog/evm/ink/decoded/call-tables.mdx @@ -1,6 +1,6 @@ --- title: Ink Call Tables -description: On Dune, we parse all message calls and transactions made to smart contracts on the Ink network in their own tables. +description: On Dune, we parse all message calls and transactions made to smart contracts on the ink network in their own tables. --- import CallTables from '/snippets/evm/decoded/call-tables-snippet.mdx' diff --git a/data-catalog/evm/ink/decoded/contracts.mdx b/data-catalog/evm/ink/decoded/contracts.mdx index 88a027d1..ea1e93fa 100644 --- a/data-catalog/evm/ink/decoded/contracts.mdx +++ b/data-catalog/evm/ink/decoded/contracts.mdx @@ -5,8 +5,6 @@ description: Description of the ink.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ink/overview.mdx b/data-catalog/evm/ink/overview.mdx index ec31bce6..eadd0b24 100644 --- a/data-catalog/evm/ink/overview.mdx +++ b/data-catalog/evm/ink/overview.mdx @@ -58,7 +58,7 @@ Ink's architecture leverages the OP Stack to deliver a robust DeFi-focused platf Detailed data on transactions - + Decoded transaction information for enhanced analysis diff --git a/data-catalog/evm/kaia/curated-data/dex/dex-trades.mdx b/data-catalog/evm/kaia/curated-data/dex/dex-trades.mdx index c3c95d4f..ebca272d 100644 --- a/data-catalog/evm/kaia/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/kaia/curated-data/dex/dex-trades.mdx @@ -1,12 +1,12 @@ --- title: dex.trades on kaia sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on kaia." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Kaia." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/kaia/curated-data/nft/nft-trades.mdx b/data-catalog/evm/kaia/curated-data/nft/nft-trades.mdx index a712ae70..088a6406 100644 --- a/data-catalog/evm/kaia/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/kaia/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on kaia +title: NFT.trades on Kaia sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on kaia." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Kaia." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/kaia/decoded/overview.mdx b/data-catalog/evm/kaia/decoded/overview.mdx index 45f2e1ea..ea1c701e 100644 --- a/data-catalog/evm/kaia/decoded/overview.mdx +++ b/data-catalog/evm/kaia/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/kaia/decoded/traces-decoded.mdx b/data-catalog/evm/kaia/decoded/traces-decoded.mdx index 6ad05aad..b178c894 100644 --- a/data-catalog/evm/kaia/decoded/traces-decoded.mdx +++ b/data-catalog/evm/kaia/decoded/traces-decoded.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Decoded Traces" description: Description of the kaia.traces_decoded table on Dune --- -import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; +import { TracesDecodedSnippet } from "/snippets/evm/decoded/traces-decoded-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/kaia/overview.mdx b/data-catalog/evm/kaia/overview.mdx index e3ada4fc..5d5eddfa 100644 --- a/data-catalog/evm/kaia/overview.mdx +++ b/data-catalog/evm/kaia/overview.mdx @@ -82,15 +82,15 @@ KAIA is built to lead Web3 adoption in Asia by offering high-performance, low-co - Detailed event logs from smart contracts, offering insights into contract interactions and the dynamics of kaia's zk-Rollup operations. + Detailed event logs from smart contracts, offering insights into contract interactions and the dynamics of KAIA's zk-Rollup operations. Information on blocks processed through KAIA’s zk-Rollups, illustrating the network's enhanced throughput and scalability. - Extensive transaction data, highlighting the efficiency and reduced costs of operations on kaia. + Extensive transaction data, highlighting the efficiency and reduced costs of operations on KAIA. - - Decoded transaction data for easier analysis and deeper understanding of smart contract executions on the kaia network. + + Decoded transaction data for easier analysis and deeper understanding of smart contract executions on the KAIA network. diff --git a/data-catalog/evm/katana/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/katana/curated-data/dex/dex-aggregator-trades.mdx index 3769a1c9..813a2324 100644 --- a/data-catalog/evm/katana/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/katana/curated-data/dex/dex-aggregator-trades.mdx @@ -8,6 +8,6 @@ description: Description of the Dex Aggregator Trades table for katana import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/katana/curated-data/dex/dex-trades.mdx b/data-catalog/evm/katana/curated-data/dex/dex-trades.mdx index e0f0a238..260dfa26 100644 --- a/data-catalog/evm/katana/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/katana/curated-data/dex/dex-trades.mdx @@ -8,6 +8,6 @@ description: "The `dex.trades` table captures detailed data on DEX trade events import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/katana/decoded/logs-decoded.mdx b/data-catalog/evm/katana/decoded/logs-decoded.mdx index a01fe075..5804262a 100644 --- a/data-catalog/evm/katana/decoded/logs-decoded.mdx +++ b/data-catalog/evm/katana/decoded/logs-decoded.mdx @@ -1,8 +1,8 @@ --- -title: katana.logs_decoded +title: "katana.logs_decoded" icon: "bolt" sidebarTitle: "Logs Decoded" -description: Description of the katana.logs_decoded table on Dune +description: Description of the katana.logs_decoded table on Dune. --- import { LogsDecodedSnippet } from '/snippets/evm/decoded/logs-decoded-snippet.mdx'; diff --git a/data-catalog/evm/katana/overview.mdx b/data-catalog/evm/katana/overview.mdx index 1c94e320..dba6f94c 100644 --- a/data-catalog/evm/katana/overview.mdx +++ b/data-catalog/evm/katana/overview.mdx @@ -43,7 +43,7 @@ Katana is a high-performance blockchain platform designed for scalability and de Detailed data on transactions - + Decoded transaction information for enhanced analysis \ No newline at end of file diff --git a/data-catalog/evm/katana/raw/traces.mdx b/data-catalog/evm/katana/raw/traces.mdx index cd9b8c75..ad153527 100644 --- a/data-catalog/evm/katana/raw/traces.mdx +++ b/data-catalog/evm/katana/raw/traces.mdx @@ -9,4 +9,4 @@ import { TracesSnippet } from '/snippets/evm/raw/traces-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/lens/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/lens/curated-data/dex/dex-aggregator-trades.mdx index a708cf2c..d5b1f2d4 100644 --- a/data-catalog/evm/lens/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/lens/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for lens import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/lens/curated-data/dex/dex-trades.mdx b/data-catalog/evm/lens/curated-data/dex/dex-trades.mdx index 85ec97c1..9c7d56f6 100644 --- a/data-catalog/evm/lens/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/lens/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/lens/curated-data/nft/nft-trades.mdx b/data-catalog/evm/lens/curated-data/nft/nft-trades.mdx index f1d87603..26273fb8 100644 --- a/data-catalog/evm/lens/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/lens/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/lens/overview.mdx b/data-catalog/evm/lens/overview.mdx index 91508569..a57f668f 100644 --- a/data-catalog/evm/lens/overview.mdx +++ b/data-catalog/evm/lens/overview.mdx @@ -36,7 +36,7 @@ The platform provides a comprehensive environment for developers to build and de Information on blocks processed using Lens's ZK technology, reflecting the network's capacity for high transaction throughput. - Detailed transaction data, showcasing the operational efficiency and cost-effectiveness of Lens's validium solution. + Detailed transaction data, showcasing the operational efficiency and cost-effectiveness of Lens's validation solution. Decoded transaction data for easier analysis and better understanding of smart contract executions on Lens. diff --git a/data-catalog/evm/linea/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/linea/curated-data/dex/dex-aggregator-trades.mdx index e5914ba6..671b2d30 100644 --- a/data-catalog/evm/linea/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/linea/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for linea import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/linea/curated-data/dex/dex-trades.mdx b/data-catalog/evm/linea/curated-data/dex/dex-trades.mdx index 25336a0d..7fa37144 100644 --- a/data-catalog/evm/linea/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/linea/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/linea/curated-data/nft/nft-trades.mdx b/data-catalog/evm/linea/curated-data/nft/nft-trades.mdx index ae9c946d..15fe007d 100644 --- a/data-catalog/evm/linea/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/linea/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on linea +title: NFT.trades on Linea sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on linea." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Linea." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/linea/decoded/overview.mdx b/data-catalog/evm/linea/decoded/overview.mdx index 80ec7100..4461228a 100644 --- a/data-catalog/evm/linea/decoded/overview.mdx +++ b/data-catalog/evm/linea/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/linea/overview.mdx b/data-catalog/evm/linea/overview.mdx index a0bc80ff..e72afd64 100644 --- a/data-catalog/evm/linea/overview.mdx +++ b/data-catalog/evm/linea/overview.mdx @@ -9,7 +9,7 @@ Linea is an EVM-equivalent network, scaling the Ethereum experience. Secured wit - + The official documentation for Linea, providing detailed information on the protocol, architecture, and developer resources diff --git a/data-catalog/evm/mantle/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/mantle/curated-data/dex/dex-aggregator-trades.mdx index 2623a136..34059f78 100644 --- a/data-catalog/evm/mantle/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/mantle/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for mantle import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/mantle/curated-data/dex/dex-trades.mdx b/data-catalog/evm/mantle/curated-data/dex/dex-trades.mdx index 0b578be4..d22c0a12 100644 --- a/data-catalog/evm/mantle/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/mantle/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/mantle/curated-data/nft/nft-trades.mdx b/data-catalog/evm/mantle/curated-data/nft/nft-trades.mdx index 02ce6feb..d94be485 100644 --- a/data-catalog/evm/mantle/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/mantle/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on mantle +title: NFT.trades on Mantle sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on mantle." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Mantle." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/mantle/decoded/overview.mdx b/data-catalog/evm/mantle/decoded/overview.mdx index af2dcb1e..5b21c7d4 100644 --- a/data-catalog/evm/mantle/decoded/overview.mdx +++ b/data-catalog/evm/mantle/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/mantle/overview.mdx b/data-catalog/evm/mantle/overview.mdx index 89727c92..c6b4864a 100644 --- a/data-catalog/evm/mantle/overview.mdx +++ b/data-catalog/evm/mantle/overview.mdx @@ -15,7 +15,7 @@ As an Ethereum L2, Mantle Network offers the security, stability, and scalabilit - **Built as a Rollup**: Utilizes Ethereum validators and consensus protocols to significantly reduce gas fees, decrease latency, and increase throughput. Users can customize transaction confirmation requirements to provide near real-time confirmation latency with minimal security settings. -- **Modular Architecture**: Unlike traditional monolithic chains that execute transaction execution, consensus, settlement, and storage at the same network layer, Mantle separates these functions into individual modules as a modular chain. These include an EVM-compatible execution layer developed by Mantle for transaction execution, a consensus layer and settlement layer completed on Ethereum, and an external DA component (currently Mantle DA powered by EigenDA technology; we will switch to EigenDA upon its mainnet stable launch). +- **Modular Architecture**: Unlike traditional monolithic chains that handle transaction execution, consensus, settlement, and storage at the same network layer, Mantle separates these functions into individual modules as a modular chain. These include an EVM-compatible execution layer developed by Mantle for transaction execution, a consensus layer and settlement layer completed on Ethereum, and an external DA component (currently Mantle DA powered by EigenDA technology; we will switch to EigenDA upon its mainnet stable launch). - **Secured by Ethereum**: L2 state transitions are verified by Ethereum validators, undergoing the same consensus and settlement processes as L1 transactions. diff --git a/data-catalog/evm/mantle/raw/traces.mdx b/data-catalog/evm/mantle/raw/traces.mdx index 72c0e11f..4bc3d46b 100644 --- a/data-catalog/evm/mantle/raw/traces.mdx +++ b/data-catalog/evm/mantle/raw/traces.mdx @@ -8,5 +8,4 @@ import { TracesSnippet } from '/snippets/evm/raw/traces-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file diff --git a/data-catalog/evm/mode/overview.mdx b/data-catalog/evm/mode/overview.mdx index e363dfd8..2325e473 100644 --- a/data-catalog/evm/mode/overview.mdx +++ b/data-catalog/evm/mode/overview.mdx @@ -16,7 +16,7 @@ Mode offers hands-on support to scale your application and earn predictable reve Mode is committed to rewarding developers who grow the Mode ecosystem via the following mechanisms: - **Sequencer Fee Sharing:** Mode incorporates contract revenue-sharing incentives at the protocol layer. Applications and users that scale the Mode blockchain are motivated to work together and directly receive a proportion of network sequencer profits. -- **Developer Airdrops:** Mode will run a series of developer airdrops which reward developers for their contributions to the Mode ecosystem. A significant portion of MODE is available for developers. +- **Developer Airdrops:** Mode will run a series of developer airdrops that reward developers for their contributions to the Mode ecosystem. A significant portion of MODE is available for developers. - **Optimism's RPG Funding:** All developers building open-source apps and tools on Mode can apply for Optimism's $2b RPG Funding program. The Mode team will assist developers with their applications. **Low Fees:** diff --git a/data-catalog/evm/mode/raw/transactions.mdx b/data-catalog/evm/mode/raw/transactions.mdx index 73606ec3..87133e29 100644 --- a/data-catalog/evm/mode/raw/transactions.mdx +++ b/data-catalog/evm/mode/raw/transactions.mdx @@ -3,7 +3,7 @@ title: mode.transactions sidebarTitle: "Transactions" description: Description of the mode.transactions table on Dune --- -import { TransactionsSnippet } from '/snippets/evm/raw/transactions-snippet.mdx'; +import { TransactionsSnippet } from "/snippets/evm/raw/transactions-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/opbnb/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/opbnb/curated-data/dex/dex-aggregator-trades.mdx index c70b04e1..6dddf999 100644 --- a/data-catalog/evm/opbnb/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/opbnb/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for opbnb import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/opbnb/curated-data/dex/dex-trades.mdx b/data-catalog/evm/opbnb/curated-data/dex/dex-trades.mdx index e2af49e7..269eccac 100644 --- a/data-catalog/evm/opbnb/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/opbnb/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/opbnb/curated-data/nft/nft-trades.mdx b/data-catalog/evm/opbnb/curated-data/nft/nft-trades.mdx index 1467cd7d..cf28e9d2 100644 --- a/data-catalog/evm/opbnb/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/opbnb/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on opbnb +title: NFT.trades on opBNB sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on opbnb." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on opBNB." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/opbnb/decoded/contracts.mdx b/data-catalog/evm/opbnb/decoded/contracts.mdx index 46fd7795..05b0d257 100644 --- a/data-catalog/evm/opbnb/decoded/contracts.mdx +++ b/data-catalog/evm/opbnb/decoded/contracts.mdx @@ -1,7 +1,7 @@ --- -title: opbnb.contracts +title: opBNB.contracts sidebarTitle: "Decoded Contracts" -description: Description of the opbnb.contracts table on Dune +description: Description of the opBNB.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/opbnb/decoded/traces-decoded.mdx b/data-catalog/evm/opbnb/decoded/traces-decoded.mdx index 0ec7538d..5c6deb13 100644 --- a/data-catalog/evm/opbnb/decoded/traces-decoded.mdx +++ b/data-catalog/evm/opbnb/decoded/traces-decoded.mdx @@ -1,7 +1,7 @@ --- -title: opbnb.traces_decoded +title: opBNB.traces_decoded sidebarTitle: "Decoded Traces" -description: Description of the opbnb.traces_decoded table on Dune +description: Description of the opBNB.traces_decoded table on Dune --- import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/opbnb/overview.mdx b/data-catalog/evm/opbnb/overview.mdx index 1955dd1b..abe6f749 100644 --- a/data-catalog/evm/opbnb/overview.mdx +++ b/data-catalog/evm/opbnb/overview.mdx @@ -62,7 +62,7 @@ opBNB is a high-performance Layer 2 scaling solution for the BNB Smart Chain, po Detailed data on transactions - + Decoded transaction information for enhanced analysis diff --git a/data-catalog/evm/opbnb/raw/blocks.mdx b/data-catalog/evm/opbnb/raw/blocks.mdx index 6331209b..c991ea09 100644 --- a/data-catalog/evm/opbnb/raw/blocks.mdx +++ b/data-catalog/evm/opbnb/raw/blocks.mdx @@ -1,7 +1,7 @@ --- -title: opbnb.blocks +title: opBNB.blocks sidebarTitle: "Blocks" -description: Description of the opbnb.blocks table on Dune +description: Description of the opBNB.blocks table on Dune --- import { BlockSnippet } from '/snippets/evm/raw/blocks-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/optimism/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/optimism/curated-data/dex/dex-aggregator-trades.mdx index efcd0d24..35464184 100644 --- a/data-catalog/evm/optimism/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/optimism/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for optimism import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/optimism/curated-data/dex/dex-trades.mdx b/data-catalog/evm/optimism/curated-data/dex/dex-trades.mdx index 70f01e32..4cb16251 100644 --- a/data-catalog/evm/optimism/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/optimism/curated-data/dex/dex-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex.trades on optimism +title: dex.trades on Optimism sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on optimism." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Optimism." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; diff --git a/data-catalog/evm/optimism/curated-data/nft/nft-trades.mdx b/data-catalog/evm/optimism/curated-data/nft/nft-trades.mdx index 0016b383..fbf7892e 100644 --- a/data-catalog/evm/optimism/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/optimism/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on optimism +title: NFT.trades on Optimism sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on optimism." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Optimism." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/optimism/decoded/contracts.mdx b/data-catalog/evm/optimism/decoded/contracts.mdx index 88289451..72f0450d 100644 --- a/data-catalog/evm/optimism/decoded/contracts.mdx +++ b/data-catalog/evm/optimism/decoded/contracts.mdx @@ -8,5 +8,4 @@ import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file diff --git a/data-catalog/evm/optimism/decoded/overview.mdx b/data-catalog/evm/optimism/decoded/overview.mdx index b2f0bcda..f397c89d 100644 --- a/data-catalog/evm/optimism/decoded/overview.mdx +++ b/data-catalog/evm/optimism/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/optimism/decoded/traces-decoded.mdx b/data-catalog/evm/optimism/decoded/traces-decoded.mdx index d155fa5c..034ef3bb 100644 --- a/data-catalog/evm/optimism/decoded/traces-decoded.mdx +++ b/data-catalog/evm/optimism/decoded/traces-decoded.mdx @@ -1,7 +1,7 @@ --- -title: ethereum.traces_decoded +title: optimism.traces_decoded sidebarTitle: "Decoded Traces" -description: Description of the ethereum.traces_decoded table on Dune +description: Description of the optimism.traces_decoded table on Dune --- import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; diff --git a/data-catalog/evm/optimism/overview.mdx b/data-catalog/evm/optimism/overview.mdx index f2863aaf..0fb2bab8 100644 --- a/data-catalog/evm/optimism/overview.mdx +++ b/data-catalog/evm/optimism/overview.mdx @@ -36,7 +36,7 @@ Optimism actively supports a community-driven approach to its governance and dev Detailed information on transactions, highlighting the operational efficiency and reduced costs facilitated by Optimistic Rollups. - + Decoded transaction data for easier analysis and understanding of contract executions on the Optimism network. diff --git a/data-catalog/evm/optimism/raw/blocks.mdx b/data-catalog/evm/optimism/raw/blocks.mdx index cbf111bb..007eb75d 100644 --- a/data-catalog/evm/optimism/raw/blocks.mdx +++ b/data-catalog/evm/optimism/raw/blocks.mdx @@ -1,12 +1,10 @@ --- -title: optimism.blocks +title: Optimism.blocks sidebarTitle: "Blocks" description: Description of the optimism.blocks table on Dune --- import { BlockSnippet } from '/snippets/evm/raw/blocks-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/overview.mdx b/data-catalog/evm/overview.mdx index f733963b..f966faea 100644 --- a/data-catalog/evm/overview.mdx +++ b/data-catalog/evm/overview.mdx @@ -13,8 +13,8 @@ The Ethereum Virtual Machine (EVM) is the runtime environment for smart contract ### EVM Chains -We provide the most comprehensive data catalog for Ethereum Mainnet and EVM-compatible rollups, sidechains and other layer 2 solutions. -All EVM chains on Dune have raw data, decoded data and curated data tables available. +We provide the most comprehensive data catalog for Ethereum Mainnet and EVM-compatible rollups, sidechains, and other layer 2 solutions. +All EVM chains on Dune have raw data, decoded data, and curated data tables available. e.g. here are the available data sets for Ethereum Mainnet: diff --git a/data-catalog/evm/plume/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/plume/curated-data/dex/dex-aggregator-trades.mdx index 6a073092..76d116c7 100644 --- a/data-catalog/evm/plume/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/plume/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the plume.dex_aggregator_trades table on Dune import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/plume/curated-data/dex/dex-trades.mdx b/data-catalog/evm/plume/curated-data/dex/dex-trades.mdx index dde8c7ec..782eb8f3 100644 --- a/data-catalog/evm/plume/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/plume/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: Description of the plume.dex_trades table on Dune import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/plume/decoded/event-logs.mdx b/data-catalog/evm/plume/decoded/event-logs.mdx index 8ad4124c..c56c08e8 100644 --- a/data-catalog/evm/plume/decoded/event-logs.mdx +++ b/data-catalog/evm/plume/decoded/event-logs.mdx @@ -1,7 +1,7 @@ --- -title: plume.event_logs +title: Plume.event_logs sidebarTitle: "Event Logs" -description: Description of the plume.event_logs table on Dune +description: Description of the Plume.event_logs table on Dune --- import EventLogs from '/snippets/evm/decoded/event-logs-snippet.mdx' diff --git a/data-catalog/evm/plume/overview.mdx b/data-catalog/evm/plume/overview.mdx index 345911a8..347dad8f 100644 --- a/data-catalog/evm/plume/overview.mdx +++ b/data-catalog/evm/plume/overview.mdx @@ -9,7 +9,7 @@ description: Plume data on Dune ## What is Plume? -Plume is a public, EVM-compatible blockchain specifically designed for Real World Assets (RWAs). It serves as the onchain home for real-world assets, enabling them to be used like crypto-native assets through features like staking, swapping, lending, borrowing, and looping. +Plume is a public, EVM-compatible blockchain specifically designed for Real World Assets (RWAs). It serves as the on-chain home for real-world assets, enabling them to be used like crypto-native assets through features like staking, swapping, lending, borrowing, and looping. ## Key Features diff --git a/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-aggregator-trades.mdx index c42a6334..e3481801 100644 --- a/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for Polygon zkEVM import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-trades.mdx b/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-trades.mdx index 94fe946f..95397bbf 100644 --- a/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/polygon-zkEVM/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/polygon-zkEVM/curated-data/nft/nft-trades.mdx b/data-catalog/evm/polygon-zkEVM/curated-data/nft/nft-trades.mdx index e7a0b0b9..2958337e 100644 --- a/data-catalog/evm/polygon-zkEVM/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/polygon-zkEVM/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/polygon-zkEVM/decoded/contracts.mdx b/data-catalog/evm/polygon-zkEVM/decoded/contracts.mdx index 5d58fa22..10055915 100644 --- a/data-catalog/evm/polygon-zkEVM/decoded/contracts.mdx +++ b/data-catalog/evm/polygon-zkEVM/decoded/contracts.mdx @@ -1,7 +1,7 @@ --- -title: zkevm.contracts +title: polygon_zkevm.contracts sidebarTitle: "Decoded Contracts" -description: Description of the zkevm.contracts table on Dune +description: Description of the polygon_zkevm.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/polygon-zkEVM/decoded/logs-decoded.mdx b/data-catalog/evm/polygon-zkEVM/decoded/logs-decoded.mdx index 92c1446d..2930ebf1 100644 --- a/data-catalog/evm/polygon-zkEVM/decoded/logs-decoded.mdx +++ b/data-catalog/evm/polygon-zkEVM/decoded/logs-decoded.mdx @@ -1,7 +1,7 @@ --- -title: zkevm.logs_decoded +title: polygon_zkevm.logs_decoded sidebarTitle: "Decoded Logs" -description: Description of the zkevm.logs_decoded table on Dune +description: Description of the polygon_zkevm.logs_decoded table on Dune --- import { LogsDecodedSnippet } from '/snippets/evm/decoded/logs-decoded-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/polygon-zkEVM/decoded/overview.mdx b/data-catalog/evm/polygon-zkEVM/decoded/overview.mdx index aedbbbeb..3f0c622e 100644 --- a/data-catalog/evm/polygon-zkEVM/decoded/overview.mdx +++ b/data-catalog/evm/polygon-zkEVM/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/polygon-zkEVM/decoded/traces-decoded.mdx b/data-catalog/evm/polygon-zkEVM/decoded/traces-decoded.mdx index 4938045c..d7352751 100644 --- a/data-catalog/evm/polygon-zkEVM/decoded/traces-decoded.mdx +++ b/data-catalog/evm/polygon-zkEVM/decoded/traces-decoded.mdx @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/polygon-zkEVM/overview.mdx b/data-catalog/evm/polygon-zkEVM/overview.mdx index a26356be..0e3c265c 100644 --- a/data-catalog/evm/polygon-zkEVM/overview.mdx +++ b/data-catalog/evm/polygon-zkEVM/overview.mdx @@ -31,7 +31,7 @@ Dune offers comprehensive datasets for Polygon zkEVM, including event logs, tran Detailed transaction data, highlighting the execution and efficiency of operations - + Decoded transaction data for easier understanding and analysis of smart contract executions diff --git a/data-catalog/evm/polygon-zkEVM/raw/blocks.mdx b/data-catalog/evm/polygon-zkEVM/raw/blocks.mdx index adb12a15..63b1913f 100644 --- a/data-catalog/evm/polygon-zkEVM/raw/blocks.mdx +++ b/data-catalog/evm/polygon-zkEVM/raw/blocks.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Blocks" description: Description of the zkevm.blocks table on Dune --- -import { BlockSnippet } from '/snippets/evm/raw/blocks-snippet.mdx'; +import { BlockSnippet } from "/snippets/evm/raw/blocks-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/polygon-zkEVM/raw/creation-traces.mdx b/data-catalog/evm/polygon-zkEVM/raw/creation-traces.mdx index 280444ca..ac27d55a 100644 --- a/data-catalog/evm/polygon-zkEVM/raw/creation-traces.mdx +++ b/data-catalog/evm/polygon-zkEVM/raw/creation-traces.mdx @@ -1,7 +1,7 @@ --- -title: zkevm.creation_traces +title: polygon_zkevm.creation_traces sidebarTitle: "Creation Traces" -description: Description of the zkevm.creation_traces table on Dune +description: Description of the polygon_zkevm.creation_traces table on Dune --- import { CreationTracesSnippet } from '/snippets/evm/raw/creation-traces-snippet.mdx'; diff --git a/data-catalog/evm/polygon-zkEVM/raw/logs.mdx b/data-catalog/evm/polygon-zkEVM/raw/logs.mdx index be56a643..a8167344 100644 --- a/data-catalog/evm/polygon-zkEVM/raw/logs.mdx +++ b/data-catalog/evm/polygon-zkEVM/raw/logs.mdx @@ -1,7 +1,7 @@ --- -title: zkevm.logs +title: zkEVM.logs sidebarTitle: "Logs" -description: Description of the zkevm.logs table on Dune +description: Description of the zkEVM.logs table on Dune --- import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/polygon/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/polygon/curated-data/dex/dex-aggregator-trades.mdx index d4fa65b8..2f873bd3 100644 --- a/data-catalog/evm/polygon/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/polygon/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for polygon import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/polygon/curated-data/dex/dex-trades.mdx b/data-catalog/evm/polygon/curated-data/dex/dex-trades.mdx index 2c7f82b1..2ba0cb75 100644 --- a/data-catalog/evm/polygon/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/polygon/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/polygon/curated-data/nft/nft-trades.mdx b/data-catalog/evm/polygon/curated-data/nft/nft-trades.mdx index 1f6374dc..9d5b337c 100644 --- a/data-catalog/evm/polygon/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/polygon/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on polygon +title: NFT.trades on Polygon sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on polygon." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Polygon." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/polygon/decoded/call-tables.mdx b/data-catalog/evm/polygon/decoded/call-tables.mdx index 64683f4e..af5e973c 100644 --- a/data-catalog/evm/polygon/decoded/call-tables.mdx +++ b/data-catalog/evm/polygon/decoded/call-tables.mdx @@ -1,6 +1,6 @@ --- title: Polygon PoS Network Call Tables -description: On Dune, we parse all message calls and transactions made to smart contracts on the Polygon PoS Network network in their own tables. +description: On Dune, we parse all message calls and transactions made to smart contracts on the Polygon PoS Network in their own tables. --- import CallTables from '/snippets/evm/decoded/call-tables-snippet.mdx' diff --git a/data-catalog/evm/ronin/curated-data/dex/dex-trades.mdx b/data-catalog/evm/ronin/curated-data/dex/dex-trades.mdx index f708b3c7..e6ff3804 100644 --- a/data-catalog/evm/ronin/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/ronin/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/ronin/curated-data/nft/nft-trades.mdx b/data-catalog/evm/ronin/curated-data/nft/nft-trades.mdx index 6a866c5a..3281619c 100644 --- a/data-catalog/evm/ronin/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/ronin/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on ronin +title: NFT Trades on Ronin sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on ronin." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Ronin." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/scroll/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/scroll/curated-data/dex/dex-aggregator-trades.mdx index db459624..33466ec9 100644 --- a/data-catalog/evm/scroll/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/scroll/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for scroll import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/scroll/curated-data/dex/dex-trades.mdx b/data-catalog/evm/scroll/curated-data/dex/dex-trades.mdx index 9192251b..2e01d3c6 100644 --- a/data-catalog/evm/scroll/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/scroll/curated-data/dex/dex-trades.mdx @@ -1,7 +1,7 @@ --- -title: dex.trades on scroll +title: dex.trades on Scroll sidebarTitle: Dex Trades -description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on scroll." +description: "The `dex.trades` table captures detailed data on decentralized exchange (DEX) trades, recording all raw trade events across various protocols on Scroll." --- import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; diff --git a/data-catalog/evm/scroll/curated-data/nft/nft-trades.mdx b/data-catalog/evm/scroll/curated-data/nft/nft-trades.mdx index ab801cd7..741751b1 100644 --- a/data-catalog/evm/scroll/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/scroll/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on scroll +title: NFT.trades on Scroll sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on scroll." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Scroll." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/scroll/decoded/overview.mdx b/data-catalog/evm/scroll/decoded/overview.mdx index c9d5ce56..54c86779 100644 --- a/data-catalog/evm/scroll/decoded/overview.mdx +++ b/data-catalog/evm/scroll/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/scroll/overview.mdx b/data-catalog/evm/scroll/overview.mdx index 43b372aa..cce4249e 100644 --- a/data-catalog/evm/scroll/overview.mdx +++ b/data-catalog/evm/scroll/overview.mdx @@ -34,7 +34,7 @@ Scroll provides a robust environment for developers, with tools that simplify th Extensive transaction data, highlighting the efficiency and reduced costs of operations on Scroll. - + Decoded transaction data for easier analysis and deeper understanding of smart contract executions on the Scroll network. diff --git a/data-catalog/evm/sei/cosmos/cosmos_block_events.mdx b/data-catalog/evm/sei/cosmos/cosmos_block_events.mdx index 5e871565..13f80753 100644 --- a/data-catalog/evm/sei/cosmos/cosmos_block_events.mdx +++ b/data-catalog/evm/sei/cosmos/cosmos_block_events.mdx @@ -10,7 +10,7 @@ Contains all block-level events and attributes in the chain, partitioned by `eve ## Column Descriptions -| Column name | Data Type | Description | +| Column name | Data Type | Description | | ---------------- | --------- | ------------------------------------------------------------- | | **block_date** | date | The date of the block. | | **block_height** | bigint | The height of the block where the event occurred. | diff --git a/data-catalog/evm/sei/cosmos/cosmos_blocks.mdx b/data-catalog/evm/sei/cosmos/cosmos_blocks.mdx index dd8fbff2..d8d69948 100644 --- a/data-catalog/evm/sei/cosmos/cosmos_blocks.mdx +++ b/data-catalog/evm/sei/cosmos/cosmos_blocks.mdx @@ -17,7 +17,7 @@ Contains each validated block in the chain. `block_timestamp` is only available | **block_timestamp** | timestamp(3) with time zone | Timestamp when the block was validated. | | **chain_id** | varchar | The ID of the chain where the block belongs. | | **proposer_address** | varchar | The address of the validator proposing the block. | -| **validators_hash** | varchar | The hash of the validators set for the block. | +| **validators_hash** | varchar | The hash of the validator set for the block. | | **updated_at** | timestamp(3) with time zone | Timestamp of when the record was last updated. | | **ingested_at** | timestamp(3) with time zone | Timestamp of when the record was ingested into Dune. | diff --git a/data-catalog/evm/sei/cosmos/cosmos_tx_messages.mdx b/data-catalog/evm/sei/cosmos/cosmos_tx_messages.mdx index 03f63998..2fa9c215 100644 --- a/data-catalog/evm/sei/cosmos/cosmos_tx_messages.mdx +++ b/data-catalog/evm/sei/cosmos/cosmos_tx_messages.mdx @@ -28,7 +28,7 @@ On execution, transactions from Cosmos emit data in two formats: | **message_index** | bigint | The index of the message in the transaction. | | **message_type** | varchar | The type of message. | | **message** | varchar | The value/content of the message. | -| **schema_version** | bigint | The version of the schema in provider database. | +| **schema_version** | bigint | The version of the schema in the provider database. | | **updated_at** | timestamp(3) with time zone | Timestamp of when the record was last updated. | | **ingested_at** | timestamp(3) with time zone | Timestamp of when the record was ingested into Dune. | diff --git a/data-catalog/evm/sei/cosmos/cosmos_validators.mdx b/data-catalog/evm/sei/cosmos/cosmos_validators.mdx index dedebae8..bb11bc95 100644 --- a/data-catalog/evm/sei/cosmos/cosmos_validators.mdx +++ b/data-catalog/evm/sei/cosmos/cosmos_validators.mdx @@ -26,7 +26,7 @@ Maps validator addresses to monikers (human-readable description) and other meta | **unbonding_height** | bigint | The block height at which the validator started unbonding. | | **unbonding_time** | varchar | The time when the validator will complete unbonding. | | **commission_rate** | double | The commission rate charged by the validator. | -| **commission_max_rate** | double | The maximum commission rate allowed for the validator. | +| **commission_max_rate** | double | The maximum commission rate allowed for the validator. | | **commission_max_change_rate** | double | The maximum rate at which the validator can change its commission. | | **commission_update_time** | varchar | The time when the validator last updated its commission. | | **min_self_delegation** | varchar | The minimum self-delegation required for the validator. | diff --git a/data-catalog/evm/sei/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/sei/curated-data/dex/dex-aggregator-trades.mdx index dd617ef4..db535fa6 100644 --- a/data-catalog/evm/sei/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/sei/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for sei import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/sei/curated-data/dex/dex-trades.mdx b/data-catalog/evm/sei/curated-data/dex/dex-trades.mdx index 17ddd9b7..e49cd9e0 100644 --- a/data-catalog/evm/sei/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/sei/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/sei/curated-data/nft/nft-trades.mdx b/data-catalog/evm/sei/curated-data/nft/nft-trades.mdx index 9ecc3b28..500fa3d2 100644 --- a/data-catalog/evm/sei/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/sei/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/sei/overview.mdx b/data-catalog/evm/sei/overview.mdx index 005a126b..37c16ce7 100644 --- a/data-catalog/evm/sei/overview.mdx +++ b/data-catalog/evm/sei/overview.mdx @@ -7,7 +7,7 @@ description: Sei data on Dune ## What is Sei? -Sei is a Layer-1 blockchain optimized for trading and decentralized finance (DeFi). It combines the strengths of Solana and Ethereum by implementing a fast parallelized EVM chain, providing a hyper optimized execution layer that benefits from the tooling and mindshare around the EVM. +Sei is a Layer-1 blockchain optimized for trading and decentralized finance (DeFi). It combines the strengths of Solana and Ethereum by implementing a fast parallelized EVM chain, providing a hyper-optimized execution layer that benefits from the tooling and mindshare around the EVM. Sei is a Cosmos chain with EVM modules added in the [v2 upgrade](https://www.mintscan.io/sei/proposals/55). Dune indexes the EVM data separately from the Cosmos data. As such, data latency between the two can be expected. @@ -19,7 +19,7 @@ Sei is a Cosmos chain with EVM modules added in the [v2 upgrade](https://www.min - For Cosmos data, Dune partners with a data provider, and these tables and schemas can be found in the [Cosmos Data](#cosmos-data) section. - The EVM and Cosmos components share the same consensus mechanism, validated by the same validators, but they operate independently with interoperability features. - Interoperability between EVM and Cosmos relies on [EVM Precompiles](https://www.docs.sei.io/dev-interoperability/precompiles/addr) and [Pointer Contracts](https://www.docs.sei.io/dev-interoperability/pointer-contracts). If these do not emit events, it may result in data gaps. -- Dune's EVM data for Sei starts from the v2 upgrade at [block height 73,123,881](https://seitrace.com/block/79123881). +- Dune's EVM data for Sei starts from the v2 upgrade at [block height 79,123,881](https://seitrace.com/block/79123881). @@ -31,9 +31,9 @@ Parallelization allows Sei to process multiple independent transactions simultan Sei introduces four major innovations: -1. **Twin Turbo Consensus**: This feature allows Sei to reach the fastest time to finality of any blockchain at 400ms, unlocking web2 like experiences for applications. +1. **Twin Turbo Consensus**: This feature allows Sei to reach the fastest time to finality of any blockchain at 400ms, unlocking web2-like experiences for applications. 2. **Optimistic Parallelization**: This feature allows developers to unlock parallel processing for their Ethereum applications, with no additional work. -3. **SeiDB**: This major upgrade allows Sei to handle the much higher rate of data storage, reads and writes which become extremely important for a high performance blockchain. +3. **SeiDB**: This major upgrade allows Sei to handle the much higher rate of data storage, reads and writes which become extremely important for a high-performance blockchain. 4. **Interoperable EVM**: This allows existing developers in the Ethereum ecosystem to deploy their applications, tooling and infrastructure to Sei with no changes, while benefiting from the 100x performance improvements offered by Sei. ### Performance Metrics diff --git a/data-catalog/evm/sepolia/decoded/overview.mdx b/data-catalog/evm/sepolia/decoded/overview.mdx index d9220be1..6185dc8e 100644 --- a/data-catalog/evm/sepolia/decoded/overview.mdx +++ b/data-catalog/evm/sepolia/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/shape/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/shape/curated-data/dex/dex-aggregator-trades.mdx index c5d4e01c..f9548137 100644 --- a/data-catalog/evm/shape/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/shape/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for shape import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/shape/curated-data/dex/dex-trades.mdx b/data-catalog/evm/shape/curated-data/dex/dex-trades.mdx index 7cce3d3f..3515d4c7 100644 --- a/data-catalog/evm/shape/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/shape/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/shape/curated-data/nft/nft-trades.mdx b/data-catalog/evm/shape/curated-data/nft/nft-trades.mdx index b4fc8fa3..e43dec1c 100644 --- a/data-catalog/evm/shape/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/shape/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on shape +title: NFT.trades on Shape sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on shape." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Shape." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/shape/overview.mdx b/data-catalog/evm/shape/overview.mdx index 1a486d6f..d33acd8b 100644 --- a/data-catalog/evm/shape/overview.mdx +++ b/data-catalog/evm/shape/overview.mdx @@ -37,7 +37,7 @@ Shape is a member of the Superchain, which unlocks a range of further benefits f Extensive transaction data, highlighting the efficiency and reduced costs of operations on Shape. - + Decoded transaction data for easier analysis and deeper understanding of smart contract executions on the Shape network. diff --git a/data-catalog/evm/sonic/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/sonic/curated-data/dex/dex-aggregator-trades.mdx index 27fd7019..3bea98ce 100644 --- a/data-catalog/evm/sonic/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/sonic/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for sonic import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/sonic/curated-data/dex/dex-trades.mdx b/data-catalog/evm/sonic/curated-data/dex/dex-trades.mdx index 695210bf..61dce6cf 100644 --- a/data-catalog/evm/sonic/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/sonic/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/sonic/curated-data/nft/nft-trades.mdx b/data-catalog/evm/sonic/curated-data/nft/nft-trades.mdx index 0a4be31c..dd8db525 100644 --- a/data-catalog/evm/sonic/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/sonic/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on sonic +title: NFT.trades on Sonic sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on sonic." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Sonic." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/sonic/decoded/contracts.mdx b/data-catalog/evm/sonic/decoded/contracts.mdx index c2d64900..d1f9fd76 100644 --- a/data-catalog/evm/sonic/decoded/contracts.mdx +++ b/data-catalog/evm/sonic/decoded/contracts.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Decoded Contracts" description: Description of the sonic.contracts table on Dune --- -import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; +import { ContractsSnippet } from '/snippets/evm/decoded/contract-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/sonic/overview.mdx b/data-catalog/evm/sonic/overview.mdx index 80b7357e..1c741bae 100644 --- a/data-catalog/evm/sonic/overview.mdx +++ b/data-catalog/evm/sonic/overview.mdx @@ -20,7 +20,7 @@ Sonic maintains robust security through its aBFT (asynchronous Byzantine Fault T **Developer-Friendly Environment:** Sonic provides developers with powerful incentives and infrastructure including: - Fee Monetization: Earn up to 90% of the fees your apps generate -- Innovator Fund: Up to 200 million S to support new ventures +- Innovator Fund: Up to 200 million $S to support new ventures - Solidity/Vyper Support - Comprehensive development tooling diff --git a/data-catalog/evm/sophon/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/sophon/curated-data/dex/dex-aggregator-trades.mdx index cc7a121b..4634d803 100644 --- a/data-catalog/evm/sophon/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/sophon/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for sophon import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/sophon/curated-data/dex/dex-trades.mdx b/data-catalog/evm/sophon/curated-data/dex/dex-trades.mdx index 78df1954..d0c1f8bd 100644 --- a/data-catalog/evm/sophon/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/sophon/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/sophon/curated-data/nft/nft-trades.mdx b/data-catalog/evm/sophon/curated-data/nft/nft-trades.mdx index 7c1099cf..cd179798 100644 --- a/data-catalog/evm/sophon/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/sophon/curated-data/nft/nft-trades.mdx @@ -1,5 +1,5 @@ --- -title: NFT.trades on sophon +title: NFT Trades on sophon sidebarTitle: NFT Trades description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on sophon." --- @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/sophon/overview.mdx b/data-catalog/evm/sophon/overview.mdx index 8d04afdf..a9185fb7 100644 --- a/data-catalog/evm/sophon/overview.mdx +++ b/data-catalog/evm/sophon/overview.mdx @@ -5,7 +5,7 @@ sidebarTitle: "Overview" description: Sophon data on Dune --- -Sophon is a ZK chain that redefines onchain experiences by combining real applications with a simple user experience and high scalability. Built on ZK technology, Sophon aims to bring crypto accessibility to a wider audience while maintaining robust security and performance. +Sophon is a ZK chain that redefines on-chain experiences by combining real applications with a simple user experience and high scalability. Built on ZK technology, Sophon aims to bring crypto accessibility to a wider audience while maintaining robust security and performance. **Architecture and Technology:** Sophon is built on three key technological pillars: diff --git a/data-catalog/evm/sophon/raw/logs.mdx b/data-catalog/evm/sophon/raw/logs.mdx index 4a7eb3d6..da344d1c 100644 --- a/data-catalog/evm/sophon/raw/logs.mdx +++ b/data-catalog/evm/sophon/raw/logs.mdx @@ -8,5 +8,4 @@ import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file diff --git a/data-catalog/evm/sophon/raw/traces.mdx b/data-catalog/evm/sophon/raw/traces.mdx index d3b97296..5c9239e1 100644 --- a/data-catalog/evm/sophon/raw/traces.mdx +++ b/data-catalog/evm/sophon/raw/traces.mdx @@ -8,7 +8,7 @@ import { TracesSnippet } from '/snippets/evm/raw/traces-snippet.mdx'; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - + You may see duplicate records in the `traces` table for the Sophon chain. This is not a bug, but a result of trace calls appearing twice within the same transaction. These consecutive calls—an outer and an inner call—are identical except for their gas values. They share the same `from`, `to`, `input`, `output`, `success`, and `value` fields. diff --git a/data-catalog/evm/superseed/curated-data/dex/dex-trades.mdx b/data-catalog/evm/superseed/curated-data/dex/dex-trades.mdx index 7272b724..f9db1694 100644 --- a/data-catalog/evm/superseed/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/superseed/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/superseed/decoded/call-tables.mdx b/data-catalog/evm/superseed/decoded/call-tables.mdx index b8f9383c..4e6e9eb6 100644 --- a/data-catalog/evm/superseed/decoded/call-tables.mdx +++ b/data-catalog/evm/superseed/decoded/call-tables.mdx @@ -1,6 +1,6 @@ --- -title: Hemi Call Tables -description: On Dune, we parse all message calls and transactions made to smart contracts on the Hemi network in their own tables. +title: Superseed Call Tables +description: On Dune, we parse all message calls and transactions made to smart contracts on the Superseed network in their own tables. --- import CallTables from '/snippets/evm/decoded/call-tables-snippet.mdx' diff --git a/data-catalog/evm/superseed/decoded/contracts.mdx b/data-catalog/evm/superseed/decoded/contracts.mdx index 7e270d3b..ba959add 100644 --- a/data-catalog/evm/superseed/decoded/contracts.mdx +++ b/data-catalog/evm/superseed/decoded/contracts.mdx @@ -1,7 +1,7 @@ --- -title: superseed.contracts +title: Superseed.contracts sidebarTitle: "Contracts" -description: Description of the superseed.contracts table on Dune +description: Description of the Superseed.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/superseed/decoded/event-logs.mdx b/data-catalog/evm/superseed/decoded/event-logs.mdx index d032d4ef..5578446a 100644 --- a/data-catalog/evm/superseed/decoded/event-logs.mdx +++ b/data-catalog/evm/superseed/decoded/event-logs.mdx @@ -1,7 +1,7 @@ --- -title: superseed.event_logs +title: Superseed.event_logs sidebarTitle: "Event Logs" -description: Description of the superseed.event_logs table on Dune +description: Description of the Superseed.event_logs table on Dune --- import EventLogs from '/snippets/evm/decoded/event-logs-snippet.mdx' diff --git a/data-catalog/evm/superseed/overview.mdx b/data-catalog/evm/superseed/overview.mdx index 10ffc50a..99a80b9c 100644 --- a/data-catalog/evm/superseed/overview.mdx +++ b/data-catalog/evm/superseed/overview.mdx @@ -20,7 +20,7 @@ Superseed is a network that transforms Ethereum scaling into self-repaying loans ## Protocol Components -- **General-purpose Ethereum Layer 2**: Built on the OP stack, open-source, permissionless, and Ethereum-equivalent +- **General-purpose Ethereum Layer 2**: Built on the OP Stack, open-source, permissionless, and Ethereum-equivalent - **CDP Protocol**: Native collateralized debt position platform integrated into the rollup - **Revenue Sources**: Sequencer profits, CDP interest, and inflationary rewards - **Automatic Loan Repayment**: All fees generated across the network are used to burn the debt of Supercollateral users diff --git a/data-catalog/evm/superseed/raw/blocks.mdx b/data-catalog/evm/superseed/raw/blocks.mdx index 3366e665..66cf5b50 100644 --- a/data-catalog/evm/superseed/raw/blocks.mdx +++ b/data-catalog/evm/superseed/raw/blocks.mdx @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/superseed/raw/logs.mdx b/data-catalog/evm/superseed/raw/logs.mdx index c11abdfa..8babd8e7 100644 --- a/data-catalog/evm/superseed/raw/logs.mdx +++ b/data-catalog/evm/superseed/raw/logs.mdx @@ -1,7 +1,7 @@ --- -title: superseed.logs +title: Superseed.logs sidebarTitle: "Logs" -description: Description of the superseed.logs table on Dune +description: Description of the Superseed.logs table on Dune --- import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/tac/decoded/traces-decoded.mdx b/data-catalog/evm/tac/decoded/traces-decoded.mdx index 145b5ccd..24968c87 100644 --- a/data-catalog/evm/tac/decoded/traces-decoded.mdx +++ b/data-catalog/evm/tac/decoded/traces-decoded.mdx @@ -1,7 +1,7 @@ --- -title: tac.traces_decoded +title: zkatana.traces_decoded sidebarTitle: "Traces Decoded" -description: Description of the tac.traces_decoded table on Dune +description: Description of the zkatana.traces_decoded table on Dune --- import { TracesDecodedSnippet } from '/snippets/evm/decoded/traces-decoded-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/taiko/decoded/contracts.mdx b/data-catalog/evm/taiko/decoded/contracts.mdx index 6e1406c5..557b63f6 100644 --- a/data-catalog/evm/taiko/decoded/contracts.mdx +++ b/data-catalog/evm/taiko/decoded/contracts.mdx @@ -4,7 +4,7 @@ sidebarTitle: "Contracts" description: Description of the taiko.contracts table on Dune --- -import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; +import { ContractsSnippet } from "/snippets/evm/decoded/contracts-snippet.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/evm/unichain/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/unichain/curated-data/dex/dex-aggregator-trades.mdx index 81031adc..6e63a7c2 100644 --- a/data-catalog/evm/unichain/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/unichain/curated-data/dex/dex-aggregator-trades.mdx @@ -7,6 +7,6 @@ description: Description of the Dex Aggregator Trades table for unichain import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/unichain/curated-data/dex/dex-trades.mdx b/data-catalog/evm/unichain/curated-data/dex/dex-trades.mdx index 1d612180..c1a4c8bb 100644 --- a/data-catalog/evm/unichain/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/unichain/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/unichain/curated-data/nft/nft-trades.mdx b/data-catalog/evm/unichain/curated-data/nft/nft-trades.mdx index 5e25b66f..172fcede 100644 --- a/data-catalog/evm/unichain/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/unichain/curated-data/nft/nft-trades.mdx @@ -1,5 +1,5 @@ --- -title: NFT.trades on unichain +title: NFT Trades on unichain sidebarTitle: NFT Trades description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on unichain." --- @@ -7,6 +7,6 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/unichain/overview.mdx b/data-catalog/evm/unichain/overview.mdx index 38a11577..243465c1 100644 --- a/data-catalog/evm/unichain/overview.mdx +++ b/data-catalog/evm/unichain/overview.mdx @@ -36,7 +36,7 @@ As part of the Superchain ecosystem, Unichain supports native interoperability a Extensive transaction data, showcasing the efficiency and execution of operations on Unichain. - + Enhanced transaction data decoded for better analysis and understanding of contract executions. \ No newline at end of file diff --git a/data-catalog/evm/unichain/raw/traces.mdx b/data-catalog/evm/unichain/raw/traces.mdx index fe743ff1..b07b7094 100644 --- a/data-catalog/evm/unichain/raw/traces.mdx +++ b/data-catalog/evm/unichain/raw/traces.mdx @@ -5,7 +5,5 @@ description: Description of the unichain.traces table on Dune --- import { TracesSnippet } from '/snippets/evm/raw/traces-snippet.mdx'; -import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSample } from "/snippets/table-sample.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/unichain/raw/transactions.mdx b/data-catalog/evm/unichain/raw/transactions.mdx index af49d792..6d8bb27e 100644 --- a/data-catalog/evm/unichain/raw/transactions.mdx +++ b/data-catalog/evm/unichain/raw/transactions.mdx @@ -8,4 +8,4 @@ import { TransactionsSnippet } from '/snippets/evm/raw/transactions-snippet.mdx' import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/viction/curated-data/dex/dex-trades.mdx b/data-catalog/evm/viction/curated-data/dex/dex-trades.mdx index de72f83e..8e1c3916 100644 --- a/data-catalog/evm/viction/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/viction/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/viction/curated-data/nft/nft-trades.mdx b/data-catalog/evm/viction/curated-data/nft/nft-trades.mdx index 72d9b307..56f69aaa 100644 --- a/data-catalog/evm/viction/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/viction/curated-data/nft/nft-trades.mdx @@ -1,7 +1,7 @@ --- -title: NFT.trades on viction +title: NFT Trades on Viction sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on viction." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Viction." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; diff --git a/data-catalog/evm/viction/decoded/overview.mdx b/data-catalog/evm/viction/decoded/overview.mdx index 959c3c14..12e67cfe 100644 --- a/data-catalog/evm/viction/decoded/overview.mdx +++ b/data-catalog/evm/viction/decoded/overview.mdx @@ -7,4 +7,4 @@ icon: "star" import { OverviewDecodedDataApproach } from "/snippets/evm/decoded/decoded-overview-snippet.mdx" import { DuneEmbed } from '/snippets/dune-embed.mdx' - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/worldchain/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/worldchain/curated-data/dex/dex-aggregator-trades.mdx index 393fc4a0..7504284e 100644 --- a/data-catalog/evm/worldchain/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/worldchain/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for worldchain import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/worldchain/curated-data/dex/dex-trades.mdx b/data-catalog/evm/worldchain/curated-data/dex/dex-trades.mdx index 0d05a93d..08acd2b8 100644 --- a/data-catalog/evm/worldchain/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/worldchain/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/worldchain/curated-data/nft/nft-trades.mdx b/data-catalog/evm/worldchain/curated-data/nft/nft-trades.mdx index 5eb5bb59..9830f29c 100644 --- a/data-catalog/evm/worldchain/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/worldchain/curated-data/nft/nft-trades.mdx @@ -1,13 +1,13 @@ --- -title: NFT.trades on worldchain +title: NFT.trades on Worldchain sidebarTitle: NFT Trades -description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on worldchain." +description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on Worldchain." --- import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/worldchain/overview.mdx b/data-catalog/evm/worldchain/overview.mdx index 1be00b70..32ba3c34 100644 --- a/data-catalog/evm/worldchain/overview.mdx +++ b/data-catalog/evm/worldchain/overview.mdx @@ -41,7 +41,7 @@ World Chain supports mini apps, allowing third-party developers to create native Extensive transaction data, showcasing the efficiency and execution of operations on World Chain. - + Enhanced transaction data decoded for better analysis and understanding of contract executions. diff --git a/data-catalog/evm/worldchain/raw/logs.mdx b/data-catalog/evm/worldchain/raw/logs.mdx index cefabfb1..2febf9c4 100644 --- a/data-catalog/evm/worldchain/raw/logs.mdx +++ b/data-catalog/evm/worldchain/raw/logs.mdx @@ -1,7 +1,7 @@ --- -title: worldchain.logs +title: World Chain.logs sidebarTitle: "Logs" -description: Description of the worldchain.logs table on Dune +description: Description of the World Chain.logs table on Dune --- import { LogsSnippet } from '/snippets/evm/raw/logs-snippet.mdx'; diff --git a/data-catalog/evm/zksync/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/zksync/curated-data/dex/dex-aggregator-trades.mdx index 4e9e3eb3..dfc1de7b 100644 --- a/data-catalog/evm/zksync/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/zksync/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for zksync import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/zksync/curated-data/dex/dex-trades.mdx b/data-catalog/evm/zksync/curated-data/dex/dex-trades.mdx index 3b84a16c..6028f269 100644 --- a/data-catalog/evm/zksync/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/zksync/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/zksync/curated-data/nft/nft-trades.mdx b/data-catalog/evm/zksync/curated-data/nft/nft-trades.mdx index c0117b6c..6fdfa69c 100644 --- a/data-catalog/evm/zksync/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/zksync/curated-data/nft/nft-trades.mdx @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/zksync/decoded/contracts.mdx b/data-catalog/evm/zksync/decoded/contracts.mdx index 194dbabd..7e07cc19 100644 --- a/data-catalog/evm/zksync/decoded/contracts.mdx +++ b/data-catalog/evm/zksync/decoded/contracts.mdx @@ -1,7 +1,7 @@ --- -title: zksync.contracts +title: zkSync.contracts sidebarTitle: "Decoded Contracts" -description: Description of the zksync.contracts table on Dune +description: Description of the zkSync.contracts table on Dune --- import { ContractsSnippet } from '/snippets/evm/decoded/contracts-snippet.mdx'; @@ -9,4 +9,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - \ No newline at end of file + \ No newline at end of file diff --git a/data-catalog/evm/zora/curated-data/dex/dex-aggregator-trades.mdx b/data-catalog/evm/zora/curated-data/dex/dex-aggregator-trades.mdx index fe9413fe..64af845f 100644 --- a/data-catalog/evm/zora/curated-data/dex/dex-aggregator-trades.mdx +++ b/data-catalog/evm/zora/curated-data/dex/dex-aggregator-trades.mdx @@ -7,7 +7,7 @@ description: Description of the Dex Aggregator Trades table for zora import { DexAggregatorTradesSnippet } from '/snippets/curated-data/dex/text/dex-aggregator-trades-snippet.mdx'; import { DexAggregatorCoverage } from "/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/zora/curated-data/dex/dex-trades.mdx b/data-catalog/evm/zora/curated-data/dex/dex-trades.mdx index 4fcfed04..295026ba 100644 --- a/data-catalog/evm/zora/curated-data/dex/dex-trades.mdx +++ b/data-catalog/evm/zora/curated-data/dex/dex-trades.mdx @@ -7,6 +7,6 @@ description: "The `dex.trades` table captures detailed data on decentralized exc import { DexTradesSnippet } from '/snippets/curated-data/dex/text/dex-trades-snippet.mdx'; import { DexCoverage } from "/snippets/curated-data/dex/embeds/dex-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; \ No newline at end of file diff --git a/data-catalog/evm/zora/curated-data/nft/nft-trades.mdx b/data-catalog/evm/zora/curated-data/nft/nft-trades.mdx index 52f9a5d4..488f301d 100644 --- a/data-catalog/evm/zora/curated-data/nft/nft-trades.mdx +++ b/data-catalog/evm/zora/curated-data/nft/nft-trades.mdx @@ -1,5 +1,5 @@ --- -title: NFT.trades on zora +title: NFT Trades on zora sidebarTitle: NFT Trades description: "The `nft.trades` table captures detailed data on NFT marketplaces, recording all trade events across various protocols on zora." --- @@ -7,7 +7,7 @@ description: "The `nft.trades` table captures detailed data on NFT marketplaces, import { NFTTradesSnippet } from '/snippets/curated-data/nft/text/nft-trades-snippet.mdx'; import { NFTCoverage } from "/snippets/curated-data/nft/embeds/nft-coverage.mdx"; import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -import { TableSampleParam} from "/snippets/table-sample-with-param.mdx"; +import { TableSampleParam } from "/snippets/table-sample-with-param.mdx"; diff --git a/data-catalog/evm/zora/overview.mdx b/data-catalog/evm/zora/overview.mdx index 7575621f..0d7e04dd 100644 --- a/data-catalog/evm/zora/overview.mdx +++ b/data-catalog/evm/zora/overview.mdx @@ -29,7 +29,7 @@ Designed for high throughput, Zora Chain ensures that the growing demand for NFT Event logs from smart contracts, offering insights into interactions and activities within the Zora Chain network. - Data on blocks processed on Zora Chain, reflects the network's capacity for handling large volumes of transactions efficiently. + Data on blocks processed on Zora Chain, which reflects the network's capacity for handling large volumes of transactions efficiently. Comprehensive transaction data, showcasing the operational efficiency and reduced costs achieved through Zora Chain’s optimized blockchain solutions. diff --git a/data-catalog/fuel/overview.mdx b/data-catalog/fuel/overview.mdx index 1ebf5da7..7a9b6f04 100644 --- a/data-catalog/fuel/overview.mdx +++ b/data-catalog/fuel/overview.mdx @@ -7,7 +7,7 @@ description: Fuel blockchain data on Dune ## What is Fuel? -Fuel is an operating system purpose built for Ethereum Rollups. It implements improvements suggested to the Ethereum VM (EVM) for many years that couldn't be implemented due to the need to maintain backward compatibility, including parallel transaction execution and multiple native assets. +Fuel is an operating system purpose-built for Ethereum Rollups. It implements improvements suggested to the Ethereum VM (EVM) for many years that couldn't be implemented due to the need to maintain backward compatibility, including parallel transaction execution and multiple native assets. Fuel delivers unmatched processing capacity through its ability to execute transactions in parallel by using strict state access lists in the form of a UTXO model. With the FuelVM, Fuel full nodes identify the accounts a transaction touches, mapping out dependencies before execution. diff --git a/data-catalog/fuel/receipts.mdx b/data-catalog/fuel/receipts.mdx index dc75862e..ba24bf7c 100644 --- a/data-catalog/fuel/receipts.mdx +++ b/data-catalog/fuel/receipts.mdx @@ -7,7 +7,7 @@ description: Fuel blockchain receipts data This table contains data about transaction receipts in the Fuel blockchain, including execution results, gas usage, and associated metadata. -## Column Description +## Column Descriptions | Column Name | Data Type | Description | |------------|-----------|-------------| diff --git a/data-catalog/layerzero/messages.mdx b/data-catalog/layerzero/messages.mdx index 50430ecf..bbc3ca9f 100644 --- a/data-catalog/layerzero/messages.mdx +++ b/data-catalog/layerzero/messages.mdx @@ -18,8 +18,8 @@ The `layerzero.messages` table contains all cross-chain messages sent through th | transfer_foreign_key | string | Foreign key reference to the transfer | | tx_hash_source | string | Transaction hash on the source chain | | tx_hash_destination | string | Transaction hash on the destination chain | -| ts_source | timestamp | Timestamp of the message on source chain | -| ts_destination | timestamp | Timestamp of the message on destination chain | +| ts_source | timestamp | Timestamp of the message on the source chain | +| ts_destination | timestamp | Timestamp of the message on the destination chain | | block_number_source | decimal(38,0) | Block number on the source chain | | block_number_destination | decimal(38,0) | Block number on the destination chain | | addr_from | string | Address of the message sender | diff --git a/data-catalog/layerzero/overview.mdx b/data-catalog/layerzero/overview.mdx index d5c89d19..ad44fbf1 100644 --- a/data-catalog/layerzero/overview.mdx +++ b/data-catalog/layerzero/overview.mdx @@ -2,7 +2,7 @@ title: LayerZero sidebarTitle: "Overview" icon: "star" -description: LayerZero crosschain data on Dune +description: LayerZero cross-chain data on Dune --- LayerZero is a cross-chain messaging protocol that enables the transfer of messages and assets between different blockchain networks. It provides a secure and efficient way for applications to communicate and transfer value across chains. diff --git a/data-catalog/layerzero/receipts.mdx b/data-catalog/layerzero/receipts.mdx index bfbea7f5..8d5a825a 100644 --- a/data-catalog/layerzero/receipts.mdx +++ b/data-catalog/layerzero/receipts.mdx @@ -1,13 +1,13 @@ --- -title: layerzero.transfers -sidebarTitle: "Transfers" -description: Description of the layerzero.transfers table on Dune +title: layerzero.receipts +sidebarTitle: "Receipts" +description: Description of the layerzero.receipts table on Dune --- import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; -The `layerzero.transfers` table contains all cross-chain transfers executed through the LayerZero protocol. Each transfer represents a value transfer event between source and destination chains. +The `layerzero.receipts` table contains all cross-chain transfer receipts executed through the LayerZero protocol. Each receipt represents a value transfer event between source and destination chains. ## Table Schema diff --git a/data-catalog/layerzero/transfers.mdx b/data-catalog/layerzero/transfers.mdx index 519cc534..709ea11c 100644 --- a/data-catalog/layerzero/transfers.mdx +++ b/data-catalog/layerzero/transfers.mdx @@ -33,7 +33,7 @@ SELECT COUNT(*) as transfer_count, SUM(usd_value) as total_volume_usd FROM layerzero.transfers -WHERE timestampUpdated >= NOW() - INTERVAL '24' HOUR +WHERE timestampUpdated >= NOW() - INTERVAL '24 HOURS' GROUP BY symbol ORDER BY total_volume_usd DESC LIMIT 10; diff --git a/data-catalog/near/actions.mdx b/data-catalog/near/actions.mdx index 549c4efd..a46722f0 100644 --- a/data-catalog/near/actions.mdx +++ b/data-catalog/near/actions.mdx @@ -80,7 +80,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ## Data Manipulation Tips -The `actions` data in NEAR can be complicated and nested, causing it hard to analyze sometimes. So here we give two examples on how to work array and json data to make it easier to analyze. +The `actions` data in NEAR can be complicated and nested, making it hard to analyze sometimes. So here we give two examples on how to work with array and json data to make it easier to analyze. ### Explode array of rows into separate rows with defined fields @@ -158,7 +158,7 @@ select block_date -- , typeof(args_parsed) as data_type /* This is how you can get fields within each parsed function call args - - first examine the fields in the args_parsed for the tye of method `call_method_name` + - first examine the fields in the args_parsed for the type of method `call_method_name` - then parse accordingly */ , json_extract(args_parsed, '$.receiver_id') AS receiver_id diff --git a/data-catalog/near/balances.mdx b/data-catalog/near/balances.mdx index d4e01d4c..d46845ba 100644 --- a/data-catalog/near/balances.mdx +++ b/data-catalog/near/balances.mdx @@ -11,7 +11,7 @@ This table tracks account balance details on NEAR, including the liquid balance, | Column | Description | Type | | -------------------------- | ------------------------------------------------------------------------ | --------------------------------- | -| epoch_date | The date of the epoch when the balance was recorded. | date | +| epoch_date | The date of the epoch when the balance was recorded. | date | | epoch_block_height | The block height of the epoch when the balance was recorded. | bigint | | account_id | The account whose balance is being tracked. | varchar | | liquid | Amount of liquid NEAR tokens in the account. | double | diff --git a/data-catalog/near/block_chunks.mdx b/data-catalog/near/block_chunks.mdx index 29d4607e..61071ffa 100644 --- a/data-catalog/near/block_chunks.mdx +++ b/data-catalog/near/block_chunks.mdx @@ -6,7 +6,7 @@ description: Description of the near.block_chunks table on Dune ## Table description -This table contains block chunk data on NEAR. Chunk of a block is a part of a block from a shard. The collection of chunks of the block forms the NEAR Protocol block. +This table contains block chunk data on NEAR. A chunk of a block is a part of a block from a shard. The collection of chunks in the block forms the NEAR Protocol block. ## Column Descriptions diff --git a/data-catalog/near/ft_transfers.mdx b/data-catalog/near/ft_transfers.mdx index d3bb1951..1fb8695a 100644 --- a/data-catalog/near/ft_transfers.mdx +++ b/data-catalog/near/ft_transfers.mdx @@ -22,12 +22,12 @@ Table tracking all Fungible Token (FT) transfers in NEAR. | token_id | ID of the Fungible Token involved in the transfer (e.g., "near"). | varchar | | receipt_id | The receipt ID associated with the FT transfer. | varchar | | contract_account_id | The contract account handling the FT transfer. | varchar | -| cause | The function name invoked to cause the FT transfer. | varchar | +| cause | The function name invoked to cause the FT transfer. | varchar | | status | The status of the FT transfer (e.g., "SUCCESS_VALUE"). | varchar | | event_memo | Memo attached to the FT transfer event. | varchar | | event_index | Event index of the FT transfer event. | uint256 | -| affected_account_id | The account affected by the FT transfer, i.e. the "to" account. | varchar | -| involved_account_id | The account involved in the FT transfer, i.e. the "from" account. | varchar | +| affected_account_id | The account affected by the FT transfer, i.e., the "to" account. | varchar | +| involved_account_id | The account involved in the FT transfer, i.e., the "from" account. | varchar | | delta_amount | The amount of FT tokens transferred. | decimal(38,0) | | processed_time | Timestamp when the FT transfer data was processed. | timestamp(3) with time zone | | updated_at | Timestamp when the FT transfer record was last updated. | timestamp(3) with time zone | diff --git a/data-catalog/near/function_call.mdx b/data-catalog/near/function_call.mdx index 64aeecd4..4eb178a4 100644 --- a/data-catalog/near/function_call.mdx +++ b/data-catalog/near/function_call.mdx @@ -52,7 +52,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ## Data Manipulation Tips -The `actions` data in NEAR can be complicated and nested, causing it hard to analyze sometimes. So here we give two examples on how to work array and json data to make it easier to analyze. +The `actions` data in NEAR can be complicated and nested, making it hard to analyze sometimes. So here we give two examples on how to work with array and json data to make it easier to analyze. ### Explode array of rows into separate rows with defined fields @@ -130,7 +130,7 @@ select block_date -- , typeof(args_parsed) as data_type /* This is how you can get fields within each parsed function call args - - first examine the fields in the args_parsed for the tye of method `call_method_name` + - first examine the fields in the args_parsed for the type of method `call_method_name` - then parse accordingly */ , json_extract(args_parsed, '$.receiver_id') AS receiver_id diff --git a/data-catalog/near/logs.mdx b/data-catalog/near/logs.mdx index 13265341..7b2010c0 100644 --- a/data-catalog/near/logs.mdx +++ b/data-catalog/near/logs.mdx @@ -12,9 +12,9 @@ This table captures the output generated during the execution of smart contracts | Column | Description | Type | | ------------------------------------ | ------------------------------------------------------------------------ | --------------------------------- | -| block_date | The date of the block where the log entry was generated. | date | -| block_height | The block height at which the log entry was generated. | bigint | -| block_time | The time when the block containing the log entry was produced. | timestamp(3) with time zone | +| block_date | The date of the block where the log entry was generated. | date | +| block_height | The block height at which the log entry was generated. | bigint | +| block_time | The time when the block containing the log entry was produced. | timestamp(3) with time zone | | execution_status | The status of the execution outcome associated with the log. | varchar | | executor_account_id | The account that executed the transaction resulting in the log. | varchar | | receipt_id | The receipt ID associated with the log. | varchar | diff --git a/data-catalog/near/overview.mdx b/data-catalog/near/overview.mdx index 2b9ad6b5..e3715c17 100644 --- a/data-catalog/near/overview.mdx +++ b/data-catalog/near/overview.mdx @@ -84,7 +84,7 @@ NEAR blockchain data is partitioned and categorized to provide developers and us - Contains flattened out actions of the `function_call` type. + Contains flattened out actions of the `function_call` type. diff --git a/data-catalog/noble/blocks.mdx b/data-catalog/noble/blocks.mdx index dfae5ac2..04d35deb 100644 --- a/data-catalog/noble/blocks.mdx +++ b/data-catalog/noble/blocks.mdx @@ -16,7 +16,7 @@ This table contains data about blocks in the Noble blockchain, including block h | **block_timestamp** | timestamp(3) with time zone | Timestamp when the block was validated. | | **chain_id** | varchar | The ID of the chain where the block belongs. | | **proposer_address** | varchar | The address of the validator proposing the block. | -| **validators_hash** | varchar | The hash of the validators set for the block. | +| **validators_hash** | varchar | The hash of the validator set for the block. | | **updated_at** | timestamp(3) with time zone | Timestamp of when the record was last updated. | | **ingested_at** | timestamp(3) with time zone | Timestamp of when the record was ingested into Dune. | diff --git a/data-catalog/noble/message_events.mdx b/data-catalog/noble/message_events.mdx index cd4dc7a7..454ad481 100644 --- a/data-catalog/noble/message_events.mdx +++ b/data-catalog/noble/message_events.mdx @@ -15,7 +15,7 @@ This table contains data about message-related events in the Noble blockchain, i | **block_height** | The height of the block where the event occurred. | bigint | | **block_timestamp** | Timestamp when the block was validated. | timestamp(3) with time zone | | **chain_id** | The ID of the chain where the block belongs. | varchar | -| **tx_id** | The hash of the transaction where the event occurred. | varchar | +| **tx_id** | The hash of the transaction where the event occurred. | varchar | | **tx_index** | The index of the transaction in the block. | bigint | | **message_index** | The index of the message in the transaction. | bigint | | **event_index** | A unique index for events within the message. | bigint | @@ -23,8 +23,8 @@ This table contains data about message-related events in the Noble blockchain, i | **attribute_key** | The key of the event attribute. | varchar | | **attribute_value** | The value of the event attribute. | varchar | | **attribute_index** | A unique index for attributes within the event. | bigint | -| **updated_at** | Timestamp of when the record was last updated. | timestamp(3) with time zone | -| **ingested_at** | Timestamp of when the record was ingested into Dune. | timestamp(3) with time zone | +| **updated_at** | Timestamp when the record was last updated. | timestamp(3) with time zone | +| **ingested_at** | Timestamp when the record was ingested into Dune. | timestamp(3) with time zone | ## Table Sample diff --git a/data-catalog/noble/overview.mdx b/data-catalog/noble/overview.mdx index 19e3b04e..e19f3892 100644 --- a/data-catalog/noble/overview.mdx +++ b/data-catalog/noble/overview.mdx @@ -47,7 +47,7 @@ Noble blockchain data is organized into several key tables that capture differen

Contains all messages submitted to the blockchain

 -

Maps validator addresses to monikers (human-readable description) and other metadata

+

Maps validator addresses to monikers (human-readable descriptions) and other metadata

 diff --git a/data-catalog/noble/transactions.mdx b/data-catalog/noble/transactions.mdx index db64c99a..a7319636 100644 --- a/data-catalog/noble/transactions.mdx +++ b/data-catalog/noble/transactions.mdx @@ -9,7 +9,7 @@ This table contains data about transactions in the Noble blockchain, including t ## Column Descriptions -| Column name | Data Type | Description | +| Column name | Data Type | Description | | ---------------- | --------- | ------------------------------------------------------------- | | **block_height** | bigint | The height of the block where the transaction occurred. | | **chain_id** | varchar | The ID of the chain where the transaction occurred. | diff --git a/data-catalog/noble/tx_messages.mdx b/data-catalog/noble/tx_messages.mdx index f3c60d52..2ba6614c 100644 --- a/data-catalog/noble/tx_messages.mdx +++ b/data-catalog/noble/tx_messages.mdx @@ -27,7 +27,7 @@ On execution, transactions from Cosmos emit data in two formats: | **message_index** | bigint | The index of the message in the transaction. | | **message_type** | varchar | The type of message. | | **message** | varchar | The value/content of the message. | -| **schema_version** | bigint | The version of the schema in provider database. | +| **schema_version** | bigint | The version of the schema in provider's database. | | **updated_at** | timestamp(3) with time zone | Timestamp of when the record was last updated. | | **ingested_at** | timestamp(3) with time zone | Timestamp of when the record was ingested into Dune. | diff --git a/data-catalog/overview.mdx b/data-catalog/overview.mdx index 4339a731..c5c798c1 100644 --- a/data-catalog/overview.mdx +++ b/data-catalog/overview.mdx @@ -109,7 +109,7 @@ We are building world-class data infrastructure so you don't have to. Our data c - **Comprehensive Chain Histories:** Full access to blockchain data histories without gaps, ensuring source integrity. - **Accurate and Validated Data:** Commitment to accuracy, with validated consistency and uniqueness for all transactions and events. - **Rich Data Variety:** Decoded data transforms complex byte arrays into clear, structured, and usable information. -- **abstracted Data:** Dune's [Spellbook](https://github.com/duneanalytics/spellbook) enables collaborative, community-driven data modeling, unlocking new insights at lightning speed. +- **Abstracted Data:** Dune's [Spellbook](https://github.com/duneanalytics/spellbook) enables collaborative, community-driven data modeling, unlocking new insights at lightning speed. - **Vibrant Community Data Pools:** Access to vast pools of data contributed by an active and innovative community. - **Cross-Chain:** Our entire data catalog is hosted in the same database, making it easy to compare and contrast data across different chains. diff --git a/data-catalog/solana/idl-tables.mdx b/data-catalog/solana/idl-tables.mdx index 3eabdc2a..fe50e187 100644 --- a/data-catalog/solana/idl-tables.mdx +++ b/data-catalog/solana/idl-tables.mdx @@ -10,7 +10,7 @@ import { DuneEmbed } from '/snippets/dune-embed.mdx' **IDL Submissions** -You can submit any program for decoding that has a public IDL or github repo (anchor and native are both supported) like [this one](https://solscan.io/account/JUP4Fb2cqiRUcaTHdrPC8h2gNsA2ETXiPDD33WcGuJB#anchorProgramIDL). You can submit to [this form](https://forms.gle/tbHZ6ZeEke5qwVjcA). +You can submit any program for decoding that has a public IDL or GitHub repo (anchor and native are both supported) like [this one](https://solscan.io/account/JUP4Fb2cqiRUcaTHdrPC8h2gNsA2ETXiPDD33WcGuJB#anchorProgramIDL). You can submit to [this form](https://forms.gle/tbHZ6ZeEke5qwVjcA). Decoded tables inherit all of the columns from [`instruction_calls`](data-catalog/solana/instruction-calls), so you can refer there for most of the types. We only add columns for each argument in the function call `data` and each account that was required to be in `account_arguments`. **These only decode from instructions, and not inner instructions.** @@ -19,11 +19,11 @@ Decoded tables inherit all of the columns from [`instruction_calls`](data-catalo Using an IDL, we decode the function data arguments and the required account arguments. Let's look at an example using Whirlpool - normally you can find the IDL [on Solscan](https://solscan.io/account/whirLbMiicVdio4qvUfM5KAg6Ct8VwpYzGff3uctyCc#anchorProgramIDL), but this time we had to dig [into the project repo](https://github.com/orca-so/whirlpools/blob/main/sdk/src/artifacts/whirlpool.json). IDLs are like ABIs on Ethereum, except they are created from the [Anchor lang](https://www.anchor-lang.com/) project instead of natively from every program. -[Here's a transaction](https://solscan.io/tx/TGDKvM2E8mWYcsG2JBnb9axFcyEcKqs7yZLyayCmrV8p8SSdA8r9SLEC7EHQ4mcXQXpczEyaCBXvnmEi9yoKVJ9) of a pool (a trading pair) being initialzed. +[Here's a transaction](https://solscan.io/tx/TGDKvM2E8mWYcsG2JBnb9axFcyEcKqs7yZLyayCmrV8p8SSdA8r9SLEC7EHQ4mcXQXpczEyaCBXvnmEi9yoKVJ9) of a pool (a trading pair) being initialized. You can see that the instruction data is decoded in "Bumps", "TickSpacing", and "InitialSqrtPrice" on the explorer. We have the same thing in a SQL table! You can also see all the account names are labelled clearly as well with an `account_` prefix. Raw table inherited columns like `tx_id`, `block_time`, `tx_index` get a `call_` prefix. -The main thing to note is that we've exploded outer and inner instructions, where the index will match what you see on explorers. This example call is at the outer instruction level, so the inner instruction index is null. For Whirlpool swaps, often times it will happen in inner_instructions so then the top level outer instruction is inherited into the `call_outer_instruction_index` and the inner index is `call_inner_instruction_index` (same idea with the `call_outer_executing_account` and `call_inner_executing_acount`) +The main thing to note is that we've exploded outer and inner instructions, where the index will match what you see on explorers. This example call is at the outer instruction level, so the inner instruction index is null. For Whirlpool swaps, often times it will happen in inner_instructions so then the top level outer instruction is inherited into the `call_outer_instruction_index` and the inner index is `call_inner_instruction_index` (same idea with the `call_outer_executing_account` and `call_inner_executing_account`)
-## Table Sample +## Table sample import { TableSample } from "/snippets/table-sample.mdx"; diff --git a/data-catalog/solana/overview.mdx b/data-catalog/solana/overview.mdx index 2dbf9328..178ff7cf 100644 --- a/data-catalog/solana/overview.mdx +++ b/data-catalog/solana/overview.mdx @@ -7,7 +7,7 @@ description: Solana data on Dune diff --git a/data-catalog/solana/vote-transactions.mdx b/data-catalog/solana/vote-transactions.mdx index bca8cad4..11a9e424 100644 --- a/data-catalog/solana/vote-transactions.mdx +++ b/data-catalog/solana/vote-transactions.mdx @@ -6,7 +6,7 @@ description: Description of the solana.vote_transactions table on Dune ## Table description -This table contains the full set of vote transactions that are submitted by validators to vote on a block. It can be joined with the non-vote transactions table above to get a full breakdown of all transactions. It has the same schema as the main transactions table. +This table contains the full set of vote transactions that are submitted by validators to vote on a block. It can be joined with the non-vote transactions table to get a full breakdown of all transactions. It has the same schema as the main transactions table. ## Column Descriptions diff --git a/data-catalog/starknet/blocks.mdx b/data-catalog/starknet/blocks.mdx index 22349438..6779dd6a 100644 --- a/data-catalog/starknet/blocks.mdx +++ b/data-catalog/starknet/blocks.mdx @@ -15,8 +15,8 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two gas types of gas fields, one for `wei` and one for `fri`. -- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Values possible are `BLOB` or `CALLDATA`. +- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two types of gas fields, one for `wei` and one for `fri`. +- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Possible values are `BLOB` or `CALLDATA`. - Visit this [Starknet doc on block structure](https://docs.starknet.io/architecture-and-concepts/network-architecture/block-structure/) to learn more. diff --git a/data-catalog/starknet/calls.mdx b/data-catalog/starknet/calls.mdx index cef4ef60..d19d5501 100644 --- a/data-catalog/starknet/calls.mdx +++ b/data-catalog/starknet/calls.mdx @@ -15,12 +15,12 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two gas types of gas fields, one for `wei` and one for `fri`. -- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Values possible are `BLOB` or `CALLDATA`. +- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two types of gas fields, one for `wei` and one for `fri`. +- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Possible values are `BLOB` or `CALLDATA`. - The `block_status` has possible values `ACCEPTED_ON_L1` or `ACCEPTED_ON_L2`. Read here to learn more about [different transaction status](https://docs.starknet.io/architecture-and-concepts/network-architecture/transaction-life-cycle/#transaction_status). -- The `transaction_type` fields denotes [different types of transactions](https://docs.starknet.io/architecture-and-concepts/network-architecture/transactions/) supported by Starknet. Possible values are: `INVOKE`, `L1_HANDLER`, `DECLARE`, `DEPLOY_ACCOUNT`, and `DEPLOY`. -- The `call_type` fields denotes what type of function calls was invoked. Possible values are [`LIBRARY_CALL`](https://docs.starknet.io/architecture-and-concepts/smart-contracts/system-calls-cairo1/#library_call), `CALL`, or `DELEGATE` -- 'entry_point_type': The type of entry point. Possible values includes - `EXTERNAL`, `L1_HANDLER`, `CONSTRUCTOR` +- The `transaction_type` field denotes [different types of transactions](https://docs.starknet.io/architecture-and-concepts/network-architecture/transactions/) supported by Starknet. Possible values are: `INVOKE`, `L1_HANDLER`, `DECLARE`, `DEPLOY_ACCOUNT`, and `DEPLOY`. +- The `call_type` field denotes what type of function call was invoked. Possible values are [`LIBRARY_CALL`](https://docs.starknet.io/architecture-and-concepts/smart-contracts/system-calls-cairo1/#library_call), `CALL`, or `DELEGATE` +- `entry_point_type`: The type of entry point. Possible values include `EXTERNAL`, `L1_HANDLER`, `CONSTRUCTOR` ## Table Sample diff --git a/data-catalog/starknet/events.mdx b/data-catalog/starknet/events.mdx index a703d85f..6d9c963f 100644 --- a/data-catalog/starknet/events.mdx +++ b/data-catalog/starknet/events.mdx @@ -15,8 +15,8 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two gas types of gas fields, one for `wei` and one for `fri`. -- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Values possible are `BLOB` or `CALLDATA`. +- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two types of gas fields, one for `wei` and one for `fri`. +- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Possible values are `BLOB` or `CALLDATA`. - The `block_status` has possible values `ACCEPTED_ON_L1` or `ACCEPTED_ON_L2`. Read here to learn more about [different transaction status](https://docs.starknet.io/architecture-and-concepts/network-architecture/transaction-life-cycle/#transaction_status). - `from_address`: The address of the L2 contract sending the message - `keys`: The keys associated with the event diff --git a/data-catalog/starknet/overview.mdx b/data-catalog/starknet/overview.mdx index b7cf1a2e..3560cf9e 100644 --- a/data-catalog/starknet/overview.mdx +++ b/data-catalog/starknet/overview.mdx @@ -35,7 +35,7 @@ Starknet uses Cairo, a Turing-complete language designed for writing provable pr Starknet introduces a novel account model where each user interacts with the network through their account contracts. This model enhances security and flexibility, allowing for features like account abstraction and multi-sig wallets. Unlike the traditional EVM model, where accounts are either externally owned accounts (EOAs) or smart contracts, Starknet uses account contracts for both user accounts and smart contracts, allowing for more advanced features and customizability. -See Starknet's documentation on [Accounts](https://docs.starknet.io/architecture-and-concepts/accounts/introduction/) and [Contracts](https://docs.starknet.io/architecture-and-concepts/smart-contracts/contract-classes/) for more information +See Starknet's documentation on [Accounts](https://docs.starknet.io/architecture-and-concepts/accounts/introduction/) and [Contracts](https://docs.starknet.io/architecture-and-concepts/smart-contracts/contract-classes/) for more information. ### Starknet Transaction Lifecycle diff --git a/data-catalog/starknet/transactions.mdx b/data-catalog/starknet/transactions.mdx index 0c7795f4..972a702f 100644 --- a/data-catalog/starknet/transactions.mdx +++ b/data-catalog/starknet/transactions.mdx @@ -15,9 +15,9 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; -- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two gas types of gas fields, one for `wei` and one for `fri`. -- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Values possible are `BLOB` or `CALLDATA`. -- The `type` fields denotes [different types of transactions](https://docs.starknet.io/architecture-and-concepts/network-architecture/transactions/) supported by Starknet. Possible values are: `INVOKE`, `L1_HANDLER`, `DECLARE`, `DEPLOY_ACCOUNT`, and `DEPLOY`. +- Prior to [v3 transactions upgrade](https://www.starknet.io/developers/roadmap/v3-transactions/), fees are denominated in `wei` as users pay gas with ETH. For transactions v3 and later, fees are denominated in `fri` as users pay gas with STRK. Hence here you can see two types of gas fields, one for `wei` and one for `fri`. +- Starting with Starknet v0.13.1, Starknet distinguishes between blocks whose state diffs are sent to L1 as calldata and blocks whose state diffs are sent to L1 as blobs. The `l1_da_mode` property in the Starknet block header contains this information. Possible values are `BLOB` or `CALLDATA`. +- The `type` field denotes [different types of transactions](https://docs.starknet.io/architecture-and-concepts/network-architecture/transactions/) supported by Starknet. Possible values are: `INVOKE`, `L1_HANDLER`, `DECLARE`, `DEPLOY_ACCOUNT`, and `DEPLOY`. - The `fee_data_availability_mode` field denotes the storage domain of the account's balance from which fee will be charged. It can be one of 'L1' or 'L2' - The `block_status` has possible values `ACCEPTED_ON_L1` or `ACCEPTED_ON_L2`. Read here to learn more about [different transaction status](https://docs.starknet.io/architecture-and-concepts/network-architecture/transaction-life-cycle/#transaction_status). - The `actual_fee` has the actual fee paid for the transaction, to be used together with `actual_fee_unit`. diff --git a/data-catalog/stellar/accounts.mdx b/data-catalog/stellar/accounts.mdx index cf9647fe..f63640f8 100644 --- a/data-catalog/stellar/accounts.mdx +++ b/data-catalog/stellar/accounts.mdx @@ -7,7 +7,7 @@ description: Description of the accounts table on Dune ## Table description This table tracks the native token (Lumens) balances held by accounts. -Accounts are the central data structure in Stellar- they hold balances, sign transactions, and issue assets. Accounts can only exist with a valid keypair and the required minimum balance of XLM. +Accounts are the central data structure in Stellar - they hold balances, sign transactions, and issue assets. Accounts can only exist with a valid keypair and the required minimum balance of XLM. ## Column Descriptions diff --git a/data-catalog/stellar/evm_v_stellar.mdx b/data-catalog/stellar/evm_v_stellar.mdx index da994be9..cb59dc1e 100644 --- a/data-catalog/stellar/evm_v_stellar.mdx +++ b/data-catalog/stellar/evm_v_stellar.mdx @@ -130,7 +130,7 @@ Operation types on Stellar are analog to transaction types on EVM networks. The Stellar network natively supports [26 operation types](https://developers.stellar.org/docs/learn/fundamentals/list-of-operations), ranging from payments to orderbook offer management to smart contract invocation. -EVM natively supports 3 transaction types: payment (regular), contract deployment, and execute contract, and does not support natively for Orderbook or AMMs. +EVM natively supports 3 transaction types: payment (regular), contract deployment, and execute contract, and does not have native support for Orderbook or AMMs. #### Schema Mapping diff --git a/data-catalog/stellar/history_effects.mdx b/data-catalog/stellar/history_effects.mdx index 38b7835a..0a54c61e 100644 --- a/data-catalog/stellar/history_effects.mdx +++ b/data-catalog/stellar/history_effects.mdx @@ -7,7 +7,7 @@ description: Description of the history_effects table on Dune ## Table description Records specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are. -Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. Each of Stellar’s operations have a unique operation object. +Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. Each of Stellar's operations has a unique operation object. ## Column Descriptions diff --git a/data-catalog/stellar/history_ledgers.mdx b/data-catalog/stellar/history_ledgers.mdx index ef80916b..84d0ed3f 100644 --- a/data-catalog/stellar/history_ledgers.mdx +++ b/data-catalog/stellar/history_ledgers.mdx @@ -5,7 +5,7 @@ description: Description of the history_ledgers table on Dune --- ## Table description -Tracks ledgers info (equivalent of blocks on other blockchain), including metadata such as sequence numbers, transactions included, and fees. +Tracks ledgers info (equivalent of blocks on other blockchains), including metadata such as sequence numbers, transactions included, and fees. ## Column Descriptions diff --git a/data-catalog/stellar/history_operations.mdx b/data-catalog/stellar/history_operations.mdx index ca7b60dc..bba037d9 100644 --- a/data-catalog/stellar/history_operations.mdx +++ b/data-catalog/stellar/history_operations.mdx @@ -5,9 +5,9 @@ description: Description of the history_operations table on Dune --- ## Table description -Tracks operational details of transaction in ledgers/blocks. +Tracks operational details of transactions in ledgers/blocks. -Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. Each of Stellar’s operations have a unique operation object. +Operations are objects that represent a desired change to the ledger: payments, offers to exchange currency, changes made to account options, etc. Operations are submitted to the Stellar network grouped in a Transaction. Each of Stellar's operations has a unique operation object. ## Column Descriptions diff --git a/data-catalog/stellar/history_trades.mdx b/data-catalog/stellar/history_trades.mdx index 8f5c8854..4dc60487 100644 --- a/data-catalog/stellar/history_trades.mdx +++ b/data-catalog/stellar/history_trades.mdx @@ -9,39 +9,39 @@ Records trades performed on Stellar's decentralized exchange. ## Column Descriptions -| **Column** | **Description** | **Type** | -| --------------------------------------|------------------------------------------------------------------------------| ------------------------------------- | -| **closed_at_date** | The date when the trade operation was closed. | date | -| **history_operation_id** | The unique identifier for the operation associated with the trade. | bigint | -| **order** | The sequence or order of the trade execution within the operation. | bigint | -| **selling_account_address** | The account address of the seller in the trade. | varchar | -| **selling_asset_code** | The code of the asset being sold in the trade. | varchar | -| **selling_asset_issuer** | The issuer of the asset being sold in the trade. | varchar | -| **selling_asset_type** | The type of asset being sold (e.g., native, issued). | varchar | -| **selling_asset_id** | The identifier for the asset being sold. | bigint | -| **selling_amount** | The amount of the asset being sold. | double | -| **buying_account_address** | The account address of the buyer in the trade. | varchar | -| **buying_asset_code** | The code of the asset being bought in the trade. | varchar | -| **buying_asset_issuer** | The issuer of the asset being bought in the trade. | varchar | -| **buying_asset_type** | The type of asset being bought (e.g., native, issued). | varchar | -| **buying_asset_id** | The identifier for the asset being bought. | bigint | -| **buying_amount** | The amount of the asset being bought. | double | -| **price_n** | The numerator of the price ratio (price as a fraction) of the trade. | bigint | -| **price_d** | The denominator of the price ratio (price as a fraction) of the trade. | bigint | -| **selling_offer_id** | The offer ID for the selling side of the trade. | bigint | -| **buying_offer_id** | The offer ID for the buying side of the trade. | bigint | -| **selling_liquidity_pool_id** | The identifier for the liquidity pool involved in the selling side of the trade, if applicable. | varchar | -| **liquidity_pool_fee** | The fee in lumens (XLM) for the liquidity pool, if applicable. | bigint | -| **trade_type** | The type of trade (e.g., market, limit). | bigint | -| **rounding_slippage** | The slippage amount due to rounding in the trade execution. | bigint | -| **seller_is_exact** | A boolean indicating whether the seller's amount was exact in the trade. | boolean | -| **closed_at** | The timestamp when the trade was closed. | timestamp(3) with time zone | -| **updated_at** | The time when the trade record was last updated. | timestamp(3) with time zone | -| **ingested_at** | The time when the trade data was ingested into the system. | timestamp(3) with time zone | +| **Column** | **Description** | **Type** | +| -------------------------------------- | -------------------------------------------------------------------------------------------------- | --------------------------- | +| **closed_at_date** | The date when the trade operation was closed. | date | +| **history_operation_id** | The unique identifier for the operation associated with the trade. | bigint | +| **order** | The sequence or order of the trade execution within the operation. | bigint | +| **selling_account_address** | The account address of the seller in the trade. | varchar | +| **selling_asset_code** | The code of the asset being sold in the trade. | varchar | +| **selling_asset_issuer** | The issuer of the asset being sold in the trade. | varchar | +| **selling_asset_type** | The type of asset being sold (e.g., native, issued). | varchar | +| **selling_asset_id** | The identifier for the asset being sold. | bigint | +| **selling_amount** | The amount of the asset being sold. | double | +| **buying_account_address** | The account address of the buyer in the trade. | varchar | +| **buying_asset_code** | The code of the asset being bought in the trade. | varchar | +| **buying_asset_issuer** | The issuer of the asset being bought in the trade. | varchar | +| **buying_asset_type** | The type of asset being bought (e.g., native, issued). | varchar | +| **buying_asset_id** | The identifier for the asset being bought. | bigint | +| **buying_amount** | The amount of the asset being bought. | double | +| **price_n** | The numerator of the price ratio (price as a fraction) of the trade. | bigint | +| **price_d** | The denominator of the price ratio (price as a fraction) of the trade. | bigint | +| **selling_offer_id** | The offer ID for the selling side of the trade. | bigint | +| **buying_offer_id** | The offer ID for the buying side of the trade. | bigint | +| **selling_liquidity_pool_id** | The identifier for the liquidity pool involved in the selling side of the trade, if applicable. | varchar | +| **liquidity_pool_fee** | The fee in lumens (XLM) for the liquidity pool, if applicable. | bigint | +| **trade_type** | The type of trade (e.g., market, limit). | bigint | +| **rounding_slippage** | The slippage amount due to rounding in the trade execution. | bigint | +| **seller_is_exact** | A boolean indicating whether the seller's amount was exact in the trade. | boolean | +| **closed_at** | The timestamp when the trade was closed. | timestamp(3) with time zone | +| **updated_at** | The time when the trade record was last updated. | timestamp(3) with time zone | +| **ingested_at** | The time when the trade data was ingested into the system. | timestamp(3) with time zone | ## Table Sample import { TableSample } from "/snippets/table-sample.mdx"; - + \ No newline at end of file diff --git a/data-catalog/stellar/history_transactions.mdx b/data-catalog/stellar/history_transactions.mdx index e6d22f4a..c36e1ef1 100644 --- a/data-catalog/stellar/history_transactions.mdx +++ b/data-catalog/stellar/history_transactions.mdx @@ -17,7 +17,7 @@ Contains transaction details, linking to multiple operations within a transactio | **ledger_sequence** | The sequence number of the ledger in which the transaction is included. | bigint | | **account** | The account address that originated the transaction. | varchar | | **account_sequence** | The source account's sequence number that this transaction consumed. | bigint | -| **max_fee** | The maximum fee that the account was willing to pay for the transaction. | bigint | +| **max_fee** | The maximum fee that the account was willing to pay for the transaction. | bigint | | **operation_count** | The number of operations contained within this transaction. | bigint | | **created_at** | The timestamp when the transaction was created. | timestamp(3) with time zone | | **memo_type** | The type of memo attached to the transaction (e.g., text, id, hash). | varchar | @@ -45,7 +45,7 @@ Contains transaction details, linking to multiple operations within a transactio | **soroban_resources_write_bytes** | The number of bytes written during Soroban smart contract execution. | bigint | | **closed_at** | The timestamp when the transaction was closed. | timestamp(3) with time zone | | **transaction_result_code** | The result code that includes error codes for failed transactions. | varchar | -| **inclusion_fee_bid** | The fee bid by the account to include the transaction in the ledger. | bigint | +| **inclusion_fee_bid** | The fee bid by the account to include the transaction in the ledger. | bigint | | **inclusion_fee_charged** | The actual fee charged for the transaction to be included in the ledger. | bigint | | **resource_fee_refund** | The refunded portion of the resource fee. | bigint | | **non_refundable_resource_fee_charged**| The portion of the resource fee that is non-refundable. | bigint | diff --git a/data-catalog/stellar/liquidity_pools.mdx b/data-catalog/stellar/liquidity_pools.mdx index e382509f..e7d7447d 100644 --- a/data-catalog/stellar/liquidity_pools.mdx +++ b/data-catalog/stellar/liquidity_pools.mdx @@ -5,7 +5,7 @@ description: Description of the liquidity_pools table on Dune --- ## Table description -Stores data on Stellar’s liquidity pools, such as the type, fee, assets involved etc. Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading. +Stores data on Stellar's liquidity pools, such as the type, fee, assets involved, etc. Liquidity Pools provide a simple, non-interactive way to trade large amounts of capital and enable high volumes of trading. ## Column Descriptions diff --git a/data-catalog/stellar/overview.mdx b/data-catalog/stellar/overview.mdx index afbde7ce..ac9b967d 100644 --- a/data-catalog/stellar/overview.mdx +++ b/data-catalog/stellar/overview.mdx @@ -61,7 +61,7 @@ Stellar blockchain data is categorized into traditional time series tables (e.g. - Stores data on Stellar’s liquidity pools, such as the type, fee, assets involved etc. + Stores data on Stellar's liquidity pools, such as the type, fee, assets involved, etc. @@ -73,11 +73,11 @@ Stellar blockchain data is categorized into traditional time series tables (e.g. - Tracks ledgers info (equivalent of blocks on other blockchain), including metadata such as sequence numbers, transactions included, and fees. + Tracks ledgers info (equivalent of blocks on other blockchains), including metadata such as sequence numbers, transactions included, and fees. - Tracks operational details of transaction in ledgers/blocks. + Tracks operational details of transactions in ledgers/blocks. @@ -89,7 +89,7 @@ Stellar blockchain data is categorized into traditional time series tables (e.g. - Records specific changes that occur in the ledger as a result of success operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are. + Records specific changes that occur in the ledger as a result of successful operations, but are not necessarily directly reflected in the ledger or history, as transactions and operations are. diff --git a/data-catalog/stellar/trust_lines.mdx b/data-catalog/stellar/trust_lines.mdx index c72df1c7..f7c7e7c7 100644 --- a/data-catalog/stellar/trust_lines.mdx +++ b/data-catalog/stellar/trust_lines.mdx @@ -1,6 +1,6 @@ --- title: stellar.trust_lines -sidebarTitle: "Trustlines" +sidebarTitle: "Trust Lines" description: Description of the trust_lines table on Dune --- diff --git a/data-catalog/stellar/ttl.mdx b/data-catalog/stellar/ttl.mdx index 40e35324..4aa2c6d2 100644 --- a/data-catalog/stellar/ttl.mdx +++ b/data-catalog/stellar/ttl.mdx @@ -16,7 +16,7 @@ Records time limits for smart contract data, enforcing storage expiry rules. | **key_hash** | The hash of the key used to identify the TTL entry, in binary format. | varbinary | | **live_until_ledger_seq** | The ledger sequence number until which the TTL entry remains live. | bigint | | **last_modified_ledger** | The ledger sequence number where the TTL entry was last modified. | bigint | -| **ledger_entry_change** | Indicates the type of change made to the ledger entry (insert, update, delete). | bigint | +| **ledger_entry_change** | Indicates the type of change made to the ledger entry (insert, update, delete). | bigint | | **deleted** | A boolean indicating whether the TTL entry has been deleted from the ledger. | boolean | | **closed_at** | The timestamp when the TTL entry was closed. | timestamp(3) with time zone | | **ledger_sequence** | The sequence number of the ledger in which the TTL entry is included. | bigint | diff --git a/data-catalog/substrate/calls.mdx b/data-catalog/substrate/calls.mdx index 2ff5ee02..eda2d038 100644 --- a/data-catalog/substrate/calls.mdx +++ b/data-catalog/substrate/calls.mdx @@ -6,7 +6,7 @@ description: Description of Substrate calls tables on Dune. ## Table description -Compared to the `extrinsics` table, which only has a top-level call, the `calls` Substrate table represents _internal_ calls, including recursive internal calls of `proxy` and `utility` (batch) pallets, and provides detailed call arguments each level of the call tree. +Compared to the `extrinsics` table, which only has a top-level call, the `calls` Substrate table represents _internal_ calls, including recursive internal calls of `proxy` and `utility` (batch) pallets, and provides detailed call arguments for each level of the call tree. Common queries on the `calls` table will typically filter on `block_time`, `call_section` and `call_method` and extract JSON encoded information in `data` or `decoded_data`. diff --git a/data-catalog/substrate/events.mdx b/data-catalog/substrate/events.mdx index fb1585ac..44632722 100644 --- a/data-catalog/substrate/events.mdx +++ b/data-catalog/substrate/events.mdx @@ -22,4 +22,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - + diff --git a/data-catalog/substrate/extrinsics.mdx b/data-catalog/substrate/extrinsics.mdx index cf9d87d8..8d967651 100644 --- a/data-catalog/substrate/extrinsics.mdx +++ b/data-catalog/substrate/extrinsics.mdx @@ -8,7 +8,7 @@ description: Description of Substrate extrinsics table on Dune. Extrinsics (aka "transactions") normally contain a signature, some data to describe if the extrinsic has passed some validity checks and a reference to the pallet and call that it is intended for. Extrinsics may be signed or unsigned. Some extrinsics have a complex structure, e.g. when using proxy or utility pallets, resulting in the top-level call initiating other calls involving other pallets. -Common queries on the `extrinsics` table (e.g. `polkadot.extrinsics`) will typically filter on `block_time`, `section` and `method` and extract JSON encoded information in `data` or `decoded_data`. In many cases, an initial query on the `extrinsics` table is best developed on the calls table instead to properly capture how users often use proxy and utility constructs to interact with the Substrate chain. +Common queries on the `extrinsics` table (e.g. `polkadot.extrinsics`) will typically filter on `block_time`, `section` and `method` and extract JSON-encoded information in `data` or `decoded_data`. In many cases, an initial query on the `extrinsics` table is best developed on the calls table instead to properly capture how users often use proxy and utility constructs to interact with the Substrate chain. ## Column Descriptions diff --git a/data-catalog/substrate/materialized_views.mdx b/data-catalog/substrate/materialized_views.mdx index 291bddc5..e727ef3b 100644 --- a/data-catalog/substrate/materialized_views.mdx +++ b/data-catalog/substrate/materialized_views.mdx @@ -46,5 +46,5 @@ A list of useful queries that we have [materialized](https://dune.com/queries?ca | Materialized View | Query ID | Description | | --------------------------------------------- | ------------------------------------------------- | ------------------------------------------------------ | | dune.substrate.result_interlay_oracle | [query_3445402](https://dune.com/queries/3445402) | All graphs that use a price on Interlay | -| dune.substrate.result_interlay_vault_creation | [query_3437565](https://dune.com/queries/3437565) | All graphs that show vaults with their collateral | +| dune.substrate.result_interlay_vault_creation | [query_3437565](https://dune.com/queries/3437565) | All graphs that show vaults with their collateral | | dune.substrate.result_hydradx_oracle | [query_3459562](https://dune.com/queries/3459562) | All graphs that use trade volume or prices on HydraDX. | diff --git a/data-catalog/substrate/overview.mdx b/data-catalog/substrate/overview.mdx index 6f2110ae..c2822ee0 100644 --- a/data-catalog/substrate/overview.mdx +++ b/data-catalog/substrate/overview.mdx @@ -67,7 +67,7 @@ As Substrate chains use SS58 Addresses, the following Dune function is very usef - [SS58 functions: from_ss58(varchar) + to_ss58(varbinary, int)](/query-engine/Functions-and-operators/ss58) -### overview of recent blocks +### Overview of recent blocks ```sql SELECT DATE(block_time) AS logDT, @@ -82,7 +82,7 @@ GROUP BY 1 order by 1 desc; ``` -### popular pallets +### Popular pallets Query the most popular pallets and their methods. @@ -92,7 +92,7 @@ where call_section not in ('timestamp', 'utility', 'proxy') group by call_section, call_method order by count(*) desc ``` -### frequent events +### Frequent events Query the most frequent events, excluding system events. @@ -102,7 +102,7 @@ where section not in ('system') group by 2 order by count(*) desc ``` -### other chains +### Other chains To query other chains, replace `polkadot` with the chain name, e.g. `kusama`, `interlay`, `astar` etc. diff --git a/data-catalog/substrate/stakings.mdx b/data-catalog/substrate/stakings.mdx index f1b63d4a..75b32fa8 100644 --- a/data-catalog/substrate/stakings.mdx +++ b/data-catalog/substrate/stakings.mdx @@ -6,7 +6,7 @@ description: Description of the polkadot.stakings table on Dune. ## Table description -The stakings table includes all the data necessary to compute staking-related metrics for Validators, Nominators, Pools, and Pool Members. This is currently supported for Polkadot and Kusama Relay Chain only. +The stakings table includes all the data necessary to compute staking-related metrics for Validators, Nominators, Pools, and Pool Members. This is currently supported for Polkadot and Kusama Relay Chains only. ## Column Descriptions diff --git a/data-catalog/substrate/traces.mdx b/data-catalog/substrate/traces.mdx index 1592aaf7..bdb342fb 100644 --- a/data-catalog/substrate/traces.mdx +++ b/data-catalog/substrate/traces.mdx @@ -6,7 +6,7 @@ description: Description of the polkadot.traces table on Dune. ## Table description -The traces table, also known as the "snapshot" table, stores relevant on-chain state data that are otherwise difficult to acquire from base Substrate tables such as extrinsics and events. The traces tables are populated with special scripts modeling key storage elements at the end of the hour or day. +The traces table, also known as the "snapshot" table, stores relevant on-chain state data that are otherwise difficult to acquire from base Substrate tables such as extrinsics and events. The traces tables are populated with special scripts modeling key storage elements at the end of the hour or day. Having these snapshots enables Dune wizards to build useful dashboards on Dune such as: diff --git a/data-catalog/substrate/transfers.mdx b/data-catalog/substrate/transfers.mdx index f4a50c65..983fd3ec 100644 --- a/data-catalog/substrate/transfers.mdx +++ b/data-catalog/substrate/transfers.mdx @@ -6,7 +6,7 @@ description: Description of the polkadot.transfers table on Dune. ## Table description -The Substrate transfers table stores the types of stored assets, the sender and recipient, and the estimated value of the tokens converted into USD, if available. +The Substrate transfers table stores the types of transferred assets, the sender and recipient, and the estimated value of the tokens converted into USD, if available. ## Column Descriptions diff --git a/data-catalog/ton/accounts.mdx b/data-catalog/ton/accounts.mdx index 631c8422..34ac6f4d 100644 --- a/data-catalog/ton/accounts.mdx +++ b/data-catalog/ton/accounts.mdx @@ -15,15 +15,15 @@ This table is created using [this SQL](https://github.com/duneanalytics/spellboo | **address** | varchar | Account raw address | | **status** | varchar | Status of account | | **last_tx_hash** | varchar | Hash of the latest transaction | -| **last_tx_at** | timestamp(3) with time zone | timetsmap of the latest transaction | +| **last_tx_at** | timestamp(3) with time zone | timestamp of the latest transaction | | **balance** | bigint | Raw ton balance | | **code_hash** | varchar | Account code hash (on-chain value) | | **deployment_tx_hash** | varchar | Hash of transaction when account was deployed | | **deployment_at** | timestamp(3) with time zone | Timestamp when account was deployed | | **deployment_by_external** | boolean | Equals true when deployment of transactions was first transaction in trace, in other words when `(deployment tx_hash = deployment trace_id)`, false otherwise | -| **initial_funding_tx_hash** | varchar | Transaction hash with the first occur of account in transactions | -| **initial_funding_at** | timestamp(3) with time zone | Timestamp of the first occur of account in transactions | -| **first_tx_sender** | varchar | Raw address of who intiated the first transaction with this account | +| **initial_funding_tx_hash** | varchar | Transaction hash with the first occurrence of account in transactions | +| **initial_funding_at** | timestamp(3) with time zone | Timestamp of the first occurrence of account in transactions | +| **first_tx_sender** | varchar | Raw address of who initiated the first transaction with this account | | **interfaces** | array(varchar) | The list of known available interfaces (for example `wallet_v4r2`, [full list available here](https://github.com/duneanalytics/spellbook/blob/main/dbt_subprojects/daily_spellbook/models/ton/ton_accounts.sql)) ## Table Sample diff --git a/data-catalog/ton/balances_history.mdx b/data-catalog/ton/balances_history.mdx index 2e206179..bc3bd59e 100644 --- a/data-catalog/ton/balances_history.mdx +++ b/data-catalog/ton/balances_history.mdx @@ -5,8 +5,8 @@ description: Description of the ton.balances_history table on Dune --- ## Table Description -Contains information about all balances changes for native TON and jettons. This table allows -to get point time balance for each address as well latest balances. +Contains information about all balance changes for native TON and jettons. This table allows +to get point-in-time balance for each address as well as latest balances. ## Column Descriptions | **Column** | **Type** | **Description** | diff --git a/data-catalog/ton/blocks.mdx b/data-catalog/ton/blocks.mdx index a638d4ef..cdd44452 100644 --- a/data-catalog/ton/blocks.mdx +++ b/data-catalog/ton/blocks.mdx @@ -31,7 +31,7 @@ Contains block-level data from the TON blockchain including block header informa | **key_block** | boolean | Flag indicating if this is a key block | | **vert_seqno_incr** | boolean | Vertical sequence number increment flag | | **flags** | int | Block flags | -| **gen_utime** | bigint | Generation unix time | +| **gen_utime** | bigint | Generation Unix time | | **start_lt** | bigint | Start logical time | | **end_lt** | bigint | End logical time | | **validator_list_hash_short** | int | Short hash of validator list | diff --git a/data-catalog/ton/dex_trades.mdx b/data-catalog/ton/dex_trades.mdx index ccc504ef..b7453e4e 100644 --- a/data-catalog/ton/dex_trades.mdx +++ b/data-catalog/ton/dex_trades.mdx @@ -11,7 +11,7 @@ Records of all trades executed on decentralized exchanges within the TON ecosyst | **Column** | **Type** | **Description** | |--------------------------|---------------|--------------------------------------------------------------| | **block_time** | timestamp | Timestamp of when the block containing the trade was created | -| **block_date** | date | Date of when the block containing the trade was created | +| **block_date** | date | Date when the block containing the trade was created | | **tx_hash** | string | Transaction hash of the trade | | **trace_id** | string | Trace identifier for trade tracking | | **project_type** | string | Type of DEX project | diff --git a/data-catalog/ton/jetton_events.mdx b/data-catalog/ton/jetton_events.mdx index 9b5edf01..ebdb8c5a 100644 --- a/data-catalog/ton/jetton_events.mdx +++ b/data-catalog/ton/jetton_events.mdx @@ -11,7 +11,7 @@ Tracks events related to Jettons (TON's equivalent of fungible tokens), includin | **Column** | **Type** | **Description** | |--------------------------|---------------|--------------------------------------------------------------| | **block_time** | timestamp | Timestamp of when the block containing the event was created | -| **block_date** | date | Date of when the block containing the event was created | +| **block_date** | date | Date when the block containing the event was created | | **type** | string | Type of the Jetton event | | **tx_hash** | string | Transaction hash of the event | | **tx_lt** | bigint | Logical time of the transaction | diff --git a/data-catalog/ton/messages.mdx b/data-catalog/ton/messages.mdx index 31fc5267..331e02fd 100644 --- a/data-catalog/ton/messages.mdx +++ b/data-catalog/ton/messages.mdx @@ -28,7 +28,7 @@ Stores message data that is exchanged between smart contracts and users on the T | **opcode** | int | Operation code of the message | | **ihr_disabled** | boolean | Whether IHR is disabled for this message | | **bounce** | boolean | Whether the message can bounce | -| **bounced** | boolean | Whether the message was bounced | +| **bounced** | boolean | Whether the message has bounced | | **import_fee** | bigint | Import fee for the message | | **body_hash** | string | Hash of the message body | | **body_boc** | binary | Binary data of the message body | diff --git a/data-catalog/ton/overview.mdx b/data-catalog/ton/overview.mdx index 0bdcd3bd..fbc9e8be 100644 --- a/data-catalog/ton/overview.mdx +++ b/data-catalog/ton/overview.mdx @@ -31,8 +31,8 @@ TON blockchain data is organized into several key tables that capture different Inter-contract messages and value transfers between accounts. - - TON and jettons balances history. + + TON and Jettons balances history. @@ -48,6 +48,6 @@ TON blockchain data is organized into several key tables that capture different - Metadata for Jettons including name, symbol, and decimals. + Metadata for Jettons including names, symbols, and decimals. diff --git a/data-catalog/ton/transactions.mdx b/data-catalog/ton/transactions.mdx index 1f6489d0..1fe54b4a 100644 --- a/data-catalog/ton/transactions.mdx +++ b/data-catalog/ton/transactions.mdx @@ -73,7 +73,7 @@ Records all transactions processed on the TON network, including transfers and s | action_action_list_hash | string | Hash of action list | | action_tot_msg_size_cells | bigint | Total message size in cells | | action_tot_msg_size_bits | bigint | Total message size in bits | -| bounce | string | Whether the transaction bounced | +| bounce | string | Bounce type of the transaction | | bounce_msg_size_cells | bigint | Bounce message size in cells | | bounce_msg_size_bits | bigint | Bounce message size in bits | | bounce_req_fwd_fees | bigint | Required forward fees for bounce | diff --git a/data-catalog/tron/decoded/event-logs.mdx b/data-catalog/tron/decoded/event-logs.mdx index f2947cf8..96a51dac 100644 --- a/data-catalog/tron/decoded/event-logs.mdx +++ b/data-catalog/tron/decoded/event-logs.mdx @@ -21,7 +21,7 @@ In Dune, we store all event logs of decoded smart contracts in separate tables. The structure published in these logs is predefined by the developer of the smart contract, the content is dynamically created during the transaction. -Logs are useful for monitoring, alerting and in general keeping track of what happens inside of a smart contract. Logs are your best friend as a data analyst since they reliably present you with data that is intended to be analyzed post factum. If you ever want to see which logs _can_ be emitted by a smart contract, you can simply search for the keyword `emit` in the source code of the smart contract. +Logs are useful for monitoring, alerting, and in general keeping track of what happens inside of a smart contract. Logs are your best friend as a data analyst since they reliably present you with data that is intended to be analyzed post factum. If you ever want to see which logs _can_ be emitted by a smart contract, you can simply search for the keyword `emit` in the source code of the smart contract. We will decode all event logs for smart contracts into tables named accordingly to this schema: diff --git a/data-catalog/tron/decoded/overview.mdx b/data-catalog/tron/decoded/overview.mdx index 6e769061..dd09a715 100644 --- a/data-catalog/tron/decoded/overview.mdx +++ b/data-catalog/tron/decoded/overview.mdx @@ -53,7 +53,7 @@ If you want to submit several contracts at the same time, there is also the poss ## How does decoding work? -Smart Contracts on the TVM blockchain are mostly written in high level languages like [Solidity](https://docs.soliditylang.org/en/v0.8.2) or [Vyper](https://vyper.readthedocs.io/en/stable). +Smart Contracts on the TVM blockchain are mostly written in high-level languages like [Solidity](https://docs.soliditylang.org/en/v0.8.2) or [Vyper](https://vyper.readthedocs.io/en/stable). For them to be able to be deployed to a TVM execution environment, they need to be compiled to TVM executable bytecode. Once deployed, the bytecode gets associated with an address on the respective chain and is permanently stored in this chain's state storage. diff --git a/data-catalog/tron/decoded/traces-decoded.mdx b/data-catalog/tron/decoded/traces-decoded.mdx index 58a25e02..11c27c8c 100644 --- a/data-catalog/tron/decoded/traces-decoded.mdx +++ b/data-catalog/tron/decoded/traces-decoded.mdx @@ -1,12 +1,12 @@ --- -title: ethereum.traces_decoded +title: tron.traces_decoded sidebarTitle: "Decoded Traces" -description: Description of the ethereum.traces_decoded table on Dune +description: Description of the tron.traces_decoded table on Dune --- ## Table Description -The `traces_decoded` table contains decoded traces from Ethereum transactions. The table matches `MethodID`, which consists of the first 4 bytes of any eth call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/evm/ethereum/decoded/traces-decoded). +The `traces_decoded` table contains decoded traces from Tron transactions. The table matches `MethodID`, which consists of the first 4 bytes of any Tron call to the trace signature and the corresponding Method name. The table does not contain the full trace data and is not suitable for analysis of smart contract level data. For that, use the specific event tables as described in [Call-tables](/data-catalog/tron/decoded/traces-decoded). This table is great for gaining a high level understanding of the types of events that are being emitted by a smart contract or smart contracts of a certain protocol. @@ -14,10 +14,10 @@ This table is great for gaining a high level understanding of the types of event import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; - + ## Table Sample import { TableSample } from "/snippets/table-sample.mdx"; - + diff --git a/data-catalog/tron/overview.mdx b/data-catalog/tron/overview.mdx index 1e825bcb..e9e23eaf 100644 --- a/data-catalog/tron/overview.mdx +++ b/data-catalog/tron/overview.mdx @@ -24,7 +24,7 @@ The datasets are similar to our EVM chains, but without internal transactions an Transaction details - + Human readable smart contract activity diff --git a/data-catalog/tron/raw/blocks.mdx b/data-catalog/tron/raw/blocks.mdx index ad17ebbc..9787c4b5 100644 --- a/data-catalog/tron/raw/blocks.mdx +++ b/data-catalog/tron/raw/blocks.mdx @@ -60,7 +60,7 @@ SELECT count(*) FROM tron.blocks -group by 1 +GROUP BY 1 LIMIT 10 ``` \ No newline at end of file diff --git a/data-catalog/tron/raw/logs.mdx b/data-catalog/tron/raw/logs.mdx index acb6cc1e..08cbcb4e 100644 --- a/data-catalog/tron/raw/logs.mdx +++ b/data-catalog/tron/raw/logs.mdx @@ -9,7 +9,7 @@ The `logs` table represents the logs generated by the Tron Virtual Machine (TVM) - topic list: a list of 0 to 4 32-byte data topics. `Topic0` is the hash of the signature of the event (indexed), and the remaining topics are indexed parameters of the event. - data: contains non-indexed data. -While working with raw logs is possible, we recommend to work with [decoded logs](../decoded/event-logs) for a more user-friendly experience. +While working with raw logs is possible, we recommend working with [decoded logs](../decoded/event-logs) for a more user-friendly experience. ## Column Descriptions diff --git a/data-catalog/tron/raw/transactions.mdx b/data-catalog/tron/raw/transactions.mdx index 9898a0a1..8c5a8bea 100644 --- a/data-catalog/tron/raw/transactions.mdx +++ b/data-catalog/tron/raw/transactions.mdx @@ -28,7 +28,7 @@ import { TableSample } from "/snippets/table-sample.mdx"; ```sql select * -from tron.transactions where "from" = 0x50A1b5c358F8D34F0d35aA2f10742c46054E247e +from tron.transactions where "from" = '0x50A1b5c358F8D34F0d35aA2f10742c46054E247e' ``` ### Count the number of transactions per block diff --git a/data-catalog/tron/tether.mdx b/data-catalog/tron/tether.mdx index 5a3e6fab..afe59e91 100644 --- a/data-catalog/tron/tether.mdx +++ b/data-catalog/tron/tether.mdx @@ -1,5 +1,5 @@ --- -title: USDT on tron +title: USDT on Tron sidebarTitle: "Tether" description: Decoded USDT data on the Tron network. --- @@ -26,7 +26,7 @@ These are the events that are logged by the USDT contract on the Tron network an - `tether_tron.tether_usd_evt_issue`: Contains records of issue events, where new USDT tokens are created and issued within the ecosystem. -- `tether_tron.tether_usd_evt_ownershipttransferred`: Logs the transfer of contract ownership events, which indicates a change in who can execute administrative functions on the contract. +- `tether_tron.tether_usd_evt_ownershiptransferred`: Logs the transfer of contract ownership events, which indicates a change in who can execute administrative functions on the contract. - `tether_tron.tether_usd_evt_params`: Stores data related to changes in the contract's operational parameters, which could include things like fees, transaction limits, or other configuration settings. @@ -43,7 +43,7 @@ You can query all of these tables in the `tether_tron` schema in the Dune databa ## Example queries -### Daily transfer count of USDT on Tron. +### Daily transfer count of USDT on Tron ```sql SELECT @@ -58,7 +58,7 @@ group by 1
-### Daily transfer volume of USDT on Tron. +### Daily transfer volume of USDT on Tron ```sql SELECT diff --git a/data-catalog/tron/tokens/overview.mdx b/data-catalog/tron/tokens/overview.mdx index 83078e68..de34edbd 100644 --- a/data-catalog/tron/tokens/overview.mdx +++ b/data-catalog/tron/tokens/overview.mdx @@ -15,7 +15,7 @@ ERC20 tokens are fungible, meaning that each token is identical to every other t On Tron, these standards are called **TRC20**, **TRC721**, and **TRC1155**, respectively. -Additionally, there is also the native asset of the TVM, `TRX`, which is used to pay for transaction fees. TRX is not an ERC20 token, but it is still a digital asset that can be transferred and owned by users. +Additionally, there is also the native asset of the TVM, `TRX`, which is used to pay for transaction fees. TRX is not a TRC20 token, but it is still a digital asset that can be transferred and owned by users. ## Data Catalog @@ -23,13 +23,13 @@ The following datasets are available for exploring the landscape of digital asse + title="TRC20" icon="layer-group" href="/data-catalog/tron/tokens/transfers/trc20-transfers"> All TRC20 token transfers that have occurred on the network. - + All TRC721 token transfers that have occurred on the network. - + All TRC1155 token transfers that have occurred on the network. diff --git a/data-catalog/tron/tokens/transfers/erc1155-transfers.mdx b/data-catalog/tron/tokens/transfers/erc1155-transfers.mdx index 3568526b..c4ccb005 100644 --- a/data-catalog/tron/tokens/transfers/erc1155-transfers.mdx +++ b/data-catalog/tron/tokens/transfers/erc1155-transfers.mdx @@ -7,7 +7,7 @@ description: Event logs for TRC1155 token transfers on the Tron blockchain. ## Table description This table captures all `Transfer` event logs for TRC1155 token transfers on the Tron blockchain. -This log is emitted when a `transfer` or `TransferFrom` function is called successfully on a TRC1155 token contract. +This log is emitted when a `transfer` or `transferFrom` function is called successfully on a TRC1155 token contract. ## Column Descriptions diff --git a/data-catalog/tron/tokens/transfers/erc20-transfers.mdx b/data-catalog/tron/tokens/transfers/erc20-transfers.mdx index baad9856..f5e87a38 100644 --- a/data-catalog/tron/tokens/transfers/erc20-transfers.mdx +++ b/data-catalog/tron/tokens/transfers/erc20-transfers.mdx @@ -7,7 +7,7 @@ description: Event logs for TRC20 token transfers on the Tron blockchain. ## Table description This table captures all `Transfer` event logs for TRC20 token transfers on the Tron blockchain. -This log is usually emitted when a `transfer` or `TransferFrom` function is called successfully on a TRC20 token contract. +This log is usually emitted when a `transfer` or `transferFrom` function is called successfully on a TRC20 token contract. ## Column Descriptions diff --git a/data-catalog/tron/tokens/transfers/erc721-transfers.mdx b/data-catalog/tron/tokens/transfers/erc721-transfers.mdx index 8f436777..a114d86d 100644 --- a/data-catalog/tron/tokens/transfers/erc721-transfers.mdx +++ b/data-catalog/tron/tokens/transfers/erc721-transfers.mdx @@ -1,13 +1,13 @@ --- title: TRC721 Transfers sidebarTitle: "TRC721 Transfers" -description: Event logs for TRC721 token transfers on the tron blockchain. +description: Event logs for TRC721 token transfers on the Tron blockchain. --- ## Table description This table captures all `Transfer` event logs for TRC721 token transfers on the Tron blockchain. -This log is usually emitted when a `transfer` or `TransferFrom` function is called successfully on a TRC721 token contract. +This log is usually emitted when a `transfer` or `transferFrom` function is called successfully on a TRC721 token contract. ## Column Descriptions diff --git a/data-catalog/xrpl/transactions.mdx b/data-catalog/xrpl/transactions.mdx index 099483a4..bee4268d 100644 --- a/data-catalog/xrpl/transactions.mdx +++ b/data-catalog/xrpl/transactions.mdx @@ -62,7 +62,7 @@ Contains all transaction data from the XRP Ledger including payment types, accou | **owner** | string | Owner of the account or asset | | **paths** | string | Payment paths for cross-currency payments | | **previous_txn_id** | string | Previous transaction identifier | -| **price_data_series** | array(struct(PriceData: struct(AssetPrice: string, BaseAsset: String, QuoteAsset: string, Scale: long))) | Price data series | +| **price_data_series** | array(struct(PriceData: struct(AssetPrice: string, BaseAsset: string, QuoteAsset: string, Scale: long))) | Price data series | | **provider** | string | Provider information | | **public_key** | string | Public key of the account | | **quality_in** | long | Quality in for exchange transactions | @@ -73,7 +73,7 @@ Contains all transaction data from the XRP Ledger including payment types, accou | **set_flag** | long | Flag to be set on the account | | **settle_delay** | long | Settlement delay | | **signature** | string | Transaction signature | -| **signer_entries** | array(struct(SignerEntry: struct(Account: String, SignerWeight: long))) | Signer entries for multi-signing | +| **signer_entries** | array(struct(SignerEntry: struct(Account: string, SignerWeight: long))) | Signer entries for multi-signing | | **signer_quorum** | long | Signer quorum | | **signers** | array(struct(Signer: struct(Account: string, SigningPubKey: string, TxnSignature: string))) | Transaction signers | | **signing_pub_key** | string | Signing public key | diff --git a/datashare/datashare-faqs.mdx b/datashare/datashare-faqs.mdx index 66875e4f..fd2bb5ca 100644 --- a/datashare/datashare-faqs.mdx +++ b/datashare/datashare-faqs.mdx @@ -4,7 +4,7 @@ sidebarTitle: FAQs description: Frequently Asked Questions about Dune Datashare --- - + **Snowflake**: Uses Snowflake's native data sharing - data stays in our account but appears as tables in yours. Zero storage costs, only compute charges. **BigQuery**: We replicate data to shared datasets in your GCP project. Data is copied to your region for performance. @@ -79,9 +79,4 @@ description: Frequently Asked Questions about Dune Datashare - **Discord**: [#datashare channel](https://discord.gg/2VCqwzzF7u) - **Enterprise**: [dune.com/enterprise](https://dune.com/enterprise) - - - - - - + \ No newline at end of file diff --git a/datashare/datashare-snowflake.mdx b/datashare/datashare-snowflake.mdx index e3bb6886..14ba4990 100644 --- a/datashare/datashare-snowflake.mdx +++ b/datashare/datashare-snowflake.mdx @@ -64,6 +64,6 @@ Use VARBINARY for exact matching (e.g., token IDs), DOUBLE for calculations. ## Details -- **Freshness**: hourly or daily depending on requirements +- **Freshness**: Hourly or daily depending on requirements - **Regions**: Available worldwide, contact us for specific region availability - **Support**: support@dune.com | [Discord](https://discord.gg/2VCqwzzF7u) \ No newline at end of file diff --git a/datashare/datashare-trial.mdx b/datashare/datashare-trial.mdx index f3802be2..3bf75057 100644 --- a/datashare/datashare-trial.mdx +++ b/datashare/datashare-trial.mdx @@ -44,7 +44,7 @@ Email datashares-sales@dune.com or use our [Enterprise form](https://dune.com/en **Include:** - GCP Project ID -- Preferred region (US Central 1 or EU West 2) +- Preferred region (US Central 1 or EU West 2) - Chains of interest We'll set up trial access in your BigQuery project with technical support. diff --git a/datashare/datashare.mdx b/datashare/datashare.mdx index 038b52d7..eeec6660 100644 --- a/datashare/datashare.mdx +++ b/datashare/datashare.mdx @@ -47,7 +47,7 @@ This is the same curated, decoded blockchain data that powers dune.com - optimiz ### What We Need From You -To set up datashare access, we need specific identifiers from your cloud environment: +To set up Datashare access, we need specific identifiers from your cloud environment: diff --git a/home.mdx b/home.mdx index 03718a07..1aeff399 100644 --- a/home.mdx +++ b/home.mdx @@ -66,7 +66,7 @@ You can also level up by following the [crypto data analyst roadmap](https://roa ### Why Dune? -Dune—along with our massive community of users and experts—provides powerful tools and analysis of all onchain data. You can find a [dashboard](https://dune.com/browse/dashboards?q=dex\&order=favorites\&time_range=all) for pretty much anything web3-related, including for EVMs like Ethereum, Polygon, Goerli, and Optimism—and non-EVM chains like Solana and Bitcoin. +Dune—along with our massive community of users and experts—provides powerful tools and analysis of all on-chain data. You can find a [dashboard](https://dune.com/browse/dashboards?q=dex\&order=favorites\&time_range=all) for pretty much anything web3-related, including for EVMs like Ethereum, Polygon, Goerli, and Optimism—and non-EVM chains like Solana and Bitcoin. Examples of real dashboards: diff --git a/learning-resources.mdx b/learning-resources.mdx index d58b0f1d..d9982851 100644 --- a/learning-resources.mdx +++ b/learning-resources.mdx @@ -24,7 +24,7 @@ To build your reputation as an expert wizard, you must stay centered on what you * To understand wallet/user segments, you'll need to leverage [labels](https://github.com/duneanalytics/spellbook/tree/main/models/labels/addresses) to enhance your analysis. -Once you have metrics and also understand the underlying tokens and users, it will start to become clear what that real narrative is. Try and pull together a few insights, and then create a compelling dashboard and story around them. Don't try too hard to capture everything at once - it will become overwhelming for both you and those you share it with. +Once you have metrics and also understand the underlying tokens and users, it will start to become clear what the real narrative is. Try and pull together a few insights, and then create a compelling dashboard and story around them. Don't try too hard to capture everything at once - it will become overwhelming for both you and those you share it with. ## Analysis Tips @@ -33,7 +33,7 @@ Once you have metrics and also understand the underlying tokens and users, it wi * Scope Your Work: When looking into a protocol, you'll need to understand the contract architecture and context. That starts with functions, events, and wallet overviews. There is a [quickstart dashboard](https://dune.com/ilemi/contract-quickstart) built just for this, you can see a walkthrough analyzing Opensea [here](https://read.cryptodatabytes.com/p/how-to-start-analyzing-any-web3-protocol). -Remember that no protocol lives in isolation - there is always some mix of onchain events happening. That could be some new airdrop, a new upstream/downstream protocol integration, large whales making moves, governance changes in protocol parameters, and more. Once you have a solid understanding of protocol history in usage, user, and integration trends, you're ready to start building some metrics. +Remember that no protocol lives in isolation - there is always some mix of on-chain events happening. That could be some new airdrop, a new upstream/downstream protocol integration, large whales making moves, governance changes in protocol parameters, and more. Once you have a solid understanding of protocol history in usage, user, and integration trends, you're ready to start building some metrics. ## Engage with the Community diff --git a/learning/flipside-migration-guide.mdx b/learning/flipside-migration-guide.mdx index 4cbd2bfb..a850d193 100644 --- a/learning/flipside-migration-guide.mdx +++ b/learning/flipside-migration-guide.mdx @@ -48,7 +48,7 @@ Below is a comprehensive mapping of Flipside's tables to their Dune equivalents. | `DIM_LABELS` | `labels.addresses`; `labels.owner_addresses`; `labels.owner_details` | Contains address labels. **Note the structural difference:** Flipside used a single table, whereas Dune employs a more granular, multi-table structure that separates labels for addresses from labels for entities/owners. You may need to `JOIN` these tables. | | `EZ_BALANCE_DELTAS` | `balances_ethereum.erc20_day`; `ethereum.traces` | Provides token and native asset balance changes. On Dune, you can calculate balance deltas from daily balance tables or derive them from transfer tables like `erc20_ethereum.evt_Transfer` and `ethereum.traces` (`value > 0`). | | `EZ_CURRENT_BALANCES` | `balances_ethereum.erc20_latest` | Provides current wallet balances. Dune's `balances_ethereum.erc20_latest` table provides the most recent balance for tokens, similar to Flipside's convenience table. | -| `EZ_NATIVE_TRANSFERS` | `tokens.transfers` | This is a direct mapping to the `tokens.transfers` table. | +| `EZ_NATIVE_TRANSFERS` | `tokens.transfers` | This is a direct mapping to the `tokens.transfers` table. | | `EZ_SNAPSHOT` | `dune.shot.dataset_follows`
`dune.shot.dataset_proposals_view`
`dune.shot.dataset_spaces_view`
`dune.shot.dataset_users`
`dune.shot.dataset_votes_view` | Contains off-chain Snapshot voting data. **Note the structural difference:** Flipside aggregated this into a single table. Dune ingests Snapshot's data into multiple, more granular tables that you will need to `JOIN` using proposal or space IDs. | | `EZ_TOKEN_TRANSFERS` | `erc20_ethereum.evt_Transfer` | Contains ERC-20 token transfer events. Dune's decoded event tables provide the raw transfer data. For aggregated, cleaned data across all chains, use the curated `tokens.transfers` table. | | `FACT_BLOCKS` | `ethereum.blocks` | Provides execution-layer block data. For raw block data, `ethereum.blocks` is a direct match. For aggregated metrics like daily gas fees, Dune offers pre-computed tables in the `dune` schema. | @@ -75,7 +75,7 @@ Below is a comprehensive mapping of Flipside's tables to their Dune equivalents. | `FACT_DAO_VOTES` | `dao.votes` | Contains DAO voting records. Dune's `dao.votes` Spell aims to standardize voting data across different DAO frameworks. | | `FACT_REGISTRATIONS` | `ens.view_registrations` | Contains ENS registration records. This is a direct mapping. | | `FACT_RENEWALS` | `ens.view_renewals` | Contains ENS domain renewal records. This is a direct mapping. | -| `FACT_TRANSFERS` | `tokens.transfers` | Contains token transfer events. Dune's `tokens.transfers` is a curated Spell that provides a standardized format for all token transfers. | +| `FACT_TRANSFERS` | `tokens.transfers` | Contains token transfer events. Dune's `tokens.transfers` is a curated Spell that provides a standardized format for all token transfers. | | `EZ_GOVERNANCE_VOTES` | `governance.votes` | Contains records of governance votes. Dune's `governance.votes` spell covers multiple protocols, including Maker. | | `FACT_CAT_BITE` | `maker_ethereum.cat_evt_bite` | Contains MakerDAO liquidation events. This is a direct mapping to the raw event table in Dune. | | `DIM_NFT_COLLECTION_METADATA` | `nft.collections` | Contains metadata for NFT collections. Dune's `nft.collections` Spell provides curated metadata for a vast number of NFT collections. | @@ -83,7 +83,7 @@ Below is a comprehensive mapping of Flipside's tables to their Dune equivalents. | `EZ_NFT_SALES` | `nft.trades` | Contains NFT sale events. **This is another major improvement on Dune.** The `nft.trades` Spell is a powerful abstraction that aggregates sales across dozens of marketplaces into a single, clean table. | | `EZ_NFT_TRANSFERS` | `nft.transfers` | Contains NFT transfer events. Dune's `nft.transfers` curated table is the standard place to find all ERC721 and ERC1155 transfers. | | `EZ_ASSET_METADATA` | `tokens.erc20`, `tokens.nft` | Contains asset metadata. Dune separates metadata for fungible (`tokens.erc20`) and non-fungible (`tokens.nft`) tokens into dedicated, curated tables. | -| `EZ_PRICES_HOURLY` | `prices.hour` | Provides hourly token prices. This is a direct mapping to Dune's hourly prices table. Dune also offers `prices.usd_daily` and `prices.usd_latest`. | +| `EZ_PRICES_HOURLY` | `prices.hour` | Provides hourly token prices. This is a direct mapping to Dune's hourly prices table. Dune also offers `prices.usd_daily` and `prices.usd_latest`. | | `EZ_SWAPS` | `dex.trades` | Contains DEX swap events. This maps to Dune's comprehensive `dex.trades` Spell, which covers a much wider array of DEXs. | | `DIM_DATES` | `utils.days`, `utils.hours`, `utils.minutes` | Provides a table of dates for time-series analysis. Dune offers several utility tables for different time granularities to simplify `JOIN` operations. | | `FACT_TRACES` | `ethereum.traces` | Contains raw trace data for internal contract calls. This is a direct one-to-one mapping. | @@ -276,7 +276,7 @@ We encourage you to explore the [data catalog](/data-catalog) in the Dune app to ### Challenge 1: Missing Convenience Tables -**Issue:** Flipside provided many "EZ\_" convenience tables that aggregated complex data. +**Issue:** Flipside provided many "EZ_" convenience tables that aggregated complex data. **Solution:** Dune's curated Spells (like `dex.trades`, `nft.trades`) often provide even better aggregations. If a specific convenience table doesn't exist, you can often recreate it using raw or decoded data. ### Challenge 2: Different Table Schemas @@ -298,6 +298,6 @@ We know migrating can be tough, but you're not alone. Here are some resources to - **Find a Query:** Fork one of the 600,000\+ public queries on Dune to get a head start. - **Data Catalog:** Explore our comprehensive [data catalog](/data-catalog) to understand available datasets. - **Query Examples:** Check out our [quickstart guide](/quickstart) for hands-on examples. -- **Onboarding: **Fill out this [onboarding form](https://forms.gle/G3x9mWmW3AYauu6FA) and we’ll schedule a live session to help you. +- **Onboarding:** Fill out this [onboarding form](https://forms.gle/G3x9mWmW3AYauu6FA) and we'll schedule a live session to help you. Welcome to Dune\! We can't wait to see what you build. \ No newline at end of file diff --git a/learning/how-tos/create-and-manage-teams.mdx b/learning/how-tos/create-and-manage-teams.mdx index 64d24f02..638bb1b6 100644 --- a/learning/how-tos/create-and-manage-teams.mdx +++ b/learning/how-tos/create-and-manage-teams.mdx @@ -39,7 +39,7 @@ description: A step-by-step guide to creating and managing team accounts on Dune height: "100%", colorScheme: "light" }} - title="Create " + title="Create team" /> diff --git a/learning/how-tos/create-new-content.mdx b/learning/how-tos/create-new-content.mdx index 6ea859be..c9344d5f 100644 --- a/learning/how-tos/create-new-content.mdx +++ b/learning/how-tos/create-new-content.mdx @@ -103,7 +103,7 @@ If you're keen on analyzing a contract or project that hasn't been decoded yet o ## Create Visualization Widgets -You can create visualization widgets from any existing query results, but clicking the “New visualization” button and choosing the type of charts you want. Of course you can customize the charts to your liking. +You can create visualization widgets from any existing query results by clicking the "New visualization" button and choosing the type of charts you want. Of course you can customize the charts to your liking.
= NOW() - INTERVAL '30 days'`: Focuses on recent activity -- `GROUP BY 1, 2, 3`: Combines trades by day, blockchain, and DEX -- `ORDER BY 1 DESC, 5 DESC`: Shows newest and highest volume trades first +- `WHERE block_date >= NOW() - INTERVAL '30' day`: Focuses on recent activity +- `GROUP BY 1, 2`: Combines trades by day and blockchain +- `ORDER BY 1 DESC, 4 DESC`: Shows newest and highest volume trades first ## Making Your Analysis Dynamic with Parameters @@ -97,7 +97,7 @@ After running your query, you can create powerful visualizations: 1. Click "New Visualization" 2. Choose "Bar Chart" -3. Set X-axis to `trading_day` +3. Set X-axis to `block_date` 4. Set Y-axis to `trading_volume_usd` 5. Group by `blockchain` diff --git a/learning/how-tos/create-your-first-visualization.mdx b/learning/how-tos/create-your-first-visualization.mdx index e9ed97da..1a378a3a 100644 --- a/learning/how-tos/create-your-first-visualization.mdx +++ b/learning/how-tos/create-your-first-visualization.mdx @@ -69,7 +69,7 @@ Here is a visual click-through version if you are more of a visual learner. Belo You can also use the AI Chart Builder to automatically generate the charts for your data. 1. **Click Generate** When you click generate, the AI Chart Builder will suggest a title and chart type based on your data. -2. If you are happy with the recommendation, click **Create Generate** to add the chart to your dashboard. -3. Otherwise, you can edit the title or the chart type and then **Create Generate** to create the chart. +2. If you are happy with the recommendation, click **Create Chart** to add the chart to your dashboard. +3. Otherwise, you can edit the title or the chart type and then **Create Chart** to create the chart. 4. (Optional) **Fine-tune Your Chart**: Customize the display values for a polished look. For detailed formatting guidance, [refer to this resource](web-app/visualizations/charts-graphs). diff --git a/learning/how-tos/credit-system-on-dune.mdx b/learning/how-tos/credit-system-on-dune.mdx index ed1e078f..4298ab9e 100644 --- a/learning/how-tos/credit-system-on-dune.mdx +++ b/learning/how-tos/credit-system-on-dune.mdx @@ -17,7 +17,7 @@ No worries, every Dune user gets a monthly credit allowance. Here's how it works ### 🎟️ Monthly Credit Allowance - **Set Number of Credits:** Each month, your subscription plan provides a set allotment of credits. -- **Top-Up:** Run out of credits? Our "pay as you go" option lets you add more anytime, ensuring your work is always in flow. +- **Top-Up:** Run out of credits? Our "pay as you go" option lets you add more anytime, ensuring your work always flows. ### 🔄 Rollover Policy - **Monthly Refresh:** Credits reset at the start of each billing cycle; they do not roll over to the next month. @@ -50,7 +50,7 @@ Credits power your work on Dune, and here's how they're typically used: ### Estimating Credit Usage Understanding how your activities on Dune consume credits can help you manage your resources more effectively: - **Credit Estimates:** Always check for tooltips or on-screen indicators that provide real-time estimates of credit costs before you perform actions. -- **Active Monitoring:** Keep a regular tab on your credit usage through your settings dashboard to avoid surprises. +- **Active Monitoring:** Keep regular tabs on your credit usage through your settings dashboard to avoid surprises. ## Managing Your Credits diff --git a/learning/how-tos/dune-ai-prompt-engineering.mdx b/learning/how-tos/dune-ai-prompt-engineering.mdx index 20d43295..d11aa0d9 100644 --- a/learning/how-tos/dune-ai-prompt-engineering.mdx +++ b/learning/how-tos/dune-ai-prompt-engineering.mdx @@ -19,7 +19,7 @@ Before we dive into the examples, it's important to understand the basics of pro Dune AI offers a range of capabilities, especially suited for blockchain analytics. Key features include: -- **Parsing smart contracts addresses** and identifying the relevant functions and their tables. +- **Parsing smart contract addresses** and identifying the relevant functions and their tables. - **Identifying and categorizing project names** and mapping them to their respective contract tables and spells (expertly curated datasets) - **Identifying token symbols** and identifying their contract addresses and contract types. - **Injecting your wallet address** (when linked in profile) to provide personalized insights and analytics. diff --git a/learning/how-tos/dune-frames.mdx b/learning/how-tos/dune-frames.mdx index b5da17b5..2702c87f 100644 --- a/learning/how-tos/dune-frames.mdx +++ b/learning/how-tos/dune-frames.mdx @@ -23,7 +23,7 @@ Next, you'll need to get a Dune API key from [your user settings](https://dune.c We call the Dune API in the `/api/dune.ts` file in the `getRecommendations(fid)` function [defined here](https://github.com/andrewhong5297/dune-frames/blob/main/api/dune.ts#L10). -Below is the main API call, which makes a [FILTER](/api-reference/executions/filtering) call on an [existing result set](/api-reference/executions/endpoint/get-query-result). Using filters, we get our results in 20-30ms instead of reruning the whole query (which may take 10-20 seconds). +Below is the main API call, which makes a [FILTER](/api-reference/executions/filtering) call on an [existing result set](/api-reference/executions/endpoint/get-query-result). Using filters, we get our results in 20-30ms instead of rerunning the whole query (which may take 10-20 seconds). ```javascript //schedule the query on a 6-hour interval, and then fetch by filtering for the user fid within the query results diff --git a/learning/how-tos/export-data-out.mdx b/learning/how-tos/export-data-out.mdx index e4b18011..26dfd355 100644 --- a/learning/how-tos/export-data-out.mdx +++ b/learning/how-tos/export-data-out.mdx @@ -120,7 +120,7 @@ import pandas as pd def get_latest_query_result(query_id): res_df = pd.DataFrame() try: - result_url = f"https://api.dune.com/api-referencev1/query/{query_id}/results" + result_url = f"https://api.dune.com/api/v1/query/{query_id}/results" result_response = requests.get(result_url, headers=headers) print(json.loads(result_response.text)) query_res = json.loads(result_response.text)["result"]["rows"] diff --git a/learning/how-tos/find-datasets.mdx b/learning/how-tos/find-datasets.mdx index 28cce9dd..c3942db0 100644 --- a/learning/how-tos/find-datasets.mdx +++ b/learning/how-tos/find-datasets.mdx @@ -11,12 +11,12 @@ Dune processes blockchain data in several stages: ingestion, decoding, aggregati Beyond these, Dune showcases the most frequently used datasets under the “essential” category. Your materialized query results are neatly categorized under “materialized views”. -![data categories](images/data categories.png) +![data categories](images/data-categories.png) ## Available Chains on Dune Dune supports 30 EVM chains and many non-EVM chains like Solana, Bitcoin, NEAR and others. For a complete list of [supported chains](/data-catalog/), visit the [data explorer and view the full selection](https://dune.com/queries?category=canonical) under "Raw blockchain data". -![all chains on dune](learning/how-tos/images/raw_blockchain_data.png) +![all chains on dune](images/raw_blockchain_data.png) ## Search via the Data Explorer The data explorer is an invaluable tool for pinpointing specific datasets among the vast collection. For instance, to locate datasets for Uniswap v2 within the “Decoded” and “Spells” categories, follow the steps illustrated here: @@ -28,7 +28,7 @@ Once you've identified the desired table, use the double-arrow symbol to instant Ensure you're at the correct search level. At times, a nested search space might yield unexpected results. We're refining this user experience. For now, the URL can help you verify your current position. - ![search path url](learning/how-tos/images/search-path-data-explorer.png) + ![search path url](images/search-path-data-explorer.png) diff --git a/learning/how-tos/navigate-query-editor.mdx b/learning/how-tos/navigate-query-editor.mdx index b147cce0..deb733d4 100644 --- a/learning/how-tos/navigate-query-editor.mdx +++ b/learning/how-tos/navigate-query-editor.mdx @@ -1,6 +1,6 @@ --- title: Navigate the Query Editor -description: How to navgigate the query editor +description: How to navigate the query editor --- In this guide, we'll provide an overview of the Dune Query Editor and its features. @@ -10,7 +10,7 @@ In this guide, we'll provide an overview of the Dune Query Editor and its featur - Query Explorer: Search and locate relevant content for your query. - Data Explorer: Discover the necessary data tables for your projects. - [Version History](/web-app/query-editor/version-history): Review the query's edit history and, if required, revert to a previous version. -- Settings: Adjust setting for your query. +- Settings: Adjust settings for your query.
## Invite to Your Team -For consistent collaboration, [invite colleagues to your team](learning/how-tos/create-and-manage-teams#inviting-members-assigning-roles) as viewers or editors. \ No newline at end of file +For consistent collaboration, [invite colleagues to your team](/learning/how-tos/create-and-manage-teams#inviting-members-assigning-roles) as viewers or editors. \ No newline at end of file diff --git a/query-engine/Functions-and-operators/aggregate.mdx b/query-engine/Functions-and-operators/aggregate.mdx index 14962d34..bfdf70e8 100644 --- a/query-engine/Functions-and-operators/aggregate.mdx +++ b/query-engine/Functions-and-operators/aggregate.mdx @@ -360,7 +360,7 @@ string type. The function uses the stream summary data structure proposed in the paper [Efficient Computation of Frequent and Top-k Elements in Data Streams](https://www.cse.ust.hk/~raywong/comp5331/References/EfficientComputationOfFrequentAndTop-kElementsInDataStreams.pdf) -by A. Metwalley, D. Agrawl and A. Abbadi. +by A. Metwally, D. Agrawal and A. Abbadi. #### approx_percentile() **``approx_percentile(x, percentage)``** → [same as x] @@ -373,11 +373,11 @@ Returns the approximate percentile for all input values of `x` at each of the sp **``approx_percentile(x, w, percentage)``** → [same as x] -Returns the approximate weighed percentile for all input values of `x` using the per-item weight `w` at the percentage `percentage`. Weights must be greater or equal to 1. Integer-value weights can be thought of as a replication count for the value `x` in the percentile set. The value of `percentage` must be between zero and one and must be constant for all input rows. +Returns the approximate weighted percentile for all input values of `x` using the per-item weight `w` at the percentage `percentage`. Weights must be greater or equal to 1. Integer-value weights can be thought of as a replication count for the value `x` in the percentile set. The value of `percentage` must be between zero and one and must be constant for all input rows. **``approx_percentile(x, w, percentages)``** → array\<[same as x]> -Returns the approximate weighed percentile for all input values of `x` using the per-item weight `w` at each of the given percentages specified in the array. Weights must be greater or equal to 1. Integer-value weights can be thought of as a replication count for the value `x` in the percentile set. Each element of the `percentages` array must be between zero and one, and the array must be constant for all input rows. +Returns the approximate weighted percentile for all input values of `x` using the per-item weight `w` at each of the given percentages specified in the array. Weights must be greater or equal to 1. Integer-value weights can be thought of as a replication count for the value `x` in the percentile set. Each element of the `percentages` array must be between zero and one, and the array must be constant for all input rows. #### approx_set() **``approx_set(x)``** → HyperLogLog diff --git a/query-engine/Functions-and-operators/array.mdx b/query-engine/Functions-and-operators/array.mdx index 4feb6d51..d4390fc4 100644 --- a/query-engine/Functions-and-operators/array.mdx +++ b/query-engine/Functions-and-operators/array.mdx @@ -7,7 +7,7 @@ title: Array functions and operators The `[]` operator is used to access an element of an array and is indexed starting from one: ```sql - SELECT my_array[1] AS f_element + SELECT my_array[1] AS first_element ``` Concatenation operator: \|\| \{concatenation_operator} @@ -89,7 +89,7 @@ Returns the minimum value of input array. #### array_position() **``array_position(x, element)``** → bigint -Returns the position of the f occurrence of the element in the array. Returns `NULL` if the element is not found. The position is counted from 1. +Returns the position of the first occurrence of the element in the array. Returns `NULL` if the element is not found. The position is counted from 1. #### array_remove() **``array_remove(x, element)``** → array @@ -105,7 +105,7 @@ Sorts and returns the array `x`. The elements of `x` must be orderable. Null ele **``array_sort(array(T), function(T,T,int))``** → array(T) -Sorts and returns the `array` based on the given comparator `function`. The comparator will take two nullable arguments representing two nullable elements of the `array`. It returns -1, 0, or 1 as the f nullable element is less than, equal to, or greater than the second nullable element. If the comparator function returns other values (including `NULL`), the query will fail and raise an error. +Sorts and returns the `array` based on the given comparator `function`. The comparator will take two nullable arguments representing two nullable elements of the `array`. It returns -1, 0, or 1 as the first nullable element is less than, equal to, or greater than the second nullable element. If the comparator function returns other values (including `NULL`), the query will fail and raise an error. ```sql SELECT array_sort(ARRAY[3, 2, 5, 1, 2], (x, y) -> IF(x < y, 1, IF(x = y, 0, -1))); @@ -181,7 +181,7 @@ SELECT combinations(ARRAY[1, 2, 3], 2); SELECT combinations(ARRAY[1, 2, 2], 2); -- [[1, 2], [1, 2], [2, 2]] ``` -Order of sub-groups is deterministic but unspecified. Order of elements within a sub-group deterministic but unspecified. n must be not be greater than 5, and the total size of sub-groups generated must be smaller than 100,000. +Order of sub-groups is deterministic but unspecified. Order of elements within a sub-group is deterministic but unspecified. n must not be greater than 5, and the total size of sub-groups generated must be smaller than 100,000. #### contains() **``contains(x, element)``** → boolean diff --git a/query-engine/Functions-and-operators/base58.mdx b/query-engine/Functions-and-operators/base58.mdx index 0c07d25c..d34f0d98 100644 --- a/query-engine/Functions-and-operators/base58.mdx +++ b/query-engine/Functions-and-operators/base58.mdx @@ -14,7 +14,7 @@ SELECT Now that we are able to convert Base58-encoded strings to `VARBINARY` values, we can use the `bytearray_to_bigint` function to convert the `VARBINARY` value to a `BIGINT` value. However, we need to consider more things: -1. The decoded `VARBINARY` value does not only contain the data we want to convert to a `BIGINT` value. It also contains a discriminator that indicates which function of a solana program was called. We need to remove this discriminator before we can convert the `VARBINARY` value to a `BIGINT` value. We do this by using the `bytearray_substring` function. +1. The decoded `VARBINARY` value does not only contain the data we want to convert to a `BIGINT` value. It also contains a discriminator that indicates which function of a Solana program was called. We need to remove this discriminator before we can convert the `VARBINARY` value to a `BIGINT` value. We do this by using the `bytearray_substring` function. 2. Solana uses little-endian byte order, so we need to reverse the byte order before we can convert the `VARBINARY` value to a `BIGINT` value. We do this by using the `bytearray_reverse` function. @@ -41,7 +41,7 @@ and call_block_slot = 187701147 [→ Query in Dune](https://dune.com/queries/2846422) - This specific query decodes the token amount that was sold in a Solana swap transaction. While probably applicable for lots of other solana programs, it is not guaranteed to work for all solana programs. You might need to adjust the query to your specific use case, depending on the solana program you are querying. + This specific query decodes the token amount that was sold in a Solana swap transaction. While probably applicable for lots of other Solana programs, it is not guaranteed to work for all Solana programs. You might need to adjust the query to your specific use case, depending on the Solana program you are querying. @@ -67,5 +67,5 @@ Converts a `VARBINARY` value to a Base58-encoded string. ```sql SELECT to_base58(0x030094357700000000) --- results in base58 encoded varchar 3DZBMRwnSU8f +-- results in Base58 encoded varchar 3DZBMRwnSU8f ``` \ No newline at end of file diff --git a/query-engine/Functions-and-operators/binary.mdx b/query-engine/Functions-and-operators/binary.mdx index 02bd549c..9c1f95be 100644 --- a/query-engine/Functions-and-operators/binary.mdx +++ b/query-engine/Functions-and-operators/binary.mdx @@ -22,12 +22,12 @@ Returns the length of binary in bytes. #### lpad() **``lpad(binary, size, padbinary)``** → varbinary -Left pads binary to size bytes with padbinary. If size is less than the length of binary, the result is truncated to size characters. size must not be negative and padbinary must be non-empty. +Left pads binary to size bytes with padbinary. If size is less than the length of binary, the result is truncated to size bytes. size must not be negative and padbinary must be non-empty. #### rpad() **``rpad(binary, size, padbinary)``** → varbinary -Right pads binary to size bytes with padbinary. If size is less than the length of binary, the result is truncated to size characters. size must not be negative and padbinary must be non-empty. +Right pads binary to size bytes with padbinary. If size is less than the length of binary, the result is truncated to size bytes. size must not be negative and padbinary must be non-empty. #### substr() **``substr(binary, start)``** → varbinary diff --git a/query-engine/Functions-and-operators/bitwise.mdx b/query-engine/Functions-and-operators/bitwise.mdx index 11c22318..fb143058 100644 --- a/query-engine/Functions-and-operators/bitwise.mdx +++ b/query-engine/Functions-and-operators/bitwise.mdx @@ -4,7 +4,7 @@ title: Bitwise #### bit_count() **``bit_count(x, bits)``** → bigint -Count the number of bits set in x (treated as bits-bit signed integer) in 2’s complement representation: +Count the number of bits set in x (treated as a bits-bit signed integer) in 2's complement representation: ```sql SELECT bit_count(9, 64); -- 2 SELECT bit_count(9, 8); -- 2 @@ -13,12 +13,14 @@ SELECT bit_count(-7, 8); -- 6 ``` #### bitwise_and() **``bitwise_and(x, y)``** → bigint -Returns the bitwise AND of x and y in 2’s complement representation. +Returns the bitwise AND of x and y in 2's complement representation. Bitwise AND of 19 (binary: 10011) and 25 (binary: 11001) results in 17 (binary: 10001): ```sql SELECT bitwise_and(19,25); -- 17 ``` + +#### bitwise_not() **``bitwise_not(x)``** → bigint Returns the bitwise NOT of x in 2’s complement representation (NOT x = -x - 1): diff --git a/query-engine/Functions-and-operators/chain-utility-functions.mdx b/query-engine/Functions-and-operators/chain-utility-functions.mdx index a1d1dee9..a60272cc 100644 --- a/query-engine/Functions-and-operators/chain-utility-functions.mdx +++ b/query-engine/Functions-and-operators/chain-utility-functions.mdx @@ -11,13 +11,13 @@ These functions are helpful to generate links to the explorer of a chain, to spe Most of the time you'll want to use ``get_href()`` in combination with one of the other functions to generate a clickable link to a specific address or transaction. ```sql -Select +SELECT get_href(get_chain_explorer_address('ethereum', to), cast(to as varchar)) FROM ethereum.transactions -limit 100 +LIMIT 100 ``` -This sql code will generate a clickable link pointing to the explorer of the Ethereum chain for each address in the ``to`` column. The displayed link will be the address itself. +This SQL code will generate a clickable link pointing to the explorer of the Ethereum chain for each address in the ``to`` column. The displayed link will be the address itself. You can find all the functions in action on this dashboard: [Chain Utility Functions](https://dune.com/dune/chain-utility-functions) @@ -40,7 +40,7 @@ This function generates a URL for the explorer of a specified chain (provided as SELECT get_chain_explorer_address('ethereum', cast(to as varchar)) FROM ethereum.transactions -limit 100 +LIMIT 100 ``` #### get_chain_explorer_address() @@ -52,7 +52,7 @@ This function generates a URL for the explorer of a specified chain (provided as SELECT get_chain_explorer_address('ethereum', to) FROM ethereum.transactions -limit 100 +LIMIT 100 ``` #### get_chain_explorer_tx_hash() @@ -64,7 +64,7 @@ This function generates a URL for the explorer of a specified chain (provided as SELECT get_chain_explorer_tx_hash('ethereum', cast(hash as varchar)) FROM ethereum.transactions -limit 100 +LIMIT 100 ``` #### get_chain_explorer_tx_hash() @@ -76,7 +76,7 @@ This function generates a URL for the explorer of a specified chain (provided as SELECT get_chain_explorer_tx_hash('ethereum', hash) FROM ethereum.transactions -limit 100 +LIMIT 100 ``` #### get_chain_explorer() @@ -98,7 +98,7 @@ This function returns a link to access a specific pool on the Balancer app. The SELECT get_balancer_link(blockchain, cast(pool_id as varchar)) FROM balancer.trades -limit 100 +LIMIT 100 ``` #### get_balancer_link() @@ -110,7 +110,7 @@ This function returns a link to access a specific pool on the Balancer app. The SELECT get_balancer_link(blockchain, pool_id) FROM balancer.trades -limit 100 +LIMIT 100 ``` #### all_evm_chains() diff --git a/query-engine/Functions-and-operators/comparison.mdx b/query-engine/Functions-and-operators/comparison.mdx index b71c6d89..e4e3e34b 100644 --- a/query-engine/Functions-and-operators/comparison.mdx +++ b/query-engine/Functions-and-operators/comparison.mdx @@ -63,7 +63,7 @@ The `IS NULL` and `IS NOT NULL` operators test whether a value is null Using `NULL` with `IS NULL` evaluates to true: ```sql - select NULL IS NULL; -- true + SELECT NULL IS NULL; -- true ``` But any other constant does not: ```sql @@ -85,7 +85,7 @@ In the example shown above, a `NULL` value is not considered distinct from `NULL`. When you are comparing values which may include `NULL` use these operators to guarantee either a `TRUE` or `FALSE` result. -The following truth table demonstrate the handling of `NULL` in +The following truth table demonstrates the handling of `NULL` in `IS DISTINCT FROM` and `IS NOT DISTINCT FROM`: | a | b | a = b | a \<\> b | a DISTINCT b | a NOT DISTINCT b | @@ -194,4 +194,4 @@ matches. If you need to match the used escape character as well, you can escape it. If you want to match for the chosen escape character, you simply escape -itself. For example, you can use `\\` to match for `''''`. +itself. For example, you can use `\\\\` to match for `\\`. diff --git a/query-engine/Functions-and-operators/conditional.mdx b/query-engine/Functions-and-operators/conditional.mdx index f03b3491..984cec0c 100644 --- a/query-engine/Functions-and-operators/conditional.mdx +++ b/query-engine/Functions-and-operators/conditional.mdx @@ -91,7 +91,7 @@ FROM tpch.sf1.orders; **``coalesce(value1, value2\[, \...\])``** -Returns the f non-null `value` in the argument list. Like a `CASE` +Returns the first non-null `value` in the argument list. Like a `CASE` expression, arguments are only evaluated if necessary. ### NULLIF diff --git a/query-engine/Functions-and-operators/conversion.mdx b/query-engine/Functions-and-operators/conversion.mdx index e7252eb8..1ba41ecb 100644 --- a/query-engine/Functions-and-operators/conversion.mdx +++ b/query-engine/Functions-and-operators/conversion.mdx @@ -12,7 +12,7 @@ When necessary, values can be explicitly cast to a particular type using the [ca ### Implicit Casting with numeric types -DuneSQL has added support for implicit casts when performing operations with `INT256` and `UINT256` and other numeric types like `INTEGER`, `BIGINTEGER`, `DECIMAL`, or `DOUBLE`. +DuneSQL has added support for implicit casts when performing operations with `INT256` and `UINT256` and other numeric types like `INTEGER`, `BIGINT`, `DECIMAL`, or `DOUBLE`. This allows you to use `INT256` and `UINT256` without adding casts explicitly. Whenever DuneSQL needs to find a common type for `INT256` or `UINT256` and another numeric type, it will generally go towards the bigger type. diff --git a/query-engine/Functions-and-operators/datetime.mdx b/query-engine/Functions-and-operators/datetime.mdx index 7b7bec3a..b2275d6e 100644 --- a/query-engine/Functions-and-operators/datetime.mdx +++ b/query-engine/Functions-and-operators/datetime.mdx @@ -49,14 +49,13 @@ Returns the current time with time zone as of the start of the query. **``current_timestamp``** Returns the current timestamp with time zone as of the start of the -query, with `3` digits of subsecond precision, +query, with `3` digits of subsecond precision. #### current_timestamp() **``current_timestamp(p)``** -Returns the current `timestamp with time zone -as `timestamp-with-time-zone-data-type` of the start of the query, with `p` digits of subsecond precision: +Returns the current timestamp with time zone as of the start of the query, with `p` digits of subsecond precision: ```sql SELECT current_timestamp(6); -- 2020-06-24 08:25:31.759993 America/Los_Angeles @@ -396,7 +395,6 @@ table, based on the MySQL manual, describes the format specifiers: | `%Y` | Year, numeric, four digits | | `%y` | Year, numeric (two digits)[^7] | | `%%` | A literal `%` character | -| `%x` | `x`, for any `x` not diff --git a/query-engine/Functions-and-operators/decimal.mdx b/query-engine/Functions-and-operators/decimal.mdx index 6db5abe9..26d55c4e 100644 --- a/query-engine/Functions-and-operators/decimal.mdx +++ b/query-engine/Functions-and-operators/decimal.mdx @@ -26,10 +26,10 @@ type `DECIMAL(xp, xs)` and `y` is of type `DECIMAL(yp, ys)`. | Operation | Result type precision | Result type scale | |--------------------|--------------------------------------------------|-------------------| -| `x + y` and `x -y` | `min(38,1 +max(xs, ys) + max(xp - xs, yp - ys))` | `max(xs, ys)` | +| `x + y` and `x -y` | `min(38, 1 + max(xs, ys) + max(xp - xs, yp - ys))` | `max(xs, ys)` | | `x * y` | `min(38, xp + yp)` | `xs + ys` | | `x / y` | `min(38, xp + ys + max(0, ys-xs))` | `max(xs, ys)` | -| `x % y` | `min(xp - xs, yp - ys) + max(xs, bs)` | `max(xs, ys)` | +| `x % y` | `min(xp - xs, yp - ys) + max(xs, ys)` | `max(xs, ys)` | If the mathematical result of the operation is not exactly representable @@ -46,7 +46,7 @@ decimal(38, 0) cannot be represented as a decimal(38, 1). ### Comparison operators -All standard `comparison` work for the +All standard `comparison` operators work for the decimal type. ### Unary decimal operators diff --git a/query-engine/Functions-and-operators/evm-decoding-functions.mdx b/query-engine/Functions-and-operators/evm-decoding-functions.mdx index 49a0ceb6..c1f451ce 100644 --- a/query-engine/Functions-and-operators/evm-decoding-functions.mdx +++ b/query-engine/Functions-and-operators/evm-decoding-functions.mdx @@ -153,7 +153,7 @@ FROM TABLE ( #### How to find the `input` and filter for the function called -- Generally, you can find the `input` by going to a block explorer. We recommend finding [an example transaction](https://basescan.org/tx/0x446c2c7c605cde83d6aba87921fceec40b111b97166ddbee513424eefae31ba5). In the "Overview" tab, scroll down and click on "click to show more". Then grab the MethodId in the Input Data filed. +- Generally, you can find the `input` by going to a block explorer. We recommend finding [an example transaction](https://basescan.org/tx/0x446c2c7c605cde83d6aba87921fceec40b111b97166ddbee513424eefae31ba5). In the "Overview" tab, scroll down and click on "click to show more". Then grab the MethodId in the Input Data field. - The MethodId you identified is the first 4 bytes of the keccak256 hash of the function signature. So we can use the function `starts_with(input, )`to filter for the function call now. diff --git a/query-engine/Functions-and-operators/http.mdx b/query-engine/Functions-and-operators/http.mdx index 381e0e79..8a7eb204 100644 --- a/query-engine/Functions-and-operators/http.mdx +++ b/query-engine/Functions-and-operators/http.mdx @@ -7,9 +7,9 @@ import { DuneEmbed } from "/snippets/dune-embed.mdx" The HTTP functions send HTTP requests to a specified URL. Using the HTTP functions, you can interact with HTTP servers directly in SQL queries. -They allow to fetch data from external APIs, as well as invoke remote procedure calls. +They allow you to fetch data from external APIs, as well as invoke remote procedure calls. -With the HTTP functions we can e.g. pull in a list of coins from coingecko: +With the HTTP functions, we can e.g. pull in a list of coins from CoinGecko: ```sql SELECT * FROM UNNEST( @@ -57,7 +57,7 @@ The function sends an HTTP GET request to the given URL, optionally including th and returns the response body as `varchar`. Often, the response is a JSON document. You can process it further with [JSON-processing SQL functions](/query-engine/Functions-and-operators/json). -Other response formats, like html, are also supported. +Other response formats, like HTML, are also supported. #### http_post() @@ -90,7 +90,7 @@ made within the query. SELECT http_get('https://api.coingecko.com/api/v3/coins/list'); ``` -### Multiple HTTP GET requests parametrized with Dune data +### Multiple HTTP GET requests parameterized with Dune data ```sql SELECT diff --git a/query-engine/Functions-and-operators/hyperloglog.mdx b/query-engine/Functions-and-operators/hyperloglog.mdx index 40abc932..5e59faa8 100644 --- a/query-engine/Functions-and-operators/hyperloglog.mdx +++ b/query-engine/Functions-and-operators/hyperloglog.mdx @@ -36,7 +36,7 @@ Examples: CREATE TABLE visit_summaries ( visit_date date, hll varbinary - ) + ); INSERT INTO visit_summaries SELECT visit_date, cast(approx_set(user_id) AS varbinary) FROM user_visits diff --git a/query-engine/Functions-and-operators/index.mdx b/query-engine/Functions-and-operators/index.mdx index d1d3243d..d1d538da 100644 --- a/query-engine/Functions-and-operators/index.mdx +++ b/query-engine/Functions-and-operators/index.mdx @@ -10,7 +10,7 @@ Using ``SHOW FUNCTIONS`` in the query editor returns a list of all available fun ### DuneSQL Added Functions: - [Varbinary datatypes for EVM data](/query-engine/Functions-and-operators/varbinary) -- [Base58 for Bitcoin&Solana data](/query-engine/Functions-and-operators/base58) +- [Base58 for Bitcoin & Solana data](/query-engine/Functions-and-operators/base58) - [ss58 for Substrate data](/query-engine/Functions-and-operators/ss58) - [Tron Address Functions](/query-engine/Functions-and-operators/tronaddress) - [Chain Utility Functions](/query-engine/Functions-and-operators/chain-utility-functions) @@ -18,7 +18,7 @@ Using ``SHOW FUNCTIONS`` in the query editor returns a list of all available fun - [LiveFetch Functions](/query-engine/Functions-and-operators/live-fetch) ### Trino Base Functions: -- [Aggregate](query-engine/Functions-and-operators/aggregate) +- [Aggregate](/query-engine/Functions-and-operators/aggregate) - [Array](/query-engine/Functions-and-operators/array) - [Binary](/query-engine/Functions-and-operators/binary) - [Bitwise](/query-engine/Functions-and-operators/bitwise) diff --git a/query-engine/Functions-and-operators/json.mdx b/query-engine/Functions-and-operators/json.mdx index 9950302c..ba9a9e8a 100644 --- a/query-engine/Functions-and-operators/json.mdx +++ b/query-engine/Functions-and-operators/json.mdx @@ -201,7 +201,7 @@ Let `` return a sequence of three JSON objects: {"customer" : 300, "region" : "AFRICA", "comment" : null} ``` -The results is: +The result is: ```text 100, "AFRICA", "ASIA", 300, "AFRICA", null @@ -384,7 +384,7 @@ evaluation throws an error, returns `unknown`. ``` The nested `` must evaluate to a sequence of textual items, and the -other operand must evaluate to a single textual item. If evaluating of either +other operand must evaluate to a single textual item. If evaluation of either operand throws an error, the result is `unknown`. All items from the sequence are checked for starting with the right operand. The result is `true` if a match is found, otherwise `false`. However, if any of the comparisons throws @@ -850,7 +850,7 @@ FROM customers The following query gets the collection of children for each customer. Note that the `json_query` function can only output a single JSON item. If -you dont use array wrapper, you get an error for every customer with multiple +you don't use array wrapper, you get an error for every customer with multiple children. The error is handled according to the `ON ERROR` clause. ```sql @@ -892,7 +892,7 @@ FROM customers | 103 | [2] | The following query gets all children above the age of 12 for each customer, -wrapped in a JSON array. The second and the third customer dont have children +wrapped in a JSON array. The second and the third customer don't have children of this age. Such case is handled according to the `ON EMPTY` clause. The default value returned `ON EMPTY` is `NULL`. In the following example, `EMPTY ARRAY ON EMPTY` is specified. @@ -1051,7 +1051,7 @@ FROM customers | 102 | problematic | | 103 | knows best | -The following query gets the first childs age for each customer as +The following query gets the first child's age for each customer as `tinyint`: ```sql @@ -1069,7 +1069,7 @@ FROM customers | 102 | 8 | | 103 | 2 | -The following query gets the third childs age for each customer. In the strict +The following query gets the third child's age for each customer. In the strict mode, this should cause a structural error for the customers who do not have the third child. This error is handled according to the `ON ERROR` clause. @@ -1625,7 +1625,7 @@ feature-rich alternative to parse and extract JSON data. #### json_extract_scalar() **``json_extract_scalar(json, json_path)``** → varchar -Like json_extract`, but returns the result value as a string (as opposed +Like `json_extract`, but returns the result value as a string (as opposed to being encoded as JSON). The value referenced by `json_path` must be a scalar (boolean, number or string). diff --git a/query-engine/Functions-and-operators/lambda.mdx b/query-engine/Functions-and-operators/lambda.mdx index 5ff9137d..ca443a19 100644 --- a/query-engine/Functions-and-operators/lambda.mdx +++ b/query-engine/Functions-and-operators/lambda.mdx @@ -45,7 +45,7 @@ Obtain the squared elements of an array column with | [5, 6, 7] | [25, 36, 49] | -The function `transform` can be also +The function `transform` can also be employed to safely cast the elements of an array to strings: ```sql SELECT transform(prices, n -> TRY_CAST(n AS VARCHAR) || '$') as price_tags @@ -98,14 +98,14 @@ with `any_match`: WHERE any_match(numbers, n -> COALESCE(n, 0) > 100); -- [100, 200, 300] ``` -Capitalize the f word in a string via `regexp_replace`: +Capitalize the first word in a string via `regexp_replace`: ```sql SELECT regexp_replace('once upon a time ...', '^(\w)(\w*)(\s+.*)$',x -> upper(x[1]) || x[2] || x[3]); -- Once upon a time ... ``` -Lambda expressions can be also applied in aggregation functions. -Following statement is a sample the overly complex calculation of the +Lambda expressions can also be applied in aggregation functions. +The following statement is a sample of the overly complex calculation of the sum of all elements of a column by making use of `reduce_agg`: ```sql SELECT reduce_agg(value, 0, (a, b) -> a + b, (a, b) -> a + b) sum_values diff --git a/query-engine/Functions-and-operators/live-fetch.mdx b/query-engine/Functions-and-operators/live-fetch.mdx index b18ac57d..4b20f01b 100644 --- a/query-engine/Functions-and-operators/live-fetch.mdx +++ b/query-engine/Functions-and-operators/live-fetch.mdx @@ -6,7 +6,7 @@ import { DuneEmbed } from '/snippets/dune-embed.mdx' The LiveFetch functions send HTTP requests to a specified URL. Using the LiveFetch functions, you can interact with HTTP servers directly in SQL queries. -They allow to fetch data from external APIs, as well as invoke remote procedure calls. +They allow you to fetch data from external APIs, as well as invoke remote procedure calls. With the LiveFetch functions we can e.g. pull in a list of coins from coingecko: @@ -85,7 +85,7 @@ made within the query. SELECT http_get('https://api.coingecko.com/api/v3/coins/list'); ``` -### Multiple HTTP GET requests parametrized with Dune data +### Multiple HTTP GET requests parameterized with Dune data ```sql SELECT diff --git a/query-engine/Functions-and-operators/logical.mdx b/query-engine/Functions-and-operators/logical.mdx index 605b5e82..aaf5e9c5 100644 --- a/query-engine/Functions-and-operators/logical.mdx +++ b/query-engine/Functions-and-operators/logical.mdx @@ -42,7 +42,7 @@ and `OR`: | `TRUE` | `FALSE` | `FALSE` | `TRUE` | | `TRUE` | `NULL` | `NULL` | `TRUE` | | `FALSE` | `TRUE` | `FALSE` | `TRUE` | -| `FALSE` | `FALSE` | `FALSE` | `FALSE`| +| `FALSE` | `FALSE` | `FALSE` | `FALSE` | | `FALSE` | `NULL` | `FALSE` | `NULL` | | `NULL` | `TRUE` | `NULL` | `TRUE` | | `NULL` | `FALSE` | `FALSE` | `NULL` | diff --git a/query-engine/Functions-and-operators/map.mdx b/query-engine/Functions-and-operators/map.mdx index 93ac7374..c5451575 100644 --- a/query-engine/Functions-and-operators/map.mdx +++ b/query-engine/Functions-and-operators/map.mdx @@ -110,7 +110,7 @@ Returns all the values in the map `x`. **``map_zip_with(map(K,V1), map(K,V2), function(K,V1,V2,V3))``** → map(K,V3) Merges the two given maps into a single map by applying `function` to -the pair of values with the same key. For keys only presented in one +the pair of values with the same key. For keys only present in one map, NULL will be passed as the value for the missing key: ```sql SELECT map_zip_with(MAP(ARRAY[1, 2, 3], ARRAY['a', 'b', 'c']), diff --git a/query-engine/Functions-and-operators/math.mdx b/query-engine/Functions-and-operators/math.mdx index 7d2408be..92248cd1 100644 --- a/query-engine/Functions-and-operators/math.mdx +++ b/query-engine/Functions-and-operators/math.mdx @@ -171,7 +171,7 @@ Returns the sine of `x`. Returns the tangent of `x`. #### sinh() -**``sinh(x)``** → double +**``sinh(x)``** → double Returns the hyperbolic sine of `x`. #### tanh() @@ -244,7 +244,7 @@ positive real values. The probability p must lie on the interval [0, #### inverse_normal_cdf() **``inverse_normal_cdf(mean, sd, p)``** → double -Compute the inverse of the Normal cdf with given mean and standard +Compute the inverse of the Normal cdf with given mean and standard deviation (sd) for the cumulative probability (p): P(N < n). The mean must be a real value and the standard deviation must be a real and positive value. The probability p must lie on the interval [0, 1]. #### normal_cdf() **``normal_cdf(mean, sd, v)``** → double diff --git a/query-engine/Functions-and-operators/ml.mdx b/query-engine/Functions-and-operators/ml.mdx index 36c45d84..bf9df504 100644 --- a/query-engine/Functions-and-operators/ml.mdx +++ b/query-engine/Functions-and-operators/ml.mdx @@ -10,7 +10,7 @@ problems. Note: The machine learning functions are not optimized for distributed -processing. The capability to train large data sets is limited by this +processing. The capability to train large data sets is limited by the execution of the final training on a single instance. # Feature vector @@ -19,7 +19,7 @@ To solve a problem with the machine learning technique, especially as a supervised learning problem, it is necessary to represent the data set with the sequence of pairs of labels and feature vector. A label is a target value you want to predict from the unseen feature and a feature -is a A N-dimensional vector whose elements are numerical values. In +is an N-dimensional vector whose elements are numerical values. In Trino, a feature vector is represented as a map-type value, whose key is an index of each feature, so that it can express a sparse vector. Since classifiers and regressors can recognize the map-type feature vector, @@ -64,7 +64,7 @@ model 68 61 72 29 3e ``` -`classify` returns the predicted label by using the trained model. The trained model can not be saved natively, +`classify` returns the predicted label by using the trained model. The trained model cannot be saved natively, and needs to be passed in the format of a nested query: ```sql SELECT @@ -92,7 +92,7 @@ internal parameters of the model. # Regression Regression is another type of supervised learning problem, predicting -continuous value, unlike the classification problem. The target must be +a continuous value, unlike the classification problem. The target must be numerical values that can be described as `double`. The following code shows the creation of the model predicting @@ -124,7 +124,7 @@ Internally, the model is trained by `learn_libsvm_regressor` provides you a way to control the training process. -# Machine learning functions \{#machine-learning-functions-1} +# Machine learning functions {#machine-learning-functions-1} #### features() **``features(double, ...)``** → map(bigint, double) diff --git a/query-engine/Functions-and-operators/qdigest.mdx b/query-engine/Functions-and-operators/qdigest.mdx index 00ac4b92..e22fcbff 100644 --- a/query-engine/Functions-and-operators/qdigest.mdx +++ b/query-engine/Functions-and-operators/qdigest.mdx @@ -24,7 +24,7 @@ Merges all input `qdigest`s into a single `qdigest`. Returns the approximate ``quantile`` number between 0 and 1 from the quantile digest given an input value. Null is returned if the quantile digest is empty or the input value is outside of the range of the quantile digest. -#### values_at_quantile() +#### value_at_quantile() **``value_at_quantile(qdigest(T), quantile)``** → T Returns the approximate percentile value from the quantile digest given diff --git a/query-engine/Functions-and-operators/regexp.mdx b/query-engine/Functions-and-operators/regexp.mdx index fb34c3bf..b057f6c0 100644 --- a/query-engine/Functions-and-operators/regexp.mdx +++ b/query-engine/Functions-and-operators/regexp.mdx @@ -34,7 +34,7 @@ with a few notable exceptions: #### regexp_count() **``regexp_count(string, pattern)``** → bigint -Returns the number of occurrence of `pattern` in `string`: +Returns the number of occurrences of `pattern` in `string`: ```sql SELECT regexp_count('1a 2b 14m', '\s*[a-z]+\s*'); -- 3 ``` @@ -58,7 +58,7 @@ and returns the [capturing group number]() `group`: #### regexp_extract() **``regexp_extract(string, pattern)``** → varchar -Returns the f substring matched by the regular expression `pattern` +Returns the first substring matched by the regular expression `pattern` in `string`: ```sql SELECT regexp_extract('1a 2b 14m', '\d+'); -- 1 @@ -66,7 +66,7 @@ in `string`: **``regexp_extract(string, pattern, group)``** → varchar -Finds the f occurrence of the regular expression `pattern` in +Finds the first occurrence of the regular expression `pattern` in `string` and returns the [capturing group number]() `group`: ```sql SELECT regexp_extract('1a 2b 14m', '(\d+)([a-z]+)', 2); -- 'a' @@ -89,7 +89,7 @@ entire string by anchoring the pattern using `^` and `$`: #### regexp_position() **``regexp_position(string, pattern)``** → integer -Returns the index of the f occurrence (counting from 1) of `pattern` +Returns the index of the first occurrence (counting from 1) of `pattern` in `string`. Returns -1 if not found: ```sql SELECT regexp_position('I have 23 apples, 5 pears and 13 oranges', '\b\d+\b'); -- 8 @@ -97,7 +97,7 @@ in `string`. Returns -1 if not found: **``regexp_position(string, pattern, start)``** → integer -Returns the index of the f occurrence of `pattern` in `string`, +Returns the index of the first occurrence of `pattern` in `string`, starting from `start` (include `start`). Returns -1 if not found: ```sql SELECT regexp_position('I have 23 apples, 5 pears and 13 oranges', '\b\d+\b', 5); -- 8 @@ -121,7 +121,9 @@ starting from `start` (include `start`). Returns -1 if not found: Removes every instance of the substring matched by the regular expression `pattern` from `string`: +```sql SELECT regexp_replace('1a 2b 14m', '\d+[ab] '); -- '14m' +``` **``regexp_replace(string, pattern, replacement)``** → varchar @@ -144,9 +146,11 @@ expression `pattern` in `string` using `function`. The invoked for each match with the [capturing groups]() passed as an array. Capturing group numbers start at one; there is no group for the entire match (if you need this, surround the entire expression with -parenthesis). : +parentheses): +```sql SELECT regexp_replace('new york', '(\w)(\w*)', x -> upper(x[1]) || lower(x[2])); --'New York' +``` #### regexp_split() **``regexp_split(string, pattern)``** → array(varchar) diff --git a/query-engine/Functions-and-operators/setdigest.mdx b/query-engine/Functions-and-operators/setdigest.mdx index d4235096..3bff3e57 100644 --- a/query-engine/Functions-and-operators/setdigest.mdx +++ b/query-engine/Functions-and-operators/setdigest.mdx @@ -75,10 +75,10 @@ The above result listing points out, as expected, that the texts with the id 1 and 3 are quite similar. One may argue that the text with the id 2 is somewhat similar to the -texts with the id 1 and 3. Due to the fact in the example above +texts with the id 1 and 3. Due to the fact that in the example above 4-shingles are taken into account for measuring the similarity of the texts, there are no intersections found for the text pairs 1 and 2, -respectively 3 and 2 and therefore there the similarity index for +respectively 3 and 2 and therefore the similarity index for these text pairs is 0. ## Data structures @@ -119,17 +119,21 @@ Create a `setdigest` corresponding to a `bigint` array: ``` Create a `setdigest` corresponding to a `varchar` array: +```sql SELECT make_set_digest(value) FROM (VALUES 'Trino', 'SQL', 'on', 'everything') T(value); +``` #### merge_set_digest() **``merge_set_digest(setdigest, setdigest)``** → setdigest - Returns the `setdigest` of the aggregate union of the individual `setdigest` Set Digest structures. +#### cardinality() +**``cardinality(x)``** → bigint + Returns the cardinality of the set digest from its internal `HyperLogLog` component. diff --git a/query-engine/Functions-and-operators/string.mdx b/query-engine/Functions-and-operators/string.mdx index d91bbad7..0aea0553 100644 --- a/query-engine/Functions-and-operators/string.mdx +++ b/query-engine/Functions-and-operators/string.mdx @@ -103,7 +103,7 @@ Replaces all instances of `search` with `replace` in `string`. #### reverse() **``reverse(string)``** → varchar -Returns `string` with the characters +Returns `string` with the characters in reverse order. #### rpad() **``rpad(string, size, padstring)``** → varchar @@ -141,7 +141,7 @@ Splits `string` on `delimiter` and returns an array. #### split() **``split(string, delimiter, limit)``** → array(varchar) -Splits `string` on `delimiter` and returns an array of size at most `limit`. The last element in the array always contain everything left in the `string`. `limit` must be a positive number. +Splits `string` on `delimiter` and returns an array of size at most `limit`. The last element in the array always contains everything left in the `string`. `limit` must be a positive number. #### split_part() **``split_part(string, delimiter, index)``** → varchar @@ -192,11 +192,6 @@ Returns a substring from `string` of length `length` from the starting position #### translate() **``translate(source, from, to)``** → varchar -Returns the `source` string translated by replacing characters found in the - - -**``translate(source, from, to)``** → varchar - Returns the `source` string translated by replacing characters found in the `from` string with the corresponding characters in the `to` string. If the `from` string contains duplicates, only the first is used. If the `source` character does not exist in the `from` string, the `source` character will be copied without translation. If the index of the matching character in the `from` string is beyond the length of the `to` string, the `source` character will be omitted from the resulting string. Here are some examples illustrating the translate function: @@ -278,7 +273,7 @@ Encodes `string` into a UTF-8 varbinary representation. ```sql SELECT to_utf8('Hello, world!'); -- 0x48656C6C6F2C20776F726C6421 - Select keccak(to_utf8('Transfer(address,address,uint256)')) --0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef + SELECT keccak(to_utf8('Transfer(address,address,uint256)')) --0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef ``` #### from_utf8() diff --git a/query-engine/Functions-and-operators/system.mdx b/query-engine/Functions-and-operators/system.mdx index b941e25b..363a2d38 100644 --- a/query-engine/Functions-and-operators/system.mdx +++ b/query-engine/Functions-and-operators/system.mdx @@ -3,7 +3,7 @@ title: System information --- ## System information -Functions providing information about the Trino cluster system environment. More information is available by querying the various schemas and tables exposed by the `/connector/system`. +Functions providing information about the Trino cluster system environment. More information is available by querying the various schemas and tables exposed by the `system` connector. ## Function diff --git a/query-engine/Functions-and-operators/tdigest.mdx b/query-engine/Functions-and-operators/tdigest.mdx index 95bd3a3f..425852db 100644 --- a/query-engine/Functions-and-operators/tdigest.mdx +++ b/query-engine/Functions-and-operators/tdigest.mdx @@ -16,7 +16,7 @@ to and from `VARBINARY`. Aggregates all inputs into a single `tdigest`. -#### values_at_quantile() +#### value_at_quantile() **``value_at_quantile(tdigest, quantile)``** → double Returns the approximate percentile value from the T-digest, given the number `quantile` between 0 and 1. @@ -34,4 +34,4 @@ Composes all input values of `x` into a `tdigest`. `x` can be of any numeric typ **``tdigest_agg(x, w)``** → tdigest -Composes all input values of `x` into a `tdigest` using the per-item weight `w`. `w` must be greater or equal than 1. `x` and `w` can be of any numeric type. +Composes all input values of `x` into a `tdigest` using the per-item weight `w`. `w` must be greater than or equal to 1. `x` and `w` can be of any numeric type. diff --git a/query-engine/Functions-and-operators/teradata.mdx b/query-engine/Functions-and-operators/teradata.mdx index 70b8ef1b..2c96b843 100644 --- a/query-engine/Functions-and-operators/teradata.mdx +++ b/query-engine/Functions-and-operators/teradata.mdx @@ -6,7 +6,7 @@ These functions provide compatibility with Teradata SQL. ## String functions -#### char2() +#### char2hexint() **``char2hexint(string)``** → varchar Returns the hexadecimal representation of the UTF-16BE encoding of the string. diff --git a/query-engine/Functions-and-operators/tonaddress.mdx b/query-engine/Functions-and-operators/tonaddress.mdx index 3a918e3b..8c112a32 100644 --- a/query-engine/Functions-and-operators/tonaddress.mdx +++ b/query-engine/Functions-and-operators/tonaddress.mdx @@ -8,7 +8,7 @@ Smart contract addresses on the TON blockchain are composed of two key component 1. Workchain Identifier. A signed 8-bit number that identifies the workchain. Currently, only the masterchain (workchain_id = -1) and occasionally the basic workchain (workchain_id = 0) are active on the TON blockchain. 1. Account Identifier. A 256-bit number unique to each account within a workchain. -There are two different representation of contract addresses on TON blockchain: +There are two different representations of contract addresses on TON blockchain: * Raw addresses: Original full representation of smart contract addresses. Raw smart contract addresses consist of a workchain ID and account ID and are displayed in the following format: `:<64 hexadecimal digits with account_id>`. Example: `-1:fcb91a3a3816d0f7b8c2c76108b8a9bc5a6b7a55bd79f8ab101c52db29232260`. * User-friendly addresses: An enhanced version of raw address designed to improve security and usability. User-friendly addresses were developed to secure and simplify the experience for TON users who share addresses on the internet (for example, on public messaging platforms or via their email service providers), as well as in the real world. User-friendly addresses are made up of 36 bytes in total. diff --git a/query-engine/Functions-and-operators/tronaddress.mdx b/query-engine/Functions-and-operators/tronaddress.mdx index f64a0304..bb0cc9a7 100644 --- a/query-engine/Functions-and-operators/tronaddress.mdx +++ b/query-engine/Functions-and-operators/tronaddress.mdx @@ -3,9 +3,9 @@ title: Tron address functions description: Utilities for working with TRON's custom address format. --- -Tron blockchain adopted a custom type of addresses. It is similar to [Base58](/query-engine/Functions-and-operators/base58) encoding format, with some modifications. +The Tron blockchain adopted a custom type of addresses. It is similar to [Base58](/query-engine/Functions-and-operators/base58) encoding format, with some modifications. -Under basic tron address encoding format an address can be encoded as: +Under the basic Tron address encoding format an address can be encoded as: ``` base58encode ( concat ( ,
, ) ) ``` @@ -31,5 +31,5 @@ Encodes a `VARBINARY` hex address to the corresponding Tron address. ```sql SELECT to_tron_address(0x503aa4ad108bd3a89ba0310e23b49fb654cd6986) --- results 'THHRK1bA7YRPZBcLnTP1SZy9ipUpsRwpo6' +-- results in 'THHRK1bA7YRPZBcLnTP1SZy9ipUpsRwpo6' ``` diff --git a/query-engine/Functions-and-operators/url.mdx b/query-engine/Functions-and-operators/url.mdx index 2b80810a..bbeb18a8 100644 --- a/query-engine/Functions-and-operators/url.mdx +++ b/query-engine/Functions-and-operators/url.mdx @@ -5,7 +5,7 @@ title: URL functions ## Extraction functions The URL extraction functions extract components from HTTP URLs (or any -valid URIs conforming to `2396`). The following syntax is supported: +valid URIs conforming to RFC `2396`). The following syntax is supported: ``` text [protocol:][//host[:port]][path][?query][#fragment] @@ -27,7 +27,7 @@ Returns the host from `url`. #### url_extract_parameter() **``url_extract_parameter(url, name)``** → varchar -Returns the value of the f query string parameter named `name` from `url`. Parameter extraction is handled in the typical manner as specified by RFC 1866#section-8.2.1. +Returns the value of the query string parameter named `name` from `url`. Parameter extraction is handled in the typical manner as specified by RFC 1866#section-8.2.1. #### url_extract_path() **``url_extract_path(url)``** → varchar diff --git a/query-engine/Functions-and-operators/uuid.mdx b/query-engine/Functions-and-operators/uuid.mdx index aa0adab1..e8935a67 100644 --- a/query-engine/Functions-and-operators/uuid.mdx +++ b/query-engine/Functions-and-operators/uuid.mdx @@ -5,4 +5,4 @@ title: UUID functions **``uuid()``** → uuid -Returns a pseudo randomly generated `uuid_type`(type 4). +Returns a pseudorandomly generated `uuid_type`(type 4). diff --git a/query-engine/Functions-and-operators/varbinary.mdx b/query-engine/Functions-and-operators/varbinary.mdx index 72cbd732..ef3d9456 100644 --- a/query-engine/Functions-and-operators/varbinary.mdx +++ b/query-engine/Functions-and-operators/varbinary.mdx @@ -4,12 +4,12 @@ title: Varbinary functions (DuneSQL) ## Varbinary Functions -Dune SQL represents varbinarys using the varbinary type. +Dune SQL represents varbinaries using the varbinary type. -To make it simpler to work with varbinarys we have the following helper functions, which work with these two kinds of representation. They simplify interactions with varbinarys, as they automatically account for the `0x`-prefix and use byte index instead of character index. For instance, the varbinary_substring methods take indexes by byte, not by character (twice the varbinary length). +To make it simpler to work with varbinaries we have the following helper functions, which work with these two kinds of representation. They simplify interactions with varbinaries, as they automatically account for the `0x`-prefix and use byte index instead of character index. For instance, the varbinary_substring methods take indexes by byte, not by character (twice the varbinary length). -You can use these function to extract data from undecoded events logs, or calldata. For instance, if you have a function that takes a `uint256` as an argument, you can use `varbinary_to_uint256` to extract the value from the calldata. You'll oftentimes need to use `varbinary_substring` to extract the correct part of the calldata or use other bytearray manipulation functions to get the correct value. +You can use these functions to extract data from undecoded events logs, or calldata. For instance, if you have a function that takes a `uint256` as an argument, you can use `varbinary_to_uint256` to extract the value from the calldata. You'll oftentimes need to use `varbinary_substring` to extract the correct part of the calldata or use other bytearray manipulation functions to get the correct value. ```sql select tx_hash, @@ -196,7 +196,7 @@ Select from_hex('0x6574686275696c646572') **``varbinary_concat(varbinary, varbinary)``** → varbinary -Concatenates two varbinarys or strings. +Concatenates two varbinaries or strings. ```sql @@ -206,7 +206,7 @@ SELECT varbinary_concat(0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2, **`varbinary_concat(varchar, varchar)`** → varchar -Concatenates two varbinarys or strings. +Concatenates two varbinaries or strings. ```sql @@ -274,7 +274,7 @@ Removes zero bytes or spaces from the end of a varbinary or string. ```sql -- this will remove the zeros at the end, -- returning 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 -SELECT varbinary_ltrim(0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc20000000000000000000000000000000000000000) +SELECT varbinary_rtrim(0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc20000000000000000000000000000000000000000) ``` #### varbinary_position() @@ -397,7 +397,7 @@ Returns a suffix varbinary or string starting at a given index. ```sql --- using varbinary_substring starting from the 21th index +-- using varbinary_substring starting from the 21st index -- this returns 0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 SELECT 0x0000000000000000000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2 as original_bytearray, varbinary_substring(0x0000000000000000000000000000000000000000c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2,21) as bytearraysubstring_data diff --git a/query-engine/Functions-and-operators/varchar-utility-functions.mdx b/query-engine/Functions-and-operators/varchar-utility-functions.mdx index bbd17bf2..c84ad859 100644 --- a/query-engine/Functions-and-operators/varchar-utility-functions.mdx +++ b/query-engine/Functions-and-operators/varchar-utility-functions.mdx @@ -45,7 +45,7 @@ will return `Hello World` This function converts a hexadecimal-formatted input string to varbinary, always producing an output of 32 bytes in length by left-padding with the 0x00 byte. The input string needs to be hexadecimal formatted, allowing characters from `[a-fA-F0-9]`; otherwise, an error is returned. While the input can be prefixed with '0x', this is not mandatory. The function accommodates the hexadecimal representation of any decimal number, provided it fits within 32 bytes. -This function proves useful in scenarios where addresses in the Aptos chain are utilized. In the Aptos chain, addresses serve as 32-byte identifiers for accounts or objects. All addresses in Aptos chain are represented as just that, using a 32-byte varbinary. However, it's quite common to represent addresses in their short-formed representation, having leading zeros trimmed. For example, a valid aptos account can have a 0x1 address. Additionally, it's typical to encounter the short format without the '0x' prefix. Therefore, this function serves to transform a short-form address into the internal representation format used for addresses +This function proves useful in scenarios where addresses in the Aptos chain are utilized. In the Aptos chain, addresses serve as 32-byte identifiers for accounts or objects. All addresses in the Aptos chain are represented as just that, using a 32-byte varbinary. However, it's quite common to represent addresses in their short-formed representation, having leading zeros trimmed. For example, a valid Aptos account can have a 0x1 address. Additionally, it's typical to encounter the short format without the '0x' prefix. Therefore, this function serves to transform a short-form address into the internal representation format used for addresses. ```sql -- The following query will return: true, true, true SELECT @@ -54,7 +54,7 @@ SELECT address_32_from_hex('0x1') = 0x0000000000000000000000000000000000000000000000000000000000000001 ``` -In the aptos context, we can use the function to find transactions with the entry function address being 0x1. +In the Aptos context, we can use the function to find transactions with the entry function address being 0x1. ```sql SELECT * FROM aptos.user_transactions WHERE entry_function_module_address = address_32_from_hex('0x1') LIMIT 10 ``` \ No newline at end of file diff --git a/query-engine/Functions-and-operators/window.mdx b/query-engine/Functions-and-operators/window.mdx index 4c3262b3..5b7981df 100644 --- a/query-engine/Functions-and-operators/window.mdx +++ b/query-engine/Functions-and-operators/window.mdx @@ -28,7 +28,7 @@ The window can be specified in two ways (see ## Aggregate functions -All `aggregate` can be used as window functions by adding the `OVER` clause. The aggregate function is +All aggregate functions can be used as window functions by adding the `OVER` clause. The aggregate function is computed for each row over the rows within the current row's window frame. @@ -67,7 +67,7 @@ For example, with `6` rows and `4` buckets, the bucket values would be as follow #### percent_rank() **percent_rank()** → double -Returns the percentage ranking of a value in group of values. The result is `(r - 1) / (n - 1)` where `r` is the `rank` of the row and `n` is the total number of rows in the window partition. +Returns the percentage ranking of a value in a group of values. The result is `(r - 1) / (n - 1)` where `r` is the `rank` of the row and `n` is the total number of rows in the window partition. #### rank() **rank()** → bigint diff --git a/query-engine/datatypes.mdx b/query-engine/datatypes.mdx index 096f9569..6981671e 100644 --- a/query-engine/datatypes.mdx +++ b/query-engine/datatypes.mdx @@ -29,23 +29,23 @@ We have built custom functions to make it easier to work with varbinaries in Dun ### `TINYINT` -A 8-bit signed two\'s complement integer with a minimum value of `-2^7` +An 8-bit signed two's complement integer with a minimum value of `-2^7` and a maximum value of `2^7 - 1`. ### `SMALLINT` -A 16-bit signed two\'s complement integer with a minimum value of +A 16-bit signed two's complement integer with a minimum value of `-2^15` and a maximum value of `2^15 - 1`. ### `INTEGER` -A 32-bit signed two\'s complement integer with a minimum value of +A 32-bit signed two's complement integer with a minimum value of `-2^31` and a maximum value of `2^31 - 1`. The name `INT` is also available for this type. ### `BIGINT` -A 64-bit signed two\'s complement integer with a minimum value of +A 64-bit signed two's complement integer with a minimum value of `-2^63` and a maximum value of `2^63 - 1`. ### `UINT256` (Dune SQL) @@ -126,9 +126,6 @@ Example type definitions: `char`, `char(20)` -```sql - Select * from ethereum.transactions where "from" = 0xc8ebccc5f5689fa8659d83713341e5ad19349448 -``` ### `JSON` @@ -295,11 +292,11 @@ Example: `ROW(1, 2.0)[1]` An IP address that can represent either an IPv4 or IPv6 address. Internally, the type is a pure IPv6 address. Support for IPv4 is handled using the _IPv4-mapped IPv6 address_ range -(`4291#section-2.5.5.2`). When creating an +([RFC 4291 section 2.5.5.2](https://tools.ietf.org/rfc/rfc4291.html#section-2.5.5.2)). When creating an `IPADDRESS`, IPv4 addresses will be mapped into that range. When formatting an `IPADDRESS`, any address within the mapped range will be formatted as an IPv4 address. Other addresses will be formatted as IPv6 -using the canonical format defined in `5952`. +using the canonical format defined in [RFC 5952](https://tools.ietf.org/rfc/rfc5952.html). Examples: `IPADDRESS '10.0.0.1'`, `IPADDRESS '2001:db8::1'` @@ -309,7 +306,7 @@ Examples: `IPADDRESS '10.0.0.1'`, `IPADDRESS '2001:db8::1'` This type represents a UUID (Universally Unique IDentifier), also known as a GUID (Globally Unique IDentifier), using the format defined in -`4122`\ +[RFC 4122](https://tools.ietf.org/rfc/rfc4122.html). Example: `UUID '12151fd2-7586-11e9-8f9e-2a86e4085a59'` @@ -327,7 +324,7 @@ efficient. ### `P4HyperLogLog` -A P4HyperLogLog sketch is similar to `hyperloglog_type`, but it starts (and remains) in the dense representation. +A P4HyperLogLog sketch is similar to `HyperLogLog`, but it starts (and remains) in the dense representation. ## SetDigest @@ -363,7 +360,7 @@ queried to retrieve approximate quantile values from the distribution. The level of accuracy for a qdigest is tunable, allowing for more precise results at the expense of space. -A qdigest can be used to give approximate answer to queries asking for +A qdigest can be used to give approximate answers to queries asking for what value belongs at a certain quantile. A useful property of qdigests is that they are additive, meaning they can be merged together without losing precision. diff --git a/query-engine/index.mdx b/query-engine/index.mdx index ae15cba1..fee91317 100644 --- a/query-engine/index.mdx +++ b/query-engine/index.mdx @@ -60,7 +60,7 @@ DuneSQL designates specific reserved keywords for internal functions, ensuring t ## Querying Capabilities -Although DuneSQL limits data modification commands to safeguard data integrity, it offers innovative solutions like query queries for creating views and tables, enhancing data analysis flexibility. +Although DuneSQL limits data modification commands to safeguard data integrity, it offers innovative solutions like query-a-query for creating views and tables, enhancing data analysis flexibility. - Utilize the query queries feature in DuneSQL to compensate for the + Utilize the query-a-query feature in DuneSQL to compensate for the restricted ability to create views and tables, enriching data analysis possibilities. diff --git a/query-engine/materialized-views.mdx b/query-engine/materialized-views.mdx index 84566edf..e4856b8b 100644 --- a/query-engine/materialized-views.mdx +++ b/query-engine/materialized-views.mdx @@ -5,12 +5,12 @@ description: Materialized tables are a way to store the results of a query in a ## Overview -The **"Materialized View"** feature on Dune allows you to use an existing query's results as table in another query. This functionality enables you to build your own simple data pipeline inside of Dune. This feature is especially useful when you have a query that takes a long time to run, or when you want to use the results of a query in another query. Instead of running the same query pattern over and over again, you can run it once and then use the results in other queries. +The **"Materialized View"** feature on Dune allows you to use an existing query's results as a table in another query. This functionality enables you to build your own simple data pipeline inside of Dune. This feature is especially useful when you have a query that takes a long time to run, or when you want to use the results of a query in another query. Instead of running the same query pattern over and over again, you can run it once and then use the results in other queries. You should think of using this feature any time you run into: 1. You use the same query pattern across multiple queries -2. Query timeouts (running longer than 30 mintes) +2. Query timeouts (running longer than 30 minutes) 3. Execution Error: Stage limits (exceeding stage limits in the planning stage, can happen when joining many tables) 4. Execution Error: Memory limits (exceeding the memory limits, can happen when you use too many large tables like `solana.transactions` or `ethereum.traces`) @@ -78,7 +78,7 @@ When you query a materialized view in another query, it does not rerun the mater - A query result has a 200MB limit in the editor but a materialized view doesn't have storage limits. Even though the results will look truncated in the editor. - This materialized view refresh schedule is DIFFERENT from the query scheduler. Results from running the query or the normal query scheduler will NOT update the materialized view. - Plans have total monthly storage limits (for premium plans, it's 50GB, plus it's 15GB, free is 1MB). -- You can delete your materialized in the same dialouge where you created it. +- You can delete your materialized view in the same dialogue where you created it. - If your team or account name starts with a number, you'll need to wrap the `name` in quotes i.e. `dune."21co".result_stablecoin_total_supply_on_ethereum` - There currently is no way to nicely ensure sequential execution of materialized views. If you have a materialized view that depends on another materialized view, you'll need to ensure that the upstream materialized view is updated first. This can be done by setting the refresh schedule to be more frequent than the downstream materialized view. diff --git a/query-engine/query-a-query.mdx b/query-engine/query-a-query.mdx index 14d0292a..184bf629 100644 --- a/query-engine/query-a-query.mdx +++ b/query-engine/query-a-query.mdx @@ -130,7 +130,7 @@ The table below shows how different parameter types are passed on when using the | UINT256 | `query(uint256Key='UINT256 \'1\'')` | **Original Query**: select * from arbitrum.transactions where gas_price = `{{uint256Key}}`
**Macro**: select * from "query_123(uint256Key='uint256 \'1\'')"
**Original Query**: select * from arbitrum.transactions where gas_price = uint256 '`{{uint256Key}}`'
**Macro**: select * from "query_123(uint256Key='1')" | | INT256 | `query(int256Key='INT256 \'-1\'')` | **Original Query**: select * from arbitrum.transactions where gas_price = `{{int256Key}}`
**Macro**: select * from "query_123(int256Key='int256 \'-1\'')"
**Original Query**: select * from arbitrum.transactions where gas_price = int256 '`{{int256Key}}`'
**Macro**: select * from "query_123(int256Key='1')" | | Date, Time, Timestamp | `query(dateKey='2023-01-02')`
`query(dateKey='date \'2023-01-02\'')`
`query(dateKey='13:45:30 +05:00')`
`query(dateKey='time \'13:45:30 +05:00\'')`
`query(dateKey='2023-08-24 13:45:30 UTC')`
`query(dateKey='timestamp \'2023-08-24 13:45:30 UTC\'')` | **Original Query**: select * from ethereum.blocks where time > `{{dateKey}}`
**Macro**: select * from "query_123(dateKey='timestamp \'2023-08-24\'')"
**Original Query**: select * from ethereum.blocks where time > timestamp '`{{dateKey}}`'
**Macro**: select * from "query_123(dateKey='2023-08-24')" | -| Array | `query(arrayKey='array[1,2,3]')`
`query(arrayKey='array[uint256 \'1\', uint256 \'2\']')`
`query(arrayKey='array[\'these\', \'are\, \'varchar\]')` | **Original Query**: select * from dex_aggregator.trades where trace_address = `{{arrayKey}}`
**Macro**: select * from "query_123(arrayKey='array\[1, 2]')" | +| Array | `query(arrayKey='array[1,2,3]')`
`query(arrayKey='array[uint256 \'1\', uint256 \'2\']')`
`query(arrayKey='array[\'these\', \'are\', \'varchar\']')` | **Original Query**: select * from dex_aggregator.trades where trace_address = `{{arrayKey}}`
**Macro**: select * from "query_123(arrayKey='array\[1, 2]')" | | Boolean | `query(booleanKey='true')` | **Original Query**: select * from bitcoin.inputs where is_coinbase = `{{booleanKey}}`
**Macro**: select * from "query_123(booleanKey='false')" | | Row | `query(rowKey='row(1, uint256 \'1\', \'hi\')')` | **Original Query**: select `{{rowKey}}`
**Macro**: select * from "query_123(rowKey='row(false, 1, uint256 \'1\', \'hi\')')" | | Map | `query(mapKey='map(array[\'key1\', \'key2\'], array[\'value1\', \'value2\'])')` | **Original Query**: select `{{mapKey}}`
**Macro**: select * from "query_123(mapKey='map(array[\'key1\', \'key2\'], array[\'value1\', \'value2\'])')" | @@ -159,7 +159,7 @@ When using the "Query View" feature, consider the following best practices: 2. **Documentation**: Provide clear documentation and comments for your queries, especially when they are intended to be used as views in other queries. 3. **Modularity**: Break down complex queries into smaller, reusable components. This will make your queries more maintainable and easier to understand. 4. **Version control**: If you need to update a query that is being used as a view in other queries, consider creating a new version of the query instead of modifying the existing one. This will help prevent unexpected changes in dependent queries. -5. **Forking** If you use the query of another user as a view in your query, consider forking the query instead of querying it. That way, you will not be affected by changes made to the **Original Query**. On the other hand, you will also not be able to benefit from any improvements made to the **Original Query**. +5. **Forking**: If you use the query of another user as a view in your query, consider forking the query instead of querying it. That way, you will not be affected by changes made to the **Original Query**. On the other hand, you will also not be able to benefit from any improvements made to the **Original Query**. diff --git a/query-engine/query-executions.mdx b/query-engine/query-executions.mdx index 491a890e..562bfd25 100644 --- a/query-engine/query-executions.mdx +++ b/query-engine/query-executions.mdx @@ -7,11 +7,11 @@ description: When and how do queries on Dune get executed? **Queries on Dune need to be triggered and will be executed on one of our query engines.** -Query executions can be triggered by any user/team in Dune for public queries and by the owner of the query for private queries. Query executions can be triggered through the query editor, the dashboard editor, or via the API. We also automatically refresh popular dashboards automatically in regular intervals. +Query executions can be triggered by any user/team in Dune for public queries and by the owner of the query for private queries. Query executions can be triggered through the query editor, the dashboard editor, or via the API. We also automatically refresh popular dashboards in regular intervals. The query engine determines the amount of resources allocated to your query. The larger the query engine, the more resources are allocated to your query. This means that queries executed on a larger query engine will run faster and are less likely to time out. -## Query executions triggers +## Query execution triggers Query executions on Dune are triggered in four ways: @@ -200,13 +200,13 @@ Executions on the community engine are free of charge and will time out after 2 The medium engine is built to handle most queries on Dune. It is cheap, reliable and fast. The medium engine will scale up and down depending on the demand. Executions on the medium engine cost 10 credits. -It has a capacity equivalent to the Free engine, but executions can run for longer, timing out only after 30 minutes. +It has a capacity equivalent to the community engine, but executions can run for longer, timing out only after 30 minutes. #### Large engine size The large engine is built to handle the most resource-intensive queries on Dune. It's blazing fast, reliable and can easily deal with large amounts of data. The large engine also scales up and down depending on the demand. -In addition to that, the large engine is also the only engine that can handle queries that requires lots of planning time. This mostly happens when you query a large amount of data, when you use a lot of joins or large aggregate window functions. +In addition to that, the large engine is also the only engine that can handle queries that require lots of planning time. This mostly happens when you query a large amount of data, when you use a lot of joins or large aggregate window functions. Executions on the large engine cost 20 credits. -It has twice the capacity of the Medium engine, and executions can also run for 30 minutes. \ No newline at end of file +It has twice the capacity of the medium engine, and executions can also run for 30 minutes. \ No newline at end of file diff --git a/query-engine/reserved-keywords.mdx b/query-engine/reserved-keywords.mdx index ee5fb0f2..6e89bb0d 100644 --- a/query-engine/reserved-keywords.mdx +++ b/query-engine/reserved-keywords.mdx @@ -5,8 +5,8 @@ description: The following table lists all of the keywords that are reserved in For example to query the transactions table for all transactions from a specific address you would use the following query with `from` in double quotes: ```sql -Select * from ethereum.transactions -where "from" = 0xc8ebccc5f5689fa8659d83713341e5ad19349448 +SELECT * FROM ethereum.transactions +WHERE "from" = 0xc8ebccc5f5689fa8659d83713341e5ad19349448 ``` ## Reserved keywords diff --git a/query-engine/writing-efficient-queries.mdx b/query-engine/writing-efficient-queries.mdx index 80a5a6e2..928f05db 100644 --- a/query-engine/writing-efficient-queries.mdx +++ b/query-engine/writing-efficient-queries.mdx @@ -13,7 +13,7 @@ DuneSQL is a Trino-based query engine designed for handling data stored in a col ### Short Introduction to Databases -Let's start with a short introduction into databases so we can understand what we need to optimize for when writing queries on DuneSQL. +Let's start with a short introduction to databases so we can understand what we need to optimize for when writing queries on DuneSQL. At their core, databases are sophisticated systems designed to store, retrieve, and manage data. Their primary goal is to provide fast, efficient, and reliable access to vast amounts of structured information. You can think of a database as a collection of tables, where each table is a collection of rows and columns. Conceptually, these tables exist in two ways: @@ -79,7 +79,7 @@ SELECT * FROM ethereum.transactions WHERE hash = 0xce1f1a2dd0c10fcf9385d14bc92c686c210e4accf00a3fe7ec2b5db7a5499cff ``` -using the steps above the query engine would do the following: +Using the steps above the query engine would do the following: 1. **File Level:** The query engine tries to locate the specific parquet files associated with the table or a portion of the table being queried. It reads the metadata contained in the footer of each parquet file to determine whether it might contain the data needed for the query. It will try to skip any files that do not contain the data needed for the query. However, since the query is based on a random hash, the engine will not be able to skip any files. It will have to read all the files associated with the table. @@ -93,7 +93,7 @@ WHERE block_number = 14854616 AND hash = 0xce1f1a2dd0c10fcf9385d14bc92c686c210e4accf00a3fe7ec2b5db7a5499cff ``` -using the steps above the query engine would do the following: +Using the steps above the query engine would do the following: 1. **File Level:** The query engine tries to locate the specific parquet files associated with the table or a portion of the table being queried. It reads the metadata contained in the footer of each parquet file to determine whether it might contain the data needed for the query. In this case, the engine will check whether the `block_number` we are searching for is within the range of `min/max` values for the `block_number` column in the footer of each parquet file. For example, if the engine starts reading the first parquet file and sees that the `min/max` values for the `block_number` column are `14854600` and `14854620`, it will know that the file does not contain the data needed for the query. It will skip the file and move on to the next one. This will significantly reduce the amount of data that needs to be read into memory, which will improve query performance. @@ -110,7 +110,7 @@ The above example is pretty theoretical, as you will most likely not be querying Usually you would write a query like this: ```sql -Select +SELECT * FROM ethereum.traces WHERE to = 0x510100D5143e011Db24E2aa38abE85d73D5B2177 @@ -119,15 +119,15 @@ WHERE to = 0x510100D5143e011Db24E2aa38abE85d73D5B2177 With our new knowledge, we can deduce that this query will be very inefficient, as the engine will have to read almost all the files and row groups associated with the table. Instead, we can optimize the query by helping the engine to skip files with a `block_number` greater than a specific value. For example, if we know that the smart contract was deployed in block `17580248`, we can write the query like this: ```sql -Select - "from" - ,to - ,block_time - ,tx_hash - ,input +SELECT + "from", + to, + block_time, + tx_hash, + input FROM ethereum.traces -where block_number > 17580247 -and to = 0x510100D5143e011Db24E2aa38abE85d73D5B2177 +WHERE block_number > 17580247 +AND to = 0x510100D5143e011Db24E2aa38abE85d73D5B2177 ``` By including the `block_number` column in the query, the engine can quickly narrow down the search to files and row groups that have a `block_number` greater than `17580247`. This significantly reduces the amount of data that needs to be read, thereby improving query performance. Additionally, only querying the columns you absolutely need will also improve query performance. @@ -135,18 +135,18 @@ By including the `block_number` column in the query, the engine can quickly narr We can also apply the same principle to join tables. For example, if we want to join `ethereum.transactions` with `uniswap_v3_ethereum.Pair_evt_Swap`, we can write the query like this: ```sql -Select +SELECT to, "from", value, block_date, - sqrt_price_x96, + sqrt_price_x96 FROM uniswap_v3_ethereum.Pair_evt_Swap swap - inner join ethereum.transactions t - on swap.evt_tx_hash = t.hash - and swap.evt_block_number = t.block_number -where + INNER JOIN ethereum.transactions t + ON swap.evt_tx_hash = t.hash + AND swap.evt_block_number = t.block_number +WHERE swap.contract_address = 0x510100D5143e011Db24E2aa38abE85d73D5B2177 ``` @@ -155,21 +155,21 @@ By including the `block_number` column in the join condition, the engine can qui It also makes a difference whether we join `ethereum.transactions` to `uniswap_v3_ethereum.Pair_evt_Swap` or the other way around. The following query will be even faster: ```sql -Select +SELECT to, "from", value, block_time, sqrt_price_x96 FROM ethereum.transactions t -inner join uniswap_v3_ethereum.Pair_evt_Swap swap - on t.hash = swap.evt_tx_hash - and t.block_number = swap.evt_block_number -where +INNER JOIN uniswap_v3_ethereum.Pair_evt_Swap swap + ON t.hash = swap.evt_tx_hash + AND t.block_number = swap.evt_block_number +WHERE swap.contract_address = 0x510100D5143e011Db24E2aa38abE85d73D5B2177 ``` - Using `block_date` is often better than using `block_number` or `block_time` as there are less distinct values to check against. Use `block_date` during joins where it is possible.{" "} + Using `block_date` is often better than using `block_number` or `block_time` as there are fewer distinct values to check against. Use `block_date` during joins where it is possible. This join order optimization is related to the size of the tables. **You should always join the smaller table on the bigger table**. In this case, `ethereum.transactions` is much bigger than `uniswap_v3_ethereum.Pair_evt_Swap`, so we should join `uniswap_v3_ethereum.Pair_evt_Swap` with `ethereum.transactions`. @@ -193,7 +193,7 @@ In addition to leveraging the columnar storage format and using sequentially ord 5. **Use window functions**: Window functions can be more efficient than self-joins or subqueries for computing aggregations over a set of rows related to the current row. -6. **Avoid using DISTINCT when possible**: DISTINCT can be computationally expensive, especially on large datasets. Trino has implemented a range of [**approximate aggregate functions**](/query-engine/Functions-and-operators/aggregate#approximate-aggregate-functions) functions that can be used to get a good estimate of the distinct values in a column with a much lower computational cost. +6. **Avoid using DISTINCT when possible**: DISTINCT can be computationally expensive, especially on large datasets. Trino has implemented a range of [**approximate aggregate functions**](/query-engine/Functions-and-operators/aggregate#approximate-aggregate-functions) that can be used to get a good estimate of the distinct values in a column with a much lower computational cost. 7. **Use `UNION ALL` instead of `UNION`**: If you're combining the results of multiple queries, use `UNION ALL` instead of `UNION` to avoid the overhead of removing duplicate rows. diff --git a/quickstart.mdx b/quickstart.mdx index 53ff0992..c7a8ef77 100644 --- a/quickstart.mdx +++ b/quickstart.mdx @@ -58,12 +58,12 @@ Begin by constructing the SQL queries you need using Dune's **Query Editor**, a - Analyze daily activity on Ethereum by entering the following SQL: ```sql ---Query to get Ethereum's unique daily active users and passive users in 2023 +--Query to get Ethereum's unique daily active users and passive users in 2023 SELECT --truncate time to day date_trunc('day', block_time) AS time, --- count distinct addresses that sent a transactions +-- count distinct addresses that sent transactions COUNT(distinct "from") AS users, -- count distinct addresses that received a transaction COUNT(distinct "to") AS receiving_addresses @@ -92,7 +92,7 @@ After executing a query, the results are displayed in a table below the Query Ed - Adjust the settings to suit your visualization needs, such as formatting axis labels and tick marks to enhance readability. -In the example below, we'll create a line chart to visualize the number of unique daily active users and passive users on Ethereum in 2023. We'll format the axis label and tick label to `0a`to make the numbers more user-friendly. +In the example below, we'll create a line chart to visualize the number of unique daily active users and passive users on Ethereum in 2023. We'll format the axis label and tick label to `0a` to make the numbers more user-friendly.
( }} />
- Datatypes on Snowflake datashare are different in some cases, read more here. + Datatypes on Snowflake data share are different in some cases, read more here. ); diff --git a/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx b/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx index 0ee6fb25..840fbb32 100644 --- a/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx +++ b/snippets/curated-data/dex/embeds/dex-aggregator-coverage.mdx @@ -1,7 +1,7 @@ export const DexAggregatorCoverage = ({ blockchain }) => (
` + ``` A great showcase for this is the [cryptoart.io](https://cryptoart.io/data) website. @@ -49,7 +49,7 @@ Dune Visualizations can easily be embedded into articles on mirror.xyz. Simply g ```html -https://dune.com/embeds/208941/391702/34ee3319-1cac-40e1-a08d-160bd93693cc?display=iframe` +https://dune.com/embeds/208941/391702/34ee3319-1cac-40e1-a08d-160bd93693cc?display=iframe ``` ### Known Issues @@ -67,7 +67,7 @@ The embed link you generate won't include the necessary parameters yet, even if We are working on automating this, but for now you'll need to manually prefix the parameter link with the parameters: -`link?[name_of_parameter_1]=[xxxx]&?[name_of_parameter_2]=[yyyy]&[...]` +`link?[name_of_parameter_1]=[xxxx]&[name_of_parameter_2]=[yyyy]&[...]` Here is a working example: ``` diff --git a/web-app/overview.mdx b/web-app/overview.mdx index b78ead3a..9e8a45d7 100644 --- a/web-app/overview.mdx +++ b/web-app/overview.mdx @@ -32,7 +32,7 @@ Explore the multitude of features within the Dune Web App that streamline your j Spread your findings and dashboards with the community or stakeholders seamlessly. - + Quickly locate the data you need with our powerful search capabilities. diff --git a/web-app/query-editor/data-explorer.mdx b/web-app/query-editor/data-explorer.mdx index 2697051e..dc7b7726 100644 --- a/web-app/query-editor/data-explorer.mdx +++ b/web-app/query-editor/data-explorer.mdx @@ -49,7 +49,7 @@ Here is a simple example of how to use the Data Explorer to find the data you ne You can also search for specific tables in the Data Explorer. 1. Choose the "decoded projects" category. -2. Type the projects name in the search bar. +2. Type the project's name in the search bar. 3. Choose the project you want to explore. 4. Type the smart contract name in the search bar. 5. Choose the smart contract you want to explore. diff --git a/web-app/query-editor/index.mdx b/web-app/query-editor/index.mdx index 54430876..fb5bc5ee 100644 --- a/web-app/query-editor/index.mdx +++ b/web-app/query-editor/index.mdx @@ -11,7 +11,7 @@ description: Learn more about how Dune's Query Editor works here! iconType="duotone" href="/web-app/query-editor/query-window" > - The Query Editor is where you work your Dune by inputting SQL code and + The Query Editor is where you work on Dune by inputting SQL code and running it. ### Start of a new version diff --git a/web-app/search.mdx b/web-app/search.mdx index 98ae8bf0..f7ab66f7 100644 --- a/web-app/search.mdx +++ b/web-app/search.mdx @@ -39,7 +39,7 @@ These are the filters we currently support: | `created_before` | Only include matches created before or at a given date. | `created_before:2023-01-30` | | `created_after` | Only include matches created after or at a given date. | `created_after:2023-01-30` | | `updated_before` | Only include matches updated before or at a given date. | `updated_before:2023-01-30` | -| `updated_after` | Only include matches updated before or at a given date. | `updated_after:2023-01-30` | +| `updated_after` | Only include matches updated after or at a given date. | `updated_after:2023-01-30` | Notes: diff --git a/web-app/teams.mdx b/web-app/teams.mdx index 4ac17b67..9a2504cd 100644 --- a/web-app/teams.mdx +++ b/web-app/teams.mdx @@ -39,7 +39,7 @@ Team Queries and Dashboards are created the same way they are for individual acc ## Switching Contexts -Once you are member of a team, you can switch between your personal context and your Team context. Accordingly, the "my creations" page will show your personal creations or your team's creations. +Once you are a member of a team, you can switch between your personal context and your Team context. Accordingly, the "my creations" page will show your personal creations or your team's creations. Additionally, all queries and dashboards created in the team context will be owned by the team and not by you personally. ![](/web-app/images/context-switcher.jpeg) @@ -56,7 +56,7 @@ In the [Version History](/web-app/query-editor/version-history) edits you make w Private dashboards and queries are available for the team or personal account they are in. - You have to ask one of your team admins. If you're an admin, you will still have to ask another admin or upgrade someone else to the admin role. That's to ensure every team always has at least an admin. + You have to ask one of your team admins. If you're an admin, you will still have to ask another admin or upgrade someone else to the admin role. That's to ensure every team always has at least one admin. Yes, you can remove people from your Team in the People section of your Team’s Settings page. diff --git a/web-app/upload-data.mdx b/web-app/upload-data.mdx index 6c5b5c8e..2f02685f 100644 --- a/web-app/upload-data.mdx +++ b/web-app/upload-data.mdx @@ -5,7 +5,7 @@ description: Upload your own data to Dune **Easily upload your own data to Dune** -This feature allows you to upload any csv file to Dune and query it like any other table in Dune. Currently, we only supports uploading CSV files with a maximum size of 200 MB. The app will return an error if the file size exceeds this limit. +This feature allows you to upload any csv file to Dune and query it like any other table in Dune. Currently, we only support uploading CSV files with a maximum size of 200 MB. The app will return an error if the file size exceeds this limit. Additionally, column names in the table can't start with a special character or digits. The files you upload will be queryable via the schema ``dune.team_name.dataset_name``. For example, if you upload a file called ``energy_data.csv`` to the team ``dune`` and name the dataset ``energy_data``, you will be able to query the data via ``dune.dune.energy_data``. @@ -144,13 +144,13 @@ You can delete your data via your settings page. 3. Find the dataset you want to delete. 4. Click on the three dots to open the options for the dataset. 5. Click on "delete dataset". -6. confirm the deletion. +6. Confirm the deletion. 7. The dataset is now deleted. ## Large Amounts of Data -If you want to share valuable off-chain data on Dune with your community, we are happy to discuss custom arrangements. Please reach indicate your interest via this [form](https://bit.ly/dune-data-integration). +If you want to share valuable off-chain data on Dune with your community, we are happy to discuss custom arrangements. Please indicate your interest via this [form](https://bit.ly/dune-data-integration). This is only applicable for datasets with positive externalities for the Dune community. Examples include: diff --git a/web-app/user-activity.mdx b/web-app/user-activity.mdx index b6cd5b86..93d2166f 100644 --- a/web-app/user-activity.mdx +++ b/web-app/user-activity.mdx @@ -32,6 +32,6 @@ Each action counts as one contribution for that day. For example, if you: - Create 1 dashboard - Submit 1 contract -Your total activity for that day would be 5 contribution. +Your total activity for that day would be 5 contributions. The activity heatmap shows your daily activity over time, helping you track your contributions to the Dune ecosystem. diff --git a/web-app/visualizations/charts-graphs.mdx b/web-app/visualizations/charts-graphs.mdx index 56c06642..aec723da 100644 --- a/web-app/visualizations/charts-graphs.mdx +++ b/web-app/visualizations/charts-graphs.mdx @@ -62,12 +62,12 @@ All graph Visualizations share a common set of editing options, see the tabs bel * If applicable, ticking this box will stack the chart values on top of each other based on the x-axis values. * If this is not turned on, the values will be plotted individually on the y-axis. - * The calculation underpinning this will always group the value corresponding to one value on the x-axis. Make sure your data is clean in able for this to work (avoid gaps in your data). + * The calculation underpinning this will always group the value corresponding to one value on the x-axis. Make sure your data is clean in order for this to work (avoid gaps in your data). **Normalize to percentage data** * This will normalize the chart to display percentage values of the chosen data table. - * The calculation underpinning this will always group the value corresponding to one value on the x-axis. Make sure your data is clean in able for this to work (avoid gaps in your data). + * The calculation underpinning this will always group the value corresponding to one value on the x-axis. Make sure your data is clean in order for this to work (avoid gaps in your data). **Show data labels** @@ -96,7 +96,7 @@ All graph Visualizations share a common set of editing options, see the tabs bel **Sort Values** - * by ticking this box you can specify if you want the values in your chart to be ordered. + * By ticking this box you can specify if you want the values in your chart to be ordered. * If your x-axis is a time series, this will automatically happen. **Reverse value** @@ -105,11 +105,11 @@ All graph Visualizations share a common set of editing options, see the tabs bel **Logarithmic** - * Ticking this box will make your x-axis values display \_\_ logarithmically. + * Ticking this box will make your x-axis values display logarithmically. - With these options you can influence how your x-axis data gets displayed. + With these options you can influence how your y-axis data gets displayed. ![see explanations below](web-app/images/charts-graphs/graphs-7.png) @@ -119,7 +119,7 @@ All graph Visualizations share a common set of editing options, see the tabs bel **Logarithmic** - * Ticking this box will make your x-axis values display \_\_ logarithmically. + * Ticking this box will make your x-axis values display logarithmically. **Enable right y-axis** @@ -164,9 +164,9 @@ Here's how to format them: | Starting Value | Tick/Label format | Output | Description | | ------------ | ----------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| 1256784.3745 | `[blank]` | 1256784.3745000 | Displays the number 7 decimal precision. | +| 1256784.3745 | `[blank]` | 1256784.3745000 | Displays the number with 7 decimal precision. | | 1256784.3745 | `0` | 1256784 | Displays only the integer. | | 1256784.3745 | `0,0` | 1,256,784 | Only displays the integer with comma separation. | -| 1256784.3745 | `0,0.00` | 1,256,784.38 | Displays the number with `[x]` decimal precision, where `[x]` is the number of `0` you add after the decimal point. | +| 1256784.3745 | `0,0.00` | 1,256,784.38 | Displays the number with `[x]` decimal precision, where `[x]` is the number of `0`s you add after the decimal point. | | 1256784.3745 | `0.0a` | 1.2M | Displays the number with `[x]` precision and a letter based on the number's `1e[y]` power (eg "m" for million, "b" for billion) | -| 1256784.3745 | `$0.0a` | $1.2M | Adds a "\$" to the number. Works with all formats above though use of the `a` suffix is recommended. Currently the only "\$" is the only supported currency symbol. | +| 1256784.3745 | `$0.0a` | $1.2M | Adds a "\$" to the number. Works with all formats above though use of the `a` suffix is recommended. Currently "\$" is the only supported currency symbol. | diff --git a/web-app/visualizations/counters.mdx b/web-app/visualizations/counters.mdx index ead8f342..9c83a42b 100644 --- a/web-app/visualizations/counters.mdx +++ b/web-app/visualizations/counters.mdx @@ -15,7 +15,7 @@ Counters are a great way to provide your audience with immediate "on a glance" s #### Counter options -In this section you can define what kind of data the counter should display: +In this section, you can define what kind of data the counter should display: * The Title will appear in all instances of this graph prominently at the top. diff --git a/web-app/visualizations/tables.mdx b/web-app/visualizations/tables.mdx index 92772d2f..5f03d9e9 100644 --- a/web-app/visualizations/tables.mdx +++ b/web-app/visualizations/tables.mdx @@ -8,7 +8,7 @@ description: Tables are a way to display your data in a tabular format. ![query results table example](/web-app/images/other-visualizations/query-results-table-example.png) -You can also make more Tables to display your data differently using the New visualization button and drop down menu: +You can also make more Tables to display your data differently using the New visualization button and dropdown menu: ![new table visualization](/web-app/images/other-visualizations/new-table-visualization.png) diff --git a/zz_unused/conduct-network-analysis.mdx b/zz_unused/conduct-network-analysis.mdx index cc60d7cb..d1cb3dd8 100644 --- a/zz_unused/conduct-network-analysis.mdx +++ b/zz_unused/conduct-network-analysis.mdx @@ -69,7 +69,7 @@ To build a network, we need nodes and their relationships. Refer to [this Dune q - Nodes are identified by a unique "fid" (Farcaster ID). - Relationships (edges) between nodes are based on four actions: follow, like, repost, and comment. - Interaction weights are: follow = 5, like = 1, repost = 3, comment = 2. They consider directionality. -- These interactions as parameterized variables, adjust as needed. +- These interactions are parameterized variables, adjust as needed. ### Packages and Imports @@ -167,7 +167,7 @@ Adjust the timeout as necessary. There are two methods to export data from Dune and into notebook: - + Retrieve the latest result, which is faster as it bypasses execution. @@ -177,8 +177,7 @@ There are two methods to export data from Dune and into notebook: ``` - + @@ -296,7 +295,7 @@ _Again, above is a brief code snippet. For the comprehensive version, visit the Visualization enhances any analysis, but visualizing extensive networks like ours can be a maze. Let's navigate two visualization paths you can adapt further: -- In Gephi: [Gephi](https://gephi.org/) is a good tool to presenting large networks comprehensively. Export the graph from Python with nx.write_gml(G, "file_name.gml") and dive into Gephi. Tweak node sizes, colors, and labels to distill insights. +- In Gephi: [Gephi](https://gephi.org/) is a good tool for presenting large networks comprehensively. Export the graph from Python with nx.write_gml(G, "file_name.gml") and dive into Gephi. Tweak node sizes, colors, and labels to distill insights. - In Python notebook: for a more focused lens, visualize the top 200 nodes by degree with NetworkX. Node color denotes out-degree: a blue node engages less, while a red one is more active. Node size illustrates in-degree, reflecting the interactions received. diff --git a/zz_unused/create-sankey-diagram.mdx b/zz_unused/create-sankey-diagram.mdx index 9d8cc6b3..9c119e94 100644 --- a/zz_unused/create-sankey-diagram.mdx +++ b/zz_unused/create-sankey-diagram.mdx @@ -10,12 +10,9 @@ While Dune's ability to easily execute queries and make visualizations are prett here](https://github.com/duneanalytics/dune-client) and installed by doing `pip install dune-client` -## 🎓 What is a Sankey Diagram? Sankey diagrams are flow diagrams in which the width -of the arrows or lines are proportional to the flow quantity they represent. They're -commonly used to depict the flow of energy, material, or costs between stages. So -if you've been longing to visualize the movement of tokens between wallets, or how -users transition between different app states, a Sankey diagram is your weapon of -choice! +## 🎓 What is a Sankey Diagram? + +Sankey diagrams are flow diagrams in which the width of the arrows or lines are proportional to the flow quantity they represent. They're commonly used to depict the flow of energy, material, or costs between stages. So if you've been longing to visualize the movement of tokens between wallets, or how users transition between different app states, a Sankey diagram is your weapon of choice! For a deeper dive, [check this article](https://medium.com/@twelsh37/understanding-plotly-sankey-charting-3ee263a81549). @@ -28,21 +25,27 @@ The key components for a Sankey are: ## ⛲ Let's Generate that Sankey! -Here, we will walk through two examples. Example 1 is to graph a Sankey for a certain subset of RabbitHole Quests with Optimism grant, see how the questors are retained after 1-month period. Example 2 is to graph a Sankey for the token flow when swapping USDC for WETH using Uniswap if the swap is not direct. +Here, we will walk through two examples. Example 1 is to graph a Sankey for a certain subset of RabbitHole Quests with Optimism grant, to see how the questors are retained after a 1-month period. Example 2 is to graph a Sankey for the token flow when swapping USDC for WETH using Uniswap if the swap is not direct. -We will show you different ways to fetch data from Dune API in the process as well. +We will show you different ways to fetch data from the Dune API in the process as well. ### 1. Setup Import all necessary libraries and authenticate to set up DuneClient. - 1. Make sure you create have a .env file created with your 'DUNE_API_KEY' in + 1. Make sure you have a .env file created with your 'DUNE_API_KEY' in it! 2. Replace the path to your own directory in `os.chdir(...)` -``` py import pandas as pd import plotly.graph_objects as go import colorlover as -cl import pandas as pd import dotenv, os, json from dune_client.types import QueryParameter -from dune_client.client import DuneClient from dune_client.query import QueryBase +``` py +import pandas as pd +import plotly.graph_objects as go +import colorlover as cl +import pandas as pd +import dotenv, os, json +from dune_client.types import QueryParameter +from dune_client.client import DuneClient +from dune_client.query import QueryBase # change the current working directory where .env file lives diff --git a/zz_unused/hosted.mdx b/zz_unused/hosted.mdx index a3468b96..46004c0c 100644 --- a/zz_unused/hosted.mdx +++ b/zz_unused/hosted.mdx @@ -51,7 +51,7 @@ There are three components in the toolkit. The blockchain team or a RaaS provide 2. **Node Indexer**: Does the heavy lifting of indexing the chain data and sending it to Dune - Provided as a [Docker image](https://github.com/duneanalytics/node-indexer) in Dune’s registry - - Run by the customer/RAAS on their preferred platform + - Run by the customer/RaaS on their preferred platform - Configured to connect to the specific RPC node and stack (e.g., OP) - Makes relevant RPC calls (`eth_getBlockReceipts`, `debug_traceBlockByNumber`, `eth_getBlockByNumber`) - Forwards data to the Dune API @@ -60,7 +60,7 @@ There are three components in the toolkit. The blockchain team or a RaaS provide 3. **Blockchain Endpoints**: - API that accepts RPC call responses, transforms the data to match Dune’s schema, and uploads it continuously to Dune - Creates four raw tables on Dune: `.blocks`, `.transactions`, `.traces`, `.logs` -Your team or a RaaS provider only needs to spin up the Node Indexer. It will handle writing to the Blockchain endpoints and transforming the RPC calls into predefined raw tables with schemas for EVM chains. +Your team or RaaS provider only needs to spin up the Node Indexer. It will handle writing to the Blockchain endpoints and transforming the RPC calls into predefined raw tables with schemas for EVM chains. ## Considerations diff --git a/zz_unused/transfers/erc1155-transfers.mdx b/zz_unused/transfers/erc1155-transfers.mdx index 8fd94b46..0bb6b852 100644 --- a/zz_unused/transfers/erc1155-transfers.mdx +++ b/zz_unused/transfers/erc1155-transfers.mdx @@ -21,4 +21,4 @@ import { ColumnDescriptions } from "/snippets/column-descriptions.mdx"; import { TableSample } from "/snippets/table-sample.mdx"; - + diff --git a/zz_unused/transfers/erc20-transfers.mdx b/zz_unused/transfers/erc20-transfers.mdx index 7d5b6efa..d019c659 100644 --- a/zz_unused/transfers/erc20-transfers.mdx +++ b/zz_unused/transfers/erc20-transfers.mdx @@ -7,7 +7,7 @@ description: Event logs for ERC20 token transfers on the Ethereum blockchain. ## Table description This table captures all `Transfer` event logs for ERC20 token transfers on its respective EVM blockchain. -This log is emitted when a `transfer` or `TransferFrom` function is successfully called on an ERC20 token contract. +This log is emitted when a `transfer` or `transferFrom` function is successfully called on an ERC20 token contract. The table schema is always `erc20_{chain}.evt_Transfer` where `chain` is the respective EVM chain. diff --git a/zz_unused/transfers/erc721-transfers.mdx b/zz_unused/transfers/erc721-transfers.mdx index 32917c7a..6263988e 100644 --- a/zz_unused/transfers/erc721-transfers.mdx +++ b/zz_unused/transfers/erc721-transfers.mdx @@ -7,7 +7,7 @@ description: Event logs for ERC721 token transfers on the Ethereum blockchain. ## Table description This table captures all `Transfer` event logs for ERC721 token transfers on the Ethereum blockchain. -This log is usually emitted when a `transfer` or `TransferFrom` function is called successfully on an ERC721 token contract. +This log is usually emitted when a `transfer` or `transferFrom` function is called successfully on an ERC721 token contract. The table schema is always `erc721_{chain}.evt_Transfer` where `chain` is the respective EVM chain.