column name
| description | +| ------------------------- | --------------------------------------------- | +| contract\_address | the contract address of the erc20 token | +| symbol | the identifier of the asset (ticker, cashtag) | +| price | the price of the asset in any given minute | +| minute | the resolution for this table is by minute | + +Note that `WETH` can be used for ETH price. + +**prices.layer\_1usd** + +This table also supports layer 1 assets on other blockchains. + +| column name | description | +| ----------------- | --------------------------------------------- | +| contract\_address | the contract address of the erc20 token | +| symbol | the identifier of the asset (ticker, cashtag) | +| price | the price of the asset in any given minute | +| minute | the resolution for this table is by minute | + +**** + +**dex.view\_token\_prices** + +We created a decentralized price feed that calculates prices based on decentralized exchange trading data. **This table covers much more assets than prices.usd.** This table is very resource intensive and can therefore only be updated every few hours, please keep that in mind when utilizing it. + +This table currently only exists for Ethereum data. + +| column name | description | +| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| contract\_address | the contract address of the erc20 token | +| sample\_size | the number of trades that occurred for this asset on all decentralized exchanges (If the number is very small you might want to exclude the data, it can lead to inaccuracies). | +| median\_price | the median price of the asset in any given hour | +| hour | the resolution for this table is hourly | + + + diff --git a/data-tables/data-tables/raw-data/README.md b/data-tables/data-tables/raw-data/README.md new file mode 100644 index 0000000..87dc82b --- /dev/null +++ b/data-tables/data-tables/raw-data/README.md @@ -0,0 +1,17 @@ +# Raw Data + +{% content-ref url="ethereum-data.md" %} +[ethereum-data.md](ethereum-data.md) +{% endcontent-ref %} + +{% content-ref url="xdai-data.md" %} +[xdai-data.md](xdai-data.md) +{% endcontent-ref %} + +{% content-ref url="../solana-data/" %} +[solana-data](../solana-data/) +{% endcontent-ref %} + + + +### diff --git a/data-tables/data-tables/raw-data/ethereum-data.md b/data-tables/data-tables/raw-data/ethereum-data.md new file mode 100644 index 0000000..4d9d06e --- /dev/null +++ b/data-tables/data-tables/raw-data/ethereum-data.md @@ -0,0 +1,110 @@ +--- +description: >- + Our Database automatically picks up different aspects of every transaction on + the Ethereum Blockchain and parses them into different tables depending on + which aspect that table is focused on. +--- + +# Ethereum data + +## Ethereum.Blocks + +| **Column Name** | **datatype** | **Description** | +| ------------------- | ------------ | ---------------------------------------------------------------------------------------- | +| time | timestamptz | the time when the block was mined. | +| number | numeric | the length of the blockchain in blocks | +| hash | bytea | a unique identifier for that block | +| parent hash | bytea | the unique identifier for the prior block | +| gas\_limit | numeric | the gas limit of the current block | +| gas\_used | numeric | the gas used in this block | +| miner | bytea | the address of the miner | +| difficulty | numeric | the effort required to mine the block | +| total\_difficulty | numeric | total difficulty of the chain until this block | +| nonce | bytea | the block nonce is used to demonstrate the proof of work during mining | +| size | numeric | this block's size in bytes (limited by gas limit) | +| base\_fee\_per\_gas | numeric | this block's base fee (introduced by [EIP1559](https://eips.ethereum.org/EIPS/eip-1559)) | + +## Ethereum.Logs + +This Table stores all logs that get generated by smart contracts. It is sometimes useful for querying contracts that are not yet decoded or are resistant to being decoded(we need an abi key for that). + +Logs are an elegant way to store tiny amounts of data on the Ethereum blockchain for a small price. Specifically, event logs are useful to let other people know something has happened without them having to query contracts individually. + +For more on this topic read [this article](https://medium.com/mycrypto/understanding-event-logs-on-the-ethereum-blockchain-f4ae7ba50378). + +| **Column Name** | **datatype** | **Description** | +| ----------------- | ------------ | ------------------------------------------------ | +| block\_hash | bytea | a unique identifier for that block | +| block\_number | int8 | the length of the blockchain in blocks | +| block\_time | timestamptz | the time when the block was mined | +| contract\_address | bytea | The address of the contract that emitted the log | +| data | bytea | event data | +| topic1 | bytea | indexed _keys_ of the event | +| topic2 | bytea | indexed _keys_ of the event | +| topic3 | bytea | indexed _keys_ of the event | +| topic4 | bytea | indexed _keys_ of the event | +| index | numeric | the transactions index position in the block | +| tx\_hash | bytea | the transaction hash of the event | +| tx\_index | numeric | the index of the transaction | + +[**Take a look for yourself**](https://dune.xyz/queries/38957) + +## Ethereum.Transactions + +| **Column Name** | **datatype** | **Description** | +| ---------------------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| block\_time | timestamptz | the time when the block was mined | +| nonce | numeric | the transaction nonce, unique to that wallet | +| index | numeric | the transactions index position in the block | +| success | boolean | a true/false value that shows if the transaction suceeded | +| from | bytea | address of the sender | +| to | bytea | address of the receiver. Null when its a contract creation transaction | +| value | numeric | the amount of ether sent in this transaction in wei. note that erc20 tokens do not show up here. | +| block\_number | int8 | the length of the blockchain in blocks | +| block\_hash | bytea | a unique identifier for that block | +| gas\_limit | numeric | the gas limit in wei | +| gas\_price | numeric | the gas price in wei | +| gas\_used | numeric | the gas consumed by the transaction in wei | +| data | bytea | event data | +| hash | bytea | the hash of the transaction | +| type | text | the type of the transaction: `Legacy, AccessList,` or`DynamicFee` | +| access\_list | jsonb | a list of addresses and storage keys the transactions intends to access. See [EIP2930](https://eips.ethereum.org/EIPS/eip-2930). Applicable if the transaction is of type `AccessList` or `DynamicFee` | +| max\_fee\_per\_gas | numeric | the maximum fee per gas the transaction sender is willing to pay total (introduced by [EIP1559](https://eips.ethereum.org/EIPS/eip-1559)) | +| max\_priority\_fee\_per\_gas | numeric | maximum fee per gas the transaction sender is willing to give to miners to incentivize them to include their transaction (introduced by [EIP1559](https://eips.ethereum.org/EIPS/eip-1559)) | +| priority\_fee\_per\_gas | numeric | the priority fee paid out to the miner for this transaction (introduced by [EIP1559](https://eips.ethereum.org/EIPS/eip-1559)) | + +\*\*\*\*[**Take a look for yourself**](https://dune.xyz/queries/38964)\*\*\*\* + +## Ethereum.Traces + +Transactions can trigger smaller atomic actions that modify the internal state of the Ethereum Virtual Machine. Information about the execution of these actions is logged and can be found stored as an EVM execution trace, or just a _trace_. + +Read more [here](https://medium.com/chainalysis/ethereum-traces-not-transactions-3f0533d26aa). + +| **Column Name** | **datatype** | **Description** | +| --------------- | ------------ | ------------------------------------------------------------------------------------------------- | +| block\_time | timestamptz | the time when the block was mined | +| tx\_success | boolean | a true/false value that shows if the transaction succeeded | +| success | boolean | a true/false value that shows if the trace action succeeded | +| block\_hash | bytea | a unique identifier for that block | +| block\_number | int8 | the length of the blockchain in blocks | +| tx\_hash | bytea | the transaction hash of the event | +| from | bytea | address of the sender | +| to | bytea | address of the receiver. Null when its a contract creation transaction | +| value | numeric | the amount of ether sent in this transaction in wei. note that erc20 tokens do not show up here. | +| gas | numeric | | +| gas\_used | numeric | the gas consumed by the transaction in wei | +| tx\_index | numeric | the index of the transaction | +| trace\_address | array | address of the trace within the call graph forest. E.g., \[0, 2, 1] is a parent of \[0, 2, 1, 0]. | +| sub\_traces | numeric | number of children of a trace | +| type | text | type of action | +| address | bytea | the contract that is called when the type is suicide or create | +| code | bytea | | +| call\_type | bytea | the type of the call | +| input | bytea | | +| output | bytea | | +| refund\_address | bytea | | + +\*\*\*\*[**Take a look for yourself**](https://dune.xyz/queries/38730)\*\*\*\* + +**You probably won’t use these too much when doing analysis with Dune (see** [**decoded data**](../decoded-data.md)**), but it’s always nice to have just in case.** diff --git a/data-tables/data-tables/raw-data/xdai-data.md b/data-tables/data-tables/raw-data/xdai-data.md new file mode 100644 index 0000000..e5ccf36 --- /dev/null +++ b/data-tables/data-tables/raw-data/xdai-data.md @@ -0,0 +1,93 @@ +# xDai Data + +### xDai.Blocks + +| **Column Name** | **datatype** | **Description** | +| ----------------- | ------------ | ---------------------------------------------------------------------- | +| time | timestamptz | the time when the block was mined. | +| number | numeric | the length of the blockchain in blocks | +| hash | bytea | a unique identifier for that block | +| parent hash | bytea | the unique identifier for the prior block | +| gas\_limit | numeric | the gas limit of the current block | +| gas\_used | numeric | the gas used in this block | +| miner | bytea | the address of the miner | +| difficulty | numeric | the effort required to mine the block | +| total\_difficulty | numeric | total difficulty of the chain until this block | +| nonce | bytea | the block nonce is used to demonstrate the proof of work during mining | +| size | numeric | this block's size in bytes (limited by gas limit) | + +### + +### xDai.Logs + +This Table stores all logs that get generated by smart contracts. It is sometimes useful for querying contracts that are not yet decoded or are resistant to being decoded(we need an abi key for that). + +Logs are an elegant way to store tiny amounts of data on the Ethereum blockchain for a small price. Specifically, event logs are useful to let other people know something has happened without them having to query contracts individually. + +For more on this topic read [this article](https://medium.com/mycrypto/understanding-event-logs-on-the-ethereum-blockchain-f4ae7ba50378). + +| **Column Name** | **datatype** | **Description** | +| ----------------- | ------------ | ------------------------------------------------ | +| block\_hash | bytea | a unique identifier for that block | +| block\_number | int8 | the length of the blockchain in blocks | +| block\_time | timestamptz | the time when the block was mined | +| contract\_address | bytea | The address of the contract that emitted the log | +| data | bytea | event data | +| topic1 | bytea | indexed _keys_ of the event | +| topic2 | bytea | indexed _keys_ of the event | +| topic3 | bytea | indexed _keys_ of the event | +| topic4 | bytea | indexed _keys_ of the event | +| index | numeric | the transactions index position in the block | +| tx\_hash | bytea | the transaction hash of the event | +| tx\_index | numeric | the index of the transaction | + +### xDai.Transactions + +| **Column Name** | **datatype** | **Description** | +| --------------- | ------------ | ------------------------------------------------------------------------------------------------ | +| block\_time | timestamptz | the time when the block was mined | +| nonce | numeric | the transaction nonce, unique to that wallet | +| index | numeric | the transactions index position in the block | +| success | boolean | a true/false value that shows if the transaction suceeded | +| from | bytea | address of the sender | +| to | bytea | address of the receiver. Null when its a contract creation transaction | +| value | numeric | the amount of ether sent in this transaction in wei. note that erc20 tokens do not show up here. | +| block\_number | int8 | the length of the blockchain in blocks | +| block\_hash | bytea | a unique identifier for that block | +| gas\_limit | numeric | the gas limit in wei | +| gas\_price | numeric | the gas price in wei | +| gas\_used | numeric | the gas consumed by the transaction in wei | +| data | bytea | event data | +| hash | bytea | the hash of the transaction | + +### xDai.Traces + + Transactions can trigger smaller atomic actions that modify the internal state of the Ethereum Virtual Machine. Information about the execution of these actions is logged and can be found stored as an EVM execution trace, or just a _trace_.\ +\ +Read more [here](https://medium.com/chainalysis/ethereum-traces-not-transactions-3f0533d26aa). + +| **Column Name** | **datatype** | **Description** | +| --------------- | ------------ | ------------------------------------------------------------------------------------------------ | +| block\_time | timestamptz | the time when the block was mined | +| tx\_success | boolean | a true/false value that shows if the transaction succeeded | +| success | boolean | a true/false value that shows if the trace action succeeded | +| block\_hash | bytea | a unique identifier for that block | +| block\_number | int8 | the length of the blockchain in blocks | +| tx\_hash | bytea | the transaction hash of the event | +| from | bytea | address of the sender | +| to | bytea | address of the receiver. Null when its a contract creation transaction | +| value | numeric | the amount of ether sent in this transaction in wei. note that erc20 tokens do not show up here. | +| gas | numeric | | +| gas\_used | numeric | the gas consumed by the transaction in wei | +| tx\_index | numeric | the index of the transaction | +| trace\_address | | | +| sub\_traces | | | +| type | text | type of action | +| address | bytea | the contract that is called when the type is suicide or create | +| code | bytea | | +| call\_type | bytea | the type of the call | +| input | bytea | | +| output | bytea | | +| refund\_address | bytea | | + +**You probably won’t use these too much when doing analysis with Dune (see** [**decoded data**](../decoded-data.md)**), but it’s always nice to have just in case.** diff --git a/data-tables/data-tables/solana-data/README.md b/data-tables/data-tables/solana-data/README.md new file mode 100644 index 0000000..2578bd4 --- /dev/null +++ b/data-tables/data-tables/solana-data/README.md @@ -0,0 +1,158 @@ +--- +description: >- + Our database automatically pulls in raw data from the Solana Blockchain and + parses them into different tables depending on which aspect that table is + focused on. +--- + +# Solana Data + +All of the tables below are built in an updated version of the Dune platform that will require a slight change to how wizards write queries in the platform. The new data platform leverages spark to increase query speed, data scale, and to support multi-chain queries. + +A reference document to use as you start to query the Solana tables is available here: + +{% embed url="https://spark.apache.org/docs/latest/sql-ref-ansi-compliance.html" %} + +## Solana.blocks + +This table contains the block data within Solana’s blockchain. It can be used to identify block activity and transaction changes over time. + +Query examples can be found here: [Solana blocks over time](https://dune.xyz/queries/389979) and [Transactions per day](https://dune.xyz/queries/390045) + +| Column Name | Column Type | Description | +| ------------------------- | ----------- | --------------------------------------------------- | +| hash | string | string The hash of this block, base-58 encoded | +| height | bigint | The number of blocks beneath this block | +| slot | bigint | This block’s slot index in the ledger | +| time | timestamp | The (estimated) time this block was produced | +| date | date | Used to partition by | +| parent\_slot | bigint | The slot index of this block's parent | +| previous\_block\_\_\_hash | string | The hash of this block's parent, base-58 encoded | +| total\_transactions | bigint | The total number of transactions in this block | +| successful\_transactions | bigint | The number of successful transactions in this block | +| failed\_transactions | bigint | The number of failed transactions in this block | + +## Solana.transactions + +This table contains the transaction data within Solana’s blockchain. Most of the relevant data related to account, protocol, and program activity is available in this table. + +Query examples can be found here: [NFT transactions of popular programs past 7 days](https://dune.xyz/queries/390720/745376) and [drift-protocol overview](https://dune.xyz/bigz/drift-\(solana\)) + +| Column Name | Column Type | Description | +| -------------------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| block\_slot | bigint | This block’s slot index in the ledger | +| block\_time | timestamp | The (estimated) time this block was produced | +| block\_date | date | Event date | +| index | bigint | Index into the block’s transactions | +| fee | bigint | Fee this transaction was charged, as paid by first account | +| block\_hash | string | The hash of this block, base-58 encoded | +| error | STRUCT error | NULL if success is true. | +| required\_signatures | bigint | The total number of signatures required to make the transaction valid. | +| readonly\_signed\_\_\_accounts | bigint | The last readonly\_signed\_accounts of the signed keys are read-only accounts. | +| readonly\_unsigned\_\_\_accounts | bigint | The last readonly\_unsigned\_accounts of the unsigned keys are read-only accounts. | +| id | string | The first signature in the transaction | +| success | boolean | The transaction was valid and thus committed. | +| recent\_block\_\_\_hash | string | The hash of a recent block in the ledger, used to prevent transaction duplication and to give transactions lifetimes | +| instructions | array\\x2a7d..
(bytea)
0x2a7d...
(string)
\x2A7D...(bytea)
Works in Postgres
0x2a7d... (string)
Has to be lowercase in Spark.
Can be done via lower('0x2A7D...').
Don’t useprices.usd decimals
Get json object
differences
("takerOutputUpdate"->'deltaWei'->'value')decode(substring(("addressSet"->'baseAsset')::TEXT, 4,40), 'hex')
get_json_object(get_json_object(takerOutputUpdate,'$.deltaWei'),'$.value')'0x'
# H1## H2### H3
1. First item2. Second item3. Third item
- First item- Second item- Third item
Displays the value in an abbreviated format.
Will display decimals of the abbreviated number according to count of zeroes after the dot.
| +| 1256784.3745 | $0\[.]0a | $1.2m | Adheres to the same methods as before, but adds a $ prefix. | diff --git a/duneapp/visualizations/README.md b/duneapp/visualizations/README.md new file mode 100644 index 0000000..e2abe39 --- /dev/null +++ b/duneapp/visualizations/README.md @@ -0,0 +1,49 @@ +--- +description: Visualizations make your data come alive! +--- + +# Visualizations + +Visualizing your query results makes the results accessible and allows you to effectively communicate your findings to your audience. + +Dune offers you a variety of different visualization options: + +* bar charts +* area charts +* scatter charts +* line charts +* pie charts +* counters + +Combining these in a thoughtful manner allows you to best communicate your data to your audience. + +### Creating Visualizations + +You can create visualizations from any query results in seconds using our visualization engine. + +Simply click on the `New visualization` button and configure the visualization to your needs. + +One query can have multiple visualizations. + + + + + +**Read more about the different visualization options here:** + +{% content-ref url="graphs.md" %} +[graphs.md](graphs.md) +{% endcontent-ref %} + +{% content-ref url="counters.md" %} +[counters.md](counters.md) +{% endcontent-ref %} + +{% content-ref url="pie-charts.md" %} +[pie-charts.md](pie-charts.md) +{% endcontent-ref %} + +## What you can do with Visualizations + +Visualizations can either live on your [dashboard](../dashboards.md) or be embedded on their own using the [embedd function](../../sharing/embeds/) + diff --git a/duneapp/visualizations/counters.md b/duneapp/visualizations/counters.md new file mode 100644 index 0000000..6000991 --- /dev/null +++ b/duneapp/visualizations/counters.md @@ -0,0 +1,57 @@ +# Counters + +#### Counters are a great way to provide your audience with immediate "on a glance" stats. + +.png>) + +## Configuring your counter + +.png>) + +### Counter options + +In this section you can define what kind of data the counter should display. + +#### Title + +* The Title will appear in all instances of this graph prominently at the top +* If left blank the query name will be the only thing that is left standing + +#### Column + +* In this field you can define which column the counter should show. + +#### Row + +* This field can be used to define which row of the underlying datatable you want displayed e.g. row 1 +* Usually this requires you to sort or limit your query results in order for row 1 to show the wanted results. + +### Formatting + +**Prefix** + +* This field allows you to define a prefix for your counter value. +* e.g.: `$`, `€`, `Ξ`, `฿` + +**Suffix** + +* This field allows you to define a suffix for your counter value. + +**Label** + +* This field allows you to define a label for your counter value. +* The label will appear beneath the counter value as text. + +**Decimals** + +* In this field you can choose how many decimals you want displayed for your counter +* This is currently limited to 3 decimal places. + +### Counters explained + +Here is an example to bring some points explained earlier home. + +.png>) + +.png>) + diff --git a/duneapp/visualizations/graphs.md b/duneapp/visualizations/graphs.md new file mode 100644 index 0000000..08c9c37 --- /dev/null +++ b/duneapp/visualizations/graphs.md @@ -0,0 +1,187 @@ +--- +description: Graphs are good for condensing data points into a visualization. +--- + +# Graphs + +**Graphs are great for condensing data points into a visualization.** + +.png>) + +.png>) + +### Dune offers you to create the following graph types: + +* bar charts +* area charts +* scatter charts +* line charts + +You can mix all of these graph types together in one visualization**.**\ +**** + +### Configuring your visualizations + +All graph visualizations share a common editing schema. + +In essence, you can define your visualization in detail here. The three different sections of this are explained below. + +.png>) + +### Chart options + +This section allows you to define how to display your data. + +.png>) + +**Title** + +* The title will appear in all instances of this graph prominently at the top. +* The graph will always keep the name of the query, even if you edit this. + + + +* [ ] **Show chart legend** + + + +* Ticking this box will enable or disable the legend for the chart. + + + +* [ ] **Enable stacking** + + + +* 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). + + + +* [ ] **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). + + + +* [ ] **Show data labels** + + + +* Ticking this box leads to the display of the individual datapoints inside of the graph. +* This only makes sense in cases where you have few datapoints that are spread out far enough from each other to not overlap. + +### Result data + +Here you can pick the data points that are to be displayed. + +.png>) + +You can choose one **x-axis** and multiple **y-axis.** + +Alternatively, you can also choose one data series on the y-axis and choose to group it by a different column of your table (as shown in the example above). + +### **X-axis options** + +Using these options you can influence how your x-axis data gets displayed. + +.png>) + +**Axis title** + +* This field allows you to specify a title for your x-axis. + + + +* [ ] **Sort Values** + + + +* by ticking this box you can specify if you want the values in your chart to be ordered. +* If your x-axis is a timeseries, this will automatically happen. + + + +* [ ] **Reverse value** + + + +* Ticking this box will reverse the order of the values on the x-axis. + + + +* [ ] **Logarithmic** + + + +* Ticking this box will make your x-axis values display __ logarithmically. + +### **Y-axis options** + +With these options you can influence how your x-axis data gets displayed. + +.png>) + +**Axis title** + +* This field allows you to specify a title for your y-axis. + + + +* [ ] **Logarithmic** + + + +* Ticking this box will make your x-axis values display __ logarithmically. + + + +* [ ] **Enable right y-axis** + + + +* Ticking this box will enable an additional y-axis that you can plot values on. +* You can choose in the [chart series section](graphs.md#ordering-your-series) what you want to be displayed on the left and right axis. + +### **Tick formats** + +****.png>)**** + +Tick formats will change how values in your chart and the axis labels will get displayed. + +It follows this logic: + +| Value | Tick format | Output | Description | +| ------------ | ----------- | --------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | +| 1256784.3745 | left blank | 1256784,3745000 | Display the full number and 7 decimals | +| 1256784.3745 | 0 | 1256784 | Only Display whole numbers | +| 1256784.3745 | 0,0 | 1,256,784 | Only displays whole numbers with comma separator | +| 1256784.3745 | 0,0.00 | 1,256,784.38 | Displays the value with decimals points according to the count of zeroes after the dot | +| 1256784.3745 | 0\[.]0a | 1.2m |Displays the value in an abbreviated format.
Will display decimals of the abbreviated number according to count of zeroes after the dot.
| +| 1256784.3745 | $0\[.]0a | $1.2m | Adheres to the same methods as before, but adds a $ prefix. | + +### Ordering your series + +.png>) + +In this section of the visualization editor you can finalize your graph. + +* You can rename the "series" by simply clicking into the field. +* You can change the chart type by clicking into the dropdown. +* You can change the colors by clicking into the color box. +* Finally you can also change the order of the series. + +### Picking Colors + +You can pick colors with your browser native color selector. + +This might look slightly different for you depending on which browser you use. + + + + + diff --git a/duneapp/visualizations/pie-charts.md b/duneapp/visualizations/pie-charts.md new file mode 100644 index 0000000..1585e25 --- /dev/null +++ b/duneapp/visualizations/pie-charts.md @@ -0,0 +1,39 @@ +# Pie Charts + +**Pie charts are great for showing the composition of something.** + +.png>) + +## Configuring your pie chart + +.png>) + +### Chart Options + +#### Title + +* The Title will appear in all instances of this graph prominently at the top +* If left blank the query name will be the only thing that is left standing + + + +* [ ] **Show data labels** + + + +* Ticking this box leads to the display of the individual datapoints inside of the graph. +* This only makes sense in cases where you have few datapoints that are spread out far enough from each other to not overlap. + +### Result data + +Here you can pick the data points that are to be displayed. + +.png>) + +You can choose one **x-axis** and one y-axis. + +### Pie Options + +**Label format** + +* This field allows you to define the [tick format](https://docs.dune.xyz/duneapp/visualizations#tick-formats) of the data labels. diff --git a/faq/does-dune-have-a-token.md b/faq/does-dune-have-a-token.md new file mode 100644 index 0000000..dcd51c8 --- /dev/null +++ b/faq/does-dune-have-a-token.md @@ -0,0 +1,3 @@ +# Does Dune have a Token? + +**Dune does not have token.** diff --git a/faq/does-dune-have-an-api.md b/faq/does-dune-have-an-api.md new file mode 100644 index 0000000..3a8032f --- /dev/null +++ b/faq/does-dune-have-an-api.md @@ -0,0 +1,7 @@ +# Does Dune have an API? + +**Dune is currently working on an API!** + +If you'd like to express interest in receiving early access and would be willing to tell us more on how you expect to use the API - please complete our [API Interest form](https://docs.google.com/forms/d/e/1FAIpQLSdoF4\_LC1BdPumRq1TJguxAsKC-g5i6u2f7-sac5v14EubLsw/viewform). + +Until then, [paid plan users](https://dune.com/pricing) can export results as CSV and anyone can embed Dune charts on their page for free by clicking "[Embed](../sharing/embeds/)" on any query visualisation. diff --git a/faq/how-are-results-refreshing.md b/faq/how-are-results-refreshing.md new file mode 100644 index 0000000..83f27d7 --- /dev/null +++ b/faq/how-are-results-refreshing.md @@ -0,0 +1,7 @@ +# How are results refreshing? + +When a visualisation is viewed, either on a query page or on a dashboard, the Dune backend will inspect the age of the most recent result. If the result is stale (currently defined as >3 hours old), Dune will automatically queue an execution for this query and run it in the background. + +This means that dashboards will always be kept up to date when they are being viewed and the query creator does not need to set a refresh schedule. + +Note that the query execution queue is separate from each individual users queue when they create and run queries in the query editor. diff --git a/faq/how-does-dune-get-its-data.md b/faq/how-does-dune-get-its-data.md new file mode 100644 index 0000000..fbbe601 --- /dev/null +++ b/faq/how-does-dune-get-its-data.md @@ -0,0 +1,7 @@ +# How does Dune get it's data ? + +We are working together with node providers across the Industry to ingest data into our database. This includes all raw historical data from these blockchains. It does not include state data.\ + + +We don't discriminate against any smart contract, you can submit any contract via our [decoding page](../data-tables/data-tables/decoded-data.md) and work with it in a matter of hours. The only prerequisite for this is an ABI so we can actually decode the contract (usually the ABI is already on etherscan, but there are edge cases). + diff --git a/onboarding/onboarding-to-dune.md b/onboarding/onboarding-to-dune.md new file mode 100644 index 0000000..95b6146 --- /dev/null +++ b/onboarding/onboarding-to-dune.md @@ -0,0 +1,28 @@ +# Onboarding to Dune + +### Dune is an open platform that anyone can build on + +Team Dune often gets asked about "possible cooperation" and "ways to work together" and while we appreciate all these kind requests, there really isn't anything you need from the core team to be able to surface your data on dune. \ +\ +Our platform is free, open and permissionless and anyone can use the platform as they see fit. \ +All you need is either a skilled freelancer or one of your team members to take care of the actually surfacing the data. + +**The Process looks like this:** + +1. **Compile a List of all relevant contracts and submit them for** [**decoding**](../duneapp/adding-new-contracts.md)**.** +2. **Surface the data using SQL queries** +3. **Visualize the results** +4. **Assemble visualizations on a dashboard.** +5. **Make the dashboard pretty** +6. **Enjoy your data** + +**** + +### How to find a freelancer + +There is quite a few people in the web3 scene which either specialized in building on dune or have the skillset in their repertoire. To reach out to this pool of freelancers, you can **fill in this** [**form**](http://bounties.dune.xyz/) **** and freelancers will get back to you in little to no time. Alternatively, you could also use platforms like gitcoin or layer3.xyz to find suitable freelancers. + +If hiring a freelancer for the first time, please make sure to check their past works and dashboards to verify that they are indeed capable of solving the task at hand. + + + diff --git a/resources/press-kit.md b/resources/press-kit.md new file mode 100644 index 0000000..71f0f33 --- /dev/null +++ b/resources/press-kit.md @@ -0,0 +1,70 @@ +--- +description: Get the Dune brand assets and learn about the usage guidelines +--- + +# Press Kit + +## Primary - Standard Logo + +This is the primary Dune logo. It should be used in this format whenever possible. + + + +{% file src="../.gitbook/assets/dune-standard-logo.svg" %} +Standard logo (SVG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-standard-logo@2x (1).png" %} +Standard logo (PNG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-standard-logo-dark.svg" %} +Standard logo dark (SVG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-standard-logo-dark@2x.png" %} +Standard logo dark (PNG) +{% endfile %} + + + +## Vertical logo + +.png>) + +{% file src="../.gitbook/assets/dune-vertical-logo (1).svg" %} +Vertical logo (SVG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-vertical-logo@2x (1).png" %} +Vertical logo (PNG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-vertical-logo-dark.svg" %} +Vertical logo dark (SVG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-vertical-logo-dark@2x (1).png" %} +Vertical logo dark (PNG) +{% endfile %} + +## Icon only + + + +{% file src="../.gitbook/assets/dune-icon-only.svg" %} +Icon only (SVG) +{% endfile %} + +{% file src="../.gitbook/assets/dune-icon-only@2x.png" %} +Icon only (PNG) +{% endfile %} + +## Complete set of all logos + +{% file src="../.gitbook/assets/Dune-logo-Full.zip" %} +All logos in SVG and PNG format (ZIP) +{% endfile %} + + + diff --git a/sharing/attribution.md b/sharing/attribution.md new file mode 100644 index 0000000..30b1852 --- /dev/null +++ b/sharing/attribution.md @@ -0,0 +1,28 @@ +--- +description: Content on Dune is community created and should be attributed accordingly! +--- + +# Attribution + +### Attribution + +Content on Dune is first and foremost the product of the creators on the platform. \ +Any mention of analysis published on our platform outside of the platform should credit the creators of this specific piece of analysis and not just "Dune". \ +\ +Crediting charts and dashboards should be done in the following way: + +_"@eliasmos via_ [_https://dune.com/queries/610591_](https://dune.com/queries/610591)_"._ + +You can find the twitter tags and more information of most creators in their [profile page](https://dune.xyz/rchen8). + + + + + +\ + + + + +## + diff --git a/sharing/embeds/README.md b/sharing/embeds/README.md new file mode 100644 index 0000000..a6e75a0 --- /dev/null +++ b/sharing/embeds/README.md @@ -0,0 +1,64 @@ +--- +description: Embeds allow you to enjoy beautiful, updating dune charts across the web! +--- + +# Embeds + +## Using Embeds + +**Screenshots are boring and tech of the past.** + +Instead of using static screenshots in varying forms of quality, Dune has a native embed function that works across most platforms. + +You can generate embed links by clicking on any query title and selecting the embed function in the top right corner. + + + + + +### Parameterized embeds + +Embed links also work with parameterized queries, but it is a bit tricky to get them to work: + +The embed link that gets generated does not include the necessary parameters yet, even if you have ran the query with it. We are already working on automating the link generation, but for now the is the only way for us to handle this. + +For now you need to manually prefix the parameter link with the parameters. + +The syntax for this is: + +`link?name_of_parameter1=xxxx&?name_of_parameter2=yyyy&...` __ + +An example of this would be: + +`>https://dune.xyz/embeds/118220/238460/aa002dd3-f9e2-4d63-86c8-b765569306c6NFT?address=0xff9c1b15b16263c61d017ee9f65c50e4ae0113d7&rolling_n_trades=500`\ +`` + +### Embeds across different platforms + +Here is a couple of exemplary use cases for Dune embeds: + +{% content-ref url="discord.md" %} +[discord.md](discord.md) +{% endcontent-ref %} + +{% content-ref url="twitter.md" %} +[twitter.md](twitter.md) +{% endcontent-ref %} + +{% content-ref url="mirror.xyz.md" %} +[mirror.xyz.md](mirror.xyz.md) +{% endcontent-ref %} + +{% content-ref url="webpages.md" %} +[webpages.md](webpages.md) +{% endcontent-ref %} + + + +### Known Issues + +Unfortunately, embeds do not work in a couple of fairly popular sites, this includes: + +* substack +* medium +* gitbook diff --git a/sharing/embeds/discord.md b/sharing/embeds/discord.md new file mode 100644 index 0000000..6c4c434 --- /dev/null +++ b/sharing/embeds/discord.md @@ -0,0 +1,16 @@ +--- +description: Dune's embeds display beautifully in Discord! +--- + +# Discord + +Dune embeds work very well in Discord: + +You can simply drop the link in the chat and the corresponding visualization will get displayed. + +This also lends itself very well to programming a bot to return the corresponding charts on command. + + + + + diff --git a/sharing/embeds/known-issues.md b/sharing/embeds/known-issues.md new file mode 100644 index 0000000..c9b8ade --- /dev/null +++ b/sharing/embeds/known-issues.md @@ -0,0 +1,11 @@ +--- +description: Sadly not every website wants to make it. +--- + +# Known Issues + +These websites currently sadly do not support dune embeds: + +* substack +* medium +* gitbook diff --git a/sharing/embeds/mirror.xyz.md b/sharing/embeds/mirror.xyz.md new file mode 100644 index 0000000..feb56a9 --- /dev/null +++ b/sharing/embeds/mirror.xyz.md @@ -0,0 +1,11 @@ +--- +description: Dune embedds work in Mirror.xyz! +--- + +# Mirror.xyz + +Dune charts can easily be embedded into articles on mirror.xyz. Simply generate an embed link and postfix it with `?display=iframe` + +An example of this would be: + +`https://dune.xyz/embeds/208941/391702/34ee3319-1cac-40e1-a08d-160bd93693cc?display=iframe` diff --git a/sharing/embeds/twitter.md b/sharing/embeds/twitter.md new file mode 100644 index 0000000..83e670a --- /dev/null +++ b/sharing/embeds/twitter.md @@ -0,0 +1,20 @@ +--- +description: >- + Sharing data on Twitter is probably the most common use case of Dune's + Visualizations. +--- + +# Twitter + +You can use embeds to share Dune's visualizations on Twitter. + +Twitter will render the visualizations automatically and they will update automatically as time progresses. + +Definitely a better experience compared to static screenshots! + + + + + + + diff --git a/sharing/embeds/webpages.md b/sharing/embeds/webpages.md new file mode 100644 index 0000000..a56031e --- /dev/null +++ b/sharing/embeds/webpages.md @@ -0,0 +1,22 @@ +--- +description: You can embedd Dune's Visualizations on most Websites with ease. +--- + +# Webpages + +### Dune Charts can live in your website! + +You can use Dune's embed function to embed the charts usually displayed on Dune Analytics Dashboards into your website. + +Here is a code snippet example: + +`` + +We have seen this feature used on project websites, websites of researchers and basically everywhere by now, the limit really is just your imagination. + +A great showcase for this is the [cryptoart.io](https://cryptoart.io/data) website. + + + + +