diff --git a/README.md b/README.md index c05b0a6..b26d8bc 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ --- -description: Flipside supports crypto analysts by providing the best onchain data. +description: >- + Flipside empowers web3 analysts and enthusiasts with the best onchain data and + activation programs. --- # Welcome to Flipside @@ -12,6 +14,6 @@ Use the best onchain data for your project. Get started for free or [find the ri Play grail, participate in quests, or build dashboards to earn real crypto. -## 👥 [Community](flipside-community/get-started.md) +## 👥 [Community]() Join the thousands of crypto analysts building on Flipside. diff --git a/SUMMARY.md b/SUMMARY.md index 7c26158..0f29b07 100644 --- a/SUMMARY.md +++ b/SUMMARY.md @@ -16,69 +16,13 @@ * [Snowflake Data Shares](choose-your-flipside-plan/snowflake-data-shares/README.md) * [Mounting a Snowflake Data Share](choose-your-flipside-plan/snowflake-data-shares/mounting-a-snowflake-data-share.md) * [Earn](welcome-to-flipside/earn.md) -* [Community](flipside-community/get-started.md) - -## Products - -* [Data Studio (SQL Analysts)](products/data-studio-sql-analysts/README.md) - * [Get Started](products/data-studio-sql-analysts/get-started/README.md) - * [Browse dashboards](products/data-studio-sql-analysts/get-started/browse-dashboards.md) - * [Write/fork your first query](products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md) - * [Customize your Studio](products/data-studio-sql-analysts/customize-your-studio.md) - * [Query Editor](products/data-studio-sql-analysts/query-editor/README.md) - * [Using Snowflake SQL](products/data-studio-sql-analysts/query-editor/using-snowflake-sql.md) - * [Keyboard Shortcuts](products/data-studio-sql-analysts/query-editor/keyboard-shortcuts.md) - * [Writing Efficient Queries](products/data-studio-sql-analysts/query-editor/writing-efficient-queries.md) - * [Dashboard Builder](products/data-studio-sql-analysts/dashboard-editor/README.md) - * [Markdown Reference](products/data-studio-sql-analysts/dashboard-editor/markdown-reference.md) - * [Explore Dashboards](products/data-studio-sql-analysts/discover.md) - * [Teams Accounts](products/data-studio-sql-analysts/teams-accounts.md) -* [LiveQuery](products/get-started/README.md) - * [Add-Ons](products/get-started/add-ons/README.md) - * [⛓️ QuickNode Setup Guide](products/get-started/add-ons/quicknode-setup-guide.md) - * [Examples](products/get-started/examples/README.md) - * [🤝 Partner Functions](products/get-started/examples/partner-functions.md) - * [🧙‍♂️ EVM Functions](products/get-started/examples/evm-functions/README.md) - * [💡 Seaport: Real-time Orders](products/get-started/examples/evm-functions/seaport-real-time-orders.md) - * [💡 WETH Pool Balances](products/get-started/examples/evm-functions/weth-pool-balances.md) - * [💡 General EVM Node Queries](products/get-started/examples/evm-functions/general-evm-node-queries.md) - * [🤖 API Functions](products/get-started/examples/api-functions/README.md) - * [💡 Query TheGraph](products/get-started/examples/api-functions/query-thegraph.md) - * [💡 Query Defi Llama](products/get-started/examples/api-functions/query-defi-llama.md) - * [⚙️ Utility Functions](products/get-started/examples/utility-functions/README.md) - * [💡 Hex Converters](products/get-started/examples/utility-functions/hex-converters.md) - * [💡 JSON RPC Request Builder](products/get-started/examples/utility-functions/json-rpc-request-builder.md) - * [💡 EVM Logs Decoder](products/get-started/examples/utility-functions/evm-logs-decoder.md) - * [💡 Keccak256 Encoder](products/get-started/examples/utility-functions/keccak256-encoder.md) - * [Secrets Manager](products/get-started/secrets-manager.md) -* [API/SDK (Developers)](products/api-sdk-developers/README.md) - * [Your first API call in < 2 min](products/api-sdk-developers/getting-started.md) - * [JSON RPC methods](products/api-sdk-developers/rest-api.md) - * [SDK in depth](products/api-sdk-developers/get-started/README.md) - * [Run Your First Query](products/api-sdk-developers/get-started/run-your-first-query.md) - * [Query Results](products/api-sdk-developers/get-started/query-results.md) - * [Pagination](products/api-sdk-developers/get-started/pagination.md) - * [Sorting](products/api-sdk-developers/get-started/sorting.md) - * [Filtering](products/api-sdk-developers/get-started/filtering.md) - * [Query Seconds](products/api-sdk-developers/get-started/query-seconds.md) - * [Caching (maxAgeMinutes)](products/api-sdk-developers/get-started/caching-maxageminutes.md) - * [Rate Limits](products/api-sdk-developers/get-started/rate-limits.md) - * [Errors](products/api-sdk-developers/get-started/errors.md) - * [More Examples](products/api-sdk-developers/get-started/templates-and-walkthroughs.md) - * [Archive](products/api-sdk-developers/get-started/archive/README.md) - * [\[ARCHIVED\] JS/TS SDK](products/api-sdk-developers/get-started/archive/js-ts-sdk.md) - * [ShroomDK Migration Guide](products/api-sdk-developers/get-started/archive/shroomdk-migration-guide.md) - * [\[LEGACY\] R](products/api-sdk-developers/get-started/archive/r.md) - * [Python/R templates (video tutorials)](products/api-sdk-developers/python-r-templates-video-tutorials.md) - * [Community Showcase](products/api-sdk-developers/community-showcase.md) - * [Have Questions?](products/api-sdk-developers/have-questions.md) +* [Community]() ## Data * [Flipside Data](data/flipside-data/README.md) - * [DBT docs by chain](data/flipside-data/data-table-documentation.md) + * [Table Docs by Chain](data/flipside-data/data-table-documentation.md) * [Data Modeling Approach](data/flipside-data/data-models.md) - * [Table Freshness Targets](data/flipside-data/table-freshness-targets.md) * [Labels](data/flipside-data/labels/README.md) * [Centralized Exchange Label Type](data/flipside-data/labels/cex-label-type.md) * [Decentralized Exchange Label Type](data/flipside-data/labels/dex-label-type.md) @@ -92,192 +36,92 @@ * [Token Label Type](data/flipside-data/labels/token-label-type.md) * [Flotsam Label Type](data/flipside-data/labels/flotsam-label-type.md) * [Tags](data/flipside-data/featured-tags-and-sql-examples.md) -* [Contribute to our data](data/contribute-to-our-data/README.md) - * [Contract Decoding & ABIs](data/contribute-to-our-data/contract-decoding-and-abis.md) - * [How to Add Your Own Tags](data/contribute-to-our-data/how-to-add-your-own-tags.md) - * [Community Curation](data/contribute-to-our-data/contribute-to-flipside-data/README.md) - * [Getting Started](data/contribute-to-our-data/contribute-to-flipside-data/getting-started/README.md) - * [Contribution Workflow](data/contribute-to-our-data/contribute-to-flipside-data/getting-started/contribution-workflow.md) - * [Model Standards](data/contribute-to-our-data/contribute-to-flipside-data/model-standards/README.md) - * [dbt Tips](data/contribute-to-our-data/contribute-to-flipside-data/model-standards/dbt-tips.md) - * [PR Checklist](data/contribute-to-our-data/contribute-to-flipside-data/pr-checklist.md) -* [Archive](data/archive/README.md) - * [Data Updates](data/archive/data-updates.md) - * [Legacy Table Documentation](data/archive/tables/README.md) - * [AAVE Tables](data/archive/tables/aave-tables/README.md) - * [Market Stats](data/archive/tables/aave-tables/market-stats.md) - * [Votes](data/archive/tables/aave-tables/votes.md) - * [Proposals](data/archive/tables/aave-tables/proposals.md) - * [Deposits](data/archive/tables/aave-tables/deposits.md) - * [Liquidations](data/archive/tables/aave-tables/liquidations.md) - * [Borrows](data/archive/tables/aave-tables/borrows.md) - * [Repayments](data/archive/tables/aave-tables/repayments.md) - * [Flashloans](data/archive/tables/aave-tables/flashloans.md) - * [Withdraws](data/archive/tables/aave-tables/withdraws.md) - * [Algorand Tables](data/archive/tables/algorand-tables/README.md) - * [Algorand Base Tables](data/archive/tables/algorand-tables/algorand-base-tables/README.md) - * [Account](data/archive/tables/algorand-tables/algorand-base-tables/account.md) - * [Account App](data/archive/tables/algorand-tables/algorand-base-tables/account-app.md) - * [Account Asset](data/archive/tables/algorand-tables/algorand-base-tables/account-asset.md) - * [App](data/archive/tables/algorand-tables/algorand-base-tables/app.md) - * [Application Call Transaction](data/archive/tables/algorand-tables/algorand-base-tables/application-call-transaction.md) - * [Asset](data/archive/tables/algorand-tables/algorand-base-tables/asset.md) - * [Asset Configuration Transaction](data/archive/tables/algorand-tables/algorand-base-tables/asset-configuration-transaction.md) - * [Asset Freeze Transaction](data/archive/tables/algorand-tables/algorand-base-tables/asset-freeze-transaction.md) - * [Asset Transfer Transaction](data/archive/tables/algorand-tables/algorand-base-tables/asset-transfer-transaction.md) - * [Block](data/archive/tables/algorand-tables/algorand-base-tables/block.md) - * [Key Registration Transaction](data/archive/tables/algorand-tables/algorand-base-tables/key-registration-transaction.md) - * [Payment Transaction](data/archive/tables/algorand-tables/algorand-base-tables/payment-transaction.md) - * [Transactions](data/archive/tables/algorand-tables/algorand-base-tables/transactions.md) - * [Transfers](data/archive/tables/algorand-tables/algorand-base-tables/transfers.md) - * [Swaps](data/archive/tables/algorand-tables/algorand-base-tables/swaps.md) - * [Transactions Participation](data/archive/tables/algorand-tables/algorand-base-tables/transactions-participation.md) - * [Prices Swap](data/archive/tables/algorand-tables/algorand-base-tables/prices-swap.md) - * [Prices Pool Balances](data/archive/tables/algorand-tables/algorand-base-tables/prices-pool-balances.md) - * [Daily Balances](data/archive/tables/algorand-tables/algorand-base-tables/daily-balances.md) - * [Core Tables](data/archive/tables/algorand-tables/core-tables.md) - * [Arbitrum Tables](data/archive/tables/arbitrum-tables.md) - * [Astroport Tables](data/archive/tables/astroport-tables/README.md) - * [Astroport Pool Reserves](data/archive/tables/astroport-tables/lp-actions.md) - * [Astroport Swaps](data/archive/tables/astroport-tables/swap.md) - * [Avalanche Tables](data/archive/tables/avalanche-tables.md) - * [Axelar Tables](data/archive/tables/axelar-tables.md) - * [BSC Tables](data/archive/tables/bsc-tables.md) - * [Compound Tables](data/archive/tables/compound-tables/README.md) - * [Repayments](data/archive/tables/compound-tables/repayments.md) - * [Redemptions](data/archive/tables/compound-tables/redemptions.md) - * [Deposits](data/archive/tables/compound-tables/mints.md) - * [Liquidations](data/archive/tables/compound-tables/liquidations.md) - * [Borrows](data/archive/tables/compound-tables/borrows.md) - * [Market Stats](data/archive/tables/compound-tables/market-stats.md) - * [Cosmos Tables](data/archive/tables/cosmos-tables.md) - * [Crosschain Tables](data/archive/tables/crosschain-tables/README.md) - * [Fact Hourly Prices](data/archive/tables/crosschain-tables/fact-hourly-prices.md) - * [Dim Asset Metadata](data/archive/tables/crosschain-tables/dim-asset-metadata.md) - * [Dim Dates](data/archive/tables/crosschain-tables/dim-dates.md) - * [Dim Date Hours](data/archive/tables/crosschain-tables/dim-date-hours.md) - * [Crosschain Address Labels](data/archive/tables/crosschain-tables/crosschain-address-labels.md) - * [Crosschain Address Tags](data/archive/tables/crosschain-tables/crosschain-address-tags.md) - * [Ethereum Tables](data/archive/tables/ethereum-tables.md) - * [Ethereum Beacon Chain Tables](data/archive/tables/ethereum-beacon-chain-tables.md) - * [Ethereum Beta Tables](data/archive/tables/ethereum-beta-tables.md) - * [Ethereum Chainlink Tables](data/archive/tables/ethereum-chainlink-tables.md) - * [Ethereum Maker DAO Tables](data/archive/tables/ethereum-maker-dao-tables.md) - * [Ethereum Sushi Tables](data/archive/tables/ethereum-sushi-tables.md) - * [FLOW Tables](data/archive/tables/flow-tables/README.md) - * [Blocks](data/archive/tables/flow-tables/blocks.md) - * [Bridge Transactions](data/archive/tables/flow-tables/bridge-transactions.md) - * [Contract Labels](data/archive/tables/flow-tables/contract-labels.md) - * [Events](data/archive/tables/flow-tables/events.md) - * [Moment Metadata](data/archive/tables/flow-tables/moment-metadata.md) - * [NFT Sales](data/archive/tables/flow-tables/nft-sales.md) - * [Prices](data/archive/tables/flow-tables/prices.md) - * [Swaps](data/archive/tables/flow-tables/swaps.md) - * [Token Transfers](data/archive/tables/flow-tables/token-transfers.md) - * [TopShot Metadata](data/archive/tables/flow-tables/topshot-metadata.md) - * [Transactions](data/archive/tables/flow-tables/transactions.md) - * [Validator Labels](data/archive/tables/flow-tables/validator-labels.md) - * [Gnosis Tables](data/archive/tables/gnosis-tables.md) - * [NEAR Tables](data/archive/tables/near-tables.md) - * [Optimism Tables](data/archive/tables/optimism-tables.md) - * [Osmosis Tables](data/archive/tables/osmosis-tables/README.md) - * [Osmosis Fact Airdrops](data/archive/tables/osmosis-tables/osmosis-fact-airdrops.md) - * [Osmosis Fact Blocks Table](data/archive/tables/osmosis-tables/osmosis-fact-blocks-table.md) - * [Osmosis Daily Balances](data/archive/tables/osmosis-tables/osmosis-daily-balances.md) - * [Osmosis Fact Governance Proposal Deposits](data/archive/tables/osmosis-tables/osmosis-fact-governance-proposal-deposits.md) - * [Osmosis Fact Governance Submit Proposal](data/archive/tables/osmosis-tables/osmosis-fact-governance-submit-proposal.md) - * [Osmosis Fact Governance Votes](data/archive/tables/osmosis-tables/osmosis-fact-governance-votes.md) - * [Osmosis Dim Labels](data/archive/tables/osmosis-tables/osmosis-dim-labels.md) - * [Osmosis Dim Liquidity Pools](data/archive/tables/osmosis-tables/osmosis-dim-liquidity-pools.md) - * [Osmosis Fact Liquidity Provider Actions](data/archive/tables/osmosis-tables/osmosis-fact-liquidity-provider-actions.md) - * [Osmosis Fact Msg Attributes Table](data/archive/tables/osmosis-tables/osmosis-fact-msg-attributes-table.md) - * [Osmosis Fact Msgs Table](data/archive/tables/osmosis-tables/osmosis-fact-msgs-table.md) - * [Osmosis Dim Prices](data/archive/tables/osmosis-tables/osmosis-dim-prices.md) - * [Osmosis Fact Staking Rewards](data/archive/tables/osmosis-tables/osmosis-fact-staking-rewards.md) - * [Osmosis Fact Staking](data/archive/tables/osmosis-tables/osmosis-fact-staking.md) - * [Osmosis Fact Superfluid Staking](data/archive/tables/osmosis-tables/osmosis-fact-superfluid-staking.md) - * [Osmosis Fact Swaps](data/archive/tables/osmosis-tables/osmosis-fact-swaps.md) - * [Osmosis Dim Tokens](data/archive/tables/osmosis-tables/osmosis-dim-tokens.md) - * [Osmosis Fact Transactions Table](data/archive/tables/osmosis-tables/osmosis-fact-transactions-table.md) - * [Osmosis Fact Transfers](data/archive/tables/osmosis-tables/osmosis-fact-transfers.md) - * [Osmosis Fact Validators](data/archive/tables/osmosis-tables/osmosis-fact-validators.md) - * [Osmosis Dim Vote Options](data/archive/tables/osmosis-tables/osmosis-dim-vote-options.md) - * [Osmosis EZ Prices](data/archive/tables/osmosis-tables/osmosis-ez-prices.md) - * [Osmosis EZ ICNS](data/archive/tables/osmosis-tables/osmosis-ez-icns.md) - * [Polygon Tables](data/archive/tables/polygon-tables/README.md) - * [Polygon Events Emitted](data/archive/tables/polygon-tables/polygon-events-emitted.md) - * [Polygon Transactions](data/archive/tables/polygon-tables/polygon-transactions.md) - * [Polygon UDM Events](data/archive/tables/polygon-tables/polygon-udm-events.md) - * [Position Collected Fees](data/archive/tables/polygon-tables/position-collected-fees.md) - * [Swaps](data/archive/tables/polygon-tables/swaps.md) - * [V3 Resources](data/archive/tables/polygon-tables/v3-resources.md) - * [Polygon 2.0 Tables](data/archive/tables/polygon-2.0-tables.md) - * [Solana Tables](data/archive/tables/solana-tables.md) - * [Terra Tables](data/archive/tables/terra-tables/README.md) - * [Terra Raw Tables](data/archive/tables/terra-tables/terra-raw-tables/README.md) - * [Blocks](data/archive/tables/terra-tables/terra-raw-tables/blocks.md) - * [Msgs](data/archive/tables/terra-tables/terra-raw-tables/msgs.md) - * [Msg\_events](data/archive/tables/terra-tables/terra-raw-tables/msg\_events.md) - * [Transactions](data/archive/tables/terra-tables/terra-raw-tables/transactions.md) - * [Transitions](data/archive/tables/terra-tables/terra-raw-tables/transitions.md) - * [Terra Base Tables](data/archive/tables/terra-tables/terra-base-tables/README.md) - * [Validator Labels](data/archive/tables/terra-tables/terra-base-tables/validator-labels.md) - * [Labels](data/archive/tables/terra-tables/terra-base-tables/labels.md) - * [Oracle Prices](data/archive/tables/terra-tables/terra-base-tables/oracle-prices.md) - * [Tax Rate](data/archive/tables/terra-tables/terra-base-tables/tax-rate.md) - * [Daily Balances](data/archive/tables/terra-tables/terra-base-tables/daily-balances.md) - * [Swaps](data/archive/tables/terra-tables/terra-base-tables/swap.md) - * [Staking](data/archive/tables/terra-tables/terra-base-tables/staking.md) - * [Reward](data/archive/tables/terra-tables/terra-base-tables/rewards.md) - * [Transfer Events](data/archive/tables/terra-tables/terra-base-tables/transfer-events.md) - * [Event Actions](data/archive/tables/terra-tables/terra-base-tables/event-actions.md) - * [Terraswap Tables](data/archive/tables/terraswap-tables/README.md) - * [Terraswap LP Actions](data/archive/tables/terraswap-tables/lp-actions.md) - * [Terraswap Pool Reserves](data/archive/tables/terraswap-tables/lp-actions-1.md) - * [Terraswap Swaps](data/archive/tables/terraswap-tables/swap.md) - * [THORChain Tables](data/archive/tables/thorchain-tables/README.md) - * [THORChain Raw Table](data/archive/tables/thorchain-tables/thorchain-raw-table/README.md) - * [Active Vault Events](data/archive/tables/thorchain-tables/thorchain-raw-table/active-vault-events.md) - * [Inactive Vault Events](data/archive/tables/thorchain-tables/thorchain-raw-table/inactive-vault-events.md) - * [Add events](data/archive/tables/thorchain-tables/thorchain-raw-table/add-events.md) - * [Block Pool Depths](data/archive/tables/thorchain-tables/thorchain-raw-table/block-pool-depths.md) - * [Bond Events](data/archive/tables/thorchain-tables/thorchain-raw-table/bond-events.md) - * [Fee Events](data/archive/tables/thorchain-tables/thorchain-raw-table/fee-events.md) - * [Gas Events](data/archive/tables/thorchain-tables/thorchain-raw-table/gas-events.md) - * [Message Events](data/archive/tables/thorchain-tables/thorchain-raw-table/message-events.md) - * [New Node Events](data/archive/tables/thorchain-tables/thorchain-raw-table/new-node-events.md) - * [Pending Liquidity Events](data/archive/tables/thorchain-tables/thorchain-raw-table/pending-liquidity-events.md) - * [Pool Balance Change Events](data/archive/tables/thorchain-tables/thorchain-raw-table/pool-balance-change-events.md) - * [Pool Events](data/archive/tables/thorchain-tables/thorchain-raw-table/pool-events.md) - * [Refund Events](data/archive/tables/thorchain-tables/thorchain-raw-table/refund-events.md) - * [Reserve Events](data/archive/tables/thorchain-tables/thorchain-raw-table/reserve-events.md) - * [Rewards Events](data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-events.md) - * [Rewards Event Entries](data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-event-entries.md) - * [Swap Events](data/archive/tables/thorchain-tables/thorchain-raw-table/swap-events.md) - * [THORChain Base Table](data/archive/tables/thorchain-tables/thorchain-base-table/README.md) - * [Block Rewards](data/archive/tables/thorchain-tables/thorchain-base-table/block-rewards.md) - * [Bond Actions](data/archive/tables/thorchain-tables/thorchain-base-table/bond-actions.md) - * [Daily Earnings](data/archive/tables/thorchain-tables/thorchain-base-table/daily-earnings.md) - * [Daily Pool Stats](data/archive/tables/thorchain-tables/thorchain-base-table/daily-pool-stats.md) - * [Daily TVL](data/archive/tables/thorchain-tables/thorchain-base-table/daily-tvl.md) - * [Prices](data/archive/tables/thorchain-tables/thorchain-base-table/prices.md) - * [Swaps](data/archive/tables/thorchain-tables/thorchain-base-table/swaps.md) - * [Liquidity Actions](data/archive/tables/thorchain-tables/thorchain-base-table/liquidity-actions.md) - * [Pool Block Balances](data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-balances.md) - * [Pool Block Fees](data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-fees.md) - * [Pool Block Statistics](data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-statistics.md) - * [Total Block Rewards](data/archive/tables/thorchain-tables/thorchain-base-table/total-block-rewards.md) - * [Total Value Locked](data/archive/tables/thorchain-tables/thorchain-base-table/total-value-locked.md) - * [Transfers](data/archive/tables/thorchain-tables/thorchain-base-table/transfers.md) - * [Upgrades](data/archive/tables/thorchain-tables/thorchain-base-table/upgrades.md) - * [Thorchain Core Tables](data/archive/tables/thorchain-tables/thorchain-core-tables.md) - * [Uniswap V3 Tables](data/archive/tables/uniswap-v3-tables/README.md) - * [Pools](data/archive/tables/uniswap-v3-tables/pools.md) - * [Pool Stats](data/archive/tables/uniswap-v3-tables/pool-stats.md) - * [Positions](data/archive/tables/uniswap-v3-tables/positions.md) - * [LP Actions](data/archive/tables/uniswap-v3-tables/lp-actions.md) - * [Algorand Tutorials](data/archive/algorand-tutorials.md) - * [Data Roadmap](data/archive/data-roadmap.md) + * [Table Freshness Targets](data/flipside-data/table-freshness-targets.md) + * [Contribute to Our Data](data/flipside-data/contribute-to-our-data/README.md) + * [Contract Decoding & ABIs](data/flipside-data/contribute-to-our-data/contract-decoding-and-abis.md) + * [How to Add Your Own Tags](data/flipside-data/contribute-to-our-data/how-to-add-your-own-tags.md) + * [Community Curation](data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/README.md) + * [Getting Started](data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/getting-started/README.md) + * [Contribution Workflow](data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/getting-started/contribution-workflow.md) + * [Model Standards](data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/model-standards/README.md) + * [dbt Tips](data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/model-standards/dbt-tips.md) + * [PR Checklist](data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/pr-checklist.md) +* [Data Products](data/data-products/README.md) + * [Data Studio (SQL Analysts)](data/data-products/data-studio-sql-analysts/README.md) + * [Get Started](data/data-products/data-studio-sql-analysts/get-started/README.md) + * [Write/fork your first query](data/data-products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md) + * [Studio in Depth](data/data-products/data-studio-sql-analysts/studio-in-depth/README.md) + * [Use the Query Editor](data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/README.md) + * [Using Snowflake SQL](data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/using-snowflake-sql.md) + * [Hex-to-Integer Function](data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/hex-to-integer-function.md) + * [Keyboard Shortcuts](data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/keyboard-shortcuts.md) + * [Writing Efficient Queries](data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/writing-efficient-queries.md) + * [Build a Dashboard](data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/README.md) + * [Markdown Reference](data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/markdown-reference.md) + * [Customize your Studio](data/data-products/data-studio-sql-analysts/studio-in-depth/customize-your-studio.md) + * [Team Accounts](data/data-products/data-studio-sql-analysts/team-accounts.md) + * [Tutorials](data/data-products/data-studio-sql-analysts/tutorials/README.md) + * [How to Analyze Web3 Data](data/data-products/data-studio-sql-analysts/tutorials/how-to-analyze-web3-data.md) + * [Video Tutorials](data/data-products/data-studio-sql-analysts/tutorials/tutorials/README.md) + * [Overview of Schemas & Tables](data/data-products/data-studio-sql-analysts/tutorials/tutorials/overview-of-schemas-and-tables.md) + * [Ethereum Tutorials](data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/README.md) + * [Getting Started with Decoded Ethereum Events](data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/getting-started-with-ethereum-events.md) + * [Getting Started with Ethereum Balances](data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/getting-started-with-ethereum-erc20-balances.md) + * [Block Level and Daily Balances](data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/using-labels-to-break-down-token-supply.md) + * [Finding Centralized Exchange Flows](data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/finding-centralized-exchange-deposits-and-withdrawals.md) + * [Solana Tutorials](data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/README.md) + * [Solana Schema & Tables: Video Walkthrough](data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/solana-schema-and-tables-video-walkthrough.md) + * [Solana Specialty Tables: Video Walkthrough](data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/solana-specialty-tables-video-walkthrough.md) + * [Exploring Transactions in solana.events](data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md) + * [THORChain Tutorials](data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/README.md) + * [THORChain Schema & Tables](data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/thorchain-schema-and-tables.md) + * [Calculating IL for THORChain](data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/calculating-il-for-thorchain.md) + * [More Tools & Resources](data/data-products/data-studio-sql-analysts/tutorials/more-tools-and-resources.md) + * [Get Inspired](data/data-products/data-studio-sql-analysts/discover.md) + * [LiveQuery](data/data-products/livequery/README.md) + * [Get Started](data/data-products/livequery/get-started.md) + * [LiveQuery in Depth](data/data-products/livequery/add-ons/README.md) + * [Functions](data/data-products/livequery/add-ons/examples/README.md) + * [🤝 Partner Functions](data/data-products/livequery/add-ons/examples/partner-functions.md) + * [🧙‍♂️ EVM Functions](data/data-products/livequery/add-ons/examples/evm-functions/README.md) + * [💡 Seaport: Real-time Orders](data/data-products/livequery/add-ons/examples/evm-functions/seaport-real-time-orders.md) + * [💡 WETH Pool Balances](data/data-products/livequery/add-ons/examples/evm-functions/weth-pool-balances.md) + * [💡 General EVM Node Queries](data/data-products/livequery/add-ons/examples/evm-functions/general-evm-node-queries.md) + * [🤖 API Functions](data/data-products/livequery/add-ons/examples/api-functions/README.md) + * [💡 Query TheGraph](data/data-products/livequery/add-ons/examples/api-functions/query-thegraph.md) + * [💡 Query Defi Llama](data/data-products/livequery/add-ons/examples/api-functions/query-defi-llama.md) + * [⚙️ Utility Functions](data/data-products/livequery/add-ons/examples/utility-functions/README.md) + * [💡 Hex Converters](data/data-products/livequery/add-ons/examples/utility-functions/hex-converters.md) + * [💡 JSON RPC Request Builder](data/data-products/livequery/add-ons/examples/utility-functions/json-rpc-request-builder.md) + * [💡 EVM Logs Decoder](data/data-products/livequery/add-ons/examples/utility-functions/evm-logs-decoder.md) + * [💡 Keccak256 Encoder](data/data-products/livequery/add-ons/examples/utility-functions/keccak256-encoder.md) + * [QuickNode Setup Guide](data/data-products/livequery/add-ons/quicknode-setup-guide.md) + * [Secrets Manager](data/data-products/livequery/secrets-manager.md) + * [Get Inspired](data/data-products/livequery/get-inspired.md) + * [Snowflake](data/data-products/snowflake.md) + * [API/SDK (Developers)](data/data-products/api-sdk-developers/README.md) + * [Get Started](data/data-products/api-sdk-developers/get-started/README.md) + * [Your first API call in < 2 min](data/data-products/api-sdk-developers/get-started/getting-started.md) + * [SDK in Depth](data/data-products/api-sdk-developers/get-started-1/README.md) + * [JSON RPC methods](data/data-products/api-sdk-developers/get-started-1/rest-api.md) + * [Run A Query](data/data-products/api-sdk-developers/get-started-1/run-your-first-query.md) + * [Query Results](data/data-products/api-sdk-developers/get-started-1/query-results.md) + * [Pagination](data/data-products/api-sdk-developers/get-started-1/pagination.md) + * [Sorting](data/data-products/api-sdk-developers/get-started-1/sorting.md) + * [Filtering](data/data-products/api-sdk-developers/get-started-1/filtering.md) + * [Query Seconds](data/data-products/api-sdk-developers/get-started-1/query-seconds.md) + * [Caching (maxAgeMinutes)](data/data-products/api-sdk-developers/get-started-1/caching-maxageminutes.md) + * [Rate Limits](data/data-products/api-sdk-developers/get-started-1/rate-limits.md) + * [Errors](data/data-products/api-sdk-developers/get-started-1/errors.md) + * [More Examples](data/data-products/api-sdk-developers/get-started-1/templates-and-walkthroughs.md) + * [Archive](data/data-products/api-sdk-developers/get-started-1/archive/README.md) + * [\[ARCHIVED\] JS/TS SDK](data/data-products/api-sdk-developers/get-started-1/archive/js-ts-sdk.md) + * [ShroomDK Migration Guide](data/data-products/api-sdk-developers/get-started-1/archive/shroomdk-migration-guide.md) + * [\[LEGACY\] R](data/data-products/api-sdk-developers/get-started-1/archive/r.md) + * [Tutorials](data/data-products/api-sdk-developers/python-r-templates-video-tutorials/README.md) + * [Have Questions?](data/data-products/api-sdk-developers/python-r-templates-video-tutorials/have-questions.md) + * [Get Inspired](data/data-products/api-sdk-developers/community-showcase.md) +* [Insights and Tools](data/insights-and-tools.md) ## Earn @@ -322,29 +166,9 @@ * [2024-02-20 | Release Notes](release-notes/2024-02-20-data-updates.md) * [2024-02-05 | Release Notes](release-notes/2024-02-05-data-updates.md) -## Resources - -* [Curated by the Flipside Team](resources/curated-by-the-flipside-team.md) -* [Hex-to-Integer Function](resources/hex-to-integer-function.md) -* [Video Tutorials](resources/tutorials/README.md) - * [Overview of Schemas & Tables](resources/tutorials/overview-of-schemas-and-tables.md) - * [Ethereum Tutorials](resources/tutorials/ethereum-tutorials/README.md) - * [Getting Started with Decoded Ethereum Events](resources/tutorials/ethereum-tutorials/getting-started-with-ethereum-events.md) - * [Getting Started with Ethereum Balances](resources/tutorials/ethereum-tutorials/getting-started-with-ethereum-erc20-balances.md) - * [Block Level and Daily Balances](resources/tutorials/ethereum-tutorials/using-labels-to-break-down-token-supply.md) - * [Finding Centralized Exchange Flows](resources/tutorials/ethereum-tutorials/finding-centralized-exchange-deposits-and-withdrawals.md) - * [Solana Tutorials](resources/tutorials/solana-tutorials/README.md) - * [Solana Schema & Tables: Video Walkthrough](resources/tutorials/solana-tutorials/solana-schema-and-tables-video-walkthrough.md) - * [Solana Specialty Tables: Video Walkthrough](resources/tutorials/solana-tutorials/solana-specialty-tables-video-walkthrough.md) - * [Exploring Transactions in solana.events](resources/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md) - * [THORChain Tutorials](resources/tutorials/thorchain-tutorials/README.md) - * [THORChain Schema & Tables](resources/tutorials/thorchain-tutorials/thorchain-schema-and-tables.md) - * [Calculating IL for THORChain](resources/tutorials/thorchain-tutorials/calculating-il-for-thorchain.md) - ## Flipside Community -* [How to Analyze Web3 Data](flipside-community/how-to-analyze-web3-data.md) +* [Get Started](flipside-community/get-started.md) * [Ambassador Program](flipside-community/ambassador-program.md) -* [Links & Resources](flipside-community/links-and-resources.md) * [Join Our Discord](https://discord.gg/flipside) * [Join Our Guild](https://guild.xyz/flipside-crypto) diff --git a/choose-your-flipside-plan/free.md b/choose-your-flipside-plan/free.md index 353629c..8a29fcd 100644 --- a/choose-your-flipside-plan/free.md +++ b/choose-your-flipside-plan/free.md @@ -12,11 +12,11 @@ To get started, simply create a free account [here](https://flipsidecrypto.com). *** -### Earn and educate +### Earn and Educate The more analysts create dashboards to help keep the industry informed, the better off we all are together. To that end, we also offer many ways to earn for sharing the insights you find. -Programs like Leaderboard Rewards, direct-to-analyst bounties, and more can help you build your portfolio and your bags 💰 +Programs like Top Dashboards, Direct-to-Analyst Comissions, and more can help you build your portfolio and your bags 💰 See [Earn with Flipside](../earn/flipside-earn.md) to learn more. diff --git a/data/archive/README.md b/data/archive/README.md deleted file mode 100644 index 60ed794..0000000 --- a/data/archive/README.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -description: Legacy documentation, for reference only. ---- - -# Archive - -Please assume documents in this area are not up to date — they're available for reference only — and refer to [data-table-documentation.md](../flipside-data/data-table-documentation.md "mention") for the latest information. Thanks! diff --git a/data/archive/algorand-tutorials.md b/data/archive/algorand-tutorials.md deleted file mode 100644 index dd83ec2..0000000 --- a/data/archive/algorand-tutorials.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Algorand Tutorials - -{% embed url="https://www.youtube.com/watch?v=WOsrxrcdy88" %} diff --git a/data/archive/data-roadmap.md b/data/archive/data-roadmap.md deleted file mode 100644 index 0b6efa2..0000000 --- a/data/archive/data-roadmap.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -description: The following is a Data Roadmap (subject to change) ---- - -# Data Roadmap - -The following chains are on-deck/under consideration. If there is a chain you would like to see prioritized please reach out to us and we will put it under consideration. - -| Blockchains | -| ----------- | -| EVMOS | -| dxdy | -| Bitcoin | -| Fantom | -| Stride | -| Juno | -| Sei | -| Sui | diff --git a/data/archive/data-updates.md b/data/archive/data-updates.md deleted file mode 100644 index 13c0ddb..0000000 --- a/data/archive/data-updates.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Data Updates - -**Join our** [**Discord**](https://discord.gg/ZmU3jQuu6W) **for recent data updates.** - -This page is used for major occasional changes that may impact existing queries (e.g. moving refactoring schemas). - -### **September 2022: Ethereum & EVM changes** - -flipside\_prod\_db.aave -->ethereum.aave\ -flipside\_prod\_db.compound -->ethereum.compound\ -fipside\_prod\_db.ethereum --> ethereum.core\ -flipside\_prod\_db.polygon --> polygon.core\ -flipside\_prod\_db.uniswapv3--> ethereum.uniswapv3 - -All queries above should be moved to the new corresponding databases. Dashboards will still populate, but there will be no new data coming into those tables. The legacy flipside\_prod\_db tables will not be seen in the Flipside query editor after September 13, 2022. - -### **June 2022: Solana Schema** - -Solana will be have its own database starting early June 2022! We will move it from - -flipside\_prod\_db --> solana - -Your queries and dashboards will continue to work for a period of time. To future proof your dashboards, you should move over **all work** to the three part naming convention in the new solana database. - -### **May 2022: Three Part Naming** - -For more information on new databases and three part naming, please see [this document](https://docs.google.com/document/d/1swYTBHYNoY27Mz5FB2Ru0KNTLRhwX6imWQtlyW5F-7Q/edit). - -### **May 2022: Ethereum Schema** - -Ethereum will have its own database starting May 25, 2022! flipside\_prod\_db.ethereum\_core will still be supported until June. We are actively making infrastructure upgrades and it will replace both flipside\_prod\_db.ethereum and ethereum\_core. - -New Ethereum tables will be released in April 2022! - -The new Ethereum schema will be **ethereum\_core**. Ethereum was one of the first blockchains that was developed within Flipside and there have been upgrades to infrastructure, warehousing, model building, etc. The Flipside developers have been working on what is being called the Ethereum facelift where many of the tables have been re-built from the ground up taking into account user feedback, usage, and lessons learned. - -Timeline:\ -\- April 18, 2022 - Eth Week! New Schema exposed for all users. All bounties will have to use ethereum\_core schema.\ -\ - - diff --git a/data/archive/tables/README.md b/data/archive/tables/README.md deleted file mode 100644 index 5db6055..0000000 --- a/data/archive/tables/README.md +++ /dev/null @@ -1,43 +0,0 @@ ---- -description: >- - [Legacy Documentation, Not Maintained, For Reference Only] This section - provides documentation on the schemas and design decisions behind every - queryable table. ---- - -# Legacy Table Documentation - -\-- **ARCHIVED -- FOR REFERENCE ONLY --** - -Table level guides are organized by schema for every blockchain or blockchain project. \ -\ -Each table guide has: - -* column descriptions and/or links to DBT docs w/ column descriptions and model lineage graphs. -* links to public Github repos.\ - - -Flipside community data include schemas for: - -| Schema | | -| -------------------------------------------------------------- | --------------------------------------------------- | -| [Crosschain Tables (prices, address tags)](crosschain-tables/) | [MakerDAO](ethereum-maker-dao-tables.md) | -| [Arbitrum](arbitrum-tables.md) | [NEAR ](near-tables.md) | -| [AAVE](aave-tables/) | [Optimism](optimism-tables.md) | -| [Avalanche](avalanche-tables.md) | [Osmosis](osmosis-tables/) | -| [Algorand](algorand-tables/) | [Polygon (legacy tables)](polygon-tables/) | -| [Astroport](astroport-tables/) | [Polygon 2.0](polygon-2.0-tables.md) | -| [BSC](bsc-tables.md) | [Solana](solana-tables.md) | -| [Compound](compound-tables/) | [Sushi](ethereum-sushi-tables.md) | -| [Ethereum (legacy tables)](broken-reference) | [Terra](terra-tables/) | -| [Ethereum Core](ethereum-tables.md) | [Terraswap](terraswap-tables/) | -| [FLOW](flow-tables/) | [THORChain](thorchain-tables/thorchain-base-table/) | -| [Gnosis](flow-tables/) | [Uniswap V3](uniswap-v3-tables/) | -| [Axelar](axelar-tables.md) | | - - - -{% hint style="info" %} -New blockchains/blockchain projects are added regularly. -{% endhint %} - diff --git a/data/archive/tables/aave-tables/README.md b/data/archive/tables/aave-tables/README.md deleted file mode 100644 index a39ee3d..0000000 --- a/data/archive/tables/aave-tables/README.md +++ /dev/null @@ -1,81 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# AAVE Tables - -AAVE is a lending platform, somewhat similar in scope and design to Compound. As a result we have a similar design schema for this project. Feedback remains very welcome as much of this data remains very beta! - -### New Tables (Compared to Compound) - -Unlike for Compound there are three further tables: - -* _Aave votes and proposals:_ Governance actions do exist on Compound and in fact can even be found within the events data, however with AAVE we've begun to opt to give these their own tables. These come as a pair -- proposals tracks all ongoing proposals and their current status, votes tracks votes for and against their proposals. The two can be joined on proposal ID. -* _Flashloans:_ AAVE has explicit support for flashloans -- loans taken and repaid within the same transaction. Once again on Compound this is technically possible but AAVE has flashloans built in as their own set of functions. - -### Variable and Stable Debts - -Additionally a key feature of AAVE's lending markets is that each market (i.e. USDC) supports two types of loans, one at a stable borrow rate and another at a variable rate. Both V1 and V2 (and AMM), support these but V2 and up has an additional feature aimed direct at these types of loans -- debt tokens. - -Debt tokens tokenize debt in the same way aTokens (or Compounds' cTokens) tokenize amounts supplied to the market. aTokens are given to suppliers proportionally based on how much they supply to that market. Stable Debt Tokens are given to borrowers based on how much debt at a stable borrow rate they have from that market. Identically Variable Debt Tokens are given to borrowers based on how much variable debt they hold - -### What about the Version columns (and blockchain)? - -![](<../../../../.gitbook/assets/Screen Shot 2021-08-16 at 3.22.45 PM.png>) - -Aave a few different subsets of markets, shown above. - -AAVE V1: Debt tokens do not exist and more technically, (though less significantly for our data) all interactions are done through the Lending Pool. aTokens do exist and stable/variable borrow rates are still available - -AAVE V2: Debt tokens exist to more easily track outstanding debt. Direct interactions are split among a Lending Pool and a Data Provider contract (though not necessary for anyone not planning to interact with the protocol directly on chain, i.e. app developers) - -AAVE AMM: Identical in design to AAVE V2 though it uses its own set of contracts. Designed for pool tokens. - -AAVE Polygon: Also shares a design with V2, with the key difference is that it is on the Polygon chain (whereas all others are Ethereum only) - -### General - -{% content-ref url="market-stats.md" %} -[market-stats.md](market-stats.md) -{% endcontent-ref %} - -### Governance - -{% content-ref url="votes.md" %} -[votes.md](votes.md) -{% endcontent-ref %} - -{% content-ref url="proposals.md" %} -[proposals.md](proposals.md) -{% endcontent-ref %} - -### Supplying - -{% content-ref url="withdraws.md" %} -[withdraws.md](withdraws.md) -{% endcontent-ref %} - -{% content-ref url="deposits.md" %} -[deposits.md](deposits.md) -{% endcontent-ref %} - -### Liquidations - -{% content-ref url="liquidations.md" %} -[liquidations.md](liquidations.md) -{% endcontent-ref %} - -### Borrowing - -{% content-ref url="borrows.md" %} -[borrows.md](borrows.md) -{% endcontent-ref %} - -{% content-ref url="repayments.md" %} -[repayments.md](repayments.md) -{% endcontent-ref %} - -{% content-ref url="flashloans.md" %} -[flashloans.md](flashloans.md) -{% endcontent-ref %} - diff --git a/data/archive/tables/aave-tables/borrows.md b/data/archive/tables/aave-tables/borrows.md deleted file mode 100644 index 0d1f5c8..0000000 --- a/data/archive/tables/aave-tables/borrows.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Borrows - - - -Borrows exist within the `aave` schema, as `aave.borrows` - -| Field | Type | Description | -| ----------------------- | --------- | --------------------------------------------- | -| `tx_id` | string | Transaction ID for this liquidation | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC timestamp for this transaction | -| `event_index` | number | Index of this event within the transaction | -| `aave_market` | address | Address of the token | -| `aave_token` | address | Address of the aToken | -| `borrowed_tokens` | number | Amount of tokens borrowed | -| `borrowed_usd` | number | USD amount borrowed | -| `borrower_address` | address | Address of the borrower | -| `borrow_rate_mode` | string | Either variable or stable | -| `lending_pool_contract` | address | Address of the lending pool contract | -| `aave_version` | string | AAVE version (V1, V2, or AMM for Ethereum) | -| `token_price` | number | Price of the token being borrowed | -| `symbol` | string | Symbol of the token being borrowed | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | - - - diff --git a/data/archive/tables/aave-tables/deposits.md b/data/archive/tables/aave-tables/deposits.md deleted file mode 100644 index d3a88cf..0000000 --- a/data/archive/tables/aave-tables/deposits.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Deposits - - - -Deposits exist within the `aave` schema, as `aave.deposits` - -| Field | Type | Description | -| ----------------------- | --------- | -------------------------------------------------------------- | -| `tx_id` | string | Transaction ID for this supply | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC timestamp for this transaction | -| `aave_market` | address | Address of the AAVE market/underlying contract | -| `aave_token` | address | aToken address | -| `issued_tokens` | number | Amount of tokens issued for providing liquidity | -| `supplied_usd` | number | USD amount provided as liquidity (decimal adjusted) | -| `depositor_address` | address | Address of liquidity provider | -| `lending_pool_contract` | address | Address of the lending pool contract used for this transaction | -| `aave_version` | string | AAVE version (V1, V2, or AMM for Ethereum) | -| `token_price` | number | Current price of the market token | -| `symbol` | string | Symbol of the market asset | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | - diff --git a/data/archive/tables/aave-tables/flashloans.md b/data/archive/tables/aave-tables/flashloans.md deleted file mode 100644 index 29f97cf..0000000 --- a/data/archive/tables/aave-tables/flashloans.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Flashloans - - - -Flashloans exist within the `aave` schema, as `aave.flashloans` - -| Field | Type | Description | -| ----------------------- | --------- | --------------------------------------------- | -| `tx_id` | string | Transaction ID for this liquidation | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC timestamp for this transaction | -| `event_index` | number | Index of this event within the transaction | -| `aave_market` | address | Address of the token | -| `aave_token` | address | Address of the aToken | -| `flashloan_amount` | number | Amount of tokens borrowed | -| `flashloan_amount_usd` | number | USD amount borrowed | -| `premium_amount` | number | Premium paid on the loan | -| `premium_amount_usd` | number | USD premium paid on the loan | -| `initiator_address` | address | Address of the initiator of the loan | -| `target_address` | address | Address of the target of the loan | -| `lending_pool_contract` | address | Address of the lending pool contract | -| `aave_version` | string | AAVE version (V1, V2, or AMM for Ethereum) | -| `token_price` | number | Price of the token being borrowed | -| `symbol` | string | Symbol of the token being borrowed | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | - - - diff --git a/data/archive/tables/aave-tables/liquidations.md b/data/archive/tables/aave-tables/liquidations.md deleted file mode 100644 index 1d96d9e..0000000 --- a/data/archive/tables/aave-tables/liquidations.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Liquidations - - - -Liquidations exist within the `aave` schema, as `aave.liquidations` - -| Field | Type | Description | -| -------------------------- | --------- | --------------------------------------------- | -| `tx_id` | string | Transaction ID for this liquidation | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC timestamp for this transaction | -| `event_index` | number | Index of this event within the transaction | -| `collateral_asset` | address | Address of the collateral asset | -| `collateral_aave_token` | address | Address of the collateral aToken | -| `liquidated_amount` | number | Amount liquidated (decimal adjusted) | -| `liquidated_amount_usd` | number | USD amount liquidated (decimal adjusted) | -| `debt_asset` | address | Address of the debt asset | -| `debt_aave_token` | address | Address of the debt aToken | -| `debt_to_cover_amount` | number | Amount of debt to cover | -| `debt_to_cover_amount_usd` | number | USD amount of debt to cover | -| `liquidator` | address | Address of the liquidator | -| `borrower` | address | Address of the borrower | -| `aave_version` | string | AAVE version (V1, V2, or AMM for Ethereum) | -| `collateral_token_price` | number | Price of the collateral token | -| `collateral_token_symbol` | string | Symbol of the collateral token | -| `debt_token_price` | number | Price of the debt token | -| `debt_token_symbol` | string | Symbol of the debt token | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | - diff --git a/data/archive/tables/aave-tables/market-stats.md b/data/archive/tables/aave-tables/market-stats.md deleted file mode 100644 index a71a203..0000000 --- a/data/archive/tables/aave-tables/market-stats.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Market Stats - - - -Market Stats exists within the `aave` schema, as `aave.market_stats` - -| **Field** | **Type** | Description | -| -------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `block_hour` | string | Market stats are aggregated by hour in UTC. `date_trunc(‘hour’,block_timestamp)` for joins on other tables | -| `lending_pool_add` | string | Lending pool contract associated with the AAVE market (used for interacting with on-chain) | -| `data_provider` | string | Data Provider contract associated with the AAVE market (used for interacting with on-chain) | -| `reserve_name` | string | Name/symbol of the underlying contract (i.e. USDT) | -| `atoken_address` | address | Address of the atoken the market serves (i.e. aUSDC). Given to suppliers proportional to how much they supply to this market | -| `stable_debt_token_address` | address | Address of the stable debt token the market serves. Given to borrowers proportional to how much debt of this type from this market they hold | -| `variable_debt_token_address` | address | Address of the variable debt token the market serves. Given to borrowers proportional to how much debt of this type from this market they hold | -| `underlying_contract` | address | Address of the underlying contract, i.e. USDC's address | -| `reserve_price` | number | Price of the underlying token contract | -| `atoken_price` | number | Price of the aToken the market uses | -| `total_liquidity_token` | number | Total liquidity/total supplied. Includes amounts currently out on loans | -| `total_liquidity_usd` | number | Total liquidity converted to USD values as of the hour recorded | -| `total_stable_debt_token` | number | Total debt out at a stable borrow rate from this market | -| `total_stable_debt_usd` | number | Total Stable Debt converted to USD values as of the hour recorded | -| `total_variable_debt_token` | number | Total debt out at a variable borrow rate from this market | -| `total_variable_debt_usd` | number | Total Variable Debt converted to USD values as of the hour recorded | -| `utilization_rate` | number | The percentage of the reserve’s total capital which is borrowed at any given time, calculated as total borrows divided by total liquidity | -| `supply_rate` | number | The supplier's APY. It depends on the current 'utilization rate', the proportion borrowed from/supplied to the market. | -| `borrow_rate_stable` | number | The borrower's stable APY. It depends on the current 'utilization rate', the proportion borrowed from/supplied to the market. | -| `borrow_rate_variable` | number | The borrower's variable APY. It depends on the current 'utilization rate', the proportion borrowed from/supplied to the market. | -| `aave_price` | number | The current price of the AAVE governance token | -| `aave_version` | string | The version of the AAVE market (can be V1, V2 or AMM for Ethereum) | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | -| `stkaave_rate_supply`\* | number | The APR for liquidity mining distributions. Calculated as pool emissions per second times seconds per year times AAVE price divided by total pool liquidity. | -| `stkaave_rate_variable_borrow`\* | number | The APR for liquidity mining distributions. Calculated as pool emissions per second times seconds per year times AAVE price divided by total pool liquidity. | - -\*AAVE price and total pool liquidity values used are USD equivalents instead of ETH, and therefore some small differences may exist vs. current rates on AAVE v2. - diff --git a/data/archive/tables/aave-tables/proposals.md b/data/archive/tables/aave-tables/proposals.md deleted file mode 100644 index 8e09873..0000000 --- a/data/archive/tables/aave-tables/proposals.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Proposals - - - -Votes exists within the `aave` schema, as `aave.proposals` - -| **Field** | **Type** | Description | -| --------------------- | -------- | ---------------------------------------------------------------------------- | -| `block_id` | number | Block number in which the proposal was created | -| `start_voting_period` | number | Block number in which voting may start | -| `end_voting_period` | number | Block number in which voting must conclude | -| `block_timestamp` | string | Timestamp of the proposal's creation | -| `governance_contract` | address | Governance contract used in this vote | -| `proposal_id` | number | ID of the proposal, which can be used to join in votes from the voting table | -| `status` | string | Current status of the proposal -- Created, Queued, Executed or Failed | -| `targets` | array | Markets that are the target of the vote | -| `proposer` | address | Address of the user which issued the proposal | -| `proposal_tx` | string | Transaction of the initial proposal creation | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | diff --git a/data/archive/tables/aave-tables/repayments.md b/data/archive/tables/aave-tables/repayments.md deleted file mode 100644 index d06377c..0000000 --- a/data/archive/tables/aave-tables/repayments.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Repayments - - - -Repayments exist within the `aave` schema, as `aave.repayments` - -| Field | Type | Description | -| ----------------------- | --------- | --------------------------------------------- | -| `tx_id` | string | Transaction ID for this liquidation | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC timestamp for this transaction | -| `event_index` | number | Index of this event within the transaction | -| `aave_market` | address | Address of the token | -| `aave_token` | address | Address of the aToken | -| `repayed_tokens` | number | Amount of tokens repayed | -| `repayed_usd` | number | USD amount repayed | -| `payer` | address | Address of the payer | -| `borrower` | address | Address of the borrower | -| `lending_pool_contract` | address | Address of the lending pool contract | -| `aave_version` | string | AAVE version (V1, V2, or AMM for Ethereum) | -| `token_price` | number | Price of the token being borrowed | -| `symbol` | string | Symbol of the token being borrowed | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | - - - diff --git a/data/archive/tables/aave-tables/votes.md b/data/archive/tables/aave-tables/votes.md deleted file mode 100644 index 13e69da..0000000 --- a/data/archive/tables/aave-tables/votes.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Votes - - - -Votes exists within the `aave` schema, as `aave.votes` - -| **Field** | **Type** | Description | -| --------------------- | -------- | ---------------------------------------------------------------------------- | -| `block_timestamp` | string | Block timestamp of the vote | -| `governance_contract` | address | Governance contract used in this vote | -| `proposal_id` | number | ID of the proposal, which can be used to join in votes from the voting table | -| `support` | string | Does the voter support the proposal? True/False | -| `voting_power` | number | Voting power, which depends on the voter's AAVE and stkAAVE balances | -| `voter` | address | voter's address | -| `tx_id` | string | Transaction of the vote | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | diff --git a/data/archive/tables/aave-tables/withdraws.md b/data/archive/tables/aave-tables/withdraws.md deleted file mode 100644 index 4ab73fc..0000000 --- a/data/archive/tables/aave-tables/withdraws.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Withdraws - - - -Withdraws exist within the `aave` schema, as `aave.withdraws` - -| Field | Type | Description | -| ------------------- | --------- | --------------------------------------------- | -| `tx_id` | string | Transaction ID for this liquidation | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC timestamp for this transaction | -| `event_index` | number | Index of this event within the transaction | -| `aave_market` | address | Address of the token | -| `aave_token` | address | Address of the aToken | -| `withdrawn_tokens` | number | Amount of tokens withdrawn | -| `withdrawn_usd` | number | USD amount withdrawn | -| `depositor_address` | address | Address of the depositor | -| `aave_version` | string | AAVE version (V1, V2, or AMM for Ethereum) | -| `token_price` | number | Price of the token being borrowed | -| `symbol` | string | Symbol of the token being borrowed | -| `blockchain` | string | Ethereum or Polygon (presently only Ethereum) | - - - diff --git a/data/archive/tables/algorand-tables/README.md b/data/archive/tables/algorand-tables/README.md deleted file mode 100644 index 8518cfd..0000000 --- a/data/archive/tables/algorand-tables/README.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Algorand Tables - -The Algorand tables schema are based on the [Algorand indexer](https://github.com/algorand/indexer/releases/tag/2.8.0). Algorand tables are available in [the Flipside app](https://app.flipsidecrypto.com/velocity) as the `algorand` schema. The tables are built based on the algorand asset, app, account, block, and transaction information. - -At Flipside, we currently offer raw tables based on the Algorand indexer with the exception of transactions broken into separate tables based on transaction type. Click the following link to learn more about the tables. We will be continuing to add further curated tables of Algorand data so check back intermittently to learn about the additional tables that have been added. - -Check out [the complete docs for our Algorand Base Tables](algorand-base-tables/) or watch this video overview: - -{% embed url="https://www.youtube.com/watch?v=WOsrxrcdy88" %} - - - diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/README.md b/data/archive/tables/algorand-tables/algorand-base-tables/README.md deleted file mode 100644 index 5bc19ae..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/README.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Algorand Base Tables - -The Algorand base tables contains data directly from the Algorand indexer with the exception of the transaction tables which are broken out into the different types of transactions that can be performed on the Algorand blockchain. diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/account-app.md b/data/archive/tables/algorand-tables/algorand-base-tables/account-app.md deleted file mode 100644 index 15f8cd1..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/account-app.md +++ /dev/null @@ -1,14 +0,0 @@ -# Account App - -The account app table contains all apps within the Algorand Ecosystem and an app ID and other information about the app, such as whether it's currently active. - -## Table Schema - -| Field | Type | Description | -| ------------ | ------- | -------------------------------------------------------------------------------------------- | -| `ADDRESS` | text | Wallet address tied to app | -| `APP_ID` | number | App ID, tied to index in the app table | -| `APP_CLOSED` | boolean | Has this app been deleted? | -| `CLOSED_AT` | number | block that the account\_app was last removed from the account | -| `CREATED_AT` | number | block that the app was added to an account | -| `APP_INFO` | array | Is the app currently deleted from the account? if not it will have json about current status | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/account-asset.md b/data/archive/tables/algorand-tables/algorand-base-tables/account-asset.md deleted file mode 100644 index 5918440..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/account-asset.md +++ /dev/null @@ -1,16 +0,0 @@ -# Account Asset - -The account asset table is contains a current list of all the address that hold the existing assets on the algorand network. - -## Table Schema - -| field | Type | Description | -| -------------------- | ------- | ------------------------------------------------------ | -| `ADDRESS` | text | Wallet Address that is holding the asset | -| `ASSET_ID` | number | Asset ID, same as index identifier in asset table | -| `ASSET_NAME` | text | Name of the asset | -| `AMOUNT` | number | Amount of asset the wallet currently holds | -| `ASSET_ADDED_AT` | number | Block that the asset was added to an account | -| `ASSET_LAST_REMOVED` | number | block that the asset was last removed from the account | -| `ASSET_CLOSED` | boolean | whether or not the asset is currently deleted | -| `FROZEN` | boolean | whether or not the holding is frozen. | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/account.md b/data/archive/tables/algorand-tables/algorand-base-tables/account.md deleted file mode 100644 index b9468f4..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/account.md +++ /dev/null @@ -1,18 +0,0 @@ -# Account - -The account table contains all address within the Algorand Ecosystem. - -## Table Schema - - - -| Field | Type | Description | -| ---------------- | ------ | ---------------------------------------------------------------------------------------------- | -| `ADDRESS` | text | The account public key | -| `ACCOUNT_CLOSED` | number | Whether or not the account is currently closed | -| `REWARDSBASE` | number | Used as part of the rewards computation. Only applicable to accounts which are participating. | -| `BALANCE` | number | Total number of ALGOs in the account | -| `CLOSED_AT` | number | Block during which this account was most recently closed | -| `CREATED_AT` | number | Block which account was created | -| `WALLET_TYPE` | text | Wallet type: sig(single signature), msig(multi-signature), lsig(programmatic-signature) | -| `ACCOUNT_DATA` | array | Optional Account data | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/app.md b/data/archive/tables/algorand-tables/algorand-base-tables/app.md deleted file mode 100644 index 0a9253d..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/app.md +++ /dev/null @@ -1,15 +0,0 @@ -# App - -The app table is contains a current list of all the apps with their app\_id and current status. - -## Table Schema - -| Field | Type | Description | -| ----------------- | ------- | ------------------------------------------- | -| `APP_ID` | number | App ID | -| `CREATOR_ADDRESS` | text | wallet creator account address | -| `APP_CLOSED` | boolean | whether or not the app is currently deleted | -| `CLOSED_AT` | number | block that the app was deleted | -| `CREATED_AT` | number | block that the app was created | -| `PARAMS` | array | | - diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/application-call-transaction.md b/data/archive/tables/algorand-tables/algorand-base-tables/application-call-transaction.md deleted file mode 100644 index 79a7aa3..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/application-call-transaction.md +++ /dev/null @@ -1,24 +0,0 @@ -# Application Call Transaction - -This is a table for all transactions whose type is application call transactions. For more details on application call transactions. Visit here: [https://developer.algorand.org/docs/get-details/transactions/transactions/#application-call-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#application-call-transaction) - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| -------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block in which the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | The ID of this transaction | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `SENDER` | text | The address of the creator of this transaction | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `APP_ID` | number | App ID associated with this application call transaction | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | - diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/asset-configuration-transaction.md b/data/archive/tables/algorand-tables/algorand-base-tables/asset-configuration-transaction.md deleted file mode 100644 index 376b2dc..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/asset-configuration-transaction.md +++ /dev/null @@ -1,25 +0,0 @@ -# Asset Configuration Transaction - -This is a table for all transactions whose type is Asset Configuration. These transactions are to create, configure and destroy an asset depending on which fields are set. For more details on asset configuration transactions. Visit here: [ ](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-configuration-transaction)[https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-configuration-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-configuration-transaction) - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| ------------------ | ------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | Transaction ID of the transaction | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_ID` | number | ID of Asset involved in the transaction | -| `ASSET_SUPPLY` | number | The total number of base units of the asset to create. This number cannot be changed. | -| `SENDER` | text | Address of the wallet creating the transaction | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `ASSET_PARAMETERS` | array | All parameters involved with the asset being created, modified or destroyed in the transaction[https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-parameters](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-parameters) | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/asset-freeze-transaction.md b/data/archive/tables/algorand-tables/algorand-base-tables/asset-freeze-transaction.md deleted file mode 100644 index 324f96d..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/asset-freeze-transaction.md +++ /dev/null @@ -1,25 +0,0 @@ -# Asset Freeze Transaction - -This is a table for all transactions whose type is Asset Freeze. As the name implies these transactions are made to freeze transactions. Visit here: [ ](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-configuration-transaction)[https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-freeze-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-freeze-transaction) - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| --------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | Transaction ID of the transaction | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_ID` | number | The asset ID being frozen or unfrozen. | -| `ASSET_ADDRESS` | text | The address of the account whose asset is being frozen or unfrozen. | -| `ASSET_FREEZE` | boolean | True to freeze the asset, otherwise null or false | -| `SENDER` | text | Address of the wallet creating the transaction | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/asset-transfer-transaction.md b/data/archive/tables/algorand-tables/algorand-base-tables/asset-transfer-transaction.md deleted file mode 100644 index b8c8e03..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/asset-transfer-transaction.md +++ /dev/null @@ -1,27 +0,0 @@ -# Asset Transfer Transaction - -This is a table for all transactions whose type is Asset Transfer. This is when an asset is transferred from one wallet to another. Visit here for more details: [ ](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-configuration-transaction)[https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-transfer-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-transfer-transaction) - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| ------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | Transaction ID of the transaction | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_ID` | number | The asset ID of the asset being transferred | -| `SENDER` | text | Address of the wallet creating the transaction | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `ASSET_SENDER` | text | The sender of the transfer. The regular [sender](https://developer.algorand.org/docs/get-details/transactions/transactions/#sender) field should be used and this one set to the zero value for regular transfers between accounts. If this value is nonzero, it indicates a clawback transaction where the [sender](https://developer.algorand.org/docs/get-details/transactions/transactions/#sender) is the asset's clawback address and the asset sender is the address from which the funds will be withdrawn. | -| `ASSET_RECEIVER` | text | The recipient of the asset transfer. | -| `ASSET_AMOUNT` | number | The amount of the asset to be transferred. A zero amount transferred to self allocates that asset in the account's Asset map. | -| `ASSET_TRANSFERRED` | number | The Asset ID of the asset transferred in the asset transfer transaction. | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/asset.md b/data/archive/tables/algorand-tables/algorand-base-tables/asset.md deleted file mode 100644 index 005cc71..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/asset.md +++ /dev/null @@ -1,17 +0,0 @@ -# Asset - -The asset table is contains a current list of all the assets with their asset\_id, current status and other info. - -## Table Schema - -| Field | Type | Description | -| ----------------- | ------- | --------------------------------------------- | -| `ASSET_ID` | number | Asset ID | -| `CREATOR_ADDRESS` | text | Address of the asset creator | -| `TOTAL_SUPPLY` | number | Total supply of the asset | -| `ASSET_NAME` | text | Name of the asset | -| `ASSET_URL` | text | The url to the asset website | -| `DECIMALS` | number | Number of decimals this asset has | -| `ASSET_DELETED` | boolean | whether or not the asset is currently deleted | -| `CLOSED_AT` | number | block that the asset was closed | -| `CREATED_AT` | number | block that the asset was created | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/block.md b/data/archive/tables/algorand-tables/algorand-base-tables/block.md deleted file mode 100644 index 446d587..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/block.md +++ /dev/null @@ -1,16 +0,0 @@ -# Block - -This table displays block\_ids, rewards associated with a block, and the time a block was minted and confirmed. In the Algorand ecosystem a block is also known as a round. - -## Table Schema - -| Field | Type | Description | -| ----------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block | -| `BLOCK_TIMESTAMP` | timestamp | Timestamp of block minting(without a timezone) | -| `REWARDSLEVEL` | number | How many rewards, in MicroAlgos, have been distributed to each RewardUnit of MicroAlgos since genesis. Link: https://algorand.github.io/java-algorand-sdk/com/algorand/algosdk/v2/client/model/BlockRewards.html | -| `NETWORK` | text | Signifying whether the block is from mainnet or testnet | -| `GENISIS_HASH` | text | ID to which this block belongs | -| `PREV_BLOCK_HASH` | number | ID to which the block before this belongs | -| `TXN_ROOT` | boolean | TransactionsRoot authenticates the set of transactions appearing in the block. More specifically, it's the root of a merkle tree whose leaves are the block's Txids, in lexicographic order. For the empty block, it's 0. Note that the TxnRoot does not authenticate the signatures on the transactions, only the transactions themselves. Two blocks with the same transactions but in a different order and with different signatures will have the same TxnRoot. | -| `HEADER` | array | Block details, see rules below- for more message details https://developer.algorand.org/docs/rest-apis/indexer/#blockrewards | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/daily-balances.md b/data/archive/tables/algorand-tables/algorand-base-tables/daily-balances.md deleted file mode 100644 index 5ce30e8..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/daily-balances.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -description: The end of day balance of ALGOs for an address. ---- - -# Daily Balances - - - -| Field | Type | Description | -| --------- | ------- | ------------------------------------- | -| `DATE` | date | The date time for this balance record | -| `ADDRESS` | address | The balance address | -| `BALANCE` | number | The amount of the balance | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/key-registration-transaction.md b/data/archive/tables/algorand-tables/algorand-base-tables/key-registration-transaction.md deleted file mode 100644 index d2a26a5..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/key-registration-transaction.md +++ /dev/null @@ -1,28 +0,0 @@ -# Key Registration Transaction - -This is a table for all transactions whose type is Key Registration. A key registration signifies whether or not a wallet is participating in rewards. To learn more about key registration transactions visit here: [https://developer.algorand.org/docs/get-details/transactions/transactions/#key-registration-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#key-registration-transaction) - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| ------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | Transaction ID of the transaction | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_ID` | number | The asset ID of the asset associated with the key registration | -| `SENDER` | text | Address of the wallet creating the transaction | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `PARTICIPATION_KEY` | text | The root participation public key. | -| `VRF_PUBLIC_KEY` | text | The VRF public key. | -| `VOTE_FIRST` | number | The first round that the participation key is valid. Not to be confused with the FirstValid round of the keyreg transaction. | -| `VOTE_LAST` | number | The last round that the participation key is valid. Not to be confused with the LastValid round of the keyreg transaction. | -| `VOTE_KEYDILUTION` | number | This is the dilution for the 2-level participation key. | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/payment-transaction.md b/data/archive/tables/algorand-tables/algorand-base-tables/payment-transaction.md deleted file mode 100644 index 1266a2a..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/payment-transaction.md +++ /dev/null @@ -1,25 +0,0 @@ -# Payment Transaction - -This is a table for all transactions whose type is Payment. This is when a user send a payment and can also be used to send the remainder of an account so it can be closed. To learn more visit: [https://developer.algorand.org/docs/get-details/transactions/transactions/#payment-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#payment-transaction) - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| -------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | Transaction ID of the transaction | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_ID` | number | The asset ID of the asset being sent | -| `SENDER` | text | Address of the wallet creating the transaction | -| `RECEIVER` | text | Address of the wallet receiving the payment | -| `AMOUNT` | number | Amount of the asset being sent to the receiver | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/prices-pool-balances.md b/data/archive/tables/algorand-tables/algorand-base-tables/prices-pool-balances.md deleted file mode 100644 index 5b7341d..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/prices-pool-balances.md +++ /dev/null @@ -1,5 +0,0 @@ -# Prices Pool Balances - -This table can be used to price assets within the Algorand blockchain using on-chain liquidity pool. Price is calculated by end-of-hour pool balances on tinyman for Algo base pairs, then using the coinmarketcap/coingiecko ALGO price to calculate the price of the other asset - -
FieldTypeDescription
BLOCK_HOURtimestampThe hour for which the price is valid
ASSET_IDnumericID associated with the asset
ASSET_NAMEstringName of the asset
PRICE_USDnumericThe USD price of the asset at the end of the hour. ALGO price pulled from coinmarketcap/coingiecko
ALGO_BALANCEnumericThe balance of ALGO tokens in the pool at the end of the hour. NULL for ALGO
NON_ALGO_BALANCEnumericThe balance of other (non-ALGO) tokens in the pool at the end of the hour. NULL for ALGO
POOL_NAMEstringThe name of the pool used for the price calculation. NULL for ALGO
POOL_ADDRESSstringThe address of the pool used for the price calculation. NULL for ALGO
diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/prices-swap.md b/data/archive/tables/algorand-tables/algorand-base-tables/prices-swap.md deleted file mode 100644 index e72cf32..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/prices-swap.md +++ /dev/null @@ -1,7 +0,0 @@ -# Prices Swap - -This table can be used to price assets within the Algorand blockchain using on-chain swaps. Price is calculated by using all swaps within two standard deviations from the hour average price, calculating the average price at the dex level, then weighting the dex price by the previous day's volume to create a weighted average across all dexes. - - - -
FieldTypeDescription
BLOCK_HOURtimestampThe hour for which the price is valid
ASSET_IDnumericID associated with the asset
ASSET_NAMEstringName of the asset
PRICE_USDnumericThis table can be used to price assets within the Algorand blockchain using on-chain swaps. Price is calculated by using all swaps within two standard deviations from the hour average price, calculating the average price at the dex level, then weighting the dex price by the previous day's volume to create a weighted average across all dexes.
MIN_PRICE_USD_HOURnumericThe lowest price found in a swap in the hour in USD
MAX_PRICE_USD_HOURnumericThe highest price found in a swap in the hour in USD
VOLATILITY_MEASUREnumericThe difference between the min and max price for the hour
SWAPS_IN_HOURintegerThe number of swap transactions in the hour that involved this asset
VOLUME_USD_IN_HOURnumericThe volume of swap transactions (in USD) in the hour for this asset
diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/swaps.md b/data/archive/tables/algorand-tables/algorand-base-tables/swaps.md deleted file mode 100644 index 9c019c1..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/swaps.md +++ /dev/null @@ -1,19 +0,0 @@ -# Swaps - -The swaps table compiles the swaps from the DEXes(decentralized exchanges) throughout the Algorand ecosystem. This table includes the Tinyman, AlgoFi, PactFi, and Wagmiswap DEX. \ -\ -**Important Note**: When looking at volume we will look at all rows for swaps. However, when looking at the number of swaps we should only count the number of swaps where swaps have a swap\_from_\__amount > 0. This is due to slippage payouts where a users signs an additional swap transaction to receive additional asset due to a change in price during the swap.\ - - -| Field | Type | Description | -| ----------------------- | --------- | ---------------------------------------------------------- | -| swap\_program | string | The DEX or program used to make the swap | -| block\_timestamp | timestamp | The time the block began | -| block\_id | integer | Unique sequential number that identifies the current block | -| tx\_id | string | A unique key that identifies a transaction | -| swapper | string | Address that initiated the swap | -| swap\_from_\__amount | integer | Total amount of the token sent in to initiate the swap | -| swap\__from\_asset\_id_ | string | Token being sent or swapped from | -| pool\_address | string | Address of the pool the swap is coming from | -| swap\_to_\__amount | integer | Total amount of the token received in the swap | -| swap\_to_\_asset\_id_ | string | Token being received or swapped for | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/transactions-participation.md b/data/archive/tables/algorand-tables/algorand-base-tables/transactions-participation.md deleted file mode 100644 index 9f019c1..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/transactions-participation.md +++ /dev/null @@ -1,12 +0,0 @@ -# Transactions Participation - -This is a transaction participation table which lists the addresses involved in a transaction within a block and what intra the address was involved in. - -## Table Schema - -| Field | Type | Description | -| ---------- | ------ | ---------------------------------------------------------- | -| `INTRA` | number | Offset into the block where this transaction was confirmed | -| `BLOCK_ID` | number | Block | -| `ADDRESS` | text | Wallet address associated with intra and block | - diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/transactions.md b/data/archive/tables/algorand-tables/algorand-base-tables/transactions.md deleted file mode 100644 index a53cf3f..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/transactions.md +++ /dev/null @@ -1,25 +0,0 @@ -# Transactions - -This is a table that includes and transactions andout transactions on the Algorand network, visit here: [https://developer.algorand.org/docs/get-details/transactions/transactions/#common-fields-header-and-type](https://developer.algorand.org/docs/get-details/transactions/transactions/#common-fields-header-and-type) . - -## Table Schema - -The structure of all transaction tables follow the structure of the overarching transaction table. Each transaction table besides the overarching transaction table are a collection of all the transaction of one of the 6 types. \ -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. One other note on the parent transactions, the parent transaction of inner transaction do not summarize the inner transactions and are seen as their own distinct transaction, which is usually an application call transaction. - -| Field | Type | Description | -| ----------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| `BLOCK_TIMESTAMP` | datetime | Timestamp of block minting(without a timezone) | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed. | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together for things like a dex swap. | -| `TX_ID` | text | Transaction ID of the transaction | -| INNER\_TX | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_ID` | number | The asset ID of the asset involved in the transaction. (This will be null for Application call transactions.) | -| `SENDER` | text | Address of the wallet creating the transaction | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/algorand-base-tables/transfers.md b/data/archive/tables/algorand-tables/algorand-base-tables/transfers.md deleted file mode 100644 index 44386bb..0000000 --- a/data/archive/tables/algorand-tables/algorand-base-tables/transfers.md +++ /dev/null @@ -1,32 +0,0 @@ -# Transfers - -This tables aims to simply the Algorand tables by combining the Payment Transaction Table and the Asset Transfer Transaction table and decimal adjusting all amounts from both of these tables. - -This means both payment transaction("pay") and asset transfer transaction("axfer") types will be included in the table. While the payment table was previously decimal adjusted we are now decimal adjusting all amounts for assets out side of ALGO(asset\_id = 0) as well. - -We have also broken out sender into **asset\_sender** which is the wallet from which the asset is sent from and **tx\_sender** which is the wallet which initiates the transaction. 99% of transactions these values are the same - however, this now gives us an easier way to look at clawback transactions([https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-transfer-transaction](https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-transfer-transaction)) which are detailed here. For most purposes we can use **asset\_sender** unless we want to look asset clawback transactions for the asset transfer transactions. - -## Table Schema - -All transactions have a distinct intra and block\_id combination. The intra is the transaction # into the block where the transaction was confirmed. Inner transactions(flagged with the inner tx flag) share the tx id of their parent application transactions so you can tie inner transaction to a parent transaction via a tx id. The inner transactions are seen as distinct transactions on the Algorand blockchain, which is signified by their intra and block id combination. - -| Field | Type | Description | -| ------------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_TIMESTAMP` | datetime | Timestamp of block minting(without a timezone) | -| `INTRA` | number | Transaction # into the block where this transaction was confirmed | -| `BLOCK_ID` | number | Block the transaction was confirmed | -| `TX_GROUP_ID` | text | Transaction group ID, can be NULL. Exists when a group of transactions are tied together | -| `TX_ID` | text | An identifier tied to a transaction and its inner transactions. | -| `INNER_TX` | boolean | A boolean true or false on whether or not this transaction has a parent transaction. The TX\_ID will be the same as the parent transaction but will have it's own intra. | -| `ASSET_SENDER` | text | The wallet address from which the asset is transferred from. This can be different from the asset\_sender if a wallet has opted in to allow another address to send an asset from its wallet(https://developer.algorand.org/docs/get-details/transactions/transactions/#asset-transfer-transaction). | -| `TX_SENDER` | text | The wallet address from which the transaction is initiated from and pays the fee. The tx\_sender can send assets from a different asset\_sender address if the asset\_sender has opted into this action. This relates to clawback transactions: see asset\_sender for more details. | -| `RECEIVER` | text | The recipient of the transfer. | -| `ASSET_ID` | number | ID associated with the asset | -| `AMOUNT` | number | The amount of the asset to be transferred. Can be 0. | -| `FEE` | number | Fee associated with the transaction, in ALGOs | -| `ASSET_TRANSFERRED` | number | The Asset ID of the asset transferred in the asset transfer transaction. | -| `TX_TYPE` | number | Number associated with transaction type | -| `TX_TYPE_NAME` | text | transaction type name | -| `GENISIS_HASH` | text | The hash of the genesis block of the network for which the transaction is valid | -| `TX_MESSAGE` | array | Encoded JSON message associated with the transaction | -| `EXTRA` | array | Extra json associated with transaction | diff --git a/data/archive/tables/algorand-tables/core-tables.md b/data/archive/tables/algorand-tables/core-tables.md deleted file mode 100644 index 9ca9819..0000000 --- a/data/archive/tables/algorand-tables/core-tables.md +++ /dev/null @@ -1,31 +0,0 @@ -# Core Tables - -Documentation for Core tables can be found [here](https://flipsidecrypto.github.io/algorand-models/#!/overview). - -The public Github repo with model source code is [here](https://github.com/FlipsideCrypto/algorand-models). - -Overview of Fact Dimensional model with Primary & Foreign Key relationships: - -
- -Quick Links to Table Docs: - -* [dim\_account](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_account) -* [dim\_application](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_application) -* [dim\_asset](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_asset) -* [dim\_block](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_block) -* [dim\_label](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_label) -* [dim\_transaction\_type](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_transaction\_type) -* [dim\_wallet\_type](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_dim\_wallet\_type) -* [fact\_account\_application](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_account\_application) -* [fact\_account\_asset](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_account\_asset) -* [fact\_account\_current\_balance](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_account\_current\_balance) -* [fact\_block](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_block) -* [fact\_daily\_balances](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_daily\_balances) -* [fact\_nft\_sales](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_nft\_sales) -* [fact\_swap](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_swap) -* [fact\_transaction](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_transaction) -* [fact\_transaction\_close](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_transaction\_close) -* [fact\_transaction\_participation](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_transaction\_participation) -* [fact\_transaction\_reward](https://flipsidecrypto.github.io/algorand-models/#!/model/model.algorand\_models.core\_\_fact\_transaction\_reward) - diff --git a/data/archive/tables/arbitrum-tables.md b/data/archive/tables/arbitrum-tables.md deleted file mode 100644 index 2879ee5..0000000 --- a/data/archive/tables/arbitrum-tables.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Arbitrum Tables - -Documentation for \`arbitrum\` tables can be found [here](https://flipsidecrypto.github.io/arbitrum-models/#!/overview). - -The public Github repo with Arbitrum model source code is [here](https://github.com/FlipsideCrypto/arbitrum-models). - -Please note, data is in 'lite mode' - meaning, historical data has not yet been backfilled. Please see the `min(block`\_`timestamp)`. - -Quick Links to Table Docs: - -* [`fact_event_logs`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_fact\_event\_logs) -* [`fact_transactions`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_fact\_blocks) -* [`fact_traces`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_fact\_traces) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_fact\_token\_transfers) -* [`dim_labels`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_dim\_labels) -* [`ez_eth_transfers`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_ez\_eth\_transfers) -* [`dim_contracts`](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.core\_\_dim\_contracts) - -Arbitrum sushi tables - -* [sushi\_\__dim\_dex\__pools](https://cloud.getdbt.com/accounts/1258/runs/68372630/docs/#!/model/model.arbitrum\_models.sushi\_\_dim\_dex\_pools) -* [sush\_\__dim\_kashi\_pairs_ ](https://cloud.getdbt.com/accounts/1258/runs/68372630/docs/#!/model/model.arbitrum\_models.sushi\_\_dim\_kashi\_pairs) -* [_sushi\_\_ez\_swaps_](https://cloud.getdbt.com/accounts/1258/runs/68372630/docs/#!/model/model.arbitrum\_models.sushi\_\_ez\_swaps) -* [_sushi\_\_ez\_borrowing_](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.sushi\_\_ez\_borrowing) -* [_sushi\_\_ez\_lending_](https://flipsidecrypto.github.io/arbitrum-models/#!/model/model.arbitrum\_models.sushi\_\_ez\_lending) - - - -Note: when working with the `fact_transactions` and `fact_event_logs` tables, you may find it useful to use the [ethereum.public.hex\_to\_int() function](../../../resources/hex-to-integer-function.md). diff --git a/data/archive/tables/astroport-tables/README.md b/data/archive/tables/astroport-tables/README.md deleted file mode 100644 index 20be0b8..0000000 --- a/data/archive/tables/astroport-tables/README.md +++ /dev/null @@ -1,10 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Astroport Tables - -Astroport is an automated market-maker (AMM) protocol on the Terra blockchain. - -From [Astroport's docs](https://docs.astroport.fi/astroport/astroport-onboarding/the-impact) : "Astroport is a next-generation AMM for Terra that was built to improve pricing and trade efficiency. Better pricing and efficiency should help Astroport attract more liquidity, further improving pricing and efficiency in a self-reinforcing loop. That is key, as trade efficiency is what ultimately drives adoption and integration with other protocols." - diff --git a/data/archive/tables/astroport-tables/lp-actions.md b/data/archive/tables/astroport-tables/lp-actions.md deleted file mode 100644 index c9a1d8a..0000000 --- a/data/archive/tables/astroport-tables/lp-actions.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -description: astroport.pool_reserves ---- - -# Astroport Pool Reserves - -This table provides block by block pool reserve information including total pool shares, pool currencies, and token amounts in Astroport pools. - -
FieldTypeDescription
FieldTypeDescription
blockchaintextThe blockchain this pool was created on.
chain_idtextID of blockchain to connect to, it can be columbus-3, columbus-4, columbus-5, etc.
block_idnumberThe block number that this pool reserve was recorded
block_timestamptimestampThe block timestamp that this pool reserve was recorded
contract_addressaddressThe address of the liquidity pool
total_sharenumberThe total amount of shares in a pool
token_0_currencytextToken 0 currency
token_0_amountnumberToken 0 amount in pool
token_1_currencytextToken 1 currency
token_1_amountnumberToken 1 amount in pool
diff --git a/data/archive/tables/astroport-tables/swap.md b/data/archive/tables/astroport-tables/swap.md deleted file mode 100644 index eb9aec2..0000000 --- a/data/archive/tables/astroport-tables/swap.md +++ /dev/null @@ -1,32 +0,0 @@ ---- -description: astroport.swaps ---- - -# Astroport Swaps - -This swaps table contains the information for swap behavior, it involves the sender (trader) and the liquidity pool where the swap takes place. - - - -## Table Schema - - - -| Field | Type | Description | -| ------------------- | --------- | ------------------------------------------------------------------------------------ | -| `BLOCKCHAIN` | text | The blockchain this swap was created on (Terra) | -| `CHAIN_ID` | text | ID of blockchain to connect to, it can be _columbus-3, columbus-4, columbus-5, etc._ | -| `BLOCK_ID` | number | The block number that this swap was recorded | -| `MSG_INDEX` | number | The message index for this swap | -| `TX_INDEX` | number | The transaction index for this swap, some transactions contain multiple swaps | -| `BLOCK_TIMESTAMP` | timestamp | The block timestamp that this swap was recorded | -| `TX_ID` | text | The transaction that contained this swap | -| `SENDER` | address | Sender (trader) address for this swap | -| `OFFER_AMOUNT` | number | Amount to offer for this swap | -| `OFFER_AMOUNT_USD` | number | USD Amount to offer for this swap | -| `OFFER_CURRENCY` | text | Currency to offer for this swap | -| `RETURN_AMOUNT` | number | Amount returned for this swap | -| `RETURN_AMOUNT_USD` | number | USD Amount returned for this swap | -| `RETURN_CURRENCY` | text | The currency returned for the swap | -| `POOL_ADDRESS` | text | The address for the pool where the currencies were swapped | -| `POOL_NAME` | text | The name of the pool where the currencies were swapped | diff --git a/data/archive/tables/avalanche-tables.md b/data/archive/tables/avalanche-tables.md deleted file mode 100644 index 1afa5ea..0000000 --- a/data/archive/tables/avalanche-tables.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Avalanche Tables - -Documentation for \`avalanche\` tables can be found [here](https://flipsidecrypto.github.io/avalanche-models/#!/overview). - -The public Github repo with Avalanche model source code is [here](https://github.com/FlipsideCrypto/avalanche-models). - -Please note, data is in 'lite mode' - meaning, historical data has not yet been backfilled. Please see the `min(block`\_`timestamp)`. - -Quick Links to Table Docs: - -* [`fact_event_logs`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_fact\_event\_logs) -* [`fact_transactions`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_fact\_blocks) -* [`fact_traces`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_fact\_traces) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_fact\_token\_transfers) -* [`dim_labels`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_dim\_labels) -* [`ez_avax_transfers`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_ez\_avax\_transfers) -* [`dim_contracts`](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.core\_\_dim\_contracts) - -`Sushi specific tables:` - -* [sushi\_\_dim\_dex\_pools](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.sushi\_\_dim\_dex\_pools) -* [sushi\_\_dim\_kashi\_pairs](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.sushi\_\_dim\_kashi\_pairs) -* [sushi\_\_ez\_swaps](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.sushi\_\_ez\_swaps) -* [sushi\_\_ez\_borrowing](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.sushi\_\_ez\_borrowing) -* [sushi\_\_ez\_lending](https://flipsidecrypto.github.io/avalanche-models/#!/model/model.avalanche\_models.sushi\_\_ez\_lending) - - - -Note: when working with the `fact_transactions` and `fact_event_logs` tables, you may find it useful to use the [ethereum.public.hex\_to\_int() function](../../../resources/hex-to-integer-function.md). diff --git a/data/archive/tables/axelar-tables.md b/data/archive/tables/axelar-tables.md deleted file mode 100644 index c5d7a6b..0000000 --- a/data/archive/tables/axelar-tables.md +++ /dev/null @@ -1,37 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Axelar Tables - -## Current Axelar Tables - -**Blockchain:** [Axelar](https://axelar.network/) - -The Axelar tables are currently in lite mode. All transaction and message data is available back to the genesis block. However, no curated tables are currently available. \ -\ -[Dim Labels](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_dim\_labels) - -[Dim Tokens](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_dim\_tokens) - -[Fact Blocks](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_blocks) - -[Fact Msg Attributes](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_msg\_attributes) - -[Fact Msgs](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_msgs) - -[Fact Transactions](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_transactions) - -[Fact Transfers](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_transfers) - -[Fact Validators](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_validators) - -[Fact Staking](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_staking) - -[Fact Staking Rewards](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_staking\_rewards) - -[Fact Governance Proposal Deposits](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_governance\_proposal\_deposits) - -[Fact Governance Submit Proposal](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_governance\_submit\_proposal) - -[Fact Governance Votes](https://flipsidecrypto.github.io/axelar-models/#!/model/model.axelar.core\_\_fact\_governance\_votes) diff --git a/data/archive/tables/bsc-tables.md b/data/archive/tables/bsc-tables.md deleted file mode 100644 index 05bd97d..0000000 --- a/data/archive/tables/bsc-tables.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# BSC Tables - -Documentation for \`bsc\` tables can be found [`here`](https://flipsidecrypto.github.io/bsc-models/#!/overview). - -The public Github repo with BSC model source code is [here](https://github.com/FlipsideCrypto/bsc-models). - -Please note, data is in 'lite mode' - meaning, historical data has not yet been backfilled. Please see the `min(block`\_`timestamp)`. - -Quick Links to Table Docs: - -* [`fact_event_logs`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_fact\_event\_logs) -* [`fact_transactions`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_fact\_blocks) -* [`fact_traces`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_fact\_traces) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_fact\_token\_transfers) -* [`dim_labels`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_dim\_labels) -* [`ez_bnb_transfers`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.core\_\_ez\_bnb\_transfers) - -`Sushi specific tables:` - -* [`dim_dex_pools`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.sushi\_\_dim\_dex\_pools) -* [`dim_kashi_pairs`](https://cloud.getdbt.com/accounts/1258/runs/77461492/docs/#!/model/model.bsc\_models.sushi\_\_dim\_kashi\_pairs) -* [`ez_swaps`](https://flipsidecrypto.github.io/bsc-models/#!/model/model.bsc\_models.sushi\_\_ez\_swaps) -* [`ez_borrowing`](https://cloud.getdbt.com/accounts/1258/runs/77461492/docs/#!/model/model.bsc\_models.sushi\_\_ez\_borrowing) -* [`ez_lending`](https://cloud.getdbt.com/accounts/1258/runs/77461492/docs/#!/model/model.bsc\_models.sushi\_\_ez\_lending) - - - -Note: when working with the `fact_transactions` and `fact_event_logs` tables, you may find it useful to use the [ethereum.public.hex\_to\_int() function](../../../resources/hex-to-integer-function.md). diff --git a/data/archive/tables/compound-tables/README.md b/data/archive/tables/compound-tables/README.md deleted file mode 100644 index 1483727..0000000 --- a/data/archive/tables/compound-tables/README.md +++ /dev/null @@ -1,62 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Compound Tables - -**Blockchain:** [Ethereum](https://ethereum.org/en/) - -The Compound table schemas build on the concepts laid out in [Flipside's event data model](broken-reference). Below is a visual overview of the Compound protocol's primary functions of decentralized borrowing and lending. - -![](<../../../../.gitbook/assets/Screen Shot 2021-04-20 at 11.44.31 AM.png>) - -We have tables for most major events within the Compound ecosystem, though the data is still early. The tables are intended to be as easy to work with as possible and paint as complete a picture of Compound as possible. Here are [sample Compound queries](https://velocity-app.flipsidecrypto.com/velocity/collections/d54dd195-163c-4153-8595-50b22f629b08). - -**What we have:** - -* A table for summarizing major metrics by market: `compound.market_stats.` This table aggregates by the hour, and should have all available markets/cTokens listed here [https://compound.finance/markets](https://compound.finance/markets) -* Tables for key events for suppliers: `compound.redemptions` and `compound.deposits.` In the diagram above these events correspond to both interactions between suppliers and the lending markets. -* Tables for key events for borrowers: `compound.borrows`, `compound.repayments` and `compound.liquidations`. These correspond to the three interactions between lending markets, borrowers, and liquidators in the diagram above. -* The data goes back only as far as October 2020, with more to come. - -**What we don't have:** - -We did choose, for now to omit tables for governance actions, such as proposals and voting. This decision was mostly due to the very different levels of activity on the two sides. There is significantly greater activity centered around the markets and what seemed to be of the greatest interest to users. However, governance actions can still be parsed from `ethereum.events`. - -**Feedback and Improvements:** - -All feedback and criticism remain very much appreciated! Send a ping in [our discord](https://discord.gg/uW5jK2jRTg)! (@connorH) or send us an email at _hello@flipsidecrypto.com._ - -**General Tips**: - -* Using marketstats as a starting point is often an excellent idea, as it tends to connect to each of the other tables and is very centrally located. This table aggregates by hour, so join on `market_stats.date_trunc('hour',block_hour) = block_timestamp AND market_stats.ctoken_address = ctoken` -* As mentioned we only have data going back to October, but we are in the process of completing a backfill of our data! -* Governance actions may not have their own tables but they are still available. If you find the appropriate event you can locate it within the table ethereum.events\_emitted . If you think you'd be using this routinely let us know, and we'll create more views for these events. - -For instance new proposals to vote on are created using ProposalCreated, so you could list all created proposals with - -``` -SELECT - block_timestamp, - tx_id, - event_name, - CASE WHEN contract_address = '0xc0da01a04c3f3e0be433606045bb7017a7323e38' THEN 'Alpha' ELSE 'Bravo' - END AS governor_contract, - event_inputs:id AS proposal_id, - REGEXP_REPLACE(event_inputs:proposer,'\"','') AS proposer, - REGEXP_REPLACE(event_inputs:targets,'\"','') AS targets, - REGEXP_REPLACE(event_inputs:description,'\"','') AS description -FROM ethereum.events_emitted -WHERE -contract_address IN ('0xc0da01a04c3f3e0be433606045bb7017a7323e38', -- governance contracts - '0xc0da02939e1441f497fd74f78ce7decb17b66529') -AND -block_timestamp >= CURRENT_DATE - 120 -AND event_name = 'ProposalCreated' -- the event -``` - -**Pro Tip for advanced users:** - -* The documentation for compound combines excellently with the events\_emitted table. If you can find an event in the docs there, you can find it in the link below or [here](https://compound.finance/docs/ctokens#key-events)! - - [https://compound.finance/docs/ctokens#key-events](https://compound.finance/docs/ctokens#key-events) diff --git a/data/archive/tables/compound-tables/borrows.md b/data/archive/tables/compound-tables/borrows.md deleted file mode 100644 index b554497..0000000 --- a/data/archive/tables/compound-tables/borrows.md +++ /dev/null @@ -1,17 +0,0 @@ -# Borrows - -Borrows exist within the `compound` schema, as `compound.borrows` - -| Field | Type | Description | -| -------------------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC block timestamp for parent block | -| `borrower` | address | Address that initiated a borrow event | -| `borrows_contract_address` | address | Address of borrowed token | -| `borrows_contract_symbol` | string | Symbol of borrowed token | -| `ctoken` | address | Respective cToken address to the borrowed token | -| `ctoken_symbol` | string | Respective cToken symbol to the borrowed token | -| `loan_amount` | number | Native amount of borrow (decimal adjusted) | -| `loan_amount_usd` | number | The equivalent borrow amount in USD. Note this is computed by taking the average hourly price around the time of the tx event | -| `tx_id` | string | Transaction id for this borrow | - diff --git a/data/archive/tables/compound-tables/liquidations.md b/data/archive/tables/compound-tables/liquidations.md deleted file mode 100644 index 677f283..0000000 --- a/data/archive/tables/compound-tables/liquidations.md +++ /dev/null @@ -1,17 +0,0 @@ -# Liquidations - -Liquidations exist within the `compound` schema, as `compound.liquidations` - -| Field | Type | Description | -| ------------------------------ | --------- | ---------------------------------------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block height this event was recorded at. | -| `block_timestamp` | timestamp | UTC block timestamp for parent block | -| `ctoken` | address | Address of cToken | -| `ctoken_symbol` | string | Symbol of cToken | -| `liquidator` | address | Address that initiated the liquidation | -| `ctokens_seized` | number | cToken collateral held by the insolvent borrower that is taken by the liquidator | -| `liquidation_amount` | number | Native amount liquidated (decimal adjusted) | -| `liquidation_amount_usd` | number | The equivalent liquidated amount in USD. Note this is computed by taking the average hourly price around the time of the tx event. | -| `liquidation_contract_address` | address | Address of liquidated token | -| `liquidation_contract_symbol` | string | Symbol of liquidated token | -| `tx_id` | string | Transaction id for this liquidation | diff --git a/data/archive/tables/compound-tables/market-stats.md b/data/archive/tables/compound-tables/market-stats.md deleted file mode 100644 index be4324c..0000000 --- a/data/archive/tables/compound-tables/market-stats.md +++ /dev/null @@ -1,27 +0,0 @@ -# Market Stats - -Market Stats exist within the `compound` schema, as `compound.market_stats` - -| **Field** | **Type** | Description | -| ----------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `block_hour` | string | Market stats are aggregated by hour in UTC. `date_trunc(‘hour’,block_timestamp)` for joins on other tables | -| `contract_name` | string | market/cToken name | -| `ctoken_address` | address | market/cToken address (i.e. cUSDC) | -| `underlying_contract` | address | Address of the underlying token the market serves (i.e. USDC) | -| `underlying_symbol` | string | Symbol of the underlying token the market serves | -| `token_price` | number | Price of the underlying token (i.e. USDC) | -| `ctoken_price` | number | Price of the cToken (i.e. cUSDC) | -| `reserves_token_amount` | number | Reserves are amounts set aside by the market that can be used/affected by governance actions through proposals voted on by COMP holders | -| `borrows_token_amount` | number | Amount borrowed from the market | -| `supply_token_amount` | number | Amount (in terms of the cToken) supplied to the market through suppliers | -| `supply_usd` | number | Supply converted to USD values as of the hour recorded | -| `reserves_usd` | number | Reserves converted to USD values as of the hour recorded | -| `borrows_usd` | number | Borrows converted to USD values as of the hour recorded | -| `comp_speed` | number | COMP is a governance token distributed equally to both suppliers and borrowers (the idea being the users of the protocol are also the ones who should be able to vote on governance actions). Comp speed controls the rate at which comp is distributed to users of the market, per block | -| `supply_apy` | number | The supplier’s APY in terms of the underlying asset. It depends on the exchange rate between the cToken/underlying token (cUSDC/USDC). This is interest paid to the supplier for their stake | -| `borrow_apy` | number | The borrower’s APY in terms of the underlying asset. It depends on the exchange rate between the cToken/underlying token (cUSDC/USDC). This is interest paid by the borrower on their loan | -| `comp_price` | number | The price of the COMP governance token | -| `comp_speed_usd` | number | Comp distributed to markets converted to USD | -| `comp_apy_borrow` | number | The APY one can expect based on COMP governance tokens distributed (which in turn can be staked elsewhere, or used in voting) | -| `comp_apy_supply` | number | The APY one can expect based on COMP governance tokens distributed (which in turn can be staked elsewhere, or used in voting) | - diff --git a/data/archive/tables/compound-tables/mints.md b/data/archive/tables/compound-tables/mints.md deleted file mode 100644 index b662b9e..0000000 --- a/data/archive/tables/compound-tables/mints.md +++ /dev/null @@ -1,18 +0,0 @@ -# Deposits - -Deposits exist within the `compound` schema, as `compound.deposits` - -| Field | Type | Description | -| --------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC block timestamp for parent block | -| `ctoken` | address | cToken address | -| `ctoken_symbol` | string | cToken symbol | -| `issued_tokens` | number | Amount of cToken issued for providing liquidity | -| `supplied_base_assets` | number | Native amount provided as liquidity (decimal adjusted) | -| `supplied_base_assets_usd` | number | The equivalent liquidity amount in USD. Note this is computed by taking the average hourly price around the time of the tx event | -| `supplied_contract_address` | address | Address of token provided liquidity for | -| `supplied_symbol` | string | Symbol of token provided liquidity for | -| `supplier` | address | Address of liquidity provider | -| `tx_id` | string | Transaction id for this mint | - diff --git a/data/archive/tables/compound-tables/redemptions.md b/data/archive/tables/compound-tables/redemptions.md deleted file mode 100644 index ff6620c..0000000 --- a/data/archive/tables/compound-tables/redemptions.md +++ /dev/null @@ -1,17 +0,0 @@ -# Redemptions - -Redemptions exist within the `compound` schema, as `compound.redemptions` - -| Field | Type | Description | -| --------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC block timestamp for parent block | -| `ctoken` | address | cToken address | -| `ctoken_symbol` | string | cToken symbol | -| `received_amount` | number | Native amount provided as liquidity (decimal adjusted) | -| `received_amount_usd` | number | The equivalent liquidity amount in USD. Note this is computed by taking the average hourly price around the time of the tx event | -| `received_contract_address` | address | Address of token refunded as part of the redemption | -| `received_contract_symbol` | string | Symbol of token refunded as part of the redemption | -| `redeemed_ctoken` | number | cToken deposited to redeem | -| `supplier` | address | Address of liquidity provider | -| `tx_id` | string | Transaction id for the redemption(s) | diff --git a/data/archive/tables/compound-tables/repayments.md b/data/archive/tables/compound-tables/repayments.md deleted file mode 100644 index 440e043..0000000 --- a/data/archive/tables/compound-tables/repayments.md +++ /dev/null @@ -1,19 +0,0 @@ -# Repayments - - - -Repayments exist within the `compound` schema, as `compound.repayments` - -| Field | Type | Description | -| ------------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block height this event was recorded at | -| `block_timestamp` | timestamp | UTC block timestamp for parent block | -| `borrower` | address | Address of initial borrower | -| `ctoken` | address | cToken address | -| `ctoken_symbol` | string | cToken symbol | -| `payer` | address | Address of user that paid out the loan | -| `repay_contract_address` | address | Address of token refunded as part of the redemption | -| `repay_contract_symbol` | string | Symbol of token refunded as part of the redemption | -| `repayed_amount` | number | Native amount repaid on loan (decimal adjusted) | -| `repayed_amount_usd` | number | The equivalent repaid amount in USD. Note this is computed by taking the average hourly price around the time of the tx event | -| `tx_id` | string | Transaction id for this repayment | diff --git a/data/archive/tables/cosmos-tables.md b/data/archive/tables/cosmos-tables.md deleted file mode 100644 index 8edab9f..0000000 --- a/data/archive/tables/cosmos-tables.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Cosmos Tables - -### **Current Cosmos Tables** - -**Blockchain:** [Cosmos](https://cosmos.network/) - -The Cosmos schema is currently in lite mode. All block, transaction, and message data is available back to the genesis block. However, no easy or curated tables are currently available. - -[Dim Labels](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_dim\_labels) - -[Dim Tokens](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_dim\_tokens) - -[Fact Blocks](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_blocks) - -[Fact Transactions](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_transactions) - -[Fact Msgs](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_msgs) - -[Fact Msg Attributes](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_msg\_attributes) - -[Fact Transfers](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_transfers) - -[Fact Validators](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_validators) - -[Fact Governance Votes](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_governance\_votes) - -[Fact Governance Submit Proposal](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_governance\_submit\_proposal) - -[Fact Governance Proposal Deposits](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_fact\_governance\_proposal\_deposits) - -[Dim Vote Options](https://flipsidecrypto.github.io/cosmos-models/#!/model/model.cosmos\_models.core\_\_dim\_vote\_options) diff --git a/data/archive/tables/crosschain-tables/README.md b/data/archive/tables/crosschain-tables/README.md deleted file mode 100644 index fe01a8a..0000000 --- a/data/archive/tables/crosschain-tables/README.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Crosschain Tables - -These tables contain data from multiple blockchains. The following tables are available in the Crosschain schema:\ -\ -[Address Labels](crosschain-address-labels.md)\ -\ -[Address Tags](crosschain-address-tags.md) - -[Dim Dates](dim-dates.md) - - - -Also see docs for legacy crosschain tables here: - -[Crosschain EZ\_Borrowing](https://flipsidecrypto.github.io/sql\_models/#!/model/model.sql\_models.crosschain\_\_ez\_borrowing)\ -[Crosschain EZ\_Lending](https://flipsidecrypto.github.io/sql\_models/#!/model/model.sql\_models.crosschain\_\_ez\_lending)\ -[Crosschain EZ\_Swaps](https://flipsidecrypto.github.io/sql\_models/#!/model/model.sql\_models.crosschain\_\_ez\_swaps)\ -[Crosschain NFT Fair Market Value](https://flipsidecrypto.github.io/sql\_models/#!/model/model.sql\_models.crosschain\_\_nft\_fair\_market\_value)\ -[Crosschain Address Labels](https://flipsidecrypto.github.io/sql\_models/#!/model/model.sql\_models.crosschain\_\_address\_labels) - diff --git a/data/archive/tables/crosschain-tables/crosschain-address-labels.md b/data/archive/tables/crosschain-tables/crosschain-address-labels.md deleted file mode 100644 index fafdd10..0000000 --- a/data/archive/tables/crosschain-tables/crosschain-address-labels.md +++ /dev/null @@ -1,19 +0,0 @@ -# Crosschain Address Labels - -### Table Schema - -`crosschain.address_labels` - -Also learn more about labels [here](../../../flipside-data/labels/). - -| Field | Type | Description | -| ------------------- | --------- | -------------------------------------------------------------------------- | -| system\_created\_at | timestamp | The time when the label was sent to the table. | -| insert\_date | timestamp | The date the label was inserted into the table. | -| blockchain | string | The name of the blockchain. | -| creator | string | The name of the creator of the label. | -| address | string | The address the label belongs to. Use this to join to other tables. | -| label\_type | string | A high-level category describing the addresses main function or ownership. | -| label\_subtype | string | A sub-category nested within label type providing further detail. | -| address\_name | string | Name of the address or the label. | -| project\_name | string | Name of the controlling entity of the address. | diff --git a/data/archive/tables/crosschain-tables/crosschain-address-tags.md b/data/archive/tables/crosschain-tables/crosschain-address-tags.md deleted file mode 100644 index 62dccc9..0000000 --- a/data/archive/tables/crosschain-tables/crosschain-address-tags.md +++ /dev/null @@ -1,17 +0,0 @@ -# Crosschain Address Tags - -### Table Schema - -`crosschain.core.address_tags` - -Also learn more about tags [here](broken-reference). - -| Field | Type | Description | -| ----------- | --------- | ---------------------------------------------------------------------- | -| blockchain | string | The name of the blockchain. | -| creator | string | The name of the creator of the tag. | -| address | string | The address that the tag belongs to. Use this to join to other tables. | -| tag\_name | string | The name of the tag or the tag itself. | -| tag\_type | string | The type of the tag. | -| start\_date | timestamp | The starting date that the tag is valid for. | -| end\_date | timestamp | The ending date of the tag's validity. | diff --git a/data/archive/tables/crosschain-tables/dim-asset-metadata.md b/data/archive/tables/crosschain-tables/dim-asset-metadata.md deleted file mode 100644 index 4d3c6e9..0000000 --- a/data/archive/tables/crosschain-tables/dim-asset-metadata.md +++ /dev/null @@ -1,16 +0,0 @@ -# Dim Asset Metadata - -### Table Schema - -A dimension table holding provider specific asset metadata - -`crosschain.dim_asset_metadata` - -| Field | Type | Description | -| -------------- | ------ | -------------------------------------------------------------- | -| PROVIDER | STRING | provider of the data | -| ID | STRING | unique identifier representing the asset | -| NAME | STRING | name of asset | -| SYMBOL | STRING | symbol of asset | -| TOKEN\_ADDRESS | STRING | specific address representing the asset in a specific platform | -| PLATFORM | STRING | platform where this asset has a token address | diff --git a/data/archive/tables/crosschain-tables/dim-date-hours.md b/data/archive/tables/crosschain-tables/dim-date-hours.md deleted file mode 100644 index f406dc1..0000000 --- a/data/archive/tables/crosschain-tables/dim-date-hours.md +++ /dev/null @@ -1,11 +0,0 @@ -# Dim Date Hours - -### Table Schema - -Hold rows for each hour from 2017 to current timestamp (UTC) - -`crosschain.dim_date_hours` - -| Field | Type | Description | -| ---------- | --------- | ----------------------------- | -| DATE\_HOUR | timestamp | Specific hour of a given date | diff --git a/data/archive/tables/crosschain-tables/dim-dates.md b/data/archive/tables/crosschain-tables/dim-dates.md deleted file mode 100644 index 6ee1313..0000000 --- a/data/archive/tables/crosschain-tables/dim-dates.md +++ /dev/null @@ -1,46 +0,0 @@ -# Dim Dates - -### Table Schema - -A utility table of common date constructs. - -`crosschain.dim_dates` - -| Field | Type | Description | -| ----------------------------------- | ------ | ----------------------------------------------------------------------- | -| DATE\_DAY | DATE | date for the row | -| PRIOR\_DATE\_DAY | DATE | date before DATE\_DAY | -| NEXT\_DATE\_DAY | DATE | date after DATE\_DAY | -| PRIOR\_YEAR\_DATE\_DAY | DATE | date exactly 1 year before DATE\_DAY | -| PRIOR\_YEAR\_OVER\_YEAR\_DATE\_DAY | DATE | date exactly 1 year after DATE\_DAY | -| DAY\_OF\_WEEK | NUMBER | number representing day of week for DATE\_DAY where 1=Sunday | -| DAY\_OF\_WEEK\_ISO | NUMBER | number representing day of week for DATE\_DAY where 1=Monday | -| DAY\_OF\_WEEK\_NAME | STRING | day of week name for DATE\_DAY | -| DAY\_OF\_WEEK\_NAME\_SHORT | STRING | day of week abbreviation for DATE\_DAY | -| DAY\_OF\_MONTH | NUMBER | day of month for DATE\_DAY | -| DAY\_OF\_YEAR | NUMBER | day of year for DATE\_DAY | -| WEEK\_START\_DATE | DATE | date representing the start of the week for DATE\_DAY | -| WEEK\_END\_DATE | DATE | date representing the end of the week for DATE\_DAY | -| PRIOR\_YEAR\_WEEK\_START\_DATE | DATE | date representing the start of the week for PRIOR\_YEAR\_DATE\_DAY | -| PRIOR\_YEAR\_WEEK\_END\_DATE | DATE | date representing the end of the week for PRIOR\_YEAR\_DATE\_DAY | -| WEEK\_OF\_YEAR | NUMBER | number representing the week of the year for DATE\_DAY | -| ISO\_WEEK\_START\_DATE | DATE | ISO date representing the start of the week for DATE\_DAY | -| ISO\_WEEK\_END\_DATE | DATE | ISO date representing the end of the week for DATE\_DAY | -| PRIOR\_YEAR\_ISO\_WEEK\_START\_DATE | DATE | ISO date representing the start of the week for PRIOR\_YEAR\_DATE\_DAY | -| PRIOR\_YEAR\_ISO\_WEEK\_END\_DATE | DATE | ISO date representing the end of the week for PRIOR\_YEAR\_DATE\_DAY | -| ISO\_WEEK\_OF\_YEAR | NUMBER | number representing the ISO week of the year for DATE\_DAY | -| PRIOR\_YEAR\_WEEK\_OF\_YEAR | NUMBER | number representing the week of the year for PRIOR\_YEAR\_DATE\_DAY | -| PRIOR\_YEAR\_ISO\_WEEK\_OF\_YEAR | NUMBER | number representing the ISO week of the year for PRIOR\_YEAR\_DATE\_DAY | -| MONTH\_OF\_YEAR | NUMBER | number representing the month of the year for DATE\_DAY | -| MONTH\_NAME | STRING | month of year name for DATE\_DAY | -| MONTH\_NAME\_SHORT | STRING | month of year abbreviation for DATE\_DAY | -| MONTH\_START\_DATE | DATE | first date of month for DATE\_DAY | -| MONTH\_END\_DATE | DATE | last date of month for DATE\_DAY | -| PRIOR\_YEAR\_MONTH\_START\_DATE | DATE | first date of month for PRIOR\_YEAR\_DATE\_DAY | -| PRIOR\_YEAR\_MONTH\_END\_DATE | DATE | last date of month for PRIOR\_YEAR\_DATE\_DAY | -| QUARTER\_OF\_YEAR | NUMBER | number representing quarter for DATE\_DAY | -| QUARTER\_START\_DATE | DATE | first date of quarter for DATE\_DAY | -| QUARTER\_END\_DATE | DATE | last date of quarter for DATE\_DAY | -| YEAR\_NUMBER | NUMBER | number presenting the year for DATE\_DAY | -| YEAR\_START\_DATE | DATE | first date of year for DATE\_DAY | -| YEAR\_END\_DATE | DATE | last date of year for DATE\_DAY | diff --git a/data/archive/tables/crosschain-tables/fact-hourly-prices.md b/data/archive/tables/crosschain-tables/fact-hourly-prices.md deleted file mode 100644 index 6529d9f..0000000 --- a/data/archive/tables/crosschain-tables/fact-hourly-prices.md +++ /dev/null @@ -1,17 +0,0 @@ -# Fact Hourly Prices - -### Table Schema - -A fact table holding provider asset prices - -`crosschain.fact_hourly_prices` - -| Field | Type | Description | -| -------------- | --------- | ---------------------------------------- | -| PROVIDER | STRING | provider of the data | -| ID | STRING | unique identifier representing the asset | -| RECORDED\_HOUR | TIMESTAMP | opening hour of price data | -| OPEN | FLOAT | open price of asset for hour | -| HIGH | FLOAT | high price of asset for hour | -| LOW | FLOAT | low price of asset for hour | -| COSE | FLOAT | close price of asset for hour | diff --git a/data/archive/tables/ethereum-beacon-chain-tables.md b/data/archive/tables/ethereum-beacon-chain-tables.md deleted file mode 100644 index 26292db..0000000 --- a/data/archive/tables/ethereum-beacon-chain-tables.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Ethereum Beacon Chain Tables - -Documentation for Ethereum.Beacon\_chain tables can be found [here](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.beacon\_chain\_\_fact\_attestations). - -The public Github repo with source code is [here](https://github.com/FlipsideCrypto/ethereum-models/tree/main/models/beacon\_chain). - -Quick Links to Table Docs: - -* [`fact_blocks`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.beacon\_chain\_\_fact\_blocks) -* [`fact_deposits`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.beacon\_chain\_\_fact\_deposits) -* [`fact_attestations`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.beacon\_chain\_\_fact\_attestations) diff --git a/data/archive/tables/ethereum-beta-tables.md b/data/archive/tables/ethereum-beta-tables.md deleted file mode 100644 index fc797cb..0000000 --- a/data/archive/tables/ethereum-beta-tables.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -description: >- - [Legacy Documentation, Not Maintained, For Reference Only] These tables are - subject to change without notice! Do not use these for dashboards or important - analysis. ---- - -# Ethereum Beta Tables - -Please report bugs in discord as you find them, and know we are already working on many of the issues you find, including coverage of popular contracts such as Uni v3 pools and Blur exchange. - -Links to the `ethereum.beta` tables can be found here: - -[`beta.fact_decoded_logs`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.beta\_\_fact\_decoded\_logs) diff --git a/data/archive/tables/ethereum-chainlink-tables.md b/data/archive/tables/ethereum-chainlink-tables.md deleted file mode 100644 index 93f820e..0000000 --- a/data/archive/tables/ethereum-chainlink-tables.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Ethereum Chainlink Tables - -Documentation for `ethereum.chainlink` tables can be found here: - -* [`dim_oracle_feeds`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.chainlink\_\_dim\_oracle\_feeds) -* [`fact_oracle_feeds`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.chainlink\_\_fact\_oracle\_feeds) -* [`ez_oracle_feeds`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.chainlink\_\_ez\_oracle\_feeds) - -Public github repo available [here](https://github.com/FlipsideCrypto/ethereum-models/tree/main/models/chainlink). diff --git a/data/archive/tables/ethereum-maker-dao-tables.md b/data/archive/tables/ethereum-maker-dao-tables.md deleted file mode 100644 index b6f7547..0000000 --- a/data/archive/tables/ethereum-maker-dao-tables.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Ethereum Maker DAO Tables - -Documentation for the curated Ethereum Maker DAO Tables are included in [the Ethereum Core DBT documentation](https://flipsidecrypto.github.io/ethereum-models/#!/overview/ethereum\_models) under the following path in the sidebar: Projects/Ethereum\_models/models/gold/maker - -The public Github repo with Ethereum Maker DAO model source code is similarly in the Ethereum Core repo [here](https://github.com/FlipsideCrypto/ethereum-models).\ -\ -Quick Links to Table Docs:\ -\ -[Maker EZ Delegations](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_delegations) - -[Maker EZ Deposits](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_deposits) - -[Maker EZ Flash Loans](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_flash\_loans) - -[Maker EZ Governance Votes](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_governance\_votes) - -[Maker EZ Liquidations](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_liquidations) - -[Maker EZ Repayments](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_repayments) - -[Maker EZ Vault Creation](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_vault\_creation) - -[Maker EZ Withdrawals](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.maker\_\_ez\_withdrawals) diff --git a/data/archive/tables/ethereum-sushi-tables.md b/data/archive/tables/ethereum-sushi-tables.md deleted file mode 100644 index fcafa41..0000000 --- a/data/archive/tables/ethereum-sushi-tables.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Ethereum Sushi Tables - -Documentation for the curated Ethereum Sushi Tables are included in [the Ethereum Core DBT documentation](https://flipsidecrypto.github.io/ethereum-models/#!/overview/ethereum\_models) under the following path in the sidebar: Projects/Ethereum\_models/models/sushi - -The public Github repo with Ethereum Maker DAO model source code is similarly in the Ethereum Core repo [here](https://github.com/FlipsideCrypto/ethereum-models).\ -\ -Quick Links to Table Docs: - -* [`ez_swaps`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.sushi\_\_ez\_swaps) -* [ez\_lending](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.sushi\_\_ez\_lending) -* [ez\_borrowing](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.sushi\_\_ez\_borrowing) diff --git a/data/archive/tables/ethereum-tables.md b/data/archive/tables/ethereum-tables.md deleted file mode 100644 index 70294fb..0000000 --- a/data/archive/tables/ethereum-tables.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Ethereum Tables - -Documentation for `Ethereum_core` tables can be found [here](https://flipsidecrypto.github.io/ethereum-models/#!/overview). - -The public Github repo with Ethereum Core model source code is [here](https://github.com/FlipsideCrypto/ethereum-models).\ -\ -Quick Links to Table Docs:\ - - -* [`fact_event_logs`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_fact\_event\_logs) -* [`fact_hourly_token_prices`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_fact\_hourly\_token\_prices) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_fact\_token\_transfers) -* [`fact_transactions`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_fact\_blocks) -* [`fact_decoded_event_logs`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_fact\_decoded\_event\_logs) -* [`ez_dex_swaps`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_dex\_swaps) -* [`ez_token_transfers`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_token\_transfers) -* [`ez_snapshot`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_snapshot) -* [`dim_contracts`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_dim\_contracts) -* [`dim_contract_abis`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_dim\_contract\_abis) -* [`dim_labels`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_dim\_labels) -* [`dim_dex_liquidity_pools`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_dim\_dex\_liquidity\_pools) -* [`dim_function_signatures`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_dim\_function\_signatures) -* [`dim_event_signatures`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_dim\_event\_signatures) -* [`ez_decoded_event_logs`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_decoded\_logs) -* [`ez_nft_sales`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_nft\_sales) -* [`ez_nft_transfers`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_nft\_transfers) -* [`ez_nft_mints`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_nft\_mints) -* [`ez_eth_transfers`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_eth\_transfers) -* [`ez_balance_deltas`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_balance\_deltas) -* [`ez_current_balances`](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.core\_\_ez\_current\_balances) - - - -Note: when working with the `fact_transactions` and `fact_event_logs` tables, you may find it useful to use the [ethereum.public.udf\_hex\_to\_int() function](../../../resources/hex-to-integer-function.md).\ -\ diff --git a/data/archive/tables/flow-tables/README.md b/data/archive/tables/flow-tables/README.md deleted file mode 100644 index 240bdd4..0000000 --- a/data/archive/tables/flow-tables/README.md +++ /dev/null @@ -1,69 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# FLOW Tables - -The [Flow blockchain](https://www.onflow.org/primer) is a fast, decentralized blockchain that enhances the development of decentralized applications and NFTs. Like other blockchains, Flow has its own native currency, known as FLOW. FLOW is the reserve asset used to pay transaction costs and staking on the network. - -## Documentation - -For more detailed documentation on the model structures that build up the `core` views you use, please refer to the full dbt documentation below, which includes a lineage graph of the models and data flow. - -{% embed url="https://flipside-flow.netlify.app/#!/overview" %} -Full Project Documentation -{% endembed %} - -The public Github repo with Flow model source code is [here](https://github.com/FlipsideCrypto/flow-models). - -### Quick Docs - -The following pages offer quick documentation with details around the schema, and descriptions of each column. - -{% content-ref url="blocks.md" %} -[blocks.md](blocks.md) -{% endcontent-ref %} - -{% content-ref url="bridge-transactions.md" %} -[bridge-transactions.md](bridge-transactions.md) -{% endcontent-ref %} - -{% content-ref url="contract-labels.md" %} -[contract-labels.md](contract-labels.md) -{% endcontent-ref %} - -{% content-ref url="events.md" %} -[events.md](events.md) -{% endcontent-ref %} - -{% content-ref url="moment-metadata.md" %} -[moment-metadata.md](moment-metadata.md) -{% endcontent-ref %} - -{% content-ref url="nft-sales.md" %} -[nft-sales.md](nft-sales.md) -{% endcontent-ref %} - -{% content-ref url="prices.md" %} -[prices.md](prices.md) -{% endcontent-ref %} - -{% content-ref url="swaps.md" %} -[swaps.md](swaps.md) -{% endcontent-ref %} - -{% content-ref url="token-transfers.md" %} -[token-transfers.md](token-transfers.md) -{% endcontent-ref %} - -{% content-ref url="topshot-metadata.md" %} -[topshot-metadata.md](topshot-metadata.md) -{% endcontent-ref %} - -{% content-ref url="transactions.md" %} -[transactions.md](transactions.md) -{% endcontent-ref %} - -{% content-ref url="validator-labels.md" %} -[validator-labels.md](validator-labels.md) -{% endcontent-ref %} diff --git a/data/archive/tables/flow-tables/blocks.md b/data/archive/tables/flow-tables/blocks.md deleted file mode 100644 index b37137e..0000000 --- a/data/archive/tables/flow-tables/blocks.md +++ /dev/null @@ -1,17 +0,0 @@ -# Blocks - - - -| Column | Type | Description | -| ---------------- | -------------- | ----------------------------------------------------------------- | -| block\_height | NUMBER | The block height the block was recorded at. | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| network | TEXT | The blockchain network the block or transaction occurred on. | -| chain\_id | TEXT | The id for the chain of the network on which this block occurred. | -| tx\_count | NUMBER | The number of transactions in the block. | -| id | TEXT | The block hash. | -| parent\_id | TEXT | The block hash for the parent block. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_blocks" %} -Full Documentation for Core Blocks -{% endembed %} diff --git a/data/archive/tables/flow-tables/bridge-transactions.md b/data/archive/tables/flow-tables/bridge-transactions.md deleted file mode 100644 index 02072f7..0000000 --- a/data/archive/tables/flow-tables/bridge-transactions.md +++ /dev/null @@ -1,19 +0,0 @@ -# Bridge Transactions - - - -| tx\_id | TEXT | ID for the transaction. | -| --------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| block\_height | NUMBER | The block height the block was recorded at. | -| bridge\_contract | TEXT | The contract address for the bridge used to move tokens to or from Flow. | -| token\_contract | TEXT | The contract address for a token on the Flow blockchain. | -| amount | FLOAT | The amount of the asset involved in the transaction. | -| flow\_wallet\_address | TEXT | Address of a FLOW wallet related to the transaction. | -| blockchain | TEXT | The name of the blockchain for this address or transaction. | -| direction | TEXT | For bridging transactions, inbound refers to tokens bridged to the Flow blockchain, while outbound indicated tokens were sent from Flow to another (i.e. to Ethereum, BSC, etc.). | -| bridge | TEXT | The name of the bridge or protocol used. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_bridge_transactions" %} -Full Documentation for Core Bridge Transactions -{% endembed %} diff --git a/data/archive/tables/flow-tables/contract-labels.md b/data/archive/tables/flow-tables/contract-labels.md deleted file mode 100644 index 51af1f2..0000000 --- a/data/archive/tables/flow-tables/contract-labels.md +++ /dev/null @@ -1,13 +0,0 @@ -# Contract Labels - - - -| Column | Type | Description | -| ---------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| event\_contract | TEXT | The contract called for this event. This is equivalent to the Contract column on Flowscan and is a concatenation of the contract's account address and primary name. | -| contract\_name | TEXT | The primary name of the contract, derived from the full contract address. | -| account\_address | TEXT | The account address in 0x form that instantiated the contract called in the event. Note, on the Flow blockchain the account and the contract are separate as the account may have created more than one contract, in rare instances, such as the following FLOW address 0x8624b52f9ddcd04a. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__dim_contract_labels" %} -Full Documentation for Core Contract Labels -{% endembed %} diff --git a/data/archive/tables/flow-tables/events.md b/data/archive/tables/flow-tables/events.md deleted file mode 100644 index f929b88..0000000 --- a/data/archive/tables/flow-tables/events.md +++ /dev/null @@ -1,18 +0,0 @@ -# Events - - - -| Column | Type | Description | -| ---------------- | -------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| tx\_id | TEXT | ID for the transaction. | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| block\_height | NUMBER | The block height the block was recorded at. | -| tx\_succeeded | BOOLEAN | Transaction status, if it succeeded or failed. | -| event\_index | NUMBER | The index of the event within the transaction, i.e. in what order the events occurred. | -| event\_contract | TEXT | The contract called for this event. This is equivalent to the Contract column on Flowscan and is a concatenation of the contract's account address and primary name. | -| event\_type | TEXT | The type of method called on the event\_contract. This is equivalent to the Type column on Flowscan. | -| event\_data | OBJECT | The data passed to the event | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_events" %} -Full Documentation for Core Events -{% endembed %} diff --git a/data/archive/tables/flow-tables/moment-metadata.md b/data/archive/tables/flow-tables/moment-metadata.md deleted file mode 100644 index 214aee6..0000000 --- a/data/archive/tables/flow-tables/moment-metadata.md +++ /dev/null @@ -1,22 +0,0 @@ -# Moment Metadata - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__dim_moment_metadata" %} -Full documentation for the Moment Metadata table -{% endembed %} - - - -| Column | Description | -| --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| nft\_collection | The contract address or ID for the NFT Collection. | -| nft\_id | The id of the NFT, usually a number. | -| serial\_number | The serial number for the Moment, such as 25, within the collection. | -| max\_mint\_size | The gross NFTs minted for the batch. | -| play\_id | The numeric ID of the play for the moment. For example, with topshot moment ABC may be a version of Play 123. The play id is 123 and moment metadata is associated with the play, rather than the moment. | -| series\_id | The numeric ID for the series of moments or plays. This corresponds with the series column found in some metadata tables. | -| series\_name | The series for this particular set of drops. | -| set\_id | The numeric ID for the set. This corresponds with the set name found in some metadata columns. | -| set\_name | Name of the set in which the moment was dropped. | -| edition\_id | The numeric ID for the edition of moments. This is likely a bundle of moment NFTs within the same type of play, differentiated by some trait like rarity. | -| tier | The tiered rarity of the edition. | -| metadata | A JSON object containing moment or play metadata. | diff --git a/data/archive/tables/flow-tables/nft-sales.md b/data/archive/tables/flow-tables/nft-sales.md deleted file mode 100644 index caeceb8..0000000 --- a/data/archive/tables/flow-tables/nft-sales.md +++ /dev/null @@ -1,23 +0,0 @@ -# NFT Sales - - - -| Column | Type | Description | -| ---------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| tx\_id | TEXT | ID for the transaction. | -| block\_height | NUMBER | The block height the block was recorded at. | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| marketplace | TEXT | Contract address for the marketplace where the transaction occurred. Flow uses a general-purpose contract at \`A.4eb8a10cb9f87357.NFTStorefront\` for a significant number of sales. This column does not necessarily indicate the website or specific platform on which the sale occurred. | -| nft\_collection | TEXT | The contract address or ID for the NFT Collection. | -| nft\_id | TEXT | The id of the NFT, usually a number. | -| buyer | TEXT | The party in the transaction purchasing the asset, this is an account address. | -| seller | TEXT | The party in the transaction selling the asset, this is an account address. | -| price | FLOAT | The price of the asset, in the currency specified in the table. | -| currency | TEXT | The contract address refering to the currency used in the transaction. This may or may not relate to a token in the prices table, depending on the marketplace or transaction. | -| tx\_succeeded | BOOLEAN | Transaction status, if it succeeded or failed. | -| tokenflow | ARRAY | An array of events tracking the flow of tokens, in event\_index order, for a transaction. This is constructed from the following events within a transaction: \`TokensDeposited\`, \`TokensWithdrawn\`, \`ForwardedDeposit\`. | -| counterparties | ARRAY | An array containing the addresses interacted with during the tokenflow of the transaction. This contains all payers and recipients of tokens within the transaction. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_nft_sales" %} -Full Documentation for Core NFT Sales -{% endembed %} diff --git a/data/archive/tables/flow-tables/prices.md b/data/archive/tables/flow-tables/prices.md deleted file mode 100644 index ea811ad..0000000 --- a/data/archive/tables/flow-tables/prices.md +++ /dev/null @@ -1,16 +0,0 @@ -# Prices - - - -| Column | Type | Description | -| --------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| timestamp | TIMESTAMP\_NTZ | Timestamp of when the data was recorded from the API or from on-chain data, depending on the source. | -| token | TEXT | Friendly name of the crypto token, e.g. Blocto Token. | -| symbol | TEXT | Short-name symbol for the crypto token, e.g. BLT. | -| token\_contract | TEXT | The contract address for a token on the Flow blockchain. | -| price\_usd | FLOAT | Asset price, in USD. | -| source | TEXT | Data source for the record in question. E.g. for the prices table, this may be an API or derived from swaps. Stableswap indicates the price was calculated from a swap where one of the assets was a stablecoin, while for a flowswap the other token was Flow. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_prices" %} -Full Documentation for Core Prices -{% endembed %} diff --git a/data/archive/tables/flow-tables/swaps.md b/data/archive/tables/flow-tables/swaps.md deleted file mode 100644 index e605adb..0000000 --- a/data/archive/tables/flow-tables/swaps.md +++ /dev/null @@ -1,19 +0,0 @@ -# Swaps - - - -| Column | Type | Description | -| -------------------- | -------------- | ------------------------------------------------------------------------------------------ | -| tx\_id | TEXT | ID for the transaction. | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| block\_height | NUMBER | The block height the block was recorded at. | -| swap\_contract | TEXT | The smart contract address of the DEX swap pool. | -| trader | TEXT | The account address of the trader performing the swap action. | -| token\_out\_amount | FLOAT | The amount of the token being swapped that the trader is sending to the pool (selling). | -| token\_out\_contract | TEXT | The smart contract address for the token that is being swapped out of the traders wallet. | -| token\_in\_amount | FLOAT | The amount of the token being swapped that the trader is receiving from the pool (buying). | -| token\_in\_contract | TEXT | The smart contract address for the token that is being swapped into the traders wallet. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_swaps" %} -Full Documentation for Core Swaps -{% endembed %} diff --git a/data/archive/tables/flow-tables/token-transfers.md b/data/archive/tables/flow-tables/token-transfers.md deleted file mode 100644 index 356e28d..0000000 --- a/data/archive/tables/flow-tables/token-transfers.md +++ /dev/null @@ -1,18 +0,0 @@ -# Token Transfers - - - -| Column | Type | Description | -| ---------------- | -------------- | -------------------------------------------------------- | -| tx\_id | TEXT | ID for the transaction. | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| block\_height | NUMBER | The block height the block was recorded at. | -| sender | TEXT | Address sending the transferred token. | -| recipient | TEXT | Address receiving the transferred token. | -| token\_contract | TEXT | The contract address for a token on the Flow blockchain. | -| amount | NUMBER | The amount of the asset involved in the transaction. | -| tx\_succeeded | BOOLEAN | Transaction status, if it succeeded or failed. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__ez_token_transfers" %} -Full Documentation for Core Token Transfers -{% endembed %} diff --git a/data/archive/tables/flow-tables/topshot-metadata.md b/data/archive/tables/flow-tables/topshot-metadata.md deleted file mode 100644 index 521cab0..0000000 --- a/data/archive/tables/flow-tables/topshot-metadata.md +++ /dev/null @@ -1,28 +0,0 @@ -# TopShot Metadata - - - -| Column | Type | Description | -| ------------------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | -| nft\_id | TEXT | The id of the NFT, usually a number. | -| nft\_collection | TEXT | The contract address or ID for the NFT Collection. | -| nbatopshot\_id | TEXT | The ID used by NBA TopShot. This can be pasted into the URL https://nbatopshot.com/moment/{nbatopshot\_id} to view the moment on the marketplace. | -| serial\_number | NUMBER | The serial number for the Moment, such as 25, within the collection. | -| total\_circulation | NUMBER | The total number of moments minted for the particular play. | -| moment\_description | TEXT | Long-form description of the play, from NBA TopShot. | -| player | TEXT | The player who is the focus of the moment. | -| team | TEXT | The team that the player from the moment is on, at the time of the moment. | -| season | TEXT | The season during which the moment occurred. | -| play\_category | TEXT | The broad category of play that is shown in the moment. | -| play\_type | TEXT | The more granular (than play\_category) type of play that is shown in the moment. | -| moment\_date | TIMESTAMP\_NTZ | When the moment occurred. | -| set\_name | TEXT | Name of the set in which the moment was dropped. | -| set\_series\_number | NUMBER | The series number for this particular set of drops, within the set\_name. | -| video\_urls | ARRAY | An array containing links to the moments. | -| moment\_stats\_full | OBJECT | A dictionary of the full moment stats. | -| player\_stats\_game | OBJECT | The statline for the player in the Moment, from the game highlighted. | -| player\_stats\_season\_to\_date | OBJECT | The season stats for the player as of the game featured in the moment. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.silver__nft_topshot_metadata" %} -Full Documentation for TopShot Metadata -{% endembed %} diff --git a/data/archive/tables/flow-tables/transactions.md b/data/archive/tables/flow-tables/transactions.md deleted file mode 100644 index be9f2ce..0000000 --- a/data/archive/tables/flow-tables/transactions.md +++ /dev/null @@ -1,23 +0,0 @@ -# Transactions - - - -| Column | Type | Description | -| ------------------- | -------------- | ----------------------------------------------------------------- | -| tx\_id | TEXT | ID for the transaction. | -| block\_timestamp | TIMESTAMP\_NTZ | The date and time for when the block was written. | -| block\_height | NUMBER | The block height the block was recorded at. | -| chain\_id | TEXT | The id for the chain of the network on which this block occurred. | -| tx\_index | NUMBER | tbd | -| proposer | TEXT | Address of the transaction proposer. | -| payer | TEXT | Address of the wallet paying for the transaction. | -| authorizers | ARRAY | Address(es) authorizing the transaction. | -| count\_authorizers | NUMBER | Number of authorizers | -| gas\_limit | NUMBER | Upper gas limit attached to the transaction. | -| transaction\_result | VARIANT | Outcome of the transaction, including events that were called. | -| tx\_succeeded | BOOLEAN | Transaction status, if it succeeded or failed. | -| error\_msg | TEXT | Error message, if the transaction failed, explaining why. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__fact_transactions" %} -Full Documentation for Core Transactions -{% endembed %} diff --git a/data/archive/tables/flow-tables/validator-labels.md b/data/archive/tables/flow-tables/validator-labels.md deleted file mode 100644 index 7e216e8..0000000 --- a/data/archive/tables/flow-tables/validator-labels.md +++ /dev/null @@ -1,13 +0,0 @@ -# Validator Labels - - - -| Column | Type | Description | -| --------------- | ---- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| node\_id | TEXT | The address, known on the Flow blockchain as Node ID, of the validator. | -| validator\_type | TEXT | The role of the node from one of the following options: collection, consensus, execution, verification, access. See the Flow [documentation](https://docs.onflow.org/node-operation/node-roles/) here for more. | -| project\_name | TEXT | The overarching project name, related to the address name. For example, Kraken (vs. Kraken Deposit Wallet for address\_names). For validators, this will be the name only if provided as most validators do not provide such a name. | - -{% embed url="https://flipside-flow.netlify.app/#!/model/model.flow_models.core__dim_validator_labels" %} -Full Documentation for Core Validator Labels -{% endembed %} diff --git a/data/archive/tables/gnosis-tables.md b/data/archive/tables/gnosis-tables.md deleted file mode 100644 index 522a1c2..0000000 --- a/data/archive/tables/gnosis-tables.md +++ /dev/null @@ -1,31 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Gnosis Tables - -Documentation for \`gnosis\` tables can be found [here](https://flipsidecrypto.github.io/gnosis-models/#!/overview). - -The public Github repo with Gnosis model source code is [here](https://github.com/FlipsideCrypto/gnosis-models). - -Please note, data is in 'lite mode' - meaning, historical data has not yet been backfilled. Please see the `min(block`\_`timestamp)`. - -Quick Links to Table Docs: - -* [`fact_event_logs`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_fact\_event\_logs) -* [`fact_transactions`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_fact\_blocks) -* [`fact_traces`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_fact\_traces) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_fact\_token\_transfers) -* [`dim_labels`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_dim\_labels) -* [`ez_xdai_transfers`](https://flipsidecrypto.github.io/gnosis-models/#!/model/model.gnosis\_models.core\_\_ez\_xdai\_transfers) - - - -`Sushi specific tables:` - -* [sushi\_\_dim\_dex\_pools](https://cloud.getdbt.com/accounts/1258/runs/80579141/docs/#!/model/model.gnosis\_models.sushi\_\_dim\_dex\_pools) -* [sushi\_\_dim\_kashi\_pairs](https://cloud.getdbt.com/accounts/1258/runs/80579141/docs/#!/model/model.gnosis\_models.sushi\_\_dim\_kashi\_pairs) -* [sushi\_\_ez\_swaps ](https://cloud.getdbt.com/accounts/1258/runs/80579141/docs/#!/model/model.gnosis\_models.sushi\_\_ez\_swaps) -* [sushi\_\_ez\_borrowing](https://cloud.getdbt.com/accounts/1258/runs/80579141/docs/#!/model/model.gnosis\_models.sushi\_\_ez\_borrowing) -* [sushi\_\_ez\_lending](https://cloud.getdbt.com/accounts/1258/runs/80579141/docs/#!/model/model.gnosis\_models.sushi\_\_ez\_lending) diff --git a/data/archive/tables/near-tables.md b/data/archive/tables/near-tables.md deleted file mode 100644 index 3bd62b5..0000000 --- a/data/archive/tables/near-tables.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# NEAR Tables - -The data models for NEAR have been updated to use the [Near Lake S3 Bucket](https://docs.near.org/tools/realtime#near-lake-indexer), which is the same data source that feeds NEAR's explorer, as of January 23rd, 2023. The core views available to Flipside data users remain the exact same, but the below linked documentation may be a bit cumbersome until the legacy models are fully deleted. If using the lineage graph, [apply a filter on the tag `s3_load`](https://flipsidecrypto.github.io/near-models/#!/overview?g\_v=1\&g\_i=%2Btag:s3\_load%2B%20%2Btag:api%2B) to exclude legacy models. Further, deprecated models have been moved to `models/silver/legacy/` to keep them out of sight. - -Please click this link below for the full documentation: - -{% embed url="https://flipsidecrypto.github.io/near-models/" %} diff --git a/data/archive/tables/optimism-tables.md b/data/archive/tables/optimism-tables.md deleted file mode 100644 index ee1c0f5..0000000 --- a/data/archive/tables/optimism-tables.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Optimism Tables - -Documentation for `optimism` tables can be found [here](https://flipsidecrypto.github.io/optimism-models/#!/overview). - -The public Github repo with Optimism model source code is [here](https://github.com/FlipsideCrypto/optimism-models).\ -\ -Please note, data is in 'lite mode' - meaning, historical data has not yet been backfilled. Please see the `min(block`\_`timestamp)`\ -\ -Quick Links to Table Docs: - -* [`fact_event_logs`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_fact\_blocks) -* [`fact_transactions`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_fact\_blocks) -* [`fact_traces`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_fact\_traces) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_fact\_token\_transfers) -* [`dim_labels`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_dim\_labels) -* [`dim_contracts`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_dim\_contracts) -* [`ez_eth_transfers`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_ez\_eth\_transfers) -* [`dim_contracts`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.core\_\_dim\_contracts) - -Velodrome - -* [`ez_claimed_rewards`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_claimed\_rewards) -* [`ez_lp_actions`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_lp\_actions) -* [`ez_pool_details`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_pool\_details) -* [`ez_staking_actions`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_staking\_actions) -* [`ez_swaps`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_swaps) -* [`ez_velo_locks`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_velo\_locks) -* [`ez_votes`](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.velodrome\_\_ez\_votes) - - - -`Sushi` - -* [dim\_ _dex_\_ pools](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.sushi\_\_dim\_dex\_pools) -* [ez\_swaps](https://flipsidecrypto.github.io/optimism-models/#!/model/model.optimism\_models.sushi\_\_ez\_swaps) - - - -Note: when working with the `fact_transactions` and `fact_event_logs` tables, you may find it useful to use the [ethereum.public.hex\_to\_int() function](../../../resources/hex-to-integer-function.md). - diff --git a/data/archive/tables/osmosis-tables/README.md b/data/archive/tables/osmosis-tables/README.md deleted file mode 100644 index eabb6a3..0000000 --- a/data/archive/tables/osmosis-tables/README.md +++ /dev/null @@ -1,75 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Osmosis Tables - -### Background of Osmosis - -**Blockchain:** [Osmosis](https://app.osmosis.zone/) - -Osmosis is a proof-of-stake IBC blockchain with a decentralized exchange application enabling users to provide liquidity, swap, and stake tokens from across the Cosmos ecosystem. The Osmosis Frontier application, which is a full permissionless listing and curation of bridged ETH and CW20 assets, exists alongside the main Osmosis application. - -The native token of Osmosis, Osmo, is used for governance and paying transaction fees for actions performed on the DEX. There are a few points that make Osmosis a unique DEX: - -* **Self-Governing Liquidity Pools:** In Osmosis, the LP shares are used to calculate the fractional ownership of a LP, as well as the right to participate in the strategic decision making of the LP via governance. To incentivize long-term liquidity commitment, shares must be locked up for an extended period. Longer-term commitments are awarded by additional voting power and additional liquidity mining revenue. -* **Superfluid Staking:** A method of staking the OSMO tokens that underlie your LP positions to earn additional rewards. Superfluid staking is at time of writing only available on certain OSMO pools on Osmosis. -* **MEV Resistance:** Osmosis was conceived with the goal of Maximal Extractable Value (MEV) resistance at its core and includes several unique solutions to help limit MEV. - -### Current Osmosis Tables - -The Osmosis tables are built on Osmosis transaction and messages information. - -[Fact Blocks](osmosis-fact-blocks-table.md) - -[Fact Daily Balances](osmosis-daily-balances.md) - -[Fact Governance Proposal Deposits](osmosis-fact-governance-proposal-deposits.md) - -[Fact Governance Submit Proposal](osmosis-fact-governance-submit-proposal.md) - -[Fact Governance Votes](osmosis-fact-governance-votes.md) - -[Dim Labels ](osmosis-dim-labels.md) - -[Dim Liquidity Pools](osmosis-dim-liquidity-pools.md) - -[Fact Liquidity Provider Actions](osmosis-fact-liquidity-provider-actions.md) - -[Fact Msg Attributes](osmosis-fact-msg-attributes-table.md) - -[Fact Msgs](osmosis-fact-msgs-table.md) - -[Dim Prices](osmosis-dim-prices.md) - -[Fact Staking Rewards](osmosis-fact-staking-rewards.md) - -[Fact Staking](osmosis-fact-staking.md) - -[Fact Superfluid Staking](osmosis-fact-superfluid-staking.md) - -[Fact Swaps](osmosis-fact-swaps.md) - -[Dim Tokens](osmosis-dim-tokens.md) - -[Fact Transactions](osmosis-fact-transactions-table.md) - -[Fact Transfers](osmosis-fact-transfers.md) - -[Fact Validators](osmosis-fact-validators.md) - -[Dim Vote Options](osmosis-dim-vote-options.md) - -[EZ Prices](osmosis-ez-prices.md) - -[EZ ICNS](osmosis-ez-icns.md) - -#### What we have: - -* All on-chain Osmosis events dating back to the genesis block in June 2021. -* Labels for all available tokens and liquidity pools on the Osmosis app and Osmosis validators. - -#### What we don't have: - -* Data related to pool APY, as this is not available on chain. -* Some labels & decimals for LP tokens and low market cap tokens. diff --git a/data/archive/tables/osmosis-tables/osmosis-daily-balances.md b/data/archive/tables/osmosis-tables/osmosis-daily-balances.md deleted file mode 100644 index 130d94b..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-daily-balances.md +++ /dev/null @@ -1,16 +0,0 @@ -# Osmosis Daily Balances - -### Table Schema - -`osmosis.core.daily_balances` - -This table is currently under development and will release in the Velocity App soon. This table only includes balances for addresses that are actively staking or providing liquidity to a liquidity pool. If an address is not doing either of these actions on a given date, it will not be represented in the table on that date. - -| Field | Type | Description | -| ------------- | --------- | ---------------------------------------------------------- | -| date | timestamp | The day that the balance corresponds to. | -| balance\_type | string | Either "staked" or "liquid." | -| address | string | The wallet that the balance belongs to. | -| currency | string | An address that corresponds to the currency in the wallet. | -| decimal | integer | Divide "balance" by POW(10, decimal) to get the balance. | -| balance | integer | The amount of currency in the wallet on the given day. | diff --git a/data/archive/tables/osmosis-tables/osmosis-dim-labels.md b/data/archive/tables/osmosis-tables/osmosis-dim-labels.md deleted file mode 100644 index 5bd8fb8..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-dim-labels.md +++ /dev/null @@ -1,16 +0,0 @@ -# Osmosis Dim Labels - -### Table Schema - -`osmosis.core.dim_labels` - -| Field | Type | Description | -| -------------- | ------ | ----------------------------------------------------------------------------------------------- | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| address | string | Address that the label is associated with. | -| creator | string | Name of the creator of the label. | -| label\_type | string | A high-level category describing the addresses main function or ownership (eg validator). | -| label\_subtype | string | A sub-category nested within label type providing further detail (e.g. exchange deposit wallet) | -| label | string | The name of the entity that controls the address (e.g. Cosmostation) | -| project\_name | string | A description of the use of the address by the controlling entity. | -| raw\_metadata | json | A json structure containing additional information about the label where available. | diff --git a/data/archive/tables/osmosis-tables/osmosis-dim-liquidity-pools.md b/data/archive/tables/osmosis-tables/osmosis-dim-liquidity-pools.md deleted file mode 100644 index 56db32c..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-dim-liquidity-pools.md +++ /dev/null @@ -1,13 +0,0 @@ -# Osmosis Dim Liquidity Pools - -### Table Schema - -`osmosis.core.dim_liquidity_pools` - -| Field | Type | Description | -| ---------- | ------- | ------------------------------------------------------------------ | -| blockchain | string | In this table, always Osmosis. Used to join to cross-chain tables. | -| module | string | Module used to create liquidity pool | -| pool\_id | integer | Identifier for the pool within the module | -| assets | object | List of 2 or more asset addresses belonging to the pool | - diff --git a/data/archive/tables/osmosis-tables/osmosis-dim-prices.md b/data/archive/tables/osmosis-tables/osmosis-dim-prices.md deleted file mode 100644 index 4ccdb2f..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-dim-prices.md +++ /dev/null @@ -1,16 +0,0 @@ -# Osmosis Dim Prices - -### Table Schema - -`osmosis.core.dim_prices` - -Three different sources are used to create this prices table. Coingecko, Coinmarketcap, and the swaps table. When using prices from the swaps table, please note that prices calculated during hours with low transaction volumes and / or a low number of swaps may be incorrect. - -| Field | Type | Description | -| ------------- | --------- | -------------------------------------------------------------------------------------------- | -| recorded\_at | timestamp | The day and hour that the price was recorded. | -| symbol | string | The short-hand, symbolic notation for the currency. This is what shows up on price tickers. | -| price | number | The fiat cost of the asset at this point in time in USD. | -| total\_supply | number | The supply of the currency in circulation. | -| volume\_24h | number | The amount in USD of the currency that has been traded in a 24 hour period. | -| provider | string | The source the price was pulled from. | diff --git a/data/archive/tables/osmosis-tables/osmosis-dim-tokens.md b/data/archive/tables/osmosis-tables/osmosis-dim-tokens.md deleted file mode 100644 index 05826ba..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-dim-tokens.md +++ /dev/null @@ -1,18 +0,0 @@ -# Osmosis Dim Tokens - -### Table Schema - -`osmosis.core.dim_tokens` - -| Field | Type | Description | -| -------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| blockchain | string | In this table, always Osmosis. Used to join to cross-chain tables. | -| address | string | Address unique to the token. | -| creator | string | Name of the label creator - for now, this will always be "Flipside." | -| label\_type | string | A broad category that describes what a label is representing. | -| label\_subtype | string | Adds more detail to the label type. | -| label | string | The label or name of the address. | -| project\_name | string | The name of the project the label belongs to. | -| alias | string | A secondary address for the token, where available | -| decimal | number | Divide the amount by POW(10, decimal) to get the amount used in the transaction. This value can be NULL, as decimals are hand curated from an outside source and not found on-chain. | -| raw\_metadata | object | Additional details about the validator or token in json format. | diff --git a/data/archive/tables/osmosis-tables/osmosis-dim-vote-options.md b/data/archive/tables/osmosis-tables/osmosis-dim-vote-options.md deleted file mode 100644 index bc6020a..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-dim-vote-options.md +++ /dev/null @@ -1,12 +0,0 @@ -# Osmosis Dim Vote Options - -### Table Schema - -`osmosis.core.dim_vote_options` - -Join this table to `osmosis.fact_governance_votes` on `vote_option = vote_id` - -| Field | Type | Description | -| ----------- | ------- | ---------------------------------------------------- | -| vote\_id | integer | Numeric option that corresponds to the user's vote. | -| description | string | Text that describes the vote option. | diff --git a/data/archive/tables/osmosis-tables/osmosis-ez-icns.md b/data/archive/tables/osmosis-tables/osmosis-ez-icns.md deleted file mode 100644 index 080acf4..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-ez-icns.md +++ /dev/null @@ -1,15 +0,0 @@ -# Osmosis EZ ICNS - -### Table Schema - -`osmosis.core.ez_icns` - -| Field | Type | Description | -| ------------- | --------- | --------------------------------------------------------------- | -| blockchain | string | Blockchain the label is applicable for. | -| creator | string | Name of the label creator. | -| address | string | Address unique to an individual wallet, validator, or token. | -| label | string | The ICNS name associated with the address. | -| project\_name | string | The name of the project the name was purchased from. | -| start\_date | timestamp | Date the ICNS name first applies to the wallet. | -| end\_date | timestamp | Date the ICNS name expires or no longer represents the wallet. | diff --git a/data/archive/tables/osmosis-tables/osmosis-ez-prices.md b/data/archive/tables/osmosis-tables/osmosis-ez-prices.md deleted file mode 100644 index 1627cdd..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-ez-prices.md +++ /dev/null @@ -1,15 +0,0 @@ -# Osmosis EZ Prices - -### Table Schema - -`osmosis.core.ez_prices` - -An to use table for finding a token's price for a given hour. The table takes the Dim\_Prices table and reduce it down to only one record per hour per token. The table also brings in the token address for easy joining to other tables that contain the address and not the token symbol. - -| Field | Type | Description | -| -------------- | --------- | -------------------------------------------------------------------------------------------- | -| recorded\_hour | timestamp | The hour the price is valid for | -| symbol | string | The short-hand, symbolic notation for the currency. This is what shows up on price tickers. | -| currency | string | An address that corresponds to the currency in the wallet. | -| price | number | The fiat cost of the asset at this point in time in USD. | -| | | | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-airdrops.md b/data/archive/tables/osmosis-tables/osmosis-fact-airdrops.md deleted file mode 100644 index e4d674c..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-airdrops.md +++ /dev/null @@ -1,20 +0,0 @@ -# Osmosis Fact Airdrops - -### Table Schema - -`osmosis.core.fact_airdrops` - -| Field | Type | Field | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| transfer\_type | string | The type of transfer that occurred (i.e. IBC transfer) | -| sender | string | The wallet address of the user that sent the transfer. | -| amount | integer | The quantity of cryptocurrency sent in the transfer. | -| currency | string | A string identifying the cryptocurrency sent in the transfer. | -| decimal | integer | Divide `amount` by POW(10, decimal) to get the actual amount. | -| receiver | string | The wallet address of the user that received the transfer. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-blocks-table.md b/data/archive/tables/osmosis-tables/osmosis-fact-blocks-table.md deleted file mode 100644 index b6fc0c8..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-blocks-table.md +++ /dev/null @@ -1,15 +0,0 @@ -# Osmosis Fact Blocks Table - -### Table Schema - -`osmosis.core.fact_blocks` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------------------------------------------------------------------------- | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_count | integer | Number of transactions that occurred on the block. | -| proposer\_address | string | The address of the validator that proposed this block and is the validator responsible for building the block. | -| validators\_hash | string | The root hash of the new validator set. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-governance-proposal-deposits.md b/data/archive/tables/osmosis-tables/osmosis-fact-governance-proposal-deposits.md deleted file mode 100644 index bc89d4f..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-governance-proposal-deposits.md +++ /dev/null @@ -1,21 +0,0 @@ -# Osmosis Fact Governance Proposal Deposits - -### Table Schema - -`osmosis.core.fact_governance_proposal_deposits` - -After a proposal on Osmosis is submitted, it is required that at least 500 OSMO be deposited into the proposal over a two week timeframe. - -| Field | Type | Description | -| ---------------- | --------- | ----------------------------------------------------------------------------------------------------- | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | Transaction status is "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| depositor | string | The wallet address of the user depositing into a proposal. | -| proposal\_id | integer | A sequential number that identifies the proposal. | -| amount | integer | The quantity deposited in the transaction. | -| currency | string | A string identifying the cryptocurrency used in the transaction. | -| decimal | integer | Divide `amount` by POW(10, decimal) to get the actual amount. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-governance-submit-proposal.md b/data/archive/tables/osmosis-tables/osmosis-fact-governance-submit-proposal.md deleted file mode 100644 index d797900..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-governance-submit-proposal.md +++ /dev/null @@ -1,17 +0,0 @@ -# Osmosis Fact Governance Submit Proposal - -### Table Schema - -`osmosis.core.fact_governance_submit_proposal` - -| Field | Type | Description | -| ---------------- | --------- | ----------------------------------------------------------------------------------------------------- | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | Transaction status is "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| proposer | string | The wallet address of the user that submitted the proposal. | -| proposal\_id | integer | A sequential number that identifies the proposal. | -| proposal\_type | string | A descriptor of what the proposal is about. Will be "text" if unknown. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-governance-votes.md b/data/archive/tables/osmosis-tables/osmosis-fact-governance-votes.md deleted file mode 100644 index 031c58b..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-governance-votes.md +++ /dev/null @@ -1,18 +0,0 @@ -# Osmosis Fact Governance Votes - -### Table Schema - -`osmosis.core.fact_governance_votes` - -| Field | Type | Description | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| voter | string | The wallet address of the user voting on the proposal. | -| proposal\_id | integer | A sequential number that identifies the proposal. | -| vote\_option | string | How the user voted on the proposal. | -| vote\_weight | float | The percentage of a user's voting power put towards this vote. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-liquidity-provider-actions.md b/data/archive/tables/osmosis-tables/osmosis-fact-liquidity-provider-actions.md deleted file mode 100644 index 55a42e6..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-liquidity-provider-actions.md +++ /dev/null @@ -1,21 +0,0 @@ -# Osmosis Fact Liquidity Provider Actions - -### Table Schema - -`osmosis.core.fact_liquidity_provider_actions` - -| Field | Type | Description | -| ---------------------------- | --------- | ---------------------------------------------------------------------------------------------------- | -| block\_id | intger | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | ransaction status is "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| liquidity\_provider\_address | string | The address of the user interacting with the liquidity pool. | -| action | string | Whether the user is joining or exiting the liquidity pool. | -| pool\_id | integer | A numeric ID that corresponds to the liquidity pool. | -| amount | integer | The quantity of cryptocurrency in the transaction. | -| currency | string | A string identifying the cryptocurrency used in the transaction. | -| decimal | integer | Divide `amount` by POW(10, decimal) to get the actual amount. | - diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-msg-attributes-table.md b/data/archive/tables/osmosis-tables/osmosis-fact-msg-attributes-table.md deleted file mode 100644 index 396f6eb..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-msg-attributes-table.md +++ /dev/null @@ -1,18 +0,0 @@ -# Osmosis Fact Msg Attributes Table - -### Table Schema - -`osmosis.core.fact_msg_attributes` - -| Field | Type | Descriptions | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| msg\_index | integer | Short for "message index," the position in which messages occur in a transaction. | -| msg\_type | string | A string containing information about the type of message occurring. | -| attribute\_index | integer | The position in which attributes occur within a message. | -| attribute\_key | string | A label of sorts for the attribute\_value. | -| attribute\_value | string | Contains critical information such as addresses, amounts, tokens sent, etc. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-msgs-table.md b/data/archive/tables/osmosis-tables/osmosis-fact-msgs-table.md deleted file mode 100644 index cb4ccd5..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-msgs-table.md +++ /dev/null @@ -1,17 +0,0 @@ -# Osmosis Fact Msgs Table - -### Table Schema - -`osmosis.core.fact_msgs` - -| Field | Type | Description | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | Transaction status is "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| msg\_index | integer | Short for "message index," the position in which messages occur in a transaction. | -| msg\_type | string | A string containing information about the type of message occurring. | -| msg | json | A block of json that contains the message attributes in base64 encoding. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-staking-rewards.md b/data/archive/tables/osmosis-tables/osmosis-fact-staking-rewards.md deleted file mode 100644 index de2a69b..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-staking-rewards.md +++ /dev/null @@ -1,22 +0,0 @@ -# Osmosis Fact Staking Rewards - -### Table Schema - -`osmosis.core.fact_staking_rewards` - -| Field | Type | Description | -| ------------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| tx\_caller\_address | string | The address of the wallet that initiated the transaction. | -| action | string | A description of what is occurring in the transaction. | -| delegator\_address | string | The wallet address that is delegating their OSMO. | -| validator\_address | string | The address of the validator that the delegator is delegating to. | -| amount | integer | The quantity of cryptocurrency in the transaction. | -| currency | string | A string identifying the cryptocurrency used in the transaction. | -| decimal | integer | Divide `amount` by POW(10, decimal) to get the actual amount. | - diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-staking.md b/data/archive/tables/osmosis-tables/osmosis-fact-staking.md deleted file mode 100644 index 3b1f74c..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-staking.md +++ /dev/null @@ -1,23 +0,0 @@ -# Osmosis Fact Staking - -### Table Schema - -`osmosis.core.fact_staking` - -| Field | Type | Description | -| -------------------------------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| tx\_caller\_address | string | The address of the wallet that initiated the transaction. | -| action | string | A description of what is occurring in the transaction. | -| delegator\_address | string | The wallet address that is delegating their OSMO. | -| amount | integer | The quantity of cryptocurrency in the transaction. | -| currency | string | A string identifying the cryptocurrency used in the transaction. | -| decimal | integer | Divide `amount` by POW(10, decimal) to get the actual amount. | -| validator\_address | string | The address of the validator that the delegator is delegating to. | -| redelegate\_source\_validator\_address | string | The address that the user redelegates to in redelegation transactions. Otherwise NULL. | -| completion\_time | timestamp | The time the transaction was completed at. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-superfluid-staking.md b/data/archive/tables/osmosis-tables/osmosis-fact-superfluid-staking.md deleted file mode 100644 index bde9d33..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-superfluid-staking.md +++ /dev/null @@ -1,24 +0,0 @@ -# Osmosis Fact Superfluid Staking - -### Table Schema - -`osmosis.core.fact_superfluid_staking` - -| Field | Type | Description | -| ---------------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| block\_id | integer | The block height the block was recorded at. | -| block\_timestamp | timestamp | The date and time at which the block began. | -| blockchain | string | In this table, always Osmosis. Used to join to cross-chain tables. | -| chain\_id | string | The name and version of the blockchain. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | Transaction status is "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| tx\_caller\_address | string | The wallet address of the individual who initiated the transaction. | -| action | string | The action taken in the msg group. For staking this includes delegate, undelegate, redelegate, withdraw\_rewards. | -| delegator\_address | string | The wallet address of the individual who owns the delegated asset. | -| amount | integer | The amount that was used in the transaction message. | -| currency | string | The currency that was used in the transaction message. | -| decimal | integer | Divide the amount by POW(10, decimal) to get the amount used in the transaction. This value can be NULL, as decimals are hand curated from an outside source and not found on-chain. | -| validator\_address | string | The wallet address of the validator related to the staking action. | -| lock\_id | integer | An ID corresponding to the locking step of the transaction. | -| original superfluid delegate tx id | string | The transaction id when the user initialized the superfluid stake. | - diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-swaps.md b/data/archive/tables/osmosis-tables/osmosis-fact-swaps.md deleted file mode 100644 index 0f95c49..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-swaps.md +++ /dev/null @@ -1,22 +0,0 @@ -# Osmosis Fact Swaps - -### Table Schema - -`osmosis.core.fact_swaps` - -| Field | Type | Description | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| trader | string | The wallet address of the user who initiated the swap. | -| from\_amount | integer | The quantity of cryptocurrency to be swapped. | -| from\_currency | string | A string identifying the cryptocurrency to be swapped. | -| from\_decimal | integer | Divide `from_amount` by POW(10, decimal) to get the actual from\_amount. | -| to\_amount | integer | The quantity of cryptocurrency received in the swap. | -| to\_currency | string | string identifying the cryptocurrency received in the swap. | -| to\_decimal | integer | Divide `to_amount` by POW(10, decimal) to get the actual to\_amount. | -| pool\_ids | array | An array containing integers corresponding to the pools the swap went through. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-transactions-table.md b/data/archive/tables/osmosis-tables/osmosis-fact-transactions-table.md deleted file mode 100644 index 8913971..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-transactions-table.md +++ /dev/null @@ -1,21 +0,0 @@ -# Osmosis Fact Transactions Table - -### Table Schema - -`osmosis.core.fact_transactions` - -| Field | Type | Description | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_from | string | Address of the individual that initiated the transaction. | -| tx\_status | string | Transaction status is "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| fee | integer | The fee is paid by the initiator of the transaction. Fee = gas \* gas price. | -| gas\_used | integer | The amount of gas consumed by the transaction. | -| gas\_wanted | integer | Amount of gas requested for a transaction. It is provided by users when the transaction is generated. | -| codespace | string | Namespace for the code. | -| tx\_code | integer | A number that corresponds to various error codes. When "0", the transaction is successful. Non-zero numbers signify different types of transaction failures. | -| msgs | json | A json structure that includes information about the message attributes and attribute types. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-transfers.md b/data/archive/tables/osmosis-tables/osmosis-fact-transfers.md deleted file mode 100644 index 5256b2c..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-transfers.md +++ /dev/null @@ -1,20 +0,0 @@ -# Osmosis Fact Transfers - -### Table Schema - -`osmosis.core.fact_transactions` - -| Field | Type | Field | -| ---------------- | --------- | ------------------------------------------------------------------------------------------------ | -| block\_id | integer | Unique sequential number that identifies the current block. Called "height" on block explorers. | -| block\_timestamp | timestamp | The time the block began. | -| blockchain | string | Cross-chain identifier. In this table, `blockchain` will always be Osmosis. | -| chain\_id | string | ID of the blockchain to connect to, i.e. Osmosis-1. | -| tx\_id | string | A unique key that identifies a transaction. Called "TxHash" on block explorers. | -| tx\_status | string | "SUCCEEDED" if the transaction went through, "FALSE" if the transaction failed. | -| transfer\_type | string | The type of transfer that occurred (i.e. IBC transfer) | -| sender | string | The wallet address of the user that sent the transfer. | -| amount | integer | The quantity of cryptocurrency sent in the transfer. | -| currency | string | A string identifying the cryptocurrency sent in the transfer. | -| decimal | integer | Divide `amount` by POW(10, decimal) to get the actual amount. | -| receiver | string | The wallet address of the user that received the transfer. | diff --git a/data/archive/tables/osmosis-tables/osmosis-fact-validators.md b/data/archive/tables/osmosis-tables/osmosis-fact-validators.md deleted file mode 100644 index 6283a34..0000000 --- a/data/archive/tables/osmosis-tables/osmosis-fact-validators.md +++ /dev/null @@ -1,25 +0,0 @@ -# Osmosis Fact Validators - -### Table Schema - -`osmosis.core.fact_validators` - -| Field | Type | Description | -| --------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------ | -| address | string | Address unique to an individual wallet, validator, or token. | -| blockchain | string | In this table, always Osmosis. Used to join to cross-chain tables. | -| creator | string | Name of the label creator - for now, this will always be "Flipside." | -| label\_type | string | A broad category that describes what a label is representing. | -| label\_subtype | string | Adds more detail to the label type. | -| label | string | The label or name of the address. | -| project\_name | string | The name of the project the label belongs to. | -| account\_address | string | The osmosis address of the user / entity that operates the validator. | -| delegator\_address | string | The number of tokens staked to the validator. | -| jailed | boolean | FALSE when a validator is not jailed, TRUE when a validator is jailed. | -| max\_change\_rate | number | The maximum rate at which a validator can change their commission per day. | -| max\_rate | number | The maximum commission rate that the validator can charge. | -| min\_self\_delegation | number | The minimum number of OSMO tokens that the operator must be staking with their own validator. | -| rank | number | The rank of the validator in the validator set. Rank is determined by the number of OSMO tokens staked to the validator. | -| missed\_blocks | number | The number of blocks the validator has been down for during it's lifetime. | -| raw\_metadata | object | Additional details about the validator or token in json format. | - diff --git a/data/archive/tables/polygon-2.0-tables.md b/data/archive/tables/polygon-2.0-tables.md deleted file mode 100644 index 55c163d..0000000 --- a/data/archive/tables/polygon-2.0-tables.md +++ /dev/null @@ -1,36 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Polygon 2.0 Tables - -Documentation for \`polygon\` tables can be found [here](https://flipsidecrypto.github.io/polygon-models/#!/overview). - -The public Github repo with Polygon 2.0 model source code is [here](https://github.com/FlipsideCrypto/polygon-models). - -Please note, data is in 'lite mode' - meaning, historical data has not yet been backfilled. Please see the `min(block`\_`timestamp)`. - -Quick Links to Table Docs: - -* [`fact_event_logs`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_fact\_event\_logs) -* [`fact_transactions`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_fact\_transactions) -* [`fact_blocks`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_fact\_blocks) -* [`fact_traces`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_fact\_traces) -* [`fact_token_transfers`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_fact\_token\_transfers) -* [`dim_labels`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_dim\_labels) -* [`ez_matic_transfers`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_ez\_matic\_transfers) -* [`dim_contracts`](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.core\_\_dim\_contracts) - - - -Polygon sushi tables - -* [sushi\_\__dim\_dex\__pools](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.sushi\_\_dim\_dex\_pools) -* [sush\_\__dim\_kashi\_pairs_ ](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.sushi\_\_dim\_kashi\_pairs) -* [_sushi\_\_ez\_lending_](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.sushi\_\_ez\_lending) -* [_sushi\_\_ez\_borrowing_](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.sushi\_\_ez\_borrowing) -* [_sushi\_\_ez\_swaps_](https://flipsidecrypto.github.io/polygon-models/#!/model/model.polygon\_models.sushi\_\_ez\_swaps) - - - -Note: when working with the `fact_transactions` and `fact_event_logs` tables, you may find it useful to use the [ethereum.public.hex\_to\_int() function](../../../resources/hex-to-integer-function.md).\ diff --git a/data/archive/tables/polygon-tables/README.md b/data/archive/tables/polygon-tables/README.md deleted file mode 100644 index a2187a3..0000000 --- a/data/archive/tables/polygon-tables/README.md +++ /dev/null @@ -1,28 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Polygon Tables - -**Blockchain:** [Polygon](https://polygon.technology/) - -The public Github repo with Polygon model source code is [here](https://github.com/FlipsideCrypto/sql\_models/tree/main/models/polygon). - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -### Tables - -{% content-ref url="polygon-events-emitted.md" %} -[polygon-events-emitted.md](polygon-events-emitted.md) -{% endcontent-ref %} - -{% content-ref url="polygon-transactions.md" %} -[polygon-transactions.md](polygon-transactions.md) -{% endcontent-ref %} - -{% content-ref url="polygon-udm-events.md" %} -[polygon-udm-events.md](polygon-udm-events.md) -{% endcontent-ref %} - diff --git a/data/archive/tables/polygon-tables/polygon-events-emitted.md b/data/archive/tables/polygon-tables/polygon-events-emitted.md deleted file mode 100644 index fe5bab4..0000000 --- a/data/archive/tables/polygon-tables/polygon-events-emitted.md +++ /dev/null @@ -1,38 +0,0 @@ -# Polygon Events Emitted - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -Polygon events emitted table contains the information for the Polygon events, it is extracted from the Polygon blockchain and there are some notable features: - -* All event inputs are decoded and stored in a fully queryable JSON column called `event_inputs` -* Flipside's labels have been merged in. -* Every contract has an associated name that corresponds 1:1 with the solidity contract code. - -## Table Schema - -`polygon.events_emitted` - -| Field | Type | Description | -| ------------------------ | --------- | -------------------------------------------------------------------------------------------------------------- | -| block\_id | number | The block height this event was recorded at. | -| block\_timestamp | timestamp | UTC block timestamp for parent block | -| tx\_id | string | Transaction hash | -| event\_index | string | The index/order of the event in the transaction | -| event\_inputs | json | Decoded event inputs (specifically topics/data are decoded) | -| event\_name | string | English decoded name for the event name. This could be a transfer, or any decoded log method or log event name | -| event\_removed | boolean | Whether the event get removed or not | -| tx\_from\_address | address | The initiator of the transaction. | -| tx\_from\_address\_name | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_from\_label | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_from\_label\_subtype | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_from\_label\_type | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_to\_address | address | The receiver of the transaction or initial contract being called | -| tx\_to\_address\_name | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_to\_label | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_to\_label\_subtype | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| tx\_to\_label\_type | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| contract\_address | address | The parent contract that is responsible for kicking off this event. | -| contract\_name | string | The name of this contract. | -| tx\_succeeded | boolean | Was this transaction successful? | diff --git a/data/archive/tables/polygon-tables/polygon-transactions.md b/data/archive/tables/polygon-tables/polygon-transactions.md deleted file mode 100644 index dc5ee26..0000000 --- a/data/archive/tables/polygon-tables/polygon-transactions.md +++ /dev/null @@ -1,42 +0,0 @@ -# Polygon Transactions - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -Polygon transactions exist within the polygon schema, as `polygon.transactions` . - -Transactions contain top-level summary information not found in `polygon.udm_events`, for example, transaction fees and gas. - -## Table Schema - -`polygon.transactions` - -| Field | Type | Description | -| -------------------- | --------------------------------------- | ---------------------------------------------------------------------- | -| block\_id | number | The block height this event was recorded at. | -| block\_timestamp | timestamp | UTC block timestamp for parent block | -| tx\_id | string | The hash (unique identifier) of the transaction. | -| tx\_position | string | The position of the transaction in the block. | -| nonce | number | The number of transactions sent from the `from_address.` | -| from\_address | address | The sender/initiator of the transaction. | -| from\_address\_name | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| from\_label | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| from\_label\_subtype | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| from\_label\_type | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| to\_address | text | The recipient of the transaction, or contract being called. | -| to\_addres\_name | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| to\_label | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| to\_label\_subtype | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| to\_label\_type | [label](../../../flipside-data/labels/) | [(see label's data model for details)](../../../flipside-data/labels/) | -| symbol | text | The project symbol (i.e. ERC-20 transaction), if applicable. | -| function\_signature | string | The function signature of the contract call, if applicable. | -| function\_name | string | The English decoded name of the function signature, if applicable. | -| gas\_price | number | The gas price at the time of this transaction. | -| gas\_limit | number | The gas limit specified in this transaction. | -| gas\_used | number | The amount of gas used by this transaction. | -| fee | number | The transaction fee calculated from the gas price and the gas used. | -| fee\_usd | number | The USD equivalent fee at the time of the transaction. | -| success | text | The success state of this transaction execution. | -| event\_count | number | The number of events contained within this transaction. | - diff --git a/data/archive/tables/polygon-tables/polygon-udm-events.md b/data/archive/tables/polygon-tables/polygon-udm-events.md deleted file mode 100644 index df6141b..0000000 --- a/data/archive/tables/polygon-tables/polygon-udm-events.md +++ /dev/null @@ -1,50 +0,0 @@ -# Polygon UDM Events - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -Polygon UDM events exist within the `polygon` schema, as `polygon.udm_events` - -Within the event table, native MATIC transfers, internal transactions, and contract calls are all modeled as "events". - -Notable Features that make querying simple: - -* "Origin" metadata is carried down to every event. This is particularly useful if you want to query an event in the context of a specific origin contract call, i.e. all "burn" events that occur in the context of a token "transfer". -* All function names, log methods, and log events have been decoded into their human-readable format. -* All amounts have been decimal adjusted. -* All amounts, where applicable, contain their USD Equivalent. - -## Table Schema - -`polygon.udm_events` - -| Field | Type | Description | -| --------------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | -| block\_timestamp | timestamp | UTC block timestamp for parent block | -| block\_id | number | The block height this event was recorded at. | -| tx\_id | string | Transaction id for this transfer | -| origin\_address | address | The initiator of the transaction | -| origin\_address\_name | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| origin\_label | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| origin\_label\_subtype | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| origin\_label\_type | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| origin\_function\_name | string | Input function signature decoded to English name for the parent tx that kicked off this event, if applicable | -| origin\_function\_signature | string | The function signature of contract call, if applicable | -| from\_address | address | The sender of the event | -| from\_address\_name | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| from\_label | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| from\_label\_subtype | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| from\_label\_type | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| to\_address | address | The receiver of the transaction or contract being called | -| to\_address\_name | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| to\_label | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| to\_label\_subtype | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| to\_label\_type | string | [(see Labels section for details)](../../../flipside-data/labels/) | -| event\_name | string | English decoded name for the event name. This could be a transfer, or any decoded log method or log event name | -| event\_type | string | The english name for the type of event. This could be a native polygon event, token transfer, or contract methods calls/events. | -| event\_id | string | The index/order of the event in the transaction | -| contract\_address | address | The parent contract that is responsible for kicking off this event. | -| symbol | string | The symbol for the contract, if applicable. | -| amount | number | Native amount of transfer (decimal adjusted) | -| amount\_usd | number | In the case of a transfer event, the equivalent amount in USD. Note this is computed by taking the average hourly price around the time of the tx event. | diff --git a/data/archive/tables/polygon-tables/position-collected-fees.md b/data/archive/tables/polygon-tables/position-collected-fees.md deleted file mode 100644 index 36420b5..0000000 --- a/data/archive/tables/polygon-tables/position-collected-fees.md +++ /dev/null @@ -1,40 +0,0 @@ ---- -description: uniswapv3.position_collected_fees ---- - -# Position Collected Fees - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -Fees collected by a Liquidity Provider (LP) on their position. In V3 fees are accrued and collected in each token within the pair. When a pool `Collect` event is emitted a new record is appended to this table. If a `Burn` event is emitted in the same transaction as the `Collect` event the amount of the burn is subtracted from the `Collect` event token1 and token0 amounts. This allows us to arrive solely at the swap fees collected. - -| Field | Type | Description | -| ----------------------------- | --------- | ------------------------------------------------------------------------------------------ | -| `block_id` | number | The block number that this Collect was recorded | -| `block_timestamp` | timestamp | The block timestamp that this Collect was recorded | -| `tx_id` | text | The transaction that contained this Collect | -| `blockchain` | text | The blockchain this Collect occurred on (Ethereum, will support L2s here shortly) | -| `pool_address` | address | The contract address of the pool | -| `pool_name` | text | The name of the Pool (format = "{token0}-{token1} {tick\_spacing} {fee}") | -| `liquidity_provider` | address | The address of the liquidity provider | -| `nf_position_manager_address` | address | The address of the peripheral nf position manager contract, if used. | -| `nf_token_id` | number | The id of the NFT associated with the liquidity position | -| `amount0_adjusted` | number | The amount of token0 collected for swap fees | -| `amount1_adjusted` | number | The amount of token1 collected for swap fees | -| `amount0_adjusted_usd` | number | The amount of token0 collected for swap fees, converted to USD | -| `amount1_adjusted_usd` | number | The amount of token1 collected for swap fees, converted to USD | -| `tick_lower` | number | Lower tick of the liquidity position | -| `tick_upper` | number | Upper tick of the liquidity position | -| `price_lower` | number | Lower bound of the liquidity position represented as token 1 per token 0 | -| `price_upper` | number | Upper bound of the liquidity position represented as token 1 per token 0 | -| `price_lower_usd` | number | Lower bound of the liquidity position represented as token 1 per token 0, converted to USD | -| `price_upper_usd` | number | Upper bound of the liquidity position represented as token 1 per token 0, converted to USD | - - - - - - - diff --git a/data/archive/tables/polygon-tables/swaps.md b/data/archive/tables/polygon-tables/swaps.md deleted file mode 100644 index a5942b7..0000000 --- a/data/archive/tables/polygon-tables/swaps.md +++ /dev/null @@ -1,35 +0,0 @@ ---- -description: uniswapv3.swaps ---- - -# Swaps - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -All swaps that occur on V3 pools. - -| Field | Type | Description | -| -------------------- | --------- | -------------------------------------------------------------------------------------- | -| `block_id` | number | The block number that this lp action was recorded | -| `block_timestamp` | timestamp | The block timestamp that this lp action was recorded | -| `tx_id` | text | The transaction that contained this lp action | -| `blockchain` | text | The blockchain this lp action was created on (Ethereum, will support L2s here shortly) | -| `pool_address` | address | The contract address of the pool | -| `pool_name` | text | The name of the Pool (format = "{token0}-{token1} {tick\_spacing} {fee}") | -| `sender` | address | The address that initiated the swap call, and that received the callback | -| `recipient` | address | The address that received the output of the swap | -| `amount0_adjusted` | number | The delta of the token0 balance of the pool, decimal adjusted. | -| `amount1_adjusted` | number | The delta of the token1 balance of the pool, decimal adjusted. | -| `amount0_usd` | number | The delta of the token0 balance of the pool, converted to USD | -| `amount1_usd` | number | The delta of the token1 balance of the pool, converted to USD | -| `tick` | number | The log base 1.0001 of the price of the pool after the swap | -| `liquidity_adjusted` | number | The liquidity of the pool after the swap, decimal adjusted. | -| `price_0_1` | number | The amount of token0 per token1 that the swap occurred at | -| `price_1_0` | number | The amount of token1 per token0 that the swap occurred at | -| `token0_address` | address | Contract address of token 0 | -| `token0_symbol` | text | Symbol of token 0 | -| `token1_address` | address | Contract address of token 1 | -| `token1_symbol` | text | Symbol of token 1 | - diff --git a/data/archive/tables/polygon-tables/v3-resources.md b/data/archive/tables/polygon-tables/v3-resources.md deleted file mode 100644 index b64f4ed..0000000 --- a/data/archive/tables/polygon-tables/v3-resources.md +++ /dev/null @@ -1,19 +0,0 @@ -# V3 Resources - -{% hint style="warning" %} -These are legacy Polygon tables. See [Polygon 2.0](../polygon-2.0-tables.md) for up-to-date Polygon models. -{% endhint %} - -In the process of putting together this data for V3, we created a map of the V3 contracts. This proved to be incredibly useful in building out our data models. - -### Pool - -![](<../../../../.gitbook/assets/Uniswap V3 - Pool.png>) - -### NF Position Manager - -![](<../../../../.gitbook/assets/Uniswap V3 - NonFungiblePositionManager.png>) - -### Factory - -![](<../../../../.gitbook/assets/Uniswap V3 - Factory.png>) diff --git a/data/archive/tables/solana-tables.md b/data/archive/tables/solana-tables.md deleted file mode 100644 index 25a4c69..0000000 --- a/data/archive/tables/solana-tables.md +++ /dev/null @@ -1,98 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Solana Tables - -### Background of Solana - -**Blockchain:** [Solana](https://solana.com/) - -Solana is a public base-layer blockchain protocol that optimizes for scalability. The goal of the Solana blockchain is to provide a platform that enables developers to create decentralized applications (dApps) without needed to design around performance bottlenecks. Solana features a new timestamp system called Proof of History (PoH) that enables automatically ordered transactions. It also uses Proof of Stake (PoS) consensus algorithm to help secure the network. - -The public Github repo with Solana model source code is [here](https://github.com/FlipsideCrypto/solana-models). - -### Current Solana Tables - -The current Solana table schemas build concepts laid out in [Flipside's event data model](broken-reference). Solana tables are available in Velocity as the `solana` schema. The tables are built based on the Solana events and transactions information. The following Solana tables are available: - -[Solana Dim Labels](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_dim\_labels) - -[Solan Dim Tokens](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_dim\_tokens) - -[Solana EZ Signers](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_ez\_signers) - -[Solan EZ Token Prices Hourly](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_ez\_token\_prices\_hourly) - -[Solana Fact Blocks](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_blocks) - -[Solana Fact Events](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_events) - -[Solana Fact Gauges Votes](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_gauges\_votes) - -[Solana Fact Gov Actions](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_gov\_actions) - -[Solana Dim NFT Metadata](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_dim\_nft\_metadata) - -[Solana Fact NFT Mints](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_nft\_mints) - -[Solana Fact NFT Sales](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_nft\_sales) - -[Solana Fact Proposal Creation](broken-reference) - -[Solana EZ Staking/LP Actions](broken-reference) - -[Solana Fact Staking/LP Actions](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_staking\_lp\_actions) - -[Solana Fact Stake Pool Actions](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_stake\_pool\_actions) - -[Solana Fact Swaps](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_swaps) - -[Solana Fact Token Prices Hourly](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_token\_prices\_hourly) - -[Solana Fact Transactions](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_transactions) - -[Solana Fact Transfers](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_transfers) - -[Solana Fact Votes Agg Blocks](https://flipsidecrypto.github.io/solana-models/#!/model/model.solana\_models.core\_\_fact\_votes\_agg\_block) - - - -#### What we have: - -* All native on-chain Solana events dating back to November 28, 2021. -* Labels for certain common Solana wallet addresses and programs. -* NFT metadata for top Solana NFT projects. - -#### What we don't have: - -* Off-chain events such as DEX order book transactions and bids on secondary NFT marketplaces. -* Data before Nov. 28th, 2021. We are in the process of backfilling the Solana tables, earlier data will be made available shortly. -* Votes anywhere besides the `solana.votes_block_agg` table and Pyth Oracle transactions. - -### Solana Labels - -Solana labels are available and located in the table `solana.labels`. To include Solana labels in your analysis, perform a join on address or program ID. Please note that all address labels stored in the `solana.labels` table are in lower case and that Solana addresses are case sensitive. To join the tables, use the SQL function `COLLATE` to create a case insensitive `JOIN` statement. - -### Solana NFT Tables And Metadata - -We have three Solana NFT tables: `solana.nfts` (mints, sales, etc), `solana.nft_metadata` (token names, images, attributes, etc), and `solana.airdrops` (NFT and token airdrops). - -The goal of these tables is to create a unified table of on-chain Solana NFT data that makes it easy to compare across and within NFTs. To do this, we have curated metadata from top Solana NFT projects. The metadata is nowhere near comprehensive, we add projects one or two at a time. That being said, we want these tables to be interesting to our community and would love feedback and recommendations for projects to add. - -### How to Contribute to Our Data - -Are there labels or NFT metadata that you would like to see added to our data? Let us know the following information in Discord or via email (hello@flipsidecrypto.com): - -**Good:** Send us the name of the token/label and the contract address. - -**Better:** Send us the name of the token/label, the contract address, and the project website. - -**Best:** Send us the name, contract address, project website, and example transactions (links to solscan.io). For an NFT, we would appreciate examples of the following transaction types: - -* minting -* list -* unlist -* bid -* sale -* any other special thing you can "do" with this NFT (ex: staking) diff --git a/data/archive/tables/terra-tables/README.md b/data/archive/tables/terra-tables/README.md deleted file mode 100644 index 543cf84..0000000 --- a/data/archive/tables/terra-tables/README.md +++ /dev/null @@ -1,116 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Terra Tables - -## Background of Terra - -**Blockchain:** [Terra](https://www.terra.money/). - -Terra is a Proof of stake chain and can also be used as a Smart contract platform. Terra protocol aims to create a stable priced currency by adopting an elastic monetary policy. Terra is supported by a basket of fiat-pegged, seigniorage share style stable coins which are algorithmically stabilized by its native crypto asset, Luna. - -## Terra Tables - -The Terra table schemas build on the concepts laid out in [Flipside's event data model](broken-reference). Terra tables are available in Velocity as the `terra` schema. The tables are built based on the terra message, transactions and transition information. - -At Flipside database, for Terra, there are two types of tables, one is the Raw Tables and the other one is the Terra Base Tables, clicking the following link to see more details about the tables. - -The public Github repo with Terra model source code is [here](https://github.com/FlipsideCrypto/sql\_models/tree/main/models/terra). - -### Terra Raw Tables: - -{% content-ref url="terra-raw-tables/blocks.md" %} -[blocks.md](terra-raw-tables/blocks.md) -{% endcontent-ref %} - -{% content-ref url="terra-raw-tables/msgs.md" %} -[msgs.md](terra-raw-tables/msgs.md) -{% endcontent-ref %} - -{% content-ref url="terra-raw-tables/msg_events.md" %} -[msg\_events.md](terra-raw-tables/msg\_events.md) -{% endcontent-ref %} - -{% content-ref url="terra-raw-tables/transactions.md" %} -[transactions.md](terra-raw-tables/transactions.md) -{% endcontent-ref %} - -{% content-ref url="terra-raw-tables/transitions.md" %} -[transitions.md](terra-raw-tables/transitions.md) -{% endcontent-ref %} - -### Terra Base Tables: - -{% content-ref url="terra-base-tables/labels.md" %} -[labels.md](terra-base-tables/labels.md) -{% endcontent-ref %} - -{% content-ref url="terra-base-tables/oracle-prices.md" %} -[oracle-prices.md](terra-base-tables/oracle-prices.md) -{% endcontent-ref %} - -{% content-ref url="terra-base-tables/tax-rate.md" %} -[tax-rate.md](terra-base-tables/tax-rate.md) -{% endcontent-ref %} - -{% content-ref url="terra-base-tables/daily-balances.md" %} -[daily-balances.md](terra-base-tables/daily-balances.md) -{% endcontent-ref %} - -{% content-ref url="terra-base-tables/swap.md" %} -[swap.md](terra-base-tables/swap.md) -{% endcontent-ref %} - -{% content-ref url="terra-base-tables/staking.md" %} -[staking.md](terra-base-tables/staking.md) -{% endcontent-ref %} - -{% content-ref url="terra-base-tables/rewards.md" %} -[rewards.md](terra-base-tables/rewards.md) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - - - - - - - -## **General Table Notes** - -### **Platform (how are other assets represented)** - -* All assets on-chain are typically represented as an object with a denomination and an amount to differentiate between different assets - -### **Precision (decimals)** - -* 0.000001 (10^6) - -### **Fees** - -* Fees can be paid in any Terra currency (Luna, TerraSDT, TerraKRW etc) -* We can get fees in the transaction payload - -### **Events** - -* Events or (Msgs) in Tendermint terms can easily be captured when we query for txs in a block -* Events are emitted from a "module" - - - diff --git a/data/archive/tables/terra-tables/terra-base-tables/README.md b/data/archive/tables/terra-tables/terra-base-tables/README.md deleted file mode 100644 index 5ccad29..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/README.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -description: This page lists all the base tables for Terra ---- - -# Terra Base Tables - -The Terra base tables contains the table from the Raw Table side, it will be used to create the Starter Queries. - -{% content-ref url="../../../../flipside-data/labels/" %} -[labels](../../../../flipside-data/labels/) -{% endcontent-ref %} - -{% content-ref url="oracle-prices.md" %} -[oracle-prices.md](oracle-prices.md) -{% endcontent-ref %} - -{% content-ref url="tax-rate.md" %} -[tax-rate.md](tax-rate.md) -{% endcontent-ref %} - -{% content-ref url="daily-balances.md" %} -[daily-balances.md](daily-balances.md) -{% endcontent-ref %} - -{% content-ref url="swap.md" %} -[swap.md](swap.md) -{% endcontent-ref %} - -{% content-ref url="staking.md" %} -[staking.md](staking.md) -{% endcontent-ref %} - -{% content-ref url="rewards.md" %} -[rewards.md](rewards.md) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} - -{% content-ref url="broken-reference" %} -[Broken link](broken-reference) -{% endcontent-ref %} diff --git a/data/archive/tables/terra-tables/terra-base-tables/daily-balances.md b/data/archive/tables/terra-tables/terra-base-tables/daily-balances.md deleted file mode 100644 index 6620945..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/daily-balances.md +++ /dev/null @@ -1,20 +0,0 @@ -# Daily Balances - -Daily Balance shows the balance amount for each address. The label information can be found at [(see Labels section for details)](../../../../flipside-data/labels/). - -## Table Schema - -**table name:** `terra.daily_balances` - -| Field | Type | Description | -| ----------------------- | ------- | -------------------------------------------------------------------------------------------------- | -| `DATE` | date | The date time for this balance record | -| `ADDRESS` | address | The balance address | -| `ADDRESS_LABEL_TYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `ADDRESS_LABEL_SUBTYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `ADDRESS_LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `ADDRESS_NAME` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `BALANCE` | number | The amount of the balance | -| `BALANCE_USD` | number | The amount of the balance in USD, it is calculated by the hourly price multiple the balance amount | -| `BALANCE_TYPE` | text | The balance type | -| `CURRENCY` | text | The balance currency | diff --git a/data/archive/tables/terra-tables/terra-base-tables/event-actions.md b/data/archive/tables/terra-tables/terra-base-tables/event-actions.md deleted file mode 100644 index 7e76fd6..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/event-actions.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -description: >- - Row based event actions table curated from terra.msg_events event attributes. - Actions or methods in the 'from_contract' event type are displayed as records - based on contract address. ---- - -# Event Actions - -## Table Schema - -table name: `terra.event_actions` - -
FieldTypeDescription
BLOCK_IDnumberThe block number for this event action
BLOCK_TIMESTAMPtimestampThe timestamp this block was recorded
BLOCKCHAINtextThe blockchain name for this block
CHAIN_IDtextID of blockchain to connect to, it can be columbus-3, columbus-4, columbus-5, etc.
TX_IDtextThe transaction that contained this event action
ACTION_INDEXnumberIndex for event actions
MSG_INDEXnumberMessage index, it is like the different steps for message, one message group can contain multiple message index values to deliver different information
ACTION_CONTRACT_ADDRESStextContract address that kicked off this event action
CONTRACT_LABELtext(see Labels section for details)
ACTION_METHODtextThe action or method within an event
ACTION_LOGobjectThe log that provides detail (amounts, to, from, etc.) to an action or method
diff --git a/data/archive/tables/terra-tables/terra-base-tables/labels.md b/data/archive/tables/terra-tables/terra-base-tables/labels.md deleted file mode 100644 index 69b6bd9..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/labels.md +++ /dev/null @@ -1,19 +0,0 @@ -# Labels - -The labels table is based on the Flipside Event label data, currently we included 4 different projects for the labels: `terraswap`, `chai`, `mirror`, `anchor` - -[(see Labels section for details)](../../../../flipside-data/labels/) - -## Table Schema - -**table name:** `terra.labels` - -| Field | Type | Description | -| --------------- | ------- | --------------------------------------------------------------------- | -| `BLOCKCHAIN` | text | The blockchain name for this block | -| `ADDRESS` | address | The label address | -| `LABEL_TYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `LABEL_SUBTYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `ADDRESS_NAME` | text | The name of this address | - diff --git a/data/archive/tables/terra-tables/terra-base-tables/oracle-prices.md b/data/archive/tables/terra-tables/terra-base-tables/oracle-prices.md deleted file mode 100644 index ad22cef..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/oracle-prices.md +++ /dev/null @@ -1,17 +0,0 @@ -# Oracle Prices - -The Oracle Prices table contains the information for the token price per timestamp - -## Table Schema - -**table name:** `terra.oracle_prices` - -| Field | Type | Description | -| -------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCKCHAIN` | text | Blockchain name, here is Terra | -| `BLOCK_TIMESTAMP` | timestamp | Block time stamp for this message events been recorded | -| `CURRENCY` | text | The currency for this token | -| `SYMBOL` | text | The token symbol | -| `LUNA_EXCHANGE_RATE` | text | The exchange ratio to change this token for `LUNA` token. How many this token you can get when you transfer it with 1`LUNA`, for example, for `MNT`, `LUNA_EXCHANGE_RATE` is 2600, which means you can use 1 `LUNA` to exchange 2600 `MNT` | -| `PRICE_USD` | number | The price for this token at this timestamp | -| `SOURCE` | text | The source for the price | diff --git a/data/archive/tables/terra-tables/terra-base-tables/rewards.md b/data/archive/tables/terra-tables/terra-base-tables/rewards.md deleted file mode 100644 index 7a6f566..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/rewards.md +++ /dev/null @@ -1,36 +0,0 @@ -# Reward - -`Reward` table shows the behaviors about how does supply enter / exist the Terra ecosystem. Staking rewards are made up of **gas (computer fees)**, **taxes**, and **seigniorage rewards**: - -* **Gas fee:** Similar concept as the Gas fee in Ethereum network, the fee paid for the transaction in the Network. -* **Taxes:** Taxes are essentially a stability fee and range from 0.1% to 1% of transactions capped at 1 TerraSDR, the taxes can be paid in ANY Terra currency -* **Seigniorage rewards:** Seigniorage rewards are given to validators for participating in the Luna exchange rate oracle process. Rewards come from the seigniorage pool. - -## Table Schema - -**table name:** `terra.rewards` - -| Field | Type | Description | -| ------------------------- | --------- | ---------------------------------------------------------------------------------------------------------------------------- | -| `BLOCKCHAIN` | text | Blockchain name, here is Terra | -| `CHAIN_ID` | text | The type of Blockchain | -| `TX_STATUS` | text | The status of this transaction, either `success` or `failure` | -| `BLOCK_ID` | number | Block number for this message events been recorded | -| `BLOCK_TIMESTAMP` | timestamp | Block time stamp for this message events been recorded | -| `TX_ID` | text | Unique transaction id for the reward | -| `MSG_INDEX` | number | The index of message, within one message there are many messaged wrapped up and index will show the position of the message | -| `ACTION` | text | Different actions for the reward, it can be `withdraw_validator_commission`or `withdraw_delegator_rewards` | -| `VALIDATOR` | address | Validator address | -| `VALIDATOR_LABEL_TYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `VALIDATOR_LABEL_SUBTYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `VALIDATOR_ADDRESS_LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `VALIDATOR_ADDRESS_NAME` | text | Validator name linked to the address | -| `DELEGATOR` | address | The address for the recipient to receive the reward | -| `DELEGATOR_LABEL_TYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `DELEGATOR_LABEL_SUBTYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `DELEGATOR_ADDRESS_LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `DELEGATOR_ADDRESS_NAME` | text | The recipient name linked to the address | -| `EVENT_AMOUNT` | number | The amount of currency for this event | -| `PRICE_USD` | number | The price of the token at current timestamp for this currency | -| `EVENT_AMOUNT_USD` | number | Event amount in USD | -| `CURRENCY` | text | The currency for this token | diff --git a/data/archive/tables/terra-tables/terra-base-tables/staking.md b/data/archive/tables/terra-tables/terra-base-tables/staking.md deleted file mode 100644 index 93626ac..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/staking.md +++ /dev/null @@ -1,31 +0,0 @@ -# Staking - -Staking table listed the information about the users who staked the tokens into the chain and it contains the information of the amount of the staking token, price and the validator and delegator address. - -## Table Schema - -**table name:** `terra.staking` - -| Field | Type | Description | -| ------------------------- | --------- | --------------------------------------------------------------------- | -| `BLOCKCHAIN` | text | Blockchain name, here is Terra | -| `CHAIN_ID` | text | The type of Blockchain | -| `TX_STATUS` | text | The transaction status for the staking | -| `BLOCK_ID` | number | Block number for this message events been recorded | -| `BLOCK_TIMESTAMP` | timestamp | Block time stamp for this message events been recorded | -| `TX_ID` | text | The unique transaction id | -| `ACTION` | text | The action taken for this transaction | -| `DELEGATOR_ADDRESS` | address | The address of the delegator for this staking event | -| `DELEGATOR_LABEL_TYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `DELEGATOR_LABEL_SUBTYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `DELEGATOR_ADDRESS_LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `DELEGATOR_ADDRESS_NAME` | text | Delegator name linked to the address | -| `VALIDATOR_ADDRESS` | address | The validator is the addresses to validate the delegation | -| `VALIDATOR_LABEL_TYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `VALIDATOR_LABEL_SUBTYPE` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `VALIDATOR_ADDRESS_LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `VALIDATOR_ADDRESS_NAME` | text | Validator name linked to the address | -| `EVENT_AMOUNT` | number | The amount of currency for this event | -| `PRICE_USD` | number | The price of the token at current timestamp for this currency | -| `EVENT_AMOUNT_USD` | number | Event amount in USD | -| `CURRENCY` | text | The currency for this token | diff --git a/data/archive/tables/terra-tables/terra-base-tables/swap.md b/data/archive/tables/terra-tables/terra-base-tables/swap.md deleted file mode 100644 index d0b13b6..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/swap.md +++ /dev/null @@ -1,33 +0,0 @@ -# Swaps - -Swaps table contains the information for the swap behavior, it involves the two parties to swap different tokens within the chain - -## Table Schema - -**table name:** `terra.swap` - -| Field | Type | Description | -| --------------------- | --------- | -------------------------------------------------------------------------------- | -| `BLOCKCHAIN` | text | The blockchain this swap was created on (Terra) | -| `CHAIN_ID` | text | The version of the Terra Core (now is **Columbus-4**) | -| `BLOCK_ID` | number | The block number that this swap was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The block timestamp that this swap was recorded | -| `TX_STATUS` | text | The transaction status for the staking | -| `TX_ID` | text | The transaction that contained this swap | -| `SWAP_FEE_AMOUNT` | number | The amount of fee for this swap | -| `SWAP_FEE_AMOUNT_USD` | number | The USD amount of fee for this swap | -| `SWAP_FEE_CURRENCY` | text | The currency of fee for this swap | -| `TRADER` | address | Trader address for this swap | -| `ASK_CURRENCY` | text | The currency asked for the swap | -| `OFFER_AMOUNT` | number | Amount to offer for this swap | -| `OFFER_AMOUNT_USD` | number | USD Amount to offer for this swap | -| `OFFER_CURRENCY` | text | Currency to offer for this swap | -| `TOKEN_0_AMOUNT` | number | The swap token 0 amount, in other word, use how many `token_0` to swap `token_1` | -| `TOKEN_0_AMOUNT_USD` | number | Amount of token\_0 in USD | -| `TOKEN_0_CURRENCY` | text | The currency of token\_0 | -| `TOKEN_1_AMOUNT` | number | The swap token 0 amount, in other word, use how many `token_0` to swap `token_1` | -| `TOKEN_1_AMOUNT_USD` | number | Amount of token\_1 in USD | -| `TOKEN_1_CURRENCY` | text | The currency of token\_1 | -| `PRICE0_USD` | number | The price for token\_0 | -| `PRICE1_USD` | number | The price for token\_1 | -| `SWAP_PAIR` | text | The concat field for the combination of `token_0` and `token_1` | diff --git a/data/archive/tables/terra-tables/terra-base-tables/tax-rate.md b/data/archive/tables/terra-tables/terra-base-tables/tax-rate.md deleted file mode 100644 index 6894124..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/tax-rate.md +++ /dev/null @@ -1,16 +0,0 @@ -# Tax Rate - -Taxes are essentially a stability fee and range from 0.1% to 1% of transactions capped at 1 TerraSDR. This can be paid in ANY Terra currency (On-chain I don't think we can distinguish between fees for gas vs taxes. They are rolled up into one).\ -\ -Note: In January 2022 the tax rate on Terra was lowered to 0%. Prior this, there were two kinds of tax on Terra, the default tax rate as the extra percentage paid for transactions on chain, and the effective tax rate which occurred when your transaction's tax value was greater than the capped 1 SDR default tax rate. - -## Table Schema - -**table name:** `terra.tax_rate` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------------------------------------------- | -| `BLOCK_NUMBER` | number | Block number for this message events been recorded, this one equals to block\_id | -| `BLOCK_TIMESTAMP` | timestamp | Block time stamp for this message events been recorded | -| `BLOCKCHAIN` | text | The blockchain name for this block | -| `TAX_RATE` | number | The tax ratio for at this block and timestamp | diff --git a/data/archive/tables/terra-tables/terra-base-tables/transfer-events.md b/data/archive/tables/terra-tables/terra-base-tables/transfer-events.md deleted file mode 100644 index f18289c..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/transfer-events.md +++ /dev/null @@ -1,14 +0,0 @@ ---- -description: >- - Terra transfer events, curated from Terra msg_events. Includes event_type - transfers, cw20 token transfers, Wormhole transfers, and Delegator rewards - transfers ---- - -# Transfer Events - -## Table Schema - -table name: `terra.transfer_events` - -
FieldTypeDescription
BLOCK_TIMESTAMPtimestampThe timestamp this block was recorded
TX_IDtextThe transaction that contained this transfer
MSG_INDEXnumberMessage index, it is like the different steps for message, one message group can contain multiple message index values to deliver different information
ACTION_INDEXnumberIndex for transfer event actions
INITIAL_ACTIONtextInitial action for a transfer event
CURRENT_ACTIONtextCurrent action for a transfer event
SENDERtextTransfer sender
SENDER_LABEL_TYPEtext(see Labels section for details)
SENDER_LABEL_SUBTYPEtext(see Labels section for details)
SENDER_ADDRESS_LABELtext(see Labels section for details)
SENDER_ADDRESS_NAMEtext(see Labels section for details)
RECIPIENTtextTransfer recipient
RECIPIENT_LABEL_TYPEtext(see Labels section for details)
RECIPIENT_LABEL_SUBTYPEtext(see Labels section for details)
RECIPIENT_ADDRESS_LABELtext(see Labels section for details)
RECIPIENT_ADDRESS_NAMEtext(see Labels section for details)
CURRENCYtextThe transfer currency
AMOUNTnumberThe transfer amount
AMOUNT_USDnumberThe transfer amount in USD, it is calculated by the hourly price multiplied by the transfer amount
MSG_SENDERtextThe message sender, from message event types
CONTRACT_ADDRESStextThe contract address that is responsible for kicking off the transfer event, if applicable
CONTRACT_LABELtext(see Labels section for details)
diff --git a/data/archive/tables/terra-tables/terra-base-tables/validator-labels.md b/data/archive/tables/terra-tables/terra-base-tables/validator-labels.md deleted file mode 100644 index 71ae23b..0000000 --- a/data/archive/tables/terra-tables/terra-base-tables/validator-labels.md +++ /dev/null @@ -1,15 +0,0 @@ -# Validator Labels - -The Validators labels table is based on few different kind of Validator addresses that show up on chain. These individual addresses are matched based on the public\_key of the Validator addresses. - -## Table Schema - -**table name:** `terra.validator_labels` - -| Field | Type | Description | -| ------------------- | ------- | --------------------------------------------------------------------- | -| `LABEL` | text | [(see Labels section for details)](../../../../flipside-data/labels/) | -| `OPERATOR_ADDRESS` | address | The validator address (terravaloper) | -| `DELEGATOR_ADDRESS` | address | The delegator address of the Validator (terra) | -| `VP_ADDRESS` | address | The Validator address used for Voting Power (terravalcons) | - diff --git a/data/archive/tables/terra-tables/terra-raw-tables/README.md b/data/archive/tables/terra-tables/terra-raw-tables/README.md deleted file mode 100644 index 8b816f3..0000000 --- a/data/archive/tables/terra-tables/terra-raw-tables/README.md +++ /dev/null @@ -1,24 +0,0 @@ -# Terra Raw Tables - -Terra Raw Tables are the first 5 tables in Terra. It contains the important information about the Terra Blockchains: - -{% content-ref url="blocks.md" %} -[blocks.md](blocks.md) -{% endcontent-ref %} - -{% content-ref url="msgs.md" %} -[msgs.md](msgs.md) -{% endcontent-ref %} - -{% content-ref url="msg_events.md" %} -[msg\_events.md](msg\_events.md) -{% endcontent-ref %} - -{% content-ref url="transactions.md" %} -[transactions.md](transactions.md) -{% endcontent-ref %} - -{% content-ref url="transitions.md" %} -[transitions.md](transitions.md) -{% endcontent-ref %} - diff --git a/data/archive/tables/terra-tables/terra-raw-tables/blocks.md b/data/archive/tables/terra-tables/terra-raw-tables/blocks.md deleted file mode 100644 index afd3179..0000000 --- a/data/archive/tables/terra-tables/terra-raw-tables/blocks.md +++ /dev/null @@ -1,16 +0,0 @@ -# Blocks - -Blocks table shows all the basic blocks information in Terra - -## Table Schema - -**table name:** `terra.blocks` - -| `BLOCK_ID` | number | The block number that this block was recorded | -| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `BLOCKCHAIN` | text | The blockchain name for this block | -| `CHAIN_ID` | number | ID of blockchain to connect to, it can be _columbus-3, columbus-4, etc._ | -| `PROPOSER_ADDRESS` | address | The address of the block proposer for this block, a _block proposer_ is the validator responsible for building a block during any given slot | -| `TX_COUNT` | number | Count of transactions per block, available for Columbus-5 onward. | - diff --git a/data/archive/tables/terra-tables/terra-raw-tables/msg_events.md b/data/archive/tables/terra-tables/terra-raw-tables/msg_events.md deleted file mode 100644 index 7b81d08..0000000 --- a/data/archive/tables/terra-tables/terra-raw-tables/msg_events.md +++ /dev/null @@ -1,24 +0,0 @@ -# Msg\_events - -Message events table shows all the message events information blocks contains. Please be aware that for now terra msgs table only contains the data for **Columbus-4** and **Columbus-5.** - -## Table Schema - -**table name:** `terra.msg_events` - -| Field | Type | Description | -| ------------------ | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | Block number for this message been recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `BLOCKCHAIN` | text | The blockchain name for this block | -| `CHAIN_ID` | text | ID of blockchain to connect to, it can be _columbus-3, columbus-4_, etc. | -| `TX_ID` | text | The transaction that contained this message, unique id to identify this message information | -| `TX_STATUS` | text | Transaction Status for this message events | -| `TX_MODULE` | text | Transaction Module for this message events | -| `TX_TYPE` | text | Transaction Type for this message events | -| `MSG_INDEX` | number | Message index, it is like the different steps for message, one message group can contain multiple message index to deliver many different information | -| `MSG_MODULE` | text | Different type of message, it can be distribution, oracle, etc. | -| `MSG_TYPE` | text | The sub type of message module, the format is like oracle/... | -| `EVENT_INDEX` | number | Event happens within message, it can be seen as the steps of message. Event Index defines the index of this event within the message | -| `EVENT_TYPE` | text | For each event, there will be a type linked to that | -| `EVENT_ATTRIBUTES` | array | The information contained within each event, it can be a JSON array format | diff --git a/data/archive/tables/terra-tables/terra-raw-tables/msgs.md b/data/archive/tables/terra-tables/terra-raw-tables/msgs.md deleted file mode 100644 index f66ad15..0000000 --- a/data/archive/tables/terra-tables/terra-raw-tables/msgs.md +++ /dev/null @@ -1,23 +0,0 @@ -# Msgs - -Message table shows all the message information blocks contains. Please be aware that for now terra msgs table only contains the data for **Columbus-4** and **Columbus-5.** - -## Table Schema - -**table name:** `terra.msgs` - -| Field | Type | Description | -| ----------------- | --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | Block number for this message been recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `BLOCKCHAIN` | text | The blockchain name for this block | -| `CHAIN_ID` | text | ID of blockchain to connect to, it can be _columbus-3, columbus-4, etc._ | -| `TX_ID` | text | The transaction that contained this message, unique id to identify this message information | -| `TX_STATUS` | text | Transaction Status for this message | -| `TX_MODULE` | text | Transaction Module for this message | -| `TX_TYPE` | text | Transaction Type for this message | -| `MSG_INDEX` | number | Message index, it is like the different steps for message, one message group can contain multiple message index to deliver many different information | -| `MSG_MODULE` | text | Different type of message, it can be _distribution, oracle, etc._ | -| `MSG_TYPE` | text | The sub type of message module, the format is like _oracle/..._ | -| `MSG_VALUE` | array | The content of this message, it can be JSON or array and there are many attributes there to identify what kind of message it delivers | - diff --git a/data/archive/tables/terra-tables/terra-raw-tables/transactions.md b/data/archive/tables/terra-tables/terra-raw-tables/transactions.md deleted file mode 100644 index bd143e3..0000000 --- a/data/archive/tables/terra-tables/terra-raw-tables/transactions.md +++ /dev/null @@ -1,24 +0,0 @@ -# Transactions - -Transactions table shows all the transactions information blocks contains - -## Table Schema - -**table name:** `terra.transactions` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number this transaction was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `BLOCKCHAIN` | text | The blockchain for this transaction | -| `CHAIN_ID` | text | ID of blockchain to connect to, it can be columbus-3, columbus-4, etc. | -| `TX_ID` | text | The transaction that contained this message, unique id to identify this message information | -| `TX_TYPE` | text | Transaction type. Luna can be unbonded (free to move wherever), bonded (ie delegated) and unbonding (21 day freeze to undelegate) | -| `TX_STATUS` | text | The transaction status | -| `TX_STATUS_MSG` | text | The transaction status for the message | -| `TX_CODE` | text | The Transaction Code | -| `TX_MODULE` | text | Transaction Module for this message | -| `CODESPACE` | text | Code space for the transaction | -| `FEE` | array | The transaction fee for this transaction, the format is `{ "amount": , "denom": },` where denom is the currency and the amount is how many token spent on this transaction | -| `GAS_USED` | number | The real used gas fee for this transaction, the gas fee is like the gas fee in ETH blockchain | -| `GAS_WANTED` | number | The requested gas fee for this transaction, the gas fee is like the gas fee in ETH blockchain | diff --git a/data/archive/tables/terra-tables/terra-raw-tables/transitions.md b/data/archive/tables/terra-tables/terra-raw-tables/transitions.md deleted file mode 100644 index da8a5d3..0000000 --- a/data/archive/tables/terra-tables/terra-raw-tables/transitions.md +++ /dev/null @@ -1,18 +0,0 @@ -# Transitions - -Transitions table shows all the Transitions information blocks contains - -## Table Schema - -**table name:** `terra.transitions` - -| Field | Type | Description | -| ------------------ | --------- | ------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number this transaction was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this transaction was recorded | -| `BLOCKCHAIN` | text | The blockchain for this transaction | -| `CHAIN_ID` | text | ID of blockchain to connect to, it can be _columbus-3, columbus-4, etc._ | -| `TRANSITION_TYPE` | text | The type of this transition | -| `INDEX` | number | The position/index for this transition | -| `EVENT` | text | The name of the event for this transition record | -| `EVENT_ATTRIBUTES` | array | It contains the information for this transition, the format will be JSON array format | diff --git a/data/archive/tables/terraswap-tables/README.md b/data/archive/tables/terraswap-tables/README.md deleted file mode 100644 index 1a31943..0000000 --- a/data/archive/tables/terraswap-tables/README.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Terraswap Tables - -From the [Terraswap docs](https://docs.terraswap.io/) : "Terraswap is a Uniswap-inspired automated market-maker (AMM) protocol implemented with smart contracts on the Terra blockchain." - -The public Github repo with Terraswap model source code is [here](https://github.com/FlipsideCrypto/sql\_models/tree/main/models/terra/swap). - -### Participants [#](https://docs.terraswap.io/#participants) - -Terraswap users can become trader, liquidity provider or both. - -A **trader** can exchange their token for another token through Terraswap using the price determined by the liquidity pool ratio. - -**Liquidity provider** adds equal value of two assets to their corresponding Terraswap pair pool, which increases liquidity for the corresponding pair market while maintaining the pool price. In this process, liquidity providers are rewarded by newly minted LP tokens. LP tokens represent the liquidity provider’s share in the pool and provide the benefit of earning trading fees, which are accumulated into the pool on every swap transaction. Liquidity providers can burn their LP tokens to withdraw their share from the pool. - diff --git a/data/archive/tables/terraswap-tables/lp-actions-1.md b/data/archive/tables/terraswap-tables/lp-actions-1.md deleted file mode 100644 index 83c29d3..0000000 --- a/data/archive/tables/terraswap-tables/lp-actions-1.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -description: terraswap.pool_reserves ---- - -# Terraswap Pool Reserves - -This table provides block by block pool reserve information including total pool shares, pool currencies, and token amounts in Terraswap pools. - -
FieldTypeDescription
FieldTypeDescription
blockchaintextThe blockchain this pool was created on.
chain_idtextID of blockchain to connect to, it can be columbus-3, columbus-4, columbus-5, etc.
block_idnumberThe block number that this pool reserve was recorded
block_timestamptimestampThe block timestamp that this pool reserve was recorded
contract_addressaddressThe address of the liquidity pool
total_sharenumberThe total amount of shares in a pool
token_0_currencytextToken 0 currency
token_0_amountnumberToken 0 amount in pool
token_1_currencytextToken 1 currency
token_1_amountnumberToken 1 amount in pool
diff --git a/data/archive/tables/terraswap-tables/lp-actions.md b/data/archive/tables/terraswap-tables/lp-actions.md deleted file mode 100644 index ac9f83a..0000000 --- a/data/archive/tables/terraswap-tables/lp-actions.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -description: terraswap.lp_actions ---- - -# Terraswap LP Actions - -Use this table to track liquidity provided or withdrawn by liquidity providers (LPs) on Terraswap. When an LP provides or withdraws liquidity from a Terraswap pool, the transaction is appended to this table. - -
FieldTypeDescription
FieldTypeDescription
blockchaintextThe blockchain this lp action was created on.
chain_idtextID of blockchain to connect to, it can be columbus-3, columbus-4, columbus-5, etc.
block_idnumberThe block number that this lp action was recorded
block_timestamptimestampThe block timestamp that this lp action was recorded
tx_idtextThe transaction that contained this lp action
event_typetextThe type of lp action, either PROVIDE_LIQUIDITY (mint) or WITHDRAW_LIQUIDITY(burn)
senderaddressThe address of the liquidity provider
token_0_amountnumberToken 0 amount in event
token_0_amount_usdnumberToken 0 amount, converted to USD
token_0_currencytextToken 0 currency
token_1_amountnumberToken 1 amount in event
token_1_amount_usdnumberToken 1 amount, converted to USD
token_1_currencytextToken 1 currency
pool_addressaddressThe contract address of the pool
pool_nametextThe name of the Pool
LP_share_amountnumberThe total amount of shares provided or withdrawn in a transaction
LP_pool_addressaddressThe address of the LP token issued
LP_pool_nametextThe name of the LP token issued
diff --git a/data/archive/tables/terraswap-tables/swap.md b/data/archive/tables/terraswap-tables/swap.md deleted file mode 100644 index f9d4fac..0000000 --- a/data/archive/tables/terraswap-tables/swap.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -description: terraswap.swaps ---- - -# Terraswap Swaps - -Swaps table contains the information for swap behavior, it involves the sender (trader) and liquidity pool where the swap takes place. - -**Note**: The terraswap.swaps table is different from terra.swaps. Terraswap swaps are swaps executed by smart contracts in Terraswap liquidity pools. Native swaps (terra.swaps) are on-chain swaps executed by Terra's minting/burning mechanism. For example, when $1 worth of UST is minted, $1 worth of LUNA is burned. - - - -## Table Schema - - - -| Field | Type | Description | -| ------------------- | --------- | ------------------------------------------------------------------------------------ | -| `BLOCKCHAIN` | text | The blockchain this swap was created on (Terra) | -| `CHAIN_ID` | text | ID of blockchain to connect to, it can be _columbus-3, columbus-4, columbus-5, etc._ | -| `BLOCK_ID` | number | The block number that this swap was recorded | -| `MSG_INDEX` | number | The message index for this swap | -| `TX_INDEX` | number | The transaction index for this swap, some transactions contain multiple swaps | -| `BLOCK_TIMESTAMP` | timestamp | The block timestamp that this swap was recorded | -| `TX_ID` | text | The transaction that contained this swap | -| `SENDER` | address | Sender (trader) address for this swap | -| `OFFER_AMOUNT` | number | Amount to offer for this swap | -| `OFFER_AMOUNT_USD` | number | USD Amount to offer for this swap | -| `OFFER_CURRENCY` | text | Currency to offer for this swap | -| `RETURN_AMOUNT` | number | Amount returned for this swap | -| `RETURN_AMOUNT_USD` | number | USD Amount returned for this swap | -| `RETURN_CURRENCY` | text | The currency returned for the swap | -| `POOL_ADDRESS` | text | The address for the pool where the currencies were swapped | -| `POOL_NAME` | text | The name of the pool where the currencies were swapped | diff --git a/data/archive/tables/thorchain-tables/README.md b/data/archive/tables/thorchain-tables/README.md deleted file mode 100644 index 93ef6ed..0000000 --- a/data/archive/tables/thorchain-tables/README.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# THORChain Tables - -**Blockchain:** [THORChain](https://thorchain.org/) - -THORChain is a decentralized cross-chain liquidity protocol that enables native swaps for tokens on separate blockchains. THORChain allows everyone in the world to trade digital asset with another asset on another chain, the process is frictionless, decentralized. Users can also earn yield on their digital assets in THORChain. Each liquidity pool on THORChain has RUNE as one of the underlying assets. - -* Native THORChain token: **RUNE** -* Consensus protocol: Proof of Bond - -![](https://lh5.googleusercontent.com/vUNT-ck46AT2GM6zYtoKTimICi1-nAHZ0RsQs2nuyAL85Da4w07FTvs5qMa-Venw\_MiwwZjDgVFqG7vbxoeFw7tNAUpEVZ7MGP0OnYLzsIr8F5G-wnDDYJKngGh2n8RXVFkgXpWs) - -Check out the complete docs for our [THORChain Raw Tables](thorchain-raw-table/) and [THORChain Base Tables](thorchain-base-table/) or watch this video overview: - -{% embed url="https://www.youtube.com/watch?v=PpTRZcE_KgI" %} diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/README.md b/data/archive/tables/thorchain-tables/thorchain-base-table/README.md deleted file mode 100644 index 4f72824..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/README.md +++ /dev/null @@ -1,62 +0,0 @@ -# THORChain Base Table - -{% content-ref url="block-rewards.md" %} -[block-rewards.md](block-rewards.md) -{% endcontent-ref %} - -{% content-ref url="bond-actions.md" %} -[bond-actions.md](bond-actions.md) -{% endcontent-ref %} - -{% content-ref url="daily-earnings.md" %} -[daily-earnings.md](daily-earnings.md) -{% endcontent-ref %} - -{% content-ref url="daily-pool-stats.md" %} -[daily-pool-stats.md](daily-pool-stats.md) -{% endcontent-ref %} - -{% content-ref url="daily-tvl.md" %} -[daily-tvl.md](daily-tvl.md) -{% endcontent-ref %} - -{% content-ref url="prices.md" %} -[prices.md](prices.md) -{% endcontent-ref %} - -{% content-ref url="swaps.md" %} -[swaps.md](swaps.md) -{% endcontent-ref %} - -{% content-ref url="liquidity-actions.md" %} -[liquidity-actions.md](liquidity-actions.md) -{% endcontent-ref %} - -{% content-ref url="pool-block-balances.md" %} -[pool-block-balances.md](pool-block-balances.md) -{% endcontent-ref %} - -{% content-ref url="pool-block-fees.md" %} -[pool-block-fees.md](pool-block-fees.md) -{% endcontent-ref %} - -{% content-ref url="pool-block-statistics.md" %} -[pool-block-statistics.md](pool-block-statistics.md) -{% endcontent-ref %} - -{% content-ref url="total-block-rewards.md" %} -[total-block-rewards.md](total-block-rewards.md) -{% endcontent-ref %} - -{% content-ref url="total-value-locked.md" %} -[total-value-locked.md](total-value-locked.md) -{% endcontent-ref %} - -{% content-ref url="transfers.md" %} -[transfers.md](transfers.md) -{% endcontent-ref %} - -{% content-ref url="upgrades.md" %} -[upgrades.md](upgrades.md) -{% endcontent-ref %} - diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/block-rewards.md b/data/archive/tables/thorchain-tables/thorchain-base-table/block-rewards.md deleted file mode 100644 index 6dd34e1..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/block-rewards.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: The summarized rewards information for each block per day ---- - -# Block Rewards - -## Table Schema - -**table name:** `thorchain.block_rewards` - -| Field | Type | Description | -| -------------------- | ------ | ------------------------------------------------------------ | -| `DAY` | date | The recorded day | -| `LIQUIDITY_FEE` | number | The summarized liquidity cost fee within this day | -| `BLOCK_REWARDS` | number | The summarized total block rewards within this day | -| `EARNINGS` | number | The summarized earnings within this day | -| `BONDING_EARNINGS` | number | The summarized bonding earnings within this day | -| `LIQUIDITY_EARNINGS` | number | The summarized liquidity earnings fee within this day | -| `AVG_NODE_COUNT` | number | The summarized average node operators number within this day | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/bond-actions.md b/data/archive/tables/thorchain-tables/thorchain-base-table/bond-actions.md deleted file mode 100644 index 4e938e0..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/bond-actions.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -description: The clean bond action table to record the node operators' behaviors ---- - -# Bond Actions - -## Table Schema - -**table name:** `thorchain.bond_actions` - -| Field | Type | Description | -| ----------------- | --------- | ----------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `TX_ID` | number | The transaction that contained this bond events, unique id to identify this message information | -| `FROM_ADDRESS` | address | The sending address for this bond event | -| `TO_ADDRES` | address | The receiving address for this bond event | -| `ASSET` | text | Same as pool name, which pool this bond events happens | -| `BLOCKCHAIN` | text | The blockchain for this event, here is "THOR" | -| `BOND_TYPE` | text | There are 4 different types of bond:`bond_reward, bond_paid, bond_cost, bond_returned` | -| `ASSET_AMOUNT` | number | The asset amount for this bond event | -| `ASSET_USD` | number | Used the price table to calculate the asset in the usd | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/daily-earnings.md b/data/archive/tables/thorchain-tables/thorchain-base-table/daily-earnings.md deleted file mode 100644 index 5f2db22..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/daily-earnings.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -description: The earnings information for the whole THORChain network broken down by daily ---- - -# Daily Earnings - -## Table Schema - -**table name:** `thorchain.daily_earnings` - -| Field | Type | Description | -| ----------------------- | ------ | ------------------------------------------------------------ | -| `DAY` | date | The recorded day | -| `LIQUIDITY_FEE` | number | The summarized liquidity cost fee within this day | -| `LIQUIDITY_FEES_USD` | number | The summarized liquidity cost fee within this day in USD | -| `BLOCK_REWARDS` | number | The summarized total block rewards within this day | -| `BLOCK_REWARDS_USD` | number | The summarized total block rewards within this day in USD | -| `TOTAL_EARNINGS` | number | The summarized total earnings within this day | -| `TOTAL_EARNINGS_USD` | number | The summarized total earnings within this day in USD | -| `EARNINGS_TO_NODES` | number | The summarized bonding earnings within this day | -| `EARNINGS_TO_NODES_USD` | number | The summarized bonding earnings within this day in USD | -| `EARNINGS_TO_POOLS` | number | The summarized liquidity earnings fee within this day | -| `EARNINGS_TO_POOLS_USD` | number | The summarized liquidity earnings fee within this day in USD | -| `AVG_NODE_COUNT` | number | The summarized average node operators number within this day | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/daily-pool-stats.md b/data/archive/tables/thorchain-tables/thorchain-base-table/daily-pool-stats.md deleted file mode 100644 index c802201..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/daily-pool-stats.md +++ /dev/null @@ -1,51 +0,0 @@ ---- -description: Daily Pool Stats shows the table for the pool statistics, broken down by daily ---- - -# Daily Pool Stats - -## Table Schema - -**table name:** `thorchain.daily_pool_stats` - -| Field | Type | Description | -| ------------------------------ | ------ | ------------------------------------------------------------------------------------------------------------------------------- | -| `DAY` | date | The recorded day | -| `POOL_NAME` | text | The asset and the pool name | -| `SYSTEM_REWARDS` | number | The total daily system rewards in RUNE to the pool | -| `SYSTEM_REWARDS_USD` | number | The total daily system rewards in USD to the pool | -| `ASSET_LIQUIDITY` | number | The total asset liquidity for this pool | -| `ASSET_PRICE` | number | Current asset price | -| `ASSET_PRICE_USD` | number | Current asset price in USD | -| `RUNE_LIQUIDITY` | number | The total RUNE liquidity for this pool | -| `RUNE_PRICE` | number | Current RUNE price | -| `RUNE_PRICE_USD` | number | Current RUNE price in USD | -| `ADD_LIQUIDITY_COUNT` | number | How many times to add liquidity to the pool | -| `ADD_ASSET_LIQUIDITY` | number | The total amount of asset liquidity added to the pool | -| `ADD_ASSET_LIQUIDITY_USD` | number | The total amount in usd of asset liquidity added to the pool | -| `ADD_RUNE_LIQUIDITY` | number | The total amount of RUNE liquidity added to the pool | -| `ADD_RUNE_LIQUIDITY_USD` | number | The total amount in usd of RUNE liquidity added to the pool | -| `WITHDRAW_COUNT` | number | Time to withdraw from the pool | -| `WITHDRAW_ASSET_LIQUDITIY` | number | The total amount of asset withdrawn from the pool | -| `WITHDRAW_ASSET_LIQUDITIY_USD` | number | The total amount in USD of asset withdrawn from the pool | -| `WITHDRAW_RUNE_LIQUIDITY` | number | The total amount of RUNE withdrawn from the pool | -| `WITHDRAW_RUNE_LIQUIDITY_USD` | number | The total amount in USD of RUNE withdrawn from the pool | -| `IL_PROTECTION_PAID` | number | Impermanent loss protection cost paid to the network | -| `IL_PROTECTION_PAID_USD` | number | Impermanent loss protection cost in USD paid to the network | -| `AVERAGE_SLIP` | number | Average slippage | -| `TO_ASSET_AVERAGE_SLIP` | number | When swap from RUNE to Asset, the average slippage | -| `TO_RUNE_AVERAGE_SLIP` | number | When swap from Asset to RUNE, the average slippage | -| `SWAP_COUNT` | number | Total number of swaps | -| `TO_ASSET_SWAP_COUNT` | number | Total number of swaps from RUNE TO Asset | -| `TO_RUNE_SWAP_COUNT` | number | Total number of swaps from Asset TO RUNE | -| `SWAP_VOLUME_RUNE` | number | The swap amount of RUNE | -| `SWAP_VOLUME_RUNE_USD` | number | The swap amount of RUNE in USD | -| `TO_ASSET_SWAP_VOLUME` | number | The swap volume from RUNE to Asset | -| `TO_RUNE_SWAP_VOLUME` | number | The swap volume from Asset to RUNE | -| `TOTAL_SWAP_FEES_RUNE` | number | Total swap fees in RUNE | -| `TOTAL_SWAP_FEES_USD` | number | Total swap fees in USD | -| `TOTAL_ASSET_SWAP_FEES` | number | Total asset swap fees in asset | -| `TOTAL_ASSET_RUNE_FEES` | number | Total asset swap fees in RUNE | -| `UNIQUE_MEMBER_COUNT` | number | All memberships with a rune address. Take the member from rune and asset and then subtract the balance = 0 then get the results | -| `UNIQUE_SWAPPER_COUNT` | number | The unique swap address for this pool | -| `LIQUIDITY_UNITS` | number | The amount of units for the liquidity in the pool | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/daily-tvl.md b/data/archive/tables/thorchain-tables/thorchain-base-table/daily-tvl.md deleted file mode 100644 index 0d0dd09..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/daily-tvl.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: The table shows the total valued locked and the total value bonded/pooled ---- - -# Daily TVL - -## Table Schema - -**table name:** `thorchain.daily_tvl` - -| Field | Type | Description | -| ------------------------ | ------ | -------------------------------------------------------------------------------------- | -| `DAY` | date | The recorded day | -| `TOTAL_VALUE_POOLED` | number | The total amount of rune provided by the liquidity provides and pooled in the pool | -| `TOTAL_VALUE_POOLED_USD` | number | The total USD amount of rune provided by the liquidity provides and pooled in the pool | -| `TOTAL_VALUE_BONDED` | number | The total amount of rune provided by the node operators and bonded in the pool | -| `TOTAL_VALUE_BONDED_USD` | number | The total USD amount of rune provided by the node operators and bonded in the pool | -| `TOTAL_VALUE_LOCKED` | number | The total rune value locked in the pool | -| `TOTAL_VALUE_LOCKED_USD` | number | The total USD value locked in the pool | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/liquidity-actions.md b/data/archive/tables/thorchain-tables/thorchain-base-table/liquidity-actions.md deleted file mode 100644 index bd400f7..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/liquidity-actions.md +++ /dev/null @@ -1,34 +0,0 @@ ---- -description: >- - The actions the liquidity providers do in the THORChain, with the amount in - RUNE/Asset ---- - -# Liquidity Actions - -## Table Schema - -**table name:** `thorchain.liquidity_actions` - -| Field | Type | Description | -| ---------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `EVENT_ID` | text | The flipside internal unique id | -| `TX_ID` | text | The unique transaction id for the this swap | -| `LP_ACTION` | text | The direction of the liquidity providers, add or remove the liquidity | -| `POOL_NAME` | text | The asset name | -| `FROM_ADDRESS` | address | The address of the liquidity provider | -| `TO_ADDRESS` | address | The address of the pool | -| `RUNE_AMOUNT` | number | How many RUNE liquidity added/removed | -| `RUNE_AMOUNT_USD` | number | How many RUNE liquidity added/removed in USD | -| `ASSET_AMOUNT` | number | How many Asset liquidity added/removed | -| `ASSET_AMOUNT_USD` | number | How many Asset liquidity added/removed in USD | -| `STAKE_UNITS` | number | Stake units are a way of representing how much liquidity an address has in the pool. THORChain converts the raw amounts you are depositing / withdrawing into `stake_units` to represent what % of the pool you own a claim to. | -| `ASSET_TX_ID` | text | The transaction id for adding/removing the asset | -| `ASSET_ADDRESS` | address | The asset address of the liquidity provider | -| `ASSET_BLOCKCHAIN` | text | The blockchain the asset is in | -| `IL_PROTECTION` | number | The total impermanent loss protection paid for this pool on this day | -| `IL_PROTECTION_USD` | number | The total impermanent loss protection paid in USD for this pool on this day | -| `UNSTAKE_ASYMMETRY` | number | Only exists in unstake, or removing the liquidity | -| `UNSTAKE_BASIS_POINTS` | number | The basis points for unstaking, or removing the liquidity | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-balances.md b/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-balances.md deleted file mode 100644 index 681a314..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-balances.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -description: The table shows the pool block balances based on the rune and asset amount ---- - -# Pool Block Balances - -## Table Schema - -**table name:** `thorchain.pool_block_balances` - -| Field | Type | Description | -| ------------------ | --------- | -------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `POOL_NAME` | text | The pool name for the balance, it can be asset in other tables | -| `RUNE_AMOUNT` | number | The rune amount balance for this pool name | -| `RUNE_AMOUNT_USD` | number | The rune amount balance in USD for this pool name | -| `ASSET_AMOUNT` | number | The asset amount balance for this pool name | -| `ASSET_AMOUNT_USD` | number | The asset amount balance in USD for this pool name | -| `SYNTH_AMOUNT` | number | The synth amount balance for this pool name | -| `SYNTH_AMOUNT_USD` | number | The synth amount balance in USD for this pool name | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-fees.md b/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-fees.md deleted file mode 100644 index f49a38e..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-fees.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: The table shows the fee paid by each pool at different timestamp ---- - -# Pool Block Fees - -## Table Schema - -**table name:** `thorchain.pool_block_fees` - -| Field | Type | Description | -| --------------------------- | ------ | ------------------------------------------------------ | -| `DAY` | date | The timestamp in day for the recorded of the block fee | -| `POOL_NAME` | text | The asset for the fee events | -| `REWARDS` | number | The total rewards | -| `TOTAL_LIQUIDITY_FEES_RUNE` | number | The total liquidity fees paid in RUNE | -| `ASSET_LIQUIDITY_FEES` | number | The liquidity fees paid in Asset | -| `RUNE_LIQUIDITY_FEES` | number | The liquidity fees paid in RUNE | -| `EARNINGS` | number | The total earnings for this pool at this time | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-statistics.md b/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-statistics.md deleted file mode 100644 index 6923c68..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/pool-block-statistics.md +++ /dev/null @@ -1,45 +0,0 @@ ---- -description: >- - The overall pool block statistics broken by day, it lists most important - metrics for the pools ---- - -# Pool Block Statistics - -## Table Schema - -**table name:** `thorchain.pool_block_statistics` - -| Field | Type | Description | -| ---------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------- | -| `DAY` | date | The timestamp in day for the recorded of the block fee | -| `ADD_ASSET_LIQUIDITY_VOLUME` | number | How many asset liquidity has been added to the pol at this time for this pool | -| `ADD_LIQUIDITY_COUNT` | number | How many times there are transactions to add liquidity | -| `ADD_LIQUIDITY_VOLUME` | number | The asset volume of liquidity added to the pool | -| `ADD_RUNE_LIQUIDITY_VOLUME` | number | The rune volume of liquidity added to the pool | -| `ASSET` | text | Asset name or pool name | -| `ASSET_DEPTH` | number | The current pool depth, which is the total Rune pooled in the asset | -| `ASSET_PRICE` | number | The asset price (how many rune) at this time | -| `ASSET_PRICE_USD` | number | The asset price in USD | -| `AVERAGE_SLIP` | number | The average slip point for this block within the day | -| `IMPERMANENT_LOSS_PROTECTION_PAID` | number | The total impermanent loss protection paid for this pool on this day | -| `RUNE_DEPTH` | number | The pool depth | -| `STATUS` | text | The pool status, which is active or not | -| `SWAP_COUNT` | number | Total swap transactions count | -| `SWAP_VOLUME` | number | Total swap volume | -| `TO_ASSET_AVERAGE_SLIP` | number | If the transaction is from Rune to Asset, the average slip point | -| `TO_ASSET_COUNT` | number | How many swaps happen from Rune to Asset | -| `TO_ASSET_FEES` | number | The total swap fees paid to transfer from Rune to Asset | -| `TO_ASSET_VOLUME` | number | The total volume transferred from Rune to Asset | -| `TO_RUNE_AVERAGE_SLIP` | number | If the transaction is from Asset to Rune, the average slip point | -| `TO_RUNE_COUNT` | number | How many swaps happen from Asset to Rune | -| `TO_RUNE_FEES` | number | The total swap fees paid to transfer from Asset to Rune | -| `TO_RUNE_VOLUME` | number | The total volume transferred from Asset to Rune | -| `TOTAL_FEES` | number | The total fees paid for the swaps | -| `UNIQUE_MEMBER_COUNT` | number | All memberships with a rune address. Take the member from rune and asset and then subtract the balance = 0 then get the results | -| `UNIQUE_SWAPPER_COUNT` | number | The unique swap addresses for this pool | -| `UNITS` | number | The swap units | -| `WITHDRAW_ASSET_VOLUME` | number | How many assets get withdrawn from the liquidity pools | -| `WITHDRAW_COUNT` | number | How many times the withdraw events happens | -| `WITHDRAW_RUNE_VOLUME` | number | How many rune volume get withdrawn from the pool | -| `WITHDRAW_VOLUME` | number | How many asset volume get withdrawn from the pool | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/prices.md b/data/archive/tables/thorchain-tables/thorchain-base-table/prices.md deleted file mode 100644 index bc503a2..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/prices.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -description: >- - The table shows the asset and rune prices in the Thorchain, it will include - the exchange ratio between rune/asset and the usd price data ---- - -# Prices - -## Table Schema - -**table name:** `thorchain.prices` - -| Field | Type | Description | -| ------------------ | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `PRICE_RUNE_ASSET` | number | How many RUNE can be exchanged by 1 Asset | -| `PRICE_ASSET_RUNE` | number | How many Asset can be exchanged by 1 RUNE | -| `ASSET_USD` | number | The Asset price in USD | -| `RUNE_USD` | number | The RUNE price in USD | -| `POOL_NAME` | text | The pool this asset in | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/swaps.md b/data/archive/tables/thorchain-tables/thorchain-base-table/swaps.md deleted file mode 100644 index 8c7abea..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/swaps.md +++ /dev/null @@ -1,33 +0,0 @@ ---- -description: The swaps table to show the swap activity in the Thorchain ---- - -# Swaps - -## Table Schema - -**table name:** `thorchain.swaps` - -| Field | Type | Description | -| ------------------- | --------- | ------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `TX_ID` | text | The unique transaction id for the this swap | -| `BLOCKCHAIN` | text | The blockchain for the swap transaction | -| `POOL_NAME` | text | The pool name where the swaps happen | -| `FROM_ADDRESS` | address | The user address that initiates the swap | -| `NATIVE_TO_ADDRESS` | address | The user address that is receiving the result of the swap | -| `TO_POOL_ADDRESS` | address | The pool address that processes the swap | -| `FROM_ASSET` | text | Initial asset to swap | -| `TO_ASSET` | text | The asset swap to | -| `FROM_AMOUNT` | number | Amount of the asset to swap from | -| `TO_AMOUNT` | number | Amount of the asset to swap for | -| `MIN_TO_AMOUNT` | number | Minimal amount to swap for | -| `FROM_AMOUNT_USD` | number | Amount in USD of the asset to swap from | -| `TO_AMOUNT_USD` | number | Amount in USD of the asset to swap for | -| `TO_AMOUNT_MIN_USD` | number | Minimal amount in USD to swap for | -| `SWAP_SLIP_BP` | number | The slippage during the swap process | -| `LIQ_FEE_RUNE` | number | The amount of RUNE liquidity fee paid in RUNE for the swaps | -| `LIQ_FEE_RUNE_USD` | number | The amount of RUNE in USD liquidity fee paid in RUNE for the swaps | -| `LIQ_FEE_ASSET` | number | The amount of Asset liquidity fee paid in RUNE for the swaps | -| `LIQ_FEE_ASSET_USD` | number | The amount of Asset in USD liquidity fee paid in RUNE for the swaps | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/total-block-rewards.md b/data/archive/tables/thorchain-tables/thorchain-base-table/total-block-rewards.md deleted file mode 100644 index 2c77adc..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/total-block-rewards.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -description: The total block rewards for each pool ---- - -# Total Block Rewards - -## Table Schema - -**table name:** `thorchain.total_block_rewards` - -| Field | Type | Description | -| ----------------- | --------- | ---------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `REWARD_ENTITY` | text | The asset or named as pool name | -| `RUNE_AMOUNT` | number | The rewards measured in RUNE amount | -| `RUNE_AMOUNT_USD` | number | The rewards measured in RUNE amount in the USD | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/total-value-locked.md b/data/archive/tables/thorchain-tables/thorchain-base-table/total-value-locked.md deleted file mode 100644 index f99db08..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/total-value-locked.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -description: The table to show the total value locked, bonded and pooled ---- - -# Total Value Locked - -## Table Schema - -**table name:** `thorchain.total_value_locked` - -| Field | Type | Description | -| -------------------- | ------ | ---------------------------------------------------------------------------------- | -| `DAY` | date | The timestamp in day for the recorded of the block fee | -| `TOTAL_VALUE_POOLED` | number | The total amount of rune provided by the liquidity provides and pooled in the pool | -| `TOTAL_VALUE_BONDED` | number | The total amount of rune provided by the node operators and bonded in the pool | -| `TOTAL_VALUE_LOCKED` | number | The total rune value locked in the pool | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/transfers.md b/data/archive/tables/thorchain-tables/thorchain-base-table/transfers.md deleted file mode 100644 index 1b1f61d..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/transfers.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -description: Transfers table shows the transfer action between different address ---- - -# Transfers - -## Table Schema - -**table name:** `thorchain.transfers` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `EVENT_ID` | text | The flipside internal unique id | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `FROM_ADDRESS` | address | The address initiated this transfers | -| `TO_ADDRESS` | address | The address received this transfers | -| `ASSET` | text | The related asset | -| `RUNE_AMOUNT` | number | The transferred RUNE amount | -| `RUNE_AMOUNT_USD` | number | The transferred RUNE amount in USD | diff --git a/data/archive/tables/thorchain-tables/thorchain-base-table/upgrades.md b/data/archive/tables/thorchain-tables/thorchain-base-table/upgrades.md deleted file mode 100644 index bf2601e..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-base-table/upgrades.md +++ /dev/null @@ -1,15 +0,0 @@ -# Upgrades - -## Table Schema - -**table name:** `thorchain.upgrades` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `FROM_ADDRESS` | address | The address initiated this transfers | -| `TO_ADDRESS` | address | The address received this transfers | -| `BURN_ASSET` | text | The burned asset | -| `RUNE_AMOUNT` | number | The transferred RUNE amount | -| `RUNE_AMOUNT_USD` | number | The transferred RUNE amount in USD | diff --git a/data/archive/tables/thorchain-tables/thorchain-core-tables.md b/data/archive/tables/thorchain-tables/thorchain-core-tables.md deleted file mode 100644 index 4296e67..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-core-tables.md +++ /dev/null @@ -1,7 +0,0 @@ -# Thorchain Core Tables - -Documentation for Core tables can be found [here](https://flipsidecrypto.github.io/thorchain\_models/#!/overview). - -The public Github repo with model source code is [here](https://github.com/FlipsideCrypto/thorchain\_models). - -Overview of Fact Dimensional model with Primary & Foreign Key relationships: diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/README.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/README.md deleted file mode 100644 index 2b3d54b..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/README.md +++ /dev/null @@ -1,66 +0,0 @@ -# THORChain Raw Table - -{% content-ref url="active-vault-events.md" %} -[active-vault-events.md](active-vault-events.md) -{% endcontent-ref %} - -{% content-ref url="inactive-vault-events.md" %} -[inactive-vault-events.md](inactive-vault-events.md) -{% endcontent-ref %} - -{% content-ref url="add-events.md" %} -[add-events.md](add-events.md) -{% endcontent-ref %} - -{% content-ref url="block-pool-depths.md" %} -[block-pool-depths.md](block-pool-depths.md) -{% endcontent-ref %} - -{% content-ref url="bond-events.md" %} -[bond-events.md](bond-events.md) -{% endcontent-ref %} - -{% content-ref url="fee-events.md" %} -[fee-events.md](fee-events.md) -{% endcontent-ref %} - -{% content-ref url="gas-events.md" %} -[gas-events.md](gas-events.md) -{% endcontent-ref %} - -{% content-ref url="message-events.md" %} -[message-events.md](message-events.md) -{% endcontent-ref %} - -{% content-ref url="new-node-events.md" %} -[new-node-events.md](new-node-events.md) -{% endcontent-ref %} - -{% content-ref url="pending-liquidity-events.md" %} -[pending-liquidity-events.md](pending-liquidity-events.md) -{% endcontent-ref %} - -{% content-ref url="pool-balance-change-events.md" %} -[pool-balance-change-events.md](pool-balance-change-events.md) -{% endcontent-ref %} - -{% content-ref url="pool-events.md" %} -[pool-events.md](pool-events.md) -{% endcontent-ref %} - -{% content-ref url="refund-events.md" %} -[refund-events.md](refund-events.md) -{% endcontent-ref %} - -{% content-ref url="reserve-events.md" %} -[reserve-events.md](reserve-events.md) -{% endcontent-ref %} - -{% content-ref url="rewards-events.md" %} -[rewards-events.md](rewards-events.md) -{% endcontent-ref %} - -{% content-ref url="rewards-event-entries.md" %} -[rewards-event-entries.md](rewards-event-entries.md) -{% endcontent-ref %} - diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/active-vault-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/active-vault-events.md deleted file mode 100644 index 02c411f..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/active-vault-events.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: Active Vault Events lists the events triggered by the churning activities ---- - -# Active Vault Events - -## Table Schema - -**table name:** `thorchain.active_vault_events` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `ADD_ASGARD_ADDR` | address | The asgard address added to the vault | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/add-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/add-events.md deleted file mode 100644 index 545431e..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/add-events.md +++ /dev/null @@ -1,2 +0,0 @@ -# Add events - diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/block-pool-depths.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/block-pool-depths.md deleted file mode 100644 index a90a585..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/block-pool-depths.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: >- - Block Pool Depth table lists all the available pools and its' rune/asset depth - at each block interval ---- - -# Block Pool Depths - -## Table Schema - -**table name:** `thorchain.block_pool_depths` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `RUNE_E8` | number | The rune depth for this pool at this block | -| `ASSET_E8` | number | The asset depth for this pool at this block | -| `POOL_NAME` | text | Pool name, which is also asset at some other tables | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/bond-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/bond-events.md deleted file mode 100644 index 44056b0..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/bond-events.md +++ /dev/null @@ -1,26 +0,0 @@ ---- -description: >- - Bond Events table lists all the information about the Bond activities. - THORChain uses a spinoff of the Proof of Stake consensus mechanism called - Proof of Bond. ---- - -# Bond Events - -## Table Schema - -**table name:** `thorchain.bond_events` - -| Field | Type | Description | -| ----------------- | --------- | ------------------------------------------------------------------------------------------------------ | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `TX_ID` | number | The transaction that contained this bond events, unique id to identify this message information | -| `TO_ADDRES` | address | The receiving address for this bond event | -| `FROM_ADDRESS` | address | The sending address for this bond event | -| `MEMO` | text | Memo for this bond event | -| `ASSET` | text | Same as pool name, which pool this bond events happens | -| `BLOCKCHAIN` | text | The blockchain for this event, here is "THOR" | -| `BOND_TYPE` | text | There are 4 different types of bond:`bond_reward, bond_paid, bond_cost, bond_returned` | -| `E8` | number | The rune amount for this bond event | -| `ASSET_E8` | number | The asset amount for this bond, using the price table we can calculate the rune amount by asset amount | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/fee-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/fee-events.md deleted file mode 100644 index afa9ffa..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/fee-events.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -description: Fee events lists all related fees happen in the Thorchain network ---- - -# Fee Events - -## Table Schema - -**table name:** `thorchain.fee_events` - -| Field | Type | Description | -| ----------------- | --------- | ----------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `TX_ID` | number | The transaction that contained this fee events, unique id to identify this message information | -| `ASSET` | text | Same as pool name, which pool this fee events happens | -| `POOL_DEDUCT` | number | The amount deduct from the pool related to the fee | -| `ASSET_E8` | number | The asset amount for this fee, using the price table we can calculate the rune amount by asset amount | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/gas-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/gas-events.md deleted file mode 100644 index 992879c..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/gas-events.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -description: Gas events table provides the summary of the gas events for each block ---- - -# Gas Events - -## Table Schema - -**table name:** `thorchain.gas_events` - -| Field | Type | Description | -| ----------------- | --------- | ----------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `RUNE_E8` | number | The total gas amount in rune | -| `TX_COUNT` | number | The total count of transactions within this block id | -| `ASSET_E8` | number | The asset amount for this fee, using the price table we can calculate the rune amount by asset amount | -| `ASSET` | text | Same as pool name, which pool this gas events happens | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/inactive-vault-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/inactive-vault-events.md deleted file mode 100644 index e6c5b30..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/inactive-vault-events.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: Inactive Vault Events lists the events triggered by the churning activities ---- - -# Inactive Vault Events - -## Table Schema - -**table name:** `thorchain.inactive_vault_events` - -| Field | Type | Description | -| ----------------- | --------- | -------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `ADD_ASGARD_ADDR` | address | The asgard address in the vault which are inactive | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/message-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/message-events.md deleted file mode 100644 index a0c729c..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/message-events.md +++ /dev/null @@ -1,19 +0,0 @@ ---- -description: >- - Message events table shows the message nodes send to the network, it will have - the block id, timestamp for identification and the action column shows the - type of message sent ---- - -# Message Events - -## Table Schema - -**table name:** `thorchain.message_events` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `ACTION` | text | The type of action of the message | -| `FROM_ADDRESS` | address | The address sends the message to the network | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/new-node-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/new-node-events.md deleted file mode 100644 index 46a6648..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/new-node-events.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: New Node Events show the new nodes into the network ---- - -# New Node Events - -## Table Schema - -**table name:** `thorchain.new_node_events` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `NODE_ADDRESS` | address | The new node address | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/pending-liquidity-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/pending-liquidity-events.md deleted file mode 100644 index 4d93469..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/pending-liquidity-events.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -description: >- - The pending liquidity events table shows the pending liquidity actions, there - are different types of pending liquidity, can be 'add' or 'withdraw' ---- - -# Pending Liquidity Events - -## Table Schema - -**table name:** `thorchain.pending_liquidity_events` - -| Field | Type | Description | -| ------------------ | --------- | ------------------------------------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `RUNE_TX_ID` | text | The unique transaction id for the rune event, the liquidity type can be add/remove the rune/asset, if the event related to rune | -| `POOL_NAME` | text | The pool name for the liquidity | -| `PENDING_TYPE` | text | The type of liquidity, can be 'add' or 'withdraw' | -| `RUNE_E8` | number | The amount of rune for the liquidity events | -| `ASSET_TX_ID` | text | The unique transaction id for the rune event, the liquidity type can be add/remove the rune/asset, if the event related to rune | -| `ASSET_E8` | number | The amount of asset for the liquidity events | -| `RUNE_ADDRESS` | address | The address of rune | -| `ASSET_ADDRESS` | address | The address of asset | -| `ASSET_BLOCKCHAIN` | text | The blockchain of the asset | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/pool-balance-change-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/pool-balance-change-events.md deleted file mode 100644 index bd03d3e..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/pool-balance-change-events.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -description: Pool Balance Change Events shows the change of the pool balance ---- - -# Pool Balance Change Events - -## Table Schema - -**table name:** `thorchain.pool_balance_change_events` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `REASON` | text | The reason for the pool balance change | -| `ASSET` | text | The related asset or pool name in other table | -| `RUNE_AMOUNT` | number | The amount of rune for the pool balance change | -| `ASSET_ADD` | boolean | False or True, if True, then the event is to add asset not rune | -| `ASSET_AMOUNT` | number | The amount of asset for the pool balance change | -| `RUNE_ADD` | boolean | False or True, if True, then the event is to add rune not asset | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/pool-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/pool-events.md deleted file mode 100644 index 734d527..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/pool-events.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -description: Pool events table shows that the status of the pool at each block id ---- - -# Pool Events - -## Table Schema - -**table name:** `thorchain.pool_events` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `ASSET` | text | The asset/pool name | -| `STATUS` | text | The current status for this pool | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/refund-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/refund-events.md deleted file mode 100644 index cfe9c14..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/refund-events.md +++ /dev/null @@ -1,21 +0,0 @@ -# Refund Events - -## Table Schema - -**table name:** `thorchain.refund_events` - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `TX_ID` | text | | -| `ASSET_E8` | number | | -| `MEMO` | text | | -| `REASON` | text | | -| `ASSET_2ND_E8` | number | | -| `CODE` | number | | -| `BLOCKCHAIN` | text | | -| `ASSET` | text | | -| `ASSET_2ND` | text | | -| `TO_ADDRESS` | address | | -| `FROM_ADDRESS` | address | | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/reserve-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/reserve-events.md deleted file mode 100644 index e43cf8a..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/reserve-events.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -description: Reserve Events table shows the amount of rune reserved into the network ---- - -# Reserve Events - -## Table Schema - -**table name:** `thorchain.reserve_events` - -| Field | Type | Description | -| ----------------- | --------- | -------------------------------------------------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `TX_ID` | text | The transaction that contained this reserve events, unique id to identify this message information | -| `BLOCKCHAIN` | text | The blockchain for this reserve event | -| `ADDRESS` | address | The address reserve the amount to the pool | -| `E8` | number | The rune amount | -| `ASSET_E8` | number | The asset amount | -| `FROM_ADDRESS` | address | The address reserve the amount to the pool | -| `TO_ADDRESS` | address | Reserve the amount to the address | -| `MEMO` | text | The memo for the reserve | -| `ASSET` | text | The reserved asset | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-event-entries.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-event-entries.md deleted file mode 100644 index 0fcdd64..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-event-entries.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -description: Rewards event entries table shows the entries for the rewards ---- - -# Rewards Event Entries - -## Table Schema - -**table name:** `thorchain.rewards_event_entries` - -| Field | Type | Description | -| ----------------- | --------- | ---------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `POOL_NAME` | text | The pool name for the rewards | -| `RUNE_E8` | number | The rune amount of the rewards for this pool at this block | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-events.md deleted file mode 100644 index 77f2a91..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/rewards-events.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -description: Rewards events table shows the rewards at each block id ---- - -# Rewards Events - -## Table Schema - -**table name:** `thorchain.rewards_events` - -| Field | Type | Description | -| ----------------- | --------- | ------------------------------------------------------- | -| `BLOCK_ID` | number | The block number that this block was recorded | -| `BLOCK_TIMESTAMP` | timestamp | The timestamp this block was recorded | -| `BOND_E8` | number | The rune amount of the bond for this pool at this block | diff --git a/data/archive/tables/thorchain-tables/thorchain-raw-table/swap-events.md b/data/archive/tables/thorchain-tables/thorchain-raw-table/swap-events.md deleted file mode 100644 index e3cc832..0000000 --- a/data/archive/tables/thorchain-tables/thorchain-raw-table/swap-events.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -description: Swap event entries table shows the entries for the swaps ---- - -# Swap Events - -| Field | Type | Description | -| -------------------- | ------ | ------------------------------------------------------------------------------- | -| `_FIVETRAN_ID` | text | A unique identifier for the swap event | -| `TO_ADDR` | text | The address we are swapping to | -| `LIQ_FEE_IN_RUNE_E8` | number | The fee in RUNE (divide by 10^8 to get the decimal amount) | -| `FROM_ADDR` | text | The address we are swapping from | -| `TO_ASSET` | text | The asset we are swapping to | -| `FROM_ASSET` | text | The asset we are swapping from | -| `SWAP_SLIP_BP` | number | The slippage | -| `BLOCK_TIMESTAMP` | number | The timestamp of when the block was created | -| `LIQ_FEE_E8` | number | The fee (divide by 10^8 to get the decimal amount) | -| `CHAIN` | text | The chain we are interacting with | -| `TO_E8` | number | The asset amount we are swapping for (divide by 10^8 to get the decimal amount) | -| `POOL` | text | The name of the pool | -| `TX` | text | The transaction ID of the swap | -| `MEMO` | text | The transaction memo | -| `TO_E8_MIN` | number | The minimum amount the swapper will receive | -| `FROM_E8` | number | The amount we are swapping from | - diff --git a/data/archive/tables/uniswap-v3-tables/README.md b/data/archive/tables/uniswap-v3-tables/README.md deleted file mode 100644 index 68c63d9..0000000 --- a/data/archive/tables/uniswap-v3-tables/README.md +++ /dev/null @@ -1,48 +0,0 @@ ---- -description: '[Legacy Documentation, Not Maintained, For Reference Only]' ---- - -# Uniswap V3 Tables - -**Blockchain:** [Ethereum](https://ethereum.org/en/) - -UniswapV3 tables are available in Velocity as the `uniswapv3` schema. These tables are built leveraging Ethereum logs, traces, and contract readings from Flipside's fully archival Ethereum cluster. Each table covers a core V3 concept. - -The public Github repo with Uniswap V3 model source code is [here](https://github.com/FlipsideCrypto/sql\_models/tree/main/models/uniswapv3/eth\_mainnet). - -### Tables - -![](<../../../../.gitbook/assets/Uniswap V3 - Copy of uniswapv3 silver\_tables.png>) - -{% content-ref url="pools.md" %} -[pools.md](pools.md) -{% endcontent-ref %} - -{% content-ref url="pool-stats.md" %} -[pool-stats.md](pool-stats.md) -{% endcontent-ref %} - -{% content-ref url="positions.md" %} -[positions.md](positions.md) -{% endcontent-ref %} - -{% content-ref url="lp-actions.md" %} -[lp-actions.md](lp-actions.md) -{% endcontent-ref %} - -{% content-ref url="../polygon-tables/position-collected-fees.md" %} -[position-collected-fees.md](../polygon-tables/position-collected-fees.md) -{% endcontent-ref %} - -{% content-ref url="../polygon-tables/swaps.md" %} -[swaps.md](../polygon-tables/swaps.md) -{% endcontent-ref %} - - - -### **General Table Notes:** - -* The suffix `_adjusted` on a column name indicates it was decimal adjusted by its underlying token pair. -* `price_1_0`is equivalent to `price` and indicates the price of token1 in terms of token0 -* `price_0_1`is equivalent to `1/price` and indicates the price of token0 in terms of token1 - diff --git a/data/archive/tables/uniswap-v3-tables/lp-actions.md b/data/archive/tables/uniswap-v3-tables/lp-actions.md deleted file mode 100644 index e41f787..0000000 --- a/data/archive/tables/uniswap-v3-tables/lp-actions.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -description: uniswapv3.lp_actions ---- - -# LP Actions - -Use this table to track increases and decreases to positions by liquidity providers (LPs) over time. Whenever a Pool `Burn` or `Mint` event is triggered on a position a record is appended to this table. - -
FieldTypeDescription
FieldTypeDescription
block_idnumberThe block number that this lp action was recorded
block_timestamptimestampThe block timestamp that this lp action was recorded
tx_idtextThe transaction that contained this lp action
blockchaintextThe blockchain this lp action was created on (Ethereum, will support L2s here shortly)
pool_addressaddressThe contract address of the pool
pool_nametextThe name of the Pool (format = "{token0}-{token1} {tick_spacing} {fee}")
actiontextThe type of lp action, either INCREASE_LIQUIDITY (mint) or DECREASE_LIQUIDITY (burn)
liquidity_adjustednumberThe amount of liquidity to mint or burn, decimal adjusted.
liquidity_provideraddressThe address of the liquidity provider
nf_position_manager_addressaddressThe address of the peripheral nf position manager contract, if used.
nf_token_idnumberThe id of the NFT associated with the liquidity position
price_lower_0_1numberLower bound of the liquidity position represented as token 0 per token 1
price_upper_0_1numberUpper bound of the liquidity position represented as token 0 per token 1
price_lower_0_1_usdnumberLower bound of the liquidity position represented as token 0 per token 1, converted to USD
price_upper_0_1_usdnumberUpper bound of the liquidity position represented as token 0 per token 1, converted to USD
price_lower_1_0numberLower bound of the liquidity position represented as token 1 per token 0
price_upper_1_0numberUpper bound of the liquidity position represented as token 1 per token 0
price_lower_1_0_usdnumberLower bound of the liquidity position represented as token 1 per token 0, converted to USD
price_upper_1_0_usdnumberUpper bound of the liquidity position represented as token 1 per token 0, converted to USD
tick_lowernumberLower tick of the liquidity position
tick_uppernumberUpper tick of the liquidity position
token_0_addressaddressContract address of token 0
token_0_symboltextSymbol of token 0
token_1_addressaddressContract address of token 1
token_1_symboltextSymbol of token 1
diff --git a/data/archive/tables/uniswap-v3-tables/pool-stats.md b/data/archive/tables/uniswap-v3-tables/pool-stats.md deleted file mode 100644 index fd05d5a..0000000 --- a/data/archive/tables/uniswap-v3-tables/pool-stats.md +++ /dev/null @@ -1,38 +0,0 @@ ---- -description: uniswapv3.pool_stats ---- - -# Pool Stats - -Statistics for each pool, appened each time a transaction triggers a Pool Event (i.e. 'Initialize', 'Mint', 'Collect', 'Burn', 'Swap', 'Flash', 'IncreaseObservationCardinalityNext', 'SetFeeProtocol', 'CollectProtocol', etc.). - -**A new record is appended each time this occurs.** These stats are read from the Pool contract state leveraging Flipside's fully archival Ethereum cluster. - -| Field | Type | Description | -| ---------------------------------- | --------- | ----------------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block number at which stats computed/read. | -| `block_timestamp` | timestamp | The block timestamp at which stats were computed/read. | -| `blockchain` | string | The blockchain this pool was created on (Ethereum, will support L2s here shortly) | -| `pool_address` | address | The contract address of the pool | -| `pool_name` | string | The name of the pool | -| `price_0_1` | number | The price of token 0 in terms of token 1 | -| `price_1_0` | number | The price of token 1 in terms of token 0 | -| `tick` | number | The tick of the pool according to the last tick transitions that was run | -| `protocol_fees_token_0_adjusted` | number | The amount of token0 owed to the protocol, decimal adjusted | -| `protocol_fees_token_1_adjusted` | number | The amount of token1 owed to the protocol, decimal adjusted | -| `token0_address` | address | The contract address of token0 | -| `token1_address` | address | The contract address of token1 | -| `token0_symbol` | text | The symbol of token0 | -| `token1_symbol` | text | The symbol of token1 | -| `token_0_balance` | number | The balance of token0 locked in the pool contract as of this block | -| `token_1_balance` | number | The balance of token1 locked in the pool contract as of this block | -| `token_0_balance_adjusted` | number | The balance of token0 locked in the pool contract as of this block, decimal adjusted | -| `token_1_balance_adjusted` | number | The balance of token1 locked in the pool contract as of this block, decimal adjusted | -| `unlocked` | boolean | Whether the pool is currently locked to reentrancy | -| `virtual_liquidity_adjusted` | number | The virtual liquidity of the pool | -| `virtual_reserves_token0_adjusted` | number | The virtual reserves of token0, decimal adjusted, in the pool | -| `virtual_reserves_token1_adjusted` | number | The virtual reserves of token1, decimal adjusted, in the pool. | -| `virtual_reserves_token0_usd` | number | The virtual reserves of token0, converted to USD. | -| `virtual_reserves_token1_usd` | number | The virtual reserves of token1 converted to USD. | -| `fee_growth_global0_x128` | number | The fee growth as a Q128.128 fees of token0 collected per unit of liquidity for the entire life of the pool | -| `fee_growth_global1_x128` | number | The fee growth as a Q128.128 fees of token1 collected per unit of liquidity for the entire life of the pool | diff --git a/data/archive/tables/uniswap-v3-tables/pools.md b/data/archive/tables/uniswap-v3-tables/pools.md deleted file mode 100644 index ab95f1d..0000000 --- a/data/archive/tables/uniswap-v3-tables/pools.md +++ /dev/null @@ -1,30 +0,0 @@ ---- -description: uniswapv3.pools ---- - -# Pools - -Pool records are appended to this table whenever a `PoolCreated` event is emitted by the UniswapV3 Factory Contract. - -| Field | Type | Description | -| ----------------- | --------- | --------------------------------------------------------------------------------- | -| `block_id` | number | The block number that this Pool record was created at | -| `block_timestamp` | timestamp | The block timestamp that this Pool record was created at | -| `tx_id` | text | The transaction that this Pool was created at | -| `blockchain` | text | The blockchain this Pool was created on (Ethereum, will support L2s here shortly) | -| `factory_address` | address | The address of the UniswapV3 factory that initialized this Pool | -| `fee_percent` | number | The fee expressed as a decimal percentage | -| `init_price_1_0` | number | The initial price of the Pool (converted from sqrtPriceX96) | -| `init_tick` | number | The initial tick of the Pool | -| `pool_address` | address | The address of the Pool | -| `pool_name` | text | The name of the Pool (format = "token0-token1 fee tick\_spacing") | -| `tick_spacing` | number | The minimum number of ticks allowed between each tick. | -| `token0_address` | address | The contract address of token0 | -| `token0_decimals` | number | The number of decimals for token0 (used for decimal adjustments) | -| `token0_name` | text | The name of token0 | -| `token0_symbol` | text | The symbol of token0 | -| `token1_address` | address | The contract address of token1 | -| `token1_decimals` | number | The number of decimals for token1 (used for decimal adjustments) | -| `token1_name` | text | The name of token1 | -| `token1_symbol` | text | The symbol of token1 | - diff --git a/data/archive/tables/uniswap-v3-tables/positions.md b/data/archive/tables/uniswap-v3-tables/positions.md deleted file mode 100644 index a3022e8..0000000 --- a/data/archive/tables/uniswap-v3-tables/positions.md +++ /dev/null @@ -1,41 +0,0 @@ ---- -description: uniswapv3.positions ---- - -# Positions - -Positions opened by liquidity providers at a specific tick range (tick\_lower_,_ tick\_upper). Whenever an event is emitted related to a position a new record is added to this table with the latest state of the position. - -| Field | Type | Description | -| ------------------------------ | --------- | --------------------------------------------------------------------------------------------------- | -| `block_id` | number | The block number that this position's state was recorded | -| `block_timestamp` | timestamp | The block timestamp that this position's state was recorded | -| `tx_id` | text | The transaction that triggered this position's state to be recorded | -| `blockchain` | text | The blockchain this position was created on (Ethereum, will support L2s here shortly) | -| `pool_address` | address | the contract address of the pool | -| `pool_name` | text | The name of the Pool (format = "{token0}-{token1} {tick\_spacing} {fee}") | -| `is_active` | boolean | Is the position currently active? When a position is closed this is set to false. | -| `liquidity_adjusted` | number | The liquidity of the position, decimal adjusted. | -| `liquidity_provider` | address | The address of the LP | -| `nf_position_manager_address` | address | The address of the peripheral nf position manager contract, if used. | -| `nf_token_id` | number | The id of the NFT associated with the liquidity position | -| `price_lower_0_1` | number | Lower bound of the liquidity position represented as token 0 per token 1 | -| `price_upper_0_1` | number | Upper bound of the liquidity position represented as token 0 per token 1 | -| `price_lower_0_1_usd` | number | Lower bound of the liquidity position represented as token 0 per token 1, converted to USD | -| `price_upper_0_1_usd` | number | Upper bound of the liquidity position represented as token 0 per token 1, converted to USD | -| `price_lower_1_0` | number | Lower bound of the liquidity position represented as token 1 per token 0 | -| `price_upper_1_0` | number | Upper bound of the liquidity position represented as token 1 per token 0 | -| `price_lower_1_0_usd` | number | Lower bound of the liquidity position represented as token 1 per token 0, converted to USD | -| `price_upper_1_0_usd` | number | Upper bound of the liquidity position represented as token 1 per token 0, converted to USD | -| `tick_lower` | number | Lower tick of the liquidity position | -| `tick_upper` | number | Upper tick of the liquidity position | -| `token_0_address` | address | Contract address of token 0 | -| `token_0_symbol` | text | Symbol of token 0 | -| `token_1_address` | address | Contract address of token 1 | -| `token_1_symbol` | text | Symbol of token 1 | -| `tokens_owed0_adjusted` | number | The uncollected amount of token0 owed to the position as of the last computation. | -| `tokens_owed1_adjusted` | number | The uncollected amount of token1 owed to the position as of the last computation | -| `tokens_owed0_usd` | number | The uncollected amount of token0 owed to the position as of the last computation, converted to USD. | -| `tokens_owed1_usd` | number | The uncollected amount of token1 owed to the position as of the last computation, converted to USD | -| `fee_growth_inside0_last_x128` | number | The fee growth of token0 as of the last action on the individual position. | -| `fee_growth_inside1_last_x128` | number | The fee growth of token1 as of the last action on the individual position. | diff --git a/data/data-products/README.md b/data/data-products/README.md new file mode 100644 index 0000000..85a4fce --- /dev/null +++ b/data/data-products/README.md @@ -0,0 +1,2 @@ +# Data Products + diff --git a/products/api-sdk-developers/README.md b/data/data-products/api-sdk-developers/README.md similarity index 100% rename from products/api-sdk-developers/README.md rename to data/data-products/api-sdk-developers/README.md diff --git a/products/api-sdk-developers/community-showcase.md b/data/data-products/api-sdk-developers/community-showcase.md similarity index 100% rename from products/api-sdk-developers/community-showcase.md rename to data/data-products/api-sdk-developers/community-showcase.md diff --git a/products/api-sdk-developers/get-started/README.md b/data/data-products/api-sdk-developers/get-started-1/README.md similarity index 100% rename from products/api-sdk-developers/get-started/README.md rename to data/data-products/api-sdk-developers/get-started-1/README.md diff --git a/products/api-sdk-developers/get-started/archive/README.md b/data/data-products/api-sdk-developers/get-started-1/archive/README.md similarity index 100% rename from products/api-sdk-developers/get-started/archive/README.md rename to data/data-products/api-sdk-developers/get-started-1/archive/README.md diff --git a/products/api-sdk-developers/get-started/archive/js-ts-sdk.md b/data/data-products/api-sdk-developers/get-started-1/archive/js-ts-sdk.md similarity index 100% rename from products/api-sdk-developers/get-started/archive/js-ts-sdk.md rename to data/data-products/api-sdk-developers/get-started-1/archive/js-ts-sdk.md diff --git a/products/api-sdk-developers/get-started/archive/r.md b/data/data-products/api-sdk-developers/get-started-1/archive/r.md similarity index 100% rename from products/api-sdk-developers/get-started/archive/r.md rename to data/data-products/api-sdk-developers/get-started-1/archive/r.md diff --git a/products/api-sdk-developers/get-started/archive/shroomdk-migration-guide.md b/data/data-products/api-sdk-developers/get-started-1/archive/shroomdk-migration-guide.md similarity index 100% rename from products/api-sdk-developers/get-started/archive/shroomdk-migration-guide.md rename to data/data-products/api-sdk-developers/get-started-1/archive/shroomdk-migration-guide.md diff --git a/products/api-sdk-developers/get-started/caching-maxageminutes.md b/data/data-products/api-sdk-developers/get-started-1/caching-maxageminutes.md similarity index 94% rename from products/api-sdk-developers/get-started/caching-maxageminutes.md rename to data/data-products/api-sdk-developers/get-started-1/caching-maxageminutes.md index aa1d05f..8f31ad6 100644 --- a/products/api-sdk-developers/get-started/caching-maxageminutes.md +++ b/data/data-products/api-sdk-developers/get-started-1/caching-maxageminutes.md @@ -17,11 +17,11 @@ WHERE The first time this query is executed it will trigger a QueryRun. That initial QueryRun saves the results along with the timestamp of when those results were recorded. -
+
Now let's attempt to re-run the query, with a `maxAgeMinutes` of 12 hours. -
+
Since the first query successfully executed and stored a result set within the last 12 hours a new QueryRun will not be triggered. diff --git a/products/api-sdk-developers/get-started/errors.md b/data/data-products/api-sdk-developers/get-started-1/errors.md similarity index 100% rename from products/api-sdk-developers/get-started/errors.md rename to data/data-products/api-sdk-developers/get-started-1/errors.md diff --git a/products/api-sdk-developers/get-started/filtering.md b/data/data-products/api-sdk-developers/get-started-1/filtering.md similarity index 100% rename from products/api-sdk-developers/get-started/filtering.md rename to data/data-products/api-sdk-developers/get-started-1/filtering.md diff --git a/products/api-sdk-developers/get-started/pagination.md b/data/data-products/api-sdk-developers/get-started-1/pagination.md similarity index 99% rename from products/api-sdk-developers/get-started/pagination.md rename to data/data-products/api-sdk-developers/get-started-1/pagination.md index 576313c..dcb20af 100644 --- a/products/api-sdk-developers/get-started/pagination.md +++ b/data/data-products/api-sdk-developers/get-started-1/pagination.md @@ -3,7 +3,7 @@ The SDK (and API) expose the ability to request a specific page of the result set by providing both a page number and a dynamically set page size (this means you control the page size). {% hint style="info" %} -By default the page size is set to 100,000 rows and, the page number is set to 1. If you don't set the page size and just use the default, always remember to check page stats in case the number of rows in the entire query result set exceeds the default page size. In this case, you'd need to use the pagination examples on this page to gather your complete result set. Also, keep in mind that there is a byte limit on the amount of data that can be returned on a single page. There may be cases where 100,000 rows are too big and you will need to decrease the page size to a lower number. More details on [rate limits around page sizing here](../get-started/rate-limits.md). +By default the page size is set to 100,000 rows and, the page number is set to 1. If you don't set the page size and just use the default, always remember to check page stats in case the number of rows in the entire query result set exceeds the default page size. In this case, you'd need to use the pagination examples on this page to gather your complete result set. Also, keep in mind that there is a byte limit on the amount of data that can be returned on a single page. There may be cases where 100,000 rows are too big and you will need to decrease the page size to a lower number. More details on [rate limits around page sizing here](rate-limits.md). {% endhint %} Let's start with the following query to return the last 50k NFT transfers on Ethereum: diff --git a/products/api-sdk-developers/get-started/query-results.md b/data/data-products/api-sdk-developers/get-started-1/query-results.md similarity index 100% rename from products/api-sdk-developers/get-started/query-results.md rename to data/data-products/api-sdk-developers/get-started-1/query-results.md diff --git a/products/api-sdk-developers/get-started/query-seconds.md b/data/data-products/api-sdk-developers/get-started-1/query-seconds.md similarity index 96% rename from products/api-sdk-developers/get-started/query-seconds.md rename to data/data-products/api-sdk-developers/get-started-1/query-seconds.md index b903ec7..e61acee 100644 --- a/products/api-sdk-developers/get-started/query-seconds.md +++ b/data/data-products/api-sdk-developers/get-started-1/query-seconds.md @@ -2,7 +2,7 @@ Query Seconds represent computational time against Flipside's data warehouse, canonically referred to as a DataSource. Every QueryRun has the following life cycle. -
+
A query run that is in the state `QUERY_STATE_READY` has been queued for execution. Once it begins execution it transitions to `QUERY_STATE_RUNNING`. From here it can transition to a number of states. If the query executes against the data source successfully it will transition to `QUERY_STATE_STREAMING_RESULTS` and begin downloading the query results for you to export. diff --git a/products/api-sdk-developers/get-started/rate-limits.md b/data/data-products/api-sdk-developers/get-started-1/rate-limits.md similarity index 100% rename from products/api-sdk-developers/get-started/rate-limits.md rename to data/data-products/api-sdk-developers/get-started-1/rate-limits.md diff --git a/products/api-sdk-developers/rest-api.md b/data/data-products/api-sdk-developers/get-started-1/rest-api.md similarity index 98% rename from products/api-sdk-developers/rest-api.md rename to data/data-products/api-sdk-developers/get-started-1/rest-api.md index 739a08d..6667bb6 100644 --- a/products/api-sdk-developers/rest-api.md +++ b/data/data-products/api-sdk-developers/get-started-1/rest-api.md @@ -12,7 +12,7 @@ Don't see an SDK for your language of choice? Interact directly with the API end Want an SDK for another language, or want to create your own SDK? [Let's talk](https://discord.gg/ZmU3jQuu6W)! {% endhint %} -Flipside makes available the following SDKs as higher-level, more developer-friendly wrappers over the API. Examples for each SDK are available throughout the [templates-and-walkthroughs.md](get-started/templates-and-walkthroughs.md "mention") +Flipside makes available the following SDKs as higher-level, more developer-friendly wrappers over the API. Examples for each SDK are available throughout the [templates-and-walkthroughs.md](templates-and-walkthroughs.md "mention")
LanguageVersionSource Code (Github)
✅ Python2.0.7Source Code
✅ JS/TypeScript2.0.0Source Code
✅ R0.2.2Source Code
@@ -255,7 +255,7 @@ query_status <- get_query_status(query_id, api_key) Every QueryRun has the following life cycle: -
+
Once the `getQueryRun` has returned a state of `QUERY_STATE_SUCCESS` call the `getQueryRunResults` RPC method to retrieve the result set in Step3. diff --git a/products/api-sdk-developers/get-started/run-your-first-query.md b/data/data-products/api-sdk-developers/get-started-1/run-your-first-query.md similarity index 100% rename from products/api-sdk-developers/get-started/run-your-first-query.md rename to data/data-products/api-sdk-developers/get-started-1/run-your-first-query.md diff --git a/products/api-sdk-developers/get-started/sorting.md b/data/data-products/api-sdk-developers/get-started-1/sorting.md similarity index 100% rename from products/api-sdk-developers/get-started/sorting.md rename to data/data-products/api-sdk-developers/get-started-1/sorting.md diff --git a/products/api-sdk-developers/get-started/templates-and-walkthroughs.md b/data/data-products/api-sdk-developers/get-started-1/templates-and-walkthroughs.md similarity index 100% rename from products/api-sdk-developers/get-started/templates-and-walkthroughs.md rename to data/data-products/api-sdk-developers/get-started-1/templates-and-walkthroughs.md diff --git a/data/data-products/api-sdk-developers/get-started/README.md b/data/data-products/api-sdk-developers/get-started/README.md new file mode 100644 index 0000000..fc82f20 --- /dev/null +++ b/data/data-products/api-sdk-developers/get-started/README.md @@ -0,0 +1,2 @@ +# Get Started + diff --git a/products/api-sdk-developers/getting-started.md b/data/data-products/api-sdk-developers/get-started/getting-started.md similarity index 100% rename from products/api-sdk-developers/getting-started.md rename to data/data-products/api-sdk-developers/get-started/getting-started.md diff --git a/products/api-sdk-developers/python-r-templates-video-tutorials.md b/data/data-products/api-sdk-developers/python-r-templates-video-tutorials/README.md similarity index 100% rename from products/api-sdk-developers/python-r-templates-video-tutorials.md rename to data/data-products/api-sdk-developers/python-r-templates-video-tutorials/README.md diff --git a/products/api-sdk-developers/have-questions.md b/data/data-products/api-sdk-developers/python-r-templates-video-tutorials/have-questions.md similarity index 50% rename from products/api-sdk-developers/have-questions.md rename to data/data-products/api-sdk-developers/python-r-templates-video-tutorials/have-questions.md index 646db48..5e67acb 100644 --- a/products/api-sdk-developers/have-questions.md +++ b/data/data-products/api-sdk-developers/python-r-templates-video-tutorials/have-questions.md @@ -6,5 +6,5 @@ description: (aka support) Introduce yourself in the SDK [Discord](https://discord.gg/ZmU3jQuu6W) channels, ask questions, and share what you're working on: -

Dedicated SDK channels in our Discord host a vibrant community of creators.

+

Dedicated SDK channels in our Discord host a vibrant community of creators.

diff --git a/products/data-studio-sql-analysts/README.md b/data/data-products/data-studio-sql-analysts/README.md similarity index 54% rename from products/data-studio-sql-analysts/README.md rename to data/data-products/data-studio-sql-analysts/README.md index b96800f..6ce29d6 100644 --- a/products/data-studio-sql-analysts/README.md +++ b/data/data-products/data-studio-sql-analysts/README.md @@ -2,7 +2,7 @@ **Unlock the power of blockchain data with Flipside Studio, no matter your SQL expertise!** Whether you're a seasoned analyst or just starting out, choose the path that best aligns with your goals: -
Analyze blockchain dataCraft your own SQL queries to dissect the data and uncover insightsquery-editorget-started
Discover InsightsKeep your finger on the pulse of what's happening in crypto datadiscover.mdbrowse-dashboards.md
Build ProductsTransform data into powerful solutionsgetting-started.mdgetting-started.md
+
Analyze blockchain dataCraft your own SQL queries to dissect the data and uncover insightsquery-editorget-started
Discover InsightsKeep your finger on the pulse of what's happening in crypto datadiscover.mdBroken link
Build ProductsTransform data into powerful solutionsgetting-started.mdgetting-started.md
@@ -10,8 +10,8 @@ The app has a few basic components, here's how they fit together: * [**Discover**](discover.md) — the best way to keep your finger on the pulse of what's happening in crypto data. Here you can see what dashboards are trending for different chains and projects, fav ones you like, keyword search for specific topics, and see which analysts are consistently topping the charts. * [**My Work**](broken-reference) — where the work lives: get here by clicking on the folder icon in the side nav. Keyword search to open any work you've done in the past. Group files by creating collections and nesting collections. Organize by using features like multi-select and drag & drop. -* [**Query Editor**](query-editor/) — where the work happens: get here by navigating to the Studio in the top nav. Run SQL queries, get results, visualize them, and publish them on a dashboard, all from one place in the app. Seamlessly switch between any of your queries and dashboards with our tabs system, and use the Data Explorer to preview data tables, and add table names directly to your queries. -* [**Dashboard Editor**](dashboard-editor/) — where you share your findings with the world: add charts, results tables, text and images to your dashboards, send them to your friends with our copy link feature, or tweet the link directly from the dashboard. Organize your findings with dashboard tabs, and let people customize or update your dashboard with parameters. +* [**Query Editor**](studio-in-depth/query-editor/) — where the work happens: get here by navigating to the Studio in the top nav. Run SQL queries, get results, visualize them, and publish them on a dashboard, all from one place in the app. Seamlessly switch between any of your queries and dashboards with our tabs system, and use the Data Explorer to preview data tables, and add table names directly to your queries. +* [**Dashboard Editor**](studio-in-depth/dashboard-editor/) — where you share your findings with the world: add charts, results tables, text and images to your dashboards, send them to your friends with our copy link feature, or tweet the link directly from the dashboard. Organize your findings with dashboard tabs, and let people customize or update your dashboard with parameters. * [**Profiles**](broken-reference) — your profile is the place where people can find all your best work, search and filter it, and see how to get get in touch with you if that's something you want! Update your avatar and background image, and add social contact details for Twitter, Telegram, and Discord. We're adding more documentation for the app over time — if you have questions or suggestions for things to add, please let us know in [Discord](https://discord.gg/ZmU3jQuu6W). diff --git a/products/data-studio-sql-analysts/discover.md b/data/data-products/data-studio-sql-analysts/discover.md similarity index 75% rename from products/data-studio-sql-analysts/discover.md rename to data/data-products/data-studio-sql-analysts/discover.md index 62d16e8..64aaaca 100644 --- a/products/data-studio-sql-analysts/discover.md +++ b/data/data-products/data-studio-sql-analysts/discover.md @@ -1,11 +1,11 @@ --- description: >- - The homepage of the app, and the best way to keep your finger on the pulse of - what's happening in crypto data. Here you can see what dashboards are trending - for different chains and projects. + The Insights tab is the best way to keep your finger on the pulse of what's + happening in crypto data. Here you can see what dashboards are trending for + different chains and projects. --- -# Explore Dashboards +# Get Inspired This section will cover: @@ -16,9 +16,9 @@ This section will cover: *** -"Top 8" refers to the first 8 dashboards listed on the [discover page](http://flipsidecrypto.xyz). These are the dashboards that fill the landing page, primed for maximum exposure to alpha-seekers. +"Top Dashboards refers to the first dashboards listed on the [discover page](http://flipsidecrypto.xyz). These are the dashboards that fill the landing page, primed for maximum exposure to alpha-seekers. -

Top 8

+

Top 8

Being in the top 8 also increases your ranking as an analyst on Flipside. In fact, the longer your work occupies a Top 8 slot, the higher your ranking climbs. @@ -36,7 +36,7 @@ That's a bit of 🧪 a l c h e m y ✨ that will stay a secret. But we can tell There are 100K+ dashboards on Flipside 🤯 Here's how to find the ones you're interested in! -

Ways to browse dashboards on Flipside.

+

Ways to browse dashboards on Flipside.

* **Search for a topic:** if you have a topic in mind (like: "impermanent loss osmosis"), type it into the search bar to see all the relevant dashboards. * **Find an analyst:** if you have someone in mind, you can search for them from the ["Analyst View"](discover.md#analyst-view) @@ -50,11 +50,11 @@ To search for an analyst, all you have to do is turn the toggle in the hero sect From [this view](https://flipsidecrypto.xyz/analysts), you can type an analyst's name into the search bar to find their profile, or explore different analyst profiles by going down the page. -
+
Once you find the analyst you're looking for, you can click on their profile to find their top dashboards, and potentially a few ways to get in touch with them. This is a great way to connect with other analysts in the space so make sure you build out your own [profile](broken-reference) too! -
+
*** @@ -62,7 +62,7 @@ Once you find the analyst you're looking for, you can click on their profile to Now, that you've found a dashboard you're interested in. Let's cover some tips to get the most out of this experience. -

Ways to interact with a Flipside dashboard.

+

Ways to interact with a Flipside dashboard.

Here are some ways you can interact with a dashboard: @@ -74,7 +74,7 @@ Here are some ways you can interact with a dashboard: -

Click "Fork" to make a copy of the query.

+

Click "Fork" to make a copy of the query.

* **Refresh:** Click the 🔁 button on the top right corner to run all the queries powering this dashboard to see the latest information. * **Like:** if you liked what you saw, hit the ❤️ button — "likes" impact the rankings and you'll help more people see good work by voting for things you enjoy. * **Share:** found something interesting, share it with your community on Twitter! diff --git a/products/data-studio-sql-analysts/get-started/README.md b/data/data-products/data-studio-sql-analysts/get-started/README.md similarity index 81% rename from products/data-studio-sql-analysts/get-started/README.md rename to data/data-products/data-studio-sql-analysts/get-started/README.md index 1458d97..384ce40 100644 --- a/products/data-studio-sql-analysts/get-started/README.md +++ b/data/data-products/data-studio-sql-analysts/get-started/README.md @@ -21,15 +21,15 @@ Steps: 2. Click on the database icon to access data on 26+ protocols 3. Quick introduction to how Flipside's data is organized: * **Hierarchy:** blockchain → schemas -> tables - * Read more on our [data modeling approach](../../../data/flipside-data/data-models.md) here. + * Read more on our [data modeling approach](../../../flipside-data/data-models.md) here. -
+
Data exploration tips: - + * **Column details:** click on a table to see it's columns, and a data type for each. @@ -73,7 +73,7 @@ order by sales_count desc limit 8 ``` -
+
*** @@ -85,7 +85,7 @@ Steps: 2. Choose the chart type that best captures your data's essence. Bar, line, pie? 3. Define the data points by setting your X and Y axes. -
+
*** diff --git a/products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md b/data/data-products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md similarity index 72% rename from products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md rename to data/data-products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md index 917b26c..358edce 100644 --- a/products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md +++ b/data/data-products/data-studio-sql-analysts/get-started/write-fork-your-first-query.md @@ -12,17 +12,17 @@ To get started, open a new query in your Studio (an easy way to do this is to vi To understand exactly what data is included in a table before you query it, click "Preview": -
+
This will populate a sample of the table for you instantly in your Studio. -
+
## Add to query To auto-populate the name of the table in your query, you can use the double-arrow "Add to query" button: -
+
Now you understand how to navigate the database and find the tables that contain the data you need, so you're ready to start writing your own SQL queries and generating onchain insights. @@ -40,13 +40,13 @@ From the [Discover page](https://flipsidecrypto.com/discover), choose any dashbo -
+
### **Click a chart title** Choose a visualization you'd like to replicate, and click its title. For example, let's click on "SOL volume in period": -
+
### Fork the query @@ -54,5 +54,5 @@ Clicking a chart title in a public dashboard will show you the query and resulti But if you want to use or edit the same query, you can just click "Fork" in the top right corner, which will auto-populate the same query and visualization settings in your studio: -
+
diff --git a/data/data-products/data-studio-sql-analysts/studio-in-depth/README.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/README.md new file mode 100644 index 0000000..487afda --- /dev/null +++ b/data/data-products/data-studio-sql-analysts/studio-in-depth/README.md @@ -0,0 +1,2 @@ +# Studio in Depth + diff --git a/products/data-studio-sql-analysts/customize-your-studio.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/customize-your-studio.md similarity index 82% rename from products/data-studio-sql-analysts/customize-your-studio.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/customize-your-studio.md index bd7bf18..8bd3349 100644 --- a/products/data-studio-sql-analysts/customize-your-studio.md +++ b/data/data-products/data-studio-sql-analysts/studio-in-depth/customize-your-studio.md @@ -25,7 +25,7 @@ In the query editor at [flipside.new](http://flipside.new/), there are several w You can resize all of these panels to your heart’s content (and in dark mode!). -
+
*** @@ -33,7 +33,7 @@ You can resize all of these panels to your heart’s content (and in dark mode!) The “My Work” section (folder icon) in the left-hand menu is also customizable, so you never have to dig through a cluttered query history to duplicate or go over old work. -
+
Under My Work, you can create a query, a dashboard, or a collection of several of either. To organize your new creation, you have a few options: @@ -54,7 +54,7 @@ Then, simply use the search bar and “sort by” function to conveniently keep Think of your Flipside profile as your professional analysis portfolio. The dashboards you create will be collected under your profile, giving you one central body of work. -

Marqu is a legendary analyst in the Flipside community, and well-worth a follow.

+

Marqu is a legendary analyst in the Flipside community, and well-worth a follow.

You can add photos to create a persona or represent yourself, as well as social links to give people a way to follow your work or contact you with requests. @@ -62,7 +62,7 @@ You can add photos to create a persona or represent yourself, as well as social **1. Click “Edit profile” in the settings menu** -
+
**2. Enter your details:** Add a profile and header image, and your preferred social handles: Twitter/X, Discord, and Telegram. You can also change your email and username here at any time. diff --git a/products/data-studio-sql-analysts/dashboard-editor/README.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/README.md similarity index 80% rename from products/data-studio-sql-analysts/dashboard-editor/README.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/README.md index d115c86..a0623b0 100644 --- a/products/data-studio-sql-analysts/dashboard-editor/README.md +++ b/data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/README.md @@ -2,7 +2,7 @@ description: Tell a story with data and share your findings with the world --- -# Dashboard Builder +# Build a Dashboard This section will cover: @@ -18,7 +18,7 @@ This section will cover: Before we go over how to populate a dashboard, we'll go over the different components of a dashboard. -
+
In the example dashboard above, we get a glimpse of how different components look on a dashboard. Starting from the top of the screen, and moving down, we see an example of each of the following: @@ -28,7 +28,7 @@ In the example dashboard above, we get a glimpse of how different components loo -

Heading styles.

+

Heading styles.

* **Text boxes:** these are regular text boxes that are best suited for paragraphs. The style of these text boxes can be adjusted using [markdown](https://www.markdownguide.org/basic-syntax/). * **Images:** this helps bring your story to life. You can upload a PNG, SVG, GIF, or JPEG. * **Charts and Tables:** the star of the show, you can add charts and tables from your queries to the dashboard. @@ -41,13 +41,13 @@ Now that we have the basics covered, we'll introduce three different ways you ca * **From the query editor:** to add tables and charts from the editor, click the "Add to Dashboard" button in the top right corner of each panel. From there, you can select a dashboard, search for a dashboard, or create a new dashboard. -

Add tables and charts to a dashboard from the editor.

+

Add tables and charts to a dashboard from the editor.

* **From the action bar:** this is the floating bar at the bottom of the dashboard builder. It is accessible via a dashboard tab that you open in the editor. Click on any component to add a block of that type, or drag any component onto the board directly to add it exactly where you want it to go: - ![Action Bar from the Dashboard Editor. ](<../../../.gitbook/assets/Screenshot 2023-03-10 at 2.03.30 PM (1).png>) + ![Action Bar from the Dashboard Editor. ](<../../../../../.gitbook/assets/Screenshot 2023-03-10 at 2.03.30 PM (1).png>) * **From My Work 😮:** drag and drop any table and chart from My Work directly into your dashboard. Click on the little caret to the left of a query's name to see all the tables and charts associated with it: - ![Expanded query item under My Work.](<../../../.gitbook/assets/Screenshot 2023-03-10 at 2.38.47 PM.png>) + ![Expanded query item under My Work.](<../../../../../.gitbook/assets/Screenshot 2023-03-10 at 2.38.47 PM.png>) @@ -64,7 +64,7 @@ Once, the components are added to the dashboard, they can be repositioned and re Once you complete a dashboard, publish it to make it publicly accessible! You can do that by clicking on the "Publish" button in the top right corner of the screen (don't worry this process is irreversible! More on that later). A published dashboard can be accessed by anyone through the Discover page, your analyst profile, and if they have the URL, directly. -
+
**Un-publishing / Editing a dashboard** diff --git a/products/data-studio-sql-analysts/dashboard-editor/markdown-reference.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/markdown-reference.md similarity index 100% rename from products/data-studio-sql-analysts/dashboard-editor/markdown-reference.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/dashboard-editor/markdown-reference.md diff --git a/products/data-studio-sql-analysts/query-editor/README.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/README.md similarity index 84% rename from products/data-studio-sql-analysts/query-editor/README.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/README.md index d3c9e2e..57412ff 100644 --- a/products/data-studio-sql-analysts/query-editor/README.md +++ b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/README.md @@ -4,7 +4,7 @@ description: >- publish them on a dashboard, all from one place in the app --- -# Query Editor +# Use the Query Editor This section will cover: @@ -19,7 +19,7 @@ This section will cover: The editor is composed of three main panels - query, results, and charts. To the left of these panels, you have access to My Work or the Data Explorer. To the top, you can see all the queries and dashboards you've opened in tabs. -

Work interface.

+

Work interface.

**Configure your Interface.** @@ -35,7 +35,7 @@ Focus on different panels as you go through your workflow by expanding/collapsin This is where you input your SQL + Run it. Here are some features of the query panel. -
+
* **Auto-Complete:** start typing and the auto-complete feature will bring up Snowflake SQL keywords as well as database, schema, and table names. * **Select & Run:** select and highlight any part of your code to only run that snippet to see the "Selection Result" in the results panel. @@ -44,7 +44,7 @@ This is where you input your SQL + Run it. Here are some features of the query p * To insert a parameter, you can click the "+ Parameter" button or simply type `{{parameter_name}}` and manage your parameters at the bottom of the query panel. * To add a select list of values for your end user to choose from, include a comma-separated list in the default values. This will show up as a dropdown list on your dashboard. See an example below: -

Comma-separated list as a dropdown in your dashboard.

+

Comma-separated list as a dropdown in your dashboard.

* **Auto-Format:** make your query more readable by using the auto-format button! *** @@ -53,7 +53,7 @@ This is where you input your SQL + Run it. Here are some features of the query p This is where you'll see the data you queried. To get results, write your SQL in the query panel and hit the blue play button in the top right corner. Or, you can run a query using your keyboard shortcut: `cmd + enter (mac)` or `ctrl + enter (windows/linux)`. -
+
The results panel is also where you'll see an error message if your query fails. There will be detailed feedback that will give you an idea of how to update your query. Here are a couple more things you can do through the results panel. @@ -67,7 +67,7 @@ The results panel is also where you'll see an error message if your query fails. This is where you visualize your data. Using the Flipside App, you can create a **Bar**, **Area**, **Line**, **Scatter**, **Big Number**, or **Donut chart**. -

The chart editor will give you some initial guidance on how to get started.

+

The chart editor will give you some initial guidance on how to get started.

Here's a quick reference on when to choose which chart: diff --git a/resources/hex-to-integer-function.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/hex-to-integer-function.md similarity index 86% rename from resources/hex-to-integer-function.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/hex-to-integer-function.md index 392368c..5db50d9 100644 --- a/resources/hex-to-integer-function.md +++ b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/hex-to-integer-function.md @@ -49,7 +49,7 @@ We can rearrange the data above to what we see on Etherscan in the screenshot be 000000000000000000000000b932a70a57673d89f4acffbe830e8ed7f75fb9e0\ 0000000000000000000000000000000000000000000000000000000000001ffb -
+
We can use the substr function to get the string that is associated with ‘auctionId’. @@ -73,6 +73,6 @@ from ethereum.core.fact_transactions This would result in 8187 which is consistent with using the decode button on Etherscan as shown in the screenshot below. -
+
-There are also more utility functions available [here](../products/get-started/examples/utility-functions/). +There are also more utility functions available [here](../../../livequery/add-ons/examples/utility-functions/). diff --git a/products/data-studio-sql-analysts/query-editor/keyboard-shortcuts.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/keyboard-shortcuts.md similarity index 100% rename from products/data-studio-sql-analysts/query-editor/keyboard-shortcuts.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/keyboard-shortcuts.md diff --git a/products/data-studio-sql-analysts/query-editor/using-snowflake-sql.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/using-snowflake-sql.md similarity index 100% rename from products/data-studio-sql-analysts/query-editor/using-snowflake-sql.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/using-snowflake-sql.md diff --git a/products/data-studio-sql-analysts/query-editor/writing-efficient-queries.md b/data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/writing-efficient-queries.md similarity index 100% rename from products/data-studio-sql-analysts/query-editor/writing-efficient-queries.md rename to data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/writing-efficient-queries.md diff --git a/products/data-studio-sql-analysts/teams-accounts.md b/data/data-products/data-studio-sql-analysts/team-accounts.md similarity index 58% rename from products/data-studio-sql-analysts/teams-accounts.md rename to data/data-products/data-studio-sql-analysts/team-accounts.md index afd07b1..e78c030 100644 --- a/products/data-studio-sql-analysts/teams-accounts.md +++ b/data/data-products/data-studio-sql-analysts/team-accounts.md @@ -2,16 +2,16 @@ description: Build, iterate, and riff with your team in real-time. --- -# Teams Accounts +# Team Accounts ### Benefits of Team accounts -* [**Bring your team together**](teams-accounts.md#create-a-team-account)**:** Invite your collaborators to a shared workspace, where you can access all of your shared queries and dashboards in one place. -* [**Collaborate in real-time:**](teams-accounts.md#real-time-collaboration) Save time with real-time collaboration and transparent workflows. See who’s currently working on a query or dashboard, and riff live. -* [**Get Credit for your work:**](teams-accounts.md#get-credit-for-your-work) Build your brand and reputation with attribution. See your name on all the dashboards you've contributed to, even if it's published by the team. -* [**Transfer work across contexts:**](teams-accounts.md#transfer-work-across-contexts) Copy any query and dashboard from one workspace to another. -* [**Context Switching:**](teams-accounts.md#context-switching) Keep your personal work separate from your team's and easily switch between different workspaces. -* [**API & LiveQuery:**](teams-accounts.md#api-+-livequery) Continue to use the API and LiveQuery as a team. +* [**Bring your team together**](team-accounts.md#create-a-team-account)**:** Invite your collaborators to a shared workspace, where you can access all of your shared queries and dashboards in one place. +* [**Collaborate in real-time:**](team-accounts.md#real-time-collaboration) Save time with real-time collaboration and transparent workflows. See who’s currently working on a query or dashboard, and riff live. +* [**Get Credit for your work:**](team-accounts.md#get-credit-for-your-work) Build your brand and reputation with attribution. See your name on all the dashboards you've contributed to, even if it's published by the team. +* [**Transfer work across contexts:**](team-accounts.md#transfer-work-across-contexts) Copy any query and dashboard from one workspace to another. +* [**Context Switching:**](team-accounts.md#context-switching) Keep your personal work separate from your team's and easily switch between different workspaces. +* [**API & LiveQuery:**](team-accounts.md#api-+-livequery) Continue to use the API and LiveQuery as a team. *** @@ -21,16 +21,16 @@ description: Build, iterate, and riff with your team in real-time. 1. Navigate to the "Account" dropdown in the top right corner of the page. In the dropdown menu, you'll find the option to "Create Team Account". -
+
2. Fill in the form with your Team name, Flipside profile link, team website URL, and Twitter handle. Click "Create Team" to land in the Team's Profile. This is the home base to invite teammates and find published dashboards. -
+
3. Add Team Members via their Flipside username or their email. Assign them a role and hang tight! -
+
4. To accept an invite, refresh the page to find invites in the "Account" dropdown. Once accepted, it's time to collaborate! -
+
*** @@ -40,10 +40,10 @@ Seamlessly collaborate with your teammates on the same query or dashboard. * See who is currently working on a query or dashboard and what they are doing by following their cursors. -
+
* Multiple analysts can work on the same query and dashboard together. For example, two analysts on the same query can simultaneously write CTEs. Or, two analysts can work on different tabs of a dashboard. -
+
*** @@ -51,7 +51,7 @@ Seamlessly collaborate with your teammates on the same query or dashboard. Regardless of what workspace you're working in, get credit for the hard work you put in. A dashboard published by a team will list individual team members who worked on the particular dashboard. -
+
*** @@ -67,7 +67,7 @@ When a dashboard is transferred, all underlying queries of that dashboard will b To transfer a dashboard or query to another workspace, click on the overflow menu **(⋅⋅⋅)** and select "Copy to Workspace". Then in the modal, select the workspace you'd like to transfer to. -
+
*** diff --git a/data/data-products/data-studio-sql-analysts/tutorials/README.md b/data/data-products/data-studio-sql-analysts/tutorials/README.md new file mode 100644 index 0000000..84ce15b --- /dev/null +++ b/data/data-products/data-studio-sql-analysts/tutorials/README.md @@ -0,0 +1,2 @@ +# Tutorials + diff --git a/flipside-community/how-to-analyze-web3-data.md b/data/data-products/data-studio-sql-analysts/tutorials/how-to-analyze-web3-data.md similarity index 79% rename from flipside-community/how-to-analyze-web3-data.md rename to data/data-products/data-studio-sql-analysts/tutorials/how-to-analyze-web3-data.md index 32d3e93..a5af78d 100644 --- a/flipside-community/how-to-analyze-web3-data.md +++ b/data/data-products/data-studio-sql-analysts/tutorials/how-to-analyze-web3-data.md @@ -2,8 +2,8 @@ Learn how to understand and analyze on-chain data on Flipside with these guides by our team & community: -1. [**User Guide: Understanding Flipside Crypto Data Models**](https://flipsidecrypto.xyz/flipcomm/user-guide-understanding-flipside-crypto-data-models-VDBJP1), by [@kenshinrhonin](https://twitter.com/KenshinRhonin). -2. [**Flipside 101 : Deep Dive into the Foundations of Crypto Using Flipside Schemas**](https://flipsidecrypto.xyz/charliemarketplace/flipside-101-ll5imK), by [@charliemarketplace](https://flipsidecrypto.xyz/charliemarketplace). +1. [**Flipside 101 : Deep Dive into the Foundations of Crypto Using Flipside Schemas**](https://flipsidecrypto.xyz/charliemarketplace/flipside-101-ll5imK), by [@charliemarketplace](https://flipsidecrypto.xyz/charliemarketplace). +2. [**User Guide: Understanding Flipside Crypto Data Models**](https://flipsidecrypto.xyz/flipcomm/user-guide-understanding-flipside-crypto-data-models-VDBJP1), by [@kenshinrhonin](https://twitter.com/KenshinRhonin). 3. [**OPOF: Only Possible on Flipside**](https://flipsidecrypto.xyz/flipcomm/opof-yI08iS)[ **(Solana data edition)**](https://flipsidecrypto.xyz/flipcomm/opof-yI08iS), by [@kellen](https://flipsidecrypto.xyz/kellen), [@flyingfish](https://flipsidecrypto.xyz/flyingfish), and [@kenshinrhonin](https://twitter.com/KenshinRhonin). Share your work on X (formerly Twitter) to earn! @@ -12,5 +12,5 @@ Share your work on X (formerly Twitter) to earn! Ready to dive deeper? -5. Visit our [Upskill](https://docs.flipsidecrypto.com/flipside-community/links-and-resources#upskill) and [Tutorial](https://docs.flipsidecrypto.com/resources/tutorials) collections. +5. Check out our Video Tutorials next. 6. Plan your learning & professional journey and find specialized resources using our [**Skill Tree**](https://verbena-soul-020.notion.site/Flipside-Crypto-Skill-Tree-v7-f15753bcf23f4208a421c2339f5b0a27?pvs=4). diff --git a/resources/curated-by-the-flipside-team.md b/data/data-products/data-studio-sql-analysts/tutorials/more-tools-and-resources.md similarity index 75% rename from resources/curated-by-the-flipside-team.md rename to data/data-products/data-studio-sql-analysts/tutorials/more-tools-and-resources.md index 355c052..0c7b46b 100644 --- a/resources/curated-by-the-flipside-team.md +++ b/data/data-products/data-studio-sql-analysts/tutorials/more-tools-and-resources.md @@ -1,8 +1,8 @@ --- -description: Get inform, get ahead. +description: Get informed, get ahead --- -# Curated by the Flipside Team +# More Tools & Resources ### [Flipside 101](https://flipsidecrypto.xyz/charliemarketplace/flipside-101-ll5imK) @@ -16,7 +16,7 @@ An ideal resource for beginners to grasp the basics of crypto data and the Studi An extensive library of Apps, Dashboards, Research reports, and Open Source Tools created by Flipside's data science team. -
+
*** @@ -24,7 +24,7 @@ An extensive library of Apps, Dashboards, Research reports, and Open Source Tool Check here for the latest insights and innovations from the Flipside team, as well as analyst tips and more to help you stay ahead of the Web3 curve. -
+
*** diff --git a/resources/tutorials/README.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/README.md similarity index 100% rename from resources/tutorials/README.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/README.md diff --git a/resources/tutorials/ethereum-tutorials/README.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/README.md similarity index 100% rename from resources/tutorials/ethereum-tutorials/README.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/README.md diff --git a/resources/tutorials/ethereum-tutorials/finding-centralized-exchange-deposits-and-withdrawals.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/finding-centralized-exchange-deposits-and-withdrawals.md similarity index 100% rename from resources/tutorials/ethereum-tutorials/finding-centralized-exchange-deposits-and-withdrawals.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/finding-centralized-exchange-deposits-and-withdrawals.md diff --git a/resources/tutorials/ethereum-tutorials/getting-started-with-ethereum-erc20-balances.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/getting-started-with-ethereum-erc20-balances.md similarity index 100% rename from resources/tutorials/ethereum-tutorials/getting-started-with-ethereum-erc20-balances.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/getting-started-with-ethereum-erc20-balances.md diff --git a/resources/tutorials/ethereum-tutorials/getting-started-with-ethereum-events.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/getting-started-with-ethereum-events.md similarity index 100% rename from resources/tutorials/ethereum-tutorials/getting-started-with-ethereum-events.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/getting-started-with-ethereum-events.md diff --git a/resources/tutorials/ethereum-tutorials/using-labels-to-break-down-token-supply.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/using-labels-to-break-down-token-supply.md similarity index 100% rename from resources/tutorials/ethereum-tutorials/using-labels-to-break-down-token-supply.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/ethereum-tutorials/using-labels-to-break-down-token-supply.md diff --git a/resources/tutorials/overview-of-schemas-and-tables.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/overview-of-schemas-and-tables.md similarity index 100% rename from resources/tutorials/overview-of-schemas-and-tables.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/overview-of-schemas-and-tables.md diff --git a/resources/tutorials/solana-tutorials/README.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/README.md similarity index 100% rename from resources/tutorials/solana-tutorials/README.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/README.md diff --git a/resources/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md similarity index 98% rename from resources/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md index c2a760a..32dc6eb 100644 --- a/resources/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md +++ b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/exploring-transactions-in-solana.events.md @@ -168,16 +168,13 @@ _**More Detail with Screenshots: Outline of our Marinade Staking Transaction**_ * program: Marinade Finance - MarBmsSgKXdrN1egZf5sqe1TMai9K1rChYNDJgjq7aD -![](<../../../.gitbook/assets/Untitled (1) (1)>) +![](<../../../../../../.gitbook/assets/Untitled (1) (1)>) -* instruction 1: Deposit +* instruction 1: Deposit + * inner instruction 1: Token Transfer + * inner instruction 2: SOL Transfer - * inner instruction 1: Token Transfer - * inner instruction 2: SOL Transfer - - - -![](<../../../.gitbook/assets/image (5).png>) +![](<../../../../../../.gitbook/assets/image (5).png>) So now that we understand that Solana transactions are organized into programs, instructions, and inner instructions, it’s clearer to see how our transaction’s data show up in the solana.events table. For example you’ll see a lot of the information from Solscan in this JSON from the INNER\_INSTRUCTIONS column: diff --git a/resources/tutorials/solana-tutorials/solana-schema-and-tables-video-walkthrough.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/solana-schema-and-tables-video-walkthrough.md similarity index 100% rename from resources/tutorials/solana-tutorials/solana-schema-and-tables-video-walkthrough.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/solana-schema-and-tables-video-walkthrough.md diff --git a/resources/tutorials/solana-tutorials/solana-specialty-tables-video-walkthrough.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/solana-specialty-tables-video-walkthrough.md similarity index 100% rename from resources/tutorials/solana-tutorials/solana-specialty-tables-video-walkthrough.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/solana-tutorials/solana-specialty-tables-video-walkthrough.md diff --git a/resources/tutorials/thorchain-tutorials/README.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/README.md similarity index 100% rename from resources/tutorials/thorchain-tutorials/README.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/README.md diff --git a/resources/tutorials/thorchain-tutorials/calculating-il-for-thorchain.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/calculating-il-for-thorchain.md similarity index 100% rename from resources/tutorials/thorchain-tutorials/calculating-il-for-thorchain.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/calculating-il-for-thorchain.md diff --git a/resources/tutorials/thorchain-tutorials/thorchain-schema-and-tables.md b/data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/thorchain-schema-and-tables.md similarity index 100% rename from resources/tutorials/thorchain-tutorials/thorchain-schema-and-tables.md rename to data/data-products/data-studio-sql-analysts/tutorials/tutorials/thorchain-tutorials/thorchain-schema-and-tables.md diff --git a/data/data-products/livequery/README.md b/data/data-products/livequery/README.md new file mode 100644 index 0000000..d865d06 --- /dev/null +++ b/data/data-products/livequery/README.md @@ -0,0 +1,2 @@ +# LiveQuery + diff --git a/products/get-started/add-ons/README.md b/data/data-products/livequery/add-ons/README.md similarity index 100% rename from products/get-started/add-ons/README.md rename to data/data-products/livequery/add-ons/README.md diff --git a/products/get-started/examples/README.md b/data/data-products/livequery/add-ons/examples/README.md similarity index 100% rename from products/get-started/examples/README.md rename to data/data-products/livequery/add-ons/examples/README.md diff --git a/products/get-started/examples/api-functions/README.md b/data/data-products/livequery/add-ons/examples/api-functions/README.md similarity index 100% rename from products/get-started/examples/api-functions/README.md rename to data/data-products/livequery/add-ons/examples/api-functions/README.md diff --git a/products/get-started/examples/api-functions/query-defi-llama.md b/data/data-products/livequery/add-ons/examples/api-functions/query-defi-llama.md similarity index 100% rename from products/get-started/examples/api-functions/query-defi-llama.md rename to data/data-products/livequery/add-ons/examples/api-functions/query-defi-llama.md diff --git a/products/get-started/examples/api-functions/query-thegraph.md b/data/data-products/livequery/add-ons/examples/api-functions/query-thegraph.md similarity index 100% rename from products/get-started/examples/api-functions/query-thegraph.md rename to data/data-products/livequery/add-ons/examples/api-functions/query-thegraph.md diff --git a/products/get-started/examples/evm-functions/README.md b/data/data-products/livequery/add-ons/examples/evm-functions/README.md similarity index 94% rename from products/get-started/examples/evm-functions/README.md rename to data/data-products/livequery/add-ons/examples/evm-functions/README.md index 733507e..9d12ae6 100644 --- a/products/get-started/examples/evm-functions/README.md +++ b/data/data-products/livequery/add-ons/examples/evm-functions/README.md @@ -2,14 +2,14 @@ description: High Level Functions for Querying EVM-compatible network --- -# 🧙♂ EVM Functions +# 🧙‍♂️ EVM Functions EVM functions are custom-built to query EVM-compatible networks and exist as an abstraction over Flipside's API functions. These functions are deployed on specific chain/network schemas under the `livequery` database, for example: `ethereum_mainnet` , `ethereum_goerli`, `polygon_mainnet`, etc. Flipside automatically defaults all queries to the `livequery` database so you do not need to specify the `livequery` db when writing your queries. View the full documentation within Data Studio on available functions and blockchains/networks. {% hint style="danger" %} -EVM functions require you to associate a node provider with your Flipside Account. See the [Add-Ons section](../../add-ons/) of the documentation for details on adding a node provider to your Flipside Account. +EVM functions require you to associate a node provider with your Flipside Account. See the [Add-Ons section](../../) of the documentation for details on adding a node provider to your Flipside Account. {% endhint %} {% hint style="warning" %} diff --git a/products/get-started/examples/evm-functions/general-evm-node-queries.md b/data/data-products/livequery/add-ons/examples/evm-functions/general-evm-node-queries.md similarity index 98% rename from products/get-started/examples/evm-functions/general-evm-node-queries.md rename to data/data-products/livequery/add-ons/examples/evm-functions/general-evm-node-queries.md index f1a8329..b783679 100644 --- a/products/get-started/examples/evm-functions/general-evm-node-queries.md +++ b/data/data-products/livequery/add-ons/examples/evm-functions/general-evm-node-queries.md @@ -9,7 +9,7 @@ In the following examples, we will use the available EVM primitives to make call We will start small by getting the latest block for Ethereum Mainnet. {% hint style="warning" %} -If you'd like to follow along in your own Flipside Studio Account please make sure you've added the QuickNode integration to your account. QuickNode [instructions here](../../add-ons/quicknode-setup-guide.md). +If you'd like to follow along in your own Flipside Studio Account please make sure you've added the QuickNode integration to your account. QuickNode [instructions here](../../quicknode-setup-guide.md). diff --git a/products/get-started/examples/evm-functions/seaport-real-time-orders.md b/data/data-products/livequery/add-ons/examples/evm-functions/seaport-real-time-orders.md similarity index 96% rename from products/get-started/examples/evm-functions/seaport-real-time-orders.md rename to data/data-products/livequery/add-ons/examples/evm-functions/seaport-real-time-orders.md index 8e80ed4..aebea77 100644 --- a/products/get-started/examples/evm-functions/seaport-real-time-orders.md +++ b/data/data-products/livequery/add-ons/examples/evm-functions/seaport-real-time-orders.md @@ -3,7 +3,7 @@ In this example, we'll use the LiveQuery table function `tf_latest_contract_events_decoded` to retrieve real-time orders from the Seaport contract. {% hint style="warning" %} -If you'd like to follow along in your own Flipside Studio Account please make sure you've added the QuickNode integration to your account. QuickNode [instructions here](../../add-ons/quicknode-setup-guide.md). +If you'd like to follow along in your own Flipside Studio Account please make sure you've added the QuickNode integration to your account. QuickNode [instructions here](../../quicknode-setup-guide.md). {% endhint %} Here we will query the Seaport Version 1.5 Contract on the Ethereum Mainnet, address: [`0x00000000000000ADc04C56Bf30aC9d3c0aAF14dC`](https://etherscan.io/address/0x00000000000000ADc04C56Bf30aC9d3c0aAF14dC#events) diff --git a/products/get-started/examples/evm-functions/weth-pool-balances.md b/data/data-products/livequery/add-ons/examples/evm-functions/weth-pool-balances.md similarity index 97% rename from products/get-started/examples/evm-functions/weth-pool-balances.md rename to data/data-products/livequery/add-ons/examples/evm-functions/weth-pool-balances.md index 8e288bb..030e641 100644 --- a/products/get-started/examples/evm-functions/weth-pool-balances.md +++ b/data/data-products/livequery/add-ons/examples/evm-functions/weth-pool-balances.md @@ -3,7 +3,7 @@ In this example, we'll use the LiveQuery table function `tf_latest_token_balance` to retrieve the real-time balance of Uniswap Pools. {% hint style="warning" %} -If you'd like to follow along in your own Flipside Studio Account please make sure you've added the QuickNode integration to your account. QuickNode [instructions here](../../add-ons/quicknode-setup-guide.md). +If you'd like to follow along in your own Flipside Studio Account please make sure you've added the QuickNode integration to your account. QuickNode [instructions here](../../quicknode-setup-guide.md). {% endhint %} Let's start with a simple example, retrieve the balance of WETH and USDC on the WETH/USDC pool. diff --git a/products/get-started/examples/partner-functions.md b/data/data-products/livequery/add-ons/examples/partner-functions.md similarity index 100% rename from products/get-started/examples/partner-functions.md rename to data/data-products/livequery/add-ons/examples/partner-functions.md diff --git a/products/get-started/examples/utility-functions/README.md b/data/data-products/livequery/add-ons/examples/utility-functions/README.md similarity index 100% rename from products/get-started/examples/utility-functions/README.md rename to data/data-products/livequery/add-ons/examples/utility-functions/README.md diff --git a/products/get-started/examples/utility-functions/evm-logs-decoder.md b/data/data-products/livequery/add-ons/examples/utility-functions/evm-logs-decoder.md similarity index 100% rename from products/get-started/examples/utility-functions/evm-logs-decoder.md rename to data/data-products/livequery/add-ons/examples/utility-functions/evm-logs-decoder.md diff --git a/products/get-started/examples/utility-functions/hex-converters.md b/data/data-products/livequery/add-ons/examples/utility-functions/hex-converters.md similarity index 100% rename from products/get-started/examples/utility-functions/hex-converters.md rename to data/data-products/livequery/add-ons/examples/utility-functions/hex-converters.md diff --git a/products/get-started/examples/utility-functions/json-rpc-request-builder.md b/data/data-products/livequery/add-ons/examples/utility-functions/json-rpc-request-builder.md similarity index 100% rename from products/get-started/examples/utility-functions/json-rpc-request-builder.md rename to data/data-products/livequery/add-ons/examples/utility-functions/json-rpc-request-builder.md diff --git a/products/get-started/examples/utility-functions/keccak256-encoder.md b/data/data-products/livequery/add-ons/examples/utility-functions/keccak256-encoder.md similarity index 100% rename from products/get-started/examples/utility-functions/keccak256-encoder.md rename to data/data-products/livequery/add-ons/examples/utility-functions/keccak256-encoder.md diff --git a/products/get-started/add-ons/quicknode-setup-guide.md b/data/data-products/livequery/add-ons/quicknode-setup-guide.md similarity index 97% rename from products/get-started/add-ons/quicknode-setup-guide.md rename to data/data-products/livequery/add-ons/quicknode-setup-guide.md index 18237d5..a26ab86 100644 --- a/products/get-started/add-ons/quicknode-setup-guide.md +++ b/data/data-products/livequery/add-ons/quicknode-setup-guide.md @@ -2,7 +2,7 @@ description: Connect your QuickNode account to query the blockchain using LiveQuery --- -# ⛓ QuickNode Setup Guide +# QuickNode Setup Guide Flipside has partnered with QuickNode to enable QuickNode users to securely connect and share their node credentials to use with LiveQuery. diff --git a/data/data-products/livequery/get-inspired.md b/data/data-products/livequery/get-inspired.md new file mode 100644 index 0000000..708c7c7 --- /dev/null +++ b/data/data-products/livequery/get-inspired.md @@ -0,0 +1,3 @@ +# Get Inspired + +Many dashboards are built with LiveQuery - find them on our [Insights page](https://flipsidecrypto.xyz/insights/dashboards)! diff --git a/products/get-started/README.md b/data/data-products/livequery/get-started.md similarity index 66% rename from products/get-started/README.md rename to data/data-products/livequery/get-started.md index 131c8de..ecc8755 100644 --- a/products/get-started/README.md +++ b/data/data-products/livequery/get-started.md @@ -2,7 +2,7 @@ description: Query external APIs, combine with Flipside data, directly in SQL --- -# LiveQuery +# Get Started **LiveQuery enables you to query any API directly within a Flipside SQL Query, from nodes to your favorite crypto data providers.** @@ -18,12 +18,12 @@ If you're already writing SQL at Flipside you already have access to the power o ## Examples -
Seaport: Real-time OrdersRetrieve the latest Seaport Orders directly from an Ethereum Node.seaport-real-time-orders.md
WETH Pool BalancesRetrieve the real-time WETH balance for the top WETH pools by volume over the past 1 week. weth-pool-balances.md
Query TheGraphRetrieve the TVL for the top 500 UniswapV3 Pools on Polygon using LiveQuery and TheGraphgeneral-evm-node-queries.md
+
Seaport: Real-time OrdersRetrieve the latest Seaport Orders directly from an Ethereum Node.seaport-real-time-orders.md
WETH Pool BalancesRetrieve the real-time WETH balance for the top WETH pools by volume over the past 1 week. weth-pool-balances.md
Query TheGraphRetrieve the TVL for the top 500 UniswapV3 Pools on Polygon using LiveQuery and TheGraphgeneral-evm-node-queries.md
Check out more examples here: -{% content-ref url="examples/" %} -[examples](examples/) +{% content-ref url="add-ons/examples/" %} +[examples](add-ons/examples/) {% endcontent-ref %} ## Add-On Setup Guides @@ -36,7 +36,7 @@ Add-Ons provide a secure means of incorporating your API keys for third-party da [quicknode-setup-guide.md](add-ons/quicknode-setup-guide.md) {% endcontent-ref %} -We're excited to announce that additional third-party cryptocurrency data add-ons are on the horizon! Until then, explore our detailed, [step-by-step examples](examples/) **or** [link your QuickNode account](add-ons/quicknode-setup-guide.md) to use LiveQuery for querying blockchain nodes. +We're excited to announce that additional third-party cryptocurrency data add-ons are on the horizon! Until then, explore our detailed, [step-by-step examples](add-ons/examples/) **or** [link your QuickNode account](add-ons/quicknode-setup-guide.md) to use LiveQuery for querying blockchain nodes. {% hint style="danger" %} Note if you publish a dashboard that contains LiveQuery-powered queries users that refresh your dashboard will trigger queries against the Add-ons you have integrated. diff --git a/products/get-started/secrets-manager.md b/data/data-products/livequery/secrets-manager.md similarity index 91% rename from products/get-started/secrets-manager.md rename to data/data-products/livequery/secrets-manager.md index f142a7b..7caf22b 100644 --- a/products/get-started/secrets-manager.md +++ b/data/data-products/livequery/secrets-manager.md @@ -10,7 +10,7 @@ description: >- Start by creating a container that corresponds with the API you want to use and then populate key/value pairs within it -
+
### 2. Reference your secret\_name diff --git a/data/data-products/snowflake.md b/data/data-products/snowflake.md new file mode 100644 index 0000000..85ea8c5 --- /dev/null +++ b/data/data-products/snowflake.md @@ -0,0 +1,3 @@ +# Snowflake + +### [**Get started with Snowflake with your Flipside Pro account**](https://docs.flipsidecrypto.xyz/welcome-to-flipside/data/choose-your-flipside-plan/pro/get-started-in-snowflake) diff --git a/data/flipside-data/README.md b/data/flipside-data/README.md index 8fde2b0..4633043 100644 --- a/data/flipside-data/README.md +++ b/data/flipside-data/README.md @@ -1,2 +1,8 @@ +--- +description: >- + What you will find in our data tables, how they are modeled and organized, how + frequently they update, and how you can contribute +--- + # Flipside Data diff --git a/data/contribute-to-our-data/README.md b/data/flipside-data/contribute-to-our-data/README.md similarity index 100% rename from data/contribute-to-our-data/README.md rename to data/flipside-data/contribute-to-our-data/README.md diff --git a/data/contribute-to-our-data/contract-decoding-and-abis.md b/data/flipside-data/contribute-to-our-data/contract-decoding-and-abis.md similarity index 100% rename from data/contribute-to-our-data/contract-decoding-and-abis.md rename to data/flipside-data/contribute-to-our-data/contract-decoding-and-abis.md diff --git a/data/contribute-to-our-data/contribute-to-flipside-data/README.md b/data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/README.md similarity index 100% rename from data/contribute-to-our-data/contribute-to-flipside-data/README.md rename to data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/README.md diff --git a/data/contribute-to-our-data/contribute-to-flipside-data/getting-started/README.md b/data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/getting-started/README.md similarity index 100% rename from data/contribute-to-our-data/contribute-to-flipside-data/getting-started/README.md rename to data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/getting-started/README.md diff --git a/data/contribute-to-our-data/contribute-to-flipside-data/getting-started/contribution-workflow.md b/data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/getting-started/contribution-workflow.md similarity index 100% rename from data/contribute-to-our-data/contribute-to-flipside-data/getting-started/contribution-workflow.md rename to data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/getting-started/contribution-workflow.md diff --git a/data/contribute-to-our-data/contribute-to-flipside-data/model-standards/README.md b/data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/model-standards/README.md similarity index 100% rename from data/contribute-to-our-data/contribute-to-flipside-data/model-standards/README.md rename to data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/model-standards/README.md diff --git a/data/contribute-to-our-data/contribute-to-flipside-data/model-standards/dbt-tips.md b/data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/model-standards/dbt-tips.md similarity index 100% rename from data/contribute-to-our-data/contribute-to-flipside-data/model-standards/dbt-tips.md rename to data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/model-standards/dbt-tips.md diff --git a/data/contribute-to-our-data/contribute-to-flipside-data/pr-checklist.md b/data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/pr-checklist.md similarity index 100% rename from data/contribute-to-our-data/contribute-to-flipside-data/pr-checklist.md rename to data/flipside-data/contribute-to-our-data/contribute-to-flipside-data/pr-checklist.md diff --git a/data/contribute-to-our-data/how-to-add-your-own-tags.md b/data/flipside-data/contribute-to-our-data/how-to-add-your-own-tags.md similarity index 97% rename from data/contribute-to-our-data/how-to-add-your-own-tags.md rename to data/flipside-data/contribute-to-our-data/how-to-add-your-own-tags.md index 732a721..89745c5 100644 --- a/data/contribute-to-our-data/how-to-add-your-own-tags.md +++ b/data/flipside-data/contribute-to-our-data/how-to-add-your-own-tags.md @@ -2,7 +2,7 @@ Tags identify traits or behaviors that belong to an address. -For a table of all tagged addresses see [the Crosschain schema](../archive/tables/crosschain-tables/crosschain-address-tags.md). +For a table of all tagged addresses see [the Crosschain schema](broken-reference). Do you often copy/paste lists of addresses into your queries? Tags are for you. Tags can be specific and provable, e.g. "OpenSea user", or simply a tool to group addresses and clean up your code. @@ -37,7 +37,7 @@ Using tag_\__type you can pull all celebrities tagged by the Flipside community, ## The tags table -The data for our tags is stored in the data table: [crosschain.core.address\_tags](../archive/tables/crosschain-tables/crosschain-address-tags.md). \ +The data for our tags is stored in the data table: [crosschain.core.address\_tags](broken-reference). \ | Column Name | Data type | Description | diff --git a/data/flipside-data/data-table-documentation.md b/data/flipside-data/data-table-documentation.md index 603fcd5..ca11ffc 100644 --- a/data/flipside-data/data-table-documentation.md +++ b/data/flipside-data/data-table-documentation.md @@ -1,10 +1,10 @@ --- -description: Looking for specific database, schema, and table details? Look no further. +description: Looking for specific database, schema, and table details? Look no further --- -# DBT docs by chain +# Table Docs by Chain -Our data documentation is kept up to date _as changes are deployed_, so check here for the very latest details on each of our covered chains: +Our DBT data documentation is kept up to date _as changes are deployed_, so check here for the very latest details on each of our covered chains: * [Aptos](https://flipsidecrypto.github.io/aptos-models/#!/overview) * [Arbitrum](https://flipsidecrypto.github.io/arbitrum-models/#!/overview) @@ -16,7 +16,7 @@ Our data documentation is kept up to date _as changes are deployed_, so check he * [Binance Smart Chain](https://flipsidecrypto.github.io/bsc-models/#!/overview) * [Blast](https://flipsidecrypto.github.io/blast-models/#!/overview) * [Cosmos](https://flipsidecrypto.github.io/cosmos-models/#!/overview) -* Crosschain Data +* [Crosschain Data](https://flipsidecrypto.github.io/crosschain-models/#!/overview) * [Ethereum](https://flipsidecrypto.github.io/ethereum-models/#!/overview) * [Flow](https://flipsidecrypto.github.io/flow-models/#!/overview) * [Gnosis](https://flipsidecrypto.github.io/gnosis-models/#!/overview) @@ -27,5 +27,5 @@ Our data documentation is kept up to date _as changes are deployed_, so check he * [Sei](https://flipsidecrypto.github.io/sei-models/#!/overview) * [Solana](https://flipsidecrypto.github.io/solana-models/#!/overview) * [Terra](https://metricsdao.github.io/terra\_dbt/#!/overview) -* Thorchain +* [Thorchain](https://flipsidecrypto.github.io/thorchain-models/#!/overview) diff --git a/data/flipside-data/featured-tags-and-sql-examples.md b/data/flipside-data/featured-tags-and-sql-examples.md index 04ac0b4..094a758 100644 --- a/data/flipside-data/featured-tags-and-sql-examples.md +++ b/data/flipside-data/featured-tags-and-sql-examples.md @@ -10,9 +10,9 @@ Tags can be specific and provable, e.g. "OpenSea user", or simply a tool to grou Check back often as our list of tags is constantly being updated! -[`crosschain.core.address_tags` table docs](../archive/tables/crosschain-tables/crosschain-address-tags.md)\ +[`crosschain.core.address_tags` table docs](broken-reference)\ \ -Don't see the perfect tag? [Add your own! ](../contribute-to-our-data/how-to-add-your-own-tags.md#how-to-add-tags) +Don't see the perfect tag? [Add your own! ](contribute-to-our-data/how-to-add-your-own-tags.md#how-to-add-tags) diff --git a/data/flipside-data/labels/README.md b/data/flipside-data/labels/README.md index 519c257..852b018 100644 --- a/data/flipside-data/labels/README.md +++ b/data/flipside-data/labels/README.md @@ -30,7 +30,7 @@ There are 10 label types within any blockchain. 10. [**token** (Token Contracts)](token-label-type.md) 11. [**flotsam** (Junk or Other)](flotsam-label-type.md) -See [the Crosschain schema](../../archive/tables/crosschain-tables/crosschain-address-labels.md) for the table containing all labeled addresses. +See [the Crosschain schema](broken-reference) for the table containing all labeled addresses. Flipside applies a 2-level hierarchy to all labeled addresses using 4 field attributes. diff --git a/data/flipside-data/table-freshness-targets.md b/data/flipside-data/table-freshness-targets.md index a3ca03a..bec29f1 100644 --- a/data/flipside-data/table-freshness-targets.md +++ b/data/flipside-data/table-freshness-targets.md @@ -1,12 +1,8 @@ ---- -description: The following can be tuned/adjusted. ---- - # Table Freshness Targets Flipside's tables target the following latency schedule from Chain Head. The following can be tuned based on use cases/needs. Please reach out if you have a specific use case that requires a latency closer to the chain head and our team would be happy to discuss solutions with you. -Flipside refreshes data across three dimensions fact tables, dim tables, and ez tables. +Flipside refreshes data across three dimensions: `fact` tables, `dim` tables, and `ez` tables. | Blockchain | Category | Target Latency from Chain Head | | ---------- | ------------- | ------------------------------ | diff --git a/data/insights-and-tools.md b/data/insights-and-tools.md new file mode 100644 index 0000000..2eb0d1f --- /dev/null +++ b/data/insights-and-tools.md @@ -0,0 +1,12 @@ +--- +description: >- + Get inspired by these examples of research and insights reports, dashboards, + and tools you can create with our data +--- + +# Insights and Tools + +* [Research and reports](https://flipsidecrypto.xyz/fc/resources?category=research-and-reports) +* [Dashboards](https://flipsidecrypto.xyz/insights/dashboards) +* [Tools](https://science.flipsidecrypto.xyz/research/) + * [BONK Burn Tool](https://science.flipsidecrypto.xyz/bonk-burns/) diff --git a/flipside-community/ambassador-program.md b/flipside-community/ambassador-program.md index 1b98897..37b05b8 100644 --- a/flipside-community/ambassador-program.md +++ b/flipside-community/ambassador-program.md @@ -1,9 +1,9 @@ +--- +description: What’s involved? What’s expected? What’s in it for me? +--- + # Ambassador Program -## Flipside Ambassador Program - -_What’s involved? What’s expected? What’s in it for me?_ - ### Executive Summary * The Ambassador program creates the best analysts in crypto: the small handful of data experts & storytellers who become _the_ analytics leaders in their selected ecosystems diff --git a/flipside-community/get-started (1).md b/flipside-community/get-started (1).md new file mode 100644 index 0000000..93fc61d --- /dev/null +++ b/flipside-community/get-started (1).md @@ -0,0 +1,53 @@ +--- +description: Everything you need to get started in our community. +--- + +# Community + +Welcome to the Flipside community! In addition to offering some of the most reliable and comprehensive blockchain data, Flipside provides community spaces and tools to help you work and learn alongside other analysts and web3 experts. + +This page will help you get started in our community. + +*** + +**TL;DR: Want to get started in our community quickly? Simply follow these steps.** + +1. **Join us on** [**Discord**](https://discord.gg/flipside)**.** +2. **Sign up for your** [**Flipside Data Studio**](https://flipsidecrypto.xyz/edit) **account.** + * **Are you looking for enterprise data?** [**Try a Flipside Pro free trial.**](https://data.flipsidecrypto.com/) +3. [**Introduce yourself**](https://discord.com/channels/784442203187314689/1001866283781984286) **in Discord and show off your work.** +4. **Need help? Check out these** [**Discord channels**](../support/support.md) **or learn how to**[ **open a ticket**](../support/open-a-ticket.md)**.** +5. **All done!** + +*** + +### 1. Join us on [Discord](https://discord.gg/flipside). + +Discord is the best place to get the newest updates on analyst rewards, Flipside announcements, educational content, and to connect with your fellow analysts. Our Discord members are some of the first to know about new opportunities to earn and learn. + +Once you've joined us on Discord, make sure to check out these channels. + +* [Help-FAQ](https://discord.com/channels/784442203187314689/1166830352459907126) channel to know what resources are available to you. +* [Start-Here](https://discord.com/channels/784442203187314689/1166858825882677278) channel for info on how to get involved in the community. + +### 2. Sign up for your [Flipside Data Studio](https://flipsidecrypto.xyz/) account. + +[Flipside Data Studio](https://flipsidecrypto.xyz/) lets you analyze blockchain data, visualize it, and share dashboards instantly. It's ideal for data exploration, analytical storytelling, and comprehensive dashboard-building. It's one of the main tools our community members use to share data, earn, and learn. + +Click the Sign Up button in the top right corner of our [website](https://flipsidecrypto.xyz/) to create your account. If you need step by step help creating an account and getting started in Data Studio, check out our [app documentation](https://docs.flipsidecrypto.xyz/products/data-studio-sql-analysts). + +You can also create a team account to collaborate with your team in real time. + +#### 2a. If you want enterprise data, sign up for your [Flipside Pro free trial](https://data.flipsidecrypto.com/). + +For those who need a more robust option, Flipside offers a professional web3 intelligence toolkit for everyone from protocol builders to enterprises looking to break into Web3. We’ve got everything you need to get informed and get ahead. + +### 3. [Introduce yourself](https://discord.com/channels/784442203187314689/1001866283781984286) in Discord and show off your work! + +Take a minute and introduce yourself within our Discord community. It's a great way to meet Flipside's official Community Team and your fellow analysts. + +Here are some channels you can use to start chatting. + +* [Introductions](https://discord.com/channels/784442203187314689/1001866283781984286) channel. +* [General](https://discord.com/channels/784442203187314689/826928846670135306) chat. + diff --git a/flipside-community/get-started.md b/flipside-community/get-started.md index aac300a..54be281 100644 --- a/flipside-community/get-started.md +++ b/flipside-community/get-started.md @@ -1,51 +1,3 @@ ---- -description: Everything you need to get started in our community. ---- - -# Community - -Welcome to the Flipside Crypto community! In addition to offering some of the most reliable and comprehensive blockchain data, Flipside Crypto provides community spaces and tools to help you work and learn alongside other analysts and web3 experts. - -This page will help you get started in our community. - -*** - -**TL;DR: Want to get started in our community quickly? Simply follow these steps.** - -1. **Join us on** [**Discord**](https://discord.gg/flipside)**.** -2. **Sign up for your** [**Flipside Data Studio**](https://flipsidecrypto.xyz/edit) **account.** - * **Are you looking for enterprise data?** [**Try a Flipside Pro free trial.**](https://data.flipsidecrypto.com/) -3. [**Introduce yourself**](https://discord.com/channels/784442203187314689/1001866283781984286) **in Discord and show off your work.** -4. **Need help? Check out these** [**Discord channels**](../support/support.md) **or learn how to**[ **open a ticket**](../support/open-a-ticket.md)**.** -5. **All done!** - -*** - -### 1. Join us on [Discord](https://discord.gg/flipside). - -Discord is the best place to get the newest updates on analyst rewards, Flipside announcements, educational content, and to connect with your fellow analysts. Our Discord members are some of the first to know about new opportunities to earn and learn. - -Once you've joined us on Discord, make sure to check out these channels. - -* [Help-FAQ](https://discord.com/channels/784442203187314689/1166830352459907126) channel to know what resources are available to you. -* [Start-Here](https://discord.com/channels/784442203187314689/1166858825882677278) channel for info on how to get involved in the community. - -### 2. Sign up for your [Flipside Data Studio](https://flipsidecrypto.xyz/) account. - -[Flipside Data Studio](https://flipsidecrypto.xyz/) lets you analyze blockchain data, visualize it, and share dashboards instantly. It's ideal for data exploration, analytical storytelling, and comprehensive dashboard-building. It's one of the main tools our community members use to share data, earn, and learn. - -Click the Sign Up button in the top right corner of our [website](https://flipsidecrypto.xyz/) to create your account. If you need step by step help creating an account and getting started in Data Studio, check out our [app documentation](https://docs.flipsidecrypto.xyz/products/data-studio-sql-analysts). - -#### 2a. If you want enterprise data, sign up for your [Flipside Pro free trial](https://data.flipsidecrypto.com/). - -For those who need a more robust option, Flipside offers a professional web3 intelligence toolkit for everyone from protocol builders to enterprises looking to break into Web3. We’ve got everything you need to get informed and get ahead. - -### 3. [Introduce yourself](https://discord.com/channels/784442203187314689/1001866283781984286) in Discord and show off your work! - -Take a minute and introduce yourself within our Discord community. It's a great way to meet Flipside's official Community Team and your fellow analysts. - -Here are some channels you can use to start chatting. - -* [Introductions](https://discord.com/channels/784442203187314689/1001866283781984286) channel. -* [General](https://discord.com/channels/784442203187314689/826928846670135306) chat. +# Get Started +### [Get started in our community of blockchain data analysts, builders, data-driven projects, and enthusiasts.](https://docs.flipsidecrypto.xyz/welcome-to-flipside/flipside-community-overview) diff --git a/flipside-community/links-and-resources.md b/flipside-community/links-and-resources.md deleted file mode 100644 index dcd86a2..0000000 --- a/flipside-community/links-and-resources.md +++ /dev/null @@ -1,22 +0,0 @@ -# Links & Resources - -## **Get Inspired** - -* [Trending dashboards](https://flipsidecrypto.xyz/discover) - -## Participate - -* [Access free data and make dashboards](https://flipsidecrypto.xyz/edit) -* [Are you looking for enterprise level data? Check out Flipside Pro.](https://data.flipsidecrypto.com/) - -## **Upskill** - -* [Snowflake SQL (the SQL on the Flipside data app)](https://docs.snowflake.com/) -* Free blockchain data analytics courses at MetricsDAO: - * [https://docs.metricsdao.xyz/education/education-overview](https://docs.metricsdao.xyz/education/education-overview) - * [Data tutorials by @sam](https://www.youtube.com/watch?v=7WCo41zdxAI\&list=PLkVNGrM4Ij2xAyu3EyDBDGFSuNLHVXphu) - -## **Connect With Us** - -* [Follow us on X (Twitter) ](https://twitter.com/flipsidecrypto) -* [Subscribe to our YouTube channel ](https://www.youtube.com/@Official\_Flipside) diff --git a/products/data-studio-sql-analysts/get-started/browse-dashboards.md b/products/data-studio-sql-analysts/get-started/browse-dashboards.md deleted file mode 100644 index 8675f73..0000000 --- a/products/data-studio-sql-analysts/get-started/browse-dashboards.md +++ /dev/null @@ -1,49 +0,0 @@ ---- -description: Find insights & query inspiration with community boards ---- - -# Browse dashboards - - - -More than 60,000 analysts have published over 100,000 dashboards covering 26 protocols so far. - -If you're looking for onchain insights, chances are you can find a board on the topic you're interested in! Maybe it contains the insights you're looking for, or maybe you can fork one of its queries to help you get started on your own dashboard. - -Either way, the process is easy! - -1. [Visit the Discover page ](browse-dashboards.md#id-1.-visit-the-discover-page) -2. [Search for any topic](browse-dashboards.md#id-2.-search-for-any-topic) -3. [Enjoy your insights ](browse-dashboards.md#id-3.-enjoy-your-insights) - -*** - - - -### 1. Visit the Discover page - -Head to [flipsidecrypto.xyz/discover](https://flipsidecrypto.xyz/discover) or click the "discover more" button from the home page. - -_(You'll see trending dashboards from the home page, and can filter by chain, but you'll be able to search all dashboards from the Discover page.)_ - -
- -*** - -### 2. Search for any topic - -Keyword search will find any topic represented in one of more than 100k dashboards. - -Using the drop-downs on the right side of the page, you can also filter by protocol, date, popularity, or even by boards you've liked previously. - -
- -*** - -### 3. Enjoy your insights! - -_**Tip:** Click a chart's title to see the query you can use to get the same data!_ - -
- -You've just taken the first step of DYOR. Endless trends await! Keep reading to learn how to navigate the Flipside database and use the SQL editor to query it. diff --git a/welcome-to-flipside/data/README.md b/welcome-to-flipside/data/README.md index 8d2f593..4c2703e 100644 --- a/welcome-to-flipside/data/README.md +++ b/welcome-to-flipside/data/README.md @@ -25,12 +25,12 @@ Want Flipside's entire database in your stack? We can do that. Just [reach out]( ### Important Things to Know -* All our data is accessible via SQL queries, and you'll use the [Snowflake SQL](../../products/data-studio-sql-analysts/query-editor/using-snowflake-sql.md) dialect to access it. -* Our core app is brand new (launched Feb 2023) and some [documentation](../../products/data-studio-sql-analysts/) is available — we're actively building this out, including both text and video content — if you have questions that aren't answered here, please reach out in [Discord](https://discord.gg/ZmU3jQuu6W). +* All our data is accessible via SQL queries, and you'll use the [Snowflake SQL](../../data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/using-snowflake-sql.md) dialect to access it. +* Our core app is brand new (launched Feb 2023) and some [documentation](../../data/data-products/data-studio-sql-analysts/) is available — we're actively building this out, including both text and video content — if you have questions that aren't answered here, please reach out in [Discord](https://discord.gg/ZmU3jQuu6W). * Our data structures are and designed for ease of use and efficient querying, and are [extensively documented](../../data/flipside-data/data-table-documentation.md). We regularly update our data structures to optimize efficiency. * Latency varies from table to table, but typically lags either 1 hour or 1 day at most. [Here's our latency targets for each blockchain](https://docs.flipsidecrypto.xyz/data/flipside-data/table-freshness-targets). -* If you run into difficulty getting your queries to run, we provide [a guide for efficient query writing](../../products/data-studio-sql-analysts/query-editor/writing-efficient-queries.md). Need more assistance? Get help anytime in our [Discord](https://discord.gg/ZmU3jQuu6W). -* Learn more about [contract decoding](../../data/contribute-to-our-data/contract-decoding-and-abis.md), and adding ABIs. +* If you run into difficulty getting your queries to run, we provide [a guide for efficient query writing](../../data/data-products/data-studio-sql-analysts/studio-in-depth/query-editor/writing-efficient-queries.md). Need more assistance? Get help anytime in our [Discord](https://discord.gg/ZmU3jQuu6W). +* Learn more about [contract decoding](../../data/flipside-data/contribute-to-our-data/contract-decoding-and-abis.md), and adding ABIs. ### What blockchains and projects does Flipside have data on? diff --git a/welcome-to-flipside/earn.md b/welcome-to-flipside/earn.md index d968413..2ab74ea 100644 --- a/welcome-to-flipside/earn.md +++ b/welcome-to-flipside/earn.md @@ -18,3 +18,5 @@ We’re dedicated to paying analysts, not charging them. Build your brand while * [Top Dashboards](../earn/analyst-rewards/top-dashboards/) * [Ambassador Program ](../earn/analyst-rewards/ambassador-program.md) * [Direct to Analyst Commissions](../earn/analyst-rewards/direct-to-analyst-commissions.md) + +[**Sign up**](https://flipsidecrypto.xyz/) **for free to participate in Earn programs**