flip/gitbook
1
0
Fork 0
mirror of https://github.com/FlipsideCrypto/gitbook.git synced 2026-02-06 10:47:06 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

GITBOOK-565: Data, Resources, Community sections reorg.

Browse Source
This commit is contained in:
Elise Contas 2024-07-16 18:13:15 +00:00 committed by gitbook-bot
parent 0ad09dde59
commit cc5791ba79
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
277 changed files with 296 additions and 4917 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -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](<flipside-community/get-started (1).md>)
Join the thousands of crypto analysts building on Flipside.

354
SUMMARY.md
View File

@ -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](<flipside-community/get-started (1).md>)
## Data&#x20;
* [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)

4
choose-your-flipside-plan/free.md
View File

@ -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.

7
data/archive/README.md
View File

@ -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!

7
data/archive/algorand-tutorials.md
View File

@ -1,7 +0,0 @@
---
description: '[Legacy Documentation, Not Maintained, For Reference Only]'
---
# Algorand Tutorials
{% embed url="https://www.youtube.com/watch?v=WOsrxrcdy88" %}

18
data/archive/data-roadmap.md
View File

@ -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.&#x20;
| Blockchains |
| ----------- |
| EVMOS |
| dxdy |
| Bitcoin |
| Fantom |
| Stride |
| Juno |
| Sei |
| Sui |

45
data/archive/data-updates.md
View File

@ -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.**&#x20;
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.&#x20;
### **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.&#x20;
### **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.&#x20;
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.&#x20;
Timeline:\
\- April 18, 2022 - Eth Week! New Schema exposed for all users. All bounties will have to use ethereum\_core schema.\
\

43
data/archive/tables/README.md
View File

@ -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 --**&#x20;
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.&#x20;
{% endhint %}

81
data/archive/tables/aave-tables/README.md
View File

@ -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.&#x20;
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 %}

30
data/archive/tables/aave-tables/borrows.md
View File

@ -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) |

26
data/archive/tables/aave-tables/deposits.md
View File

@ -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) |

32
data/archive/tables/aave-tables/flashloans.md
View File

@ -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) |

33
data/archive/tables/aave-tables/liquidations.md
View File

@ -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) |

40
data/archive/tables/aave-tables/market-stats.md
View File

@ -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.

23
data/archive/tables/aave-tables/proposals.md
View File

@ -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) |

30
data/archive/tables/aave-tables/repayments.md
View File

@ -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) |

20
data/archive/tables/aave-tables/votes.md
View File

@ -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) |

28
data/archive/tables/aave-tables/withdraws.md
View File

@ -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) |

16
data/archive/tables/algorand-tables/README.md
View File

@ -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" %}

7
data/archive/tables/algorand-tables/algorand-base-tables/README.md
View File

@ -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.

14
data/archive/tables/algorand-tables/algorand-base-tables/account-app.md
View File

@ -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 |

16
data/archive/tables/algorand-tables/algorand-base-tables/account-asset.md
View File

@ -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. |

18
data/archive/tables/algorand-tables/algorand-base-tables/account.md
View File

@ -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 |

15
data/archive/tables/algorand-tables/algorand-base-tables/app.md
View File

@ -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 | |

24
data/archive/tables/algorand-tables/algorand-base-tables/application-call-transaction.md
View File

@ -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)&#x20;
## 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.&#x20;
| 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 |

25
data/archive/tables/algorand-tables/algorand-base-tables/asset-configuration-transaction.md
View File

@ -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.&#x20;
| 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 |

25
data/archive/tables/algorand-tables/algorand-base-tables/asset-freeze-transaction.md
View File

@ -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.&#x20;
| 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 |

27
data/archive/tables/algorand-tables/algorand-base-tables/asset-transfer-transaction.md
View File

@ -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.&#x20;
| 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 |

17
data/archive/tables/algorand-tables/algorand-base-tables/asset.md
View File

@ -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 |

16
data/archive/tables/algorand-tables/algorand-base-tables/block.md
View File

@ -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 |

13
data/archive/tables/algorand-tables/algorand-base-tables/daily-balances.md
View File

@ -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 |

28
data/archive/tables/algorand-tables/algorand-base-tables/key-registration-transaction.md
View File

@ -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.&#x20;
| 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 |

25
data/archive/tables/algorand-tables/algorand-base-tables/payment-transaction.md
View File

@ -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.&#x20;
| 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 |

5
data/archive/tables/algorand-tables/algorand-base-tables/prices-pool-balances.md
View File

@ -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
<table><thead><tr><th>Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td>BLOCK_HOUR</td><td>timestamp</td><td>The hour for which the price is valid</td></tr><tr><td>ASSET_ID</td><td>numeric</td><td>ID associated with the asset</td></tr><tr><td>ASSET_NAME</td><td>string</td><td>Name of the asset</td></tr><tr><td>PRICE_USD</td><td>numeric</td><td>The USD price of the asset at the end of the hour. ALGO price pulled from coinmarketcap/coingiecko</td></tr><tr><td>ALGO_BALANCE</td><td>numeric</td><td>The balance of ALGO tokens in the pool at the end of the hour. NULL for ALGO</td></tr><tr><td>NON_ALGO_BALANCE</td><td>numeric</td><td>The balance of other (non-ALGO) tokens in the pool at the end of the hour. NULL for ALGO</td></tr><tr><td>POOL_NAME</td><td>string</td><td>The name of the pool used for the price calculation. NULL for ALGO</td></tr><tr><td>POOL_ADDRESS</td><td>string</td><td>The address of the pool used for the price calculation. NULL for ALGO</td></tr></tbody></table>

7
data/archive/tables/algorand-tables/algorand-base-tables/prices-swap.md
View File

@ -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.
<table><thead><tr><th>Field</th><th width="150">Type</th><th>Description</th></tr></thead><tbody><tr><td>BLOCK_HOUR</td><td>timestamp</td><td>The hour for which the price is valid</td></tr><tr><td>ASSET_ID</td><td>numeric</td><td>ID associated with the asset</td></tr><tr><td>ASSET_NAME</td><td>string</td><td>Name of the asset</td></tr><tr><td>PRICE_USD</td><td>numeric</td><td>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.</td></tr><tr><td>MIN_PRICE_USD_HOUR</td><td>numeric</td><td>The lowest price found in a swap in the hour in USD</td></tr><tr><td>MAX_PRICE_USD_HOUR</td><td>numeric</td><td>The highest price found in a swap in the hour in USD</td></tr><tr><td>VOLATILITY_MEASURE</td><td>numeric</td><td>The difference between the min and max price for the hour</td></tr><tr><td>SWAPS_IN_HOUR</td><td>integer</td><td>The number of swap transactions in the hour that involved this asset</td></tr><tr><td>VOLUME_USD_IN_HOUR</td><td>numeric</td><td>The volume of swap transactions (in USD) in the hour for this asset</td></tr></tbody></table>

19
data/archive/tables/algorand-tables/algorand-base-tables/swaps.md
View File

@ -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 |

12
data/archive/tables/algorand-tables/algorand-base-tables/transactions-participation.md
View File

@ -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 |

25
data/archive/tables/algorand-tables/algorand-base-tables/transactions.md
View File

@ -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) .&#x20;
## 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.&#x20;
| 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 |

32
data/archive/tables/algorand-tables/algorand-base-tables/transfers.md
View File

@ -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.&#x20;
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.&#x20;
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 |

31
data/archive/tables/algorand-tables/core-tables.md
View File

@ -1,31 +0,0 @@
# Core Tables
Documentation for Core tables can be found [here](https://flipsidecrypto.github.io/algorand-models/#!/overview).&#x20;
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:
<figure><img src="../../../../.gitbook/assets/Algorand - FACT- DIM (1).png" alt=""><figcaption></figcaption></figure>
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)

34
data/archive/tables/arbitrum-tables.md
View File

@ -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)`.&#x20;
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).

10
data/archive/tables/astroport-tables/README.md
View File

@ -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.&#x20;
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."

9
data/archive/tables/astroport-tables/lp-actions.md
View File

@ -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.&#x20;
<table data-header-hidden><thead><tr><th width="227.33333333333331">Field</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>Field</td><td>Type</td><td>Description</td></tr><tr><td><code>blockchain</code></td><td>text</td><td>The blockchain this pool was created on.</td></tr><tr><td><code>chain_id</code></td><td>text</td><td>ID of blockchain to connect to, it can be <em>columbus-3, columbus-4, columbus-5, etc.</em></td></tr><tr><td><code>block_id</code></td><td>number</td><td>The block number that this pool reserve was recorded</td></tr><tr><td><code>block_timestamp</code></td><td>timestamp</td><td>The block timestamp that this pool reserve was recorded</td></tr><tr><td><code>contract_address</code></td><td>address</td><td>The address of the liquidity pool</td></tr><tr><td><code>total_share</code></td><td>number</td><td>The total amount of shares in a pool</td></tr><tr><td><code>token_0_currency</code></td><td>text</td><td>Token 0 currency</td></tr><tr><td><code>token_0_amount</code></td><td>number</td><td>Token 0 amount in pool</td></tr><tr><td><code>token_1_currency</code></td><td>text</td><td>Token 1 currency</td></tr><tr><td><code>token_1_amount</code></td><td>number</td><td>Token 1 amount in pool</td></tr></tbody></table>

32
data/archive/tables/astroport-tables/swap.md
View File

@ -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.&#x20;
## 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 |

34
data/archive/tables/avalanche-tables.md
View File

@ -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)`.&#x20;
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)
* &#x20;[`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)&#x20;
* [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).

37
data/archive/tables/axelar-tables.md
View File

@ -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)

33
data/archive/tables/bsc-tables.md
View File

@ -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)`.&#x20;
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).

62
data/archive/tables/compound-tables/README.md
View File

@ -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.&#x20;
![](<../../../../.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:**&#x20;
* 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**:
* &#x20;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!&#x20;
* 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)!&#x20;
&#x20; [https://compound.finance/docs/ctokens#key-events](https://compound.finance/docs/ctokens#key-events)

17
data/archive/tables/compound-tables/borrows.md
View File

@ -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 |

17
data/archive/tables/compound-tables/liquidations.md
View File

@ -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 |

27
data/archive/tables/compound-tables/market-stats.md
View File

@ -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) |

18
data/archive/tables/compound-tables/mints.md
View File

@ -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 |

17
data/archive/tables/compound-tables/redemptions.md
View File

@ -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) |

19
data/archive/tables/compound-tables/repayments.md
View File

@ -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 |

35
data/archive/tables/cosmos-tables.md
View File

@ -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.&#x20;
[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)

24
data/archive/tables/crosschain-tables/README.md
View File

@ -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)

19
data/archive/tables/crosschain-tables/crosschain-address-labels.md
View File

@ -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. |

17
data/archive/tables/crosschain-tables/crosschain-address-tags.md
View File

@ -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. |

16
data/archive/tables/crosschain-tables/dim-asset-metadata.md
View File

@ -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 |

11
data/archive/tables/crosschain-tables/dim-date-hours.md
View File

@ -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 |

46
data/archive/tables/crosschain-tables/dim-dates.md
View File

@ -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 |

17
data/archive/tables/crosschain-tables/fact-hourly-prices.md
View File

@ -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 |

15
data/archive/tables/ethereum-beacon-chain-tables.md
View File

@ -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)

14
data/archive/tables/ethereum-beta-tables.md
View File

@ -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)

13
data/archive/tables/ethereum-chainlink-tables.md
View File

@ -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).&#x20;

27
data/archive/tables/ethereum-maker-dao-tables.md
View File

@ -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)

15
data/archive/tables/ethereum-sushi-tables.md
View File

@ -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)
* &#x20; [ez\_lending](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.sushi\_\_ez\_lending)
* &#x20; [ez\_borrowing](https://flipsidecrypto.github.io/ethereum-models/#!/model/model.ethereum\_models.sushi\_\_ez\_borrowing)

40
data/archive/tables/ethereum-tables.md
View File

@ -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).&#x20;
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).\
\

69
data/archive/tables/flow-tables/README.md
View File

@ -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 %}

17
data/archive/tables/flow-tables/blocks.md
View File

@ -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 %}

19
data/archive/tables/flow-tables/bridge-transactions.md
View File

@ -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 %}

13
data/archive/tables/flow-tables/contract-labels.md
View File

@ -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 %}

18
data/archive/tables/flow-tables/events.md
View File

@ -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 %}

22
data/archive/tables/flow-tables/moment-metadata.md
View File

@ -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. |

23
data/archive/tables/flow-tables/nft-sales.md
View File

@ -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 %}

16
data/archive/tables/flow-tables/prices.md
View File

@ -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 %}

19
data/archive/tables/flow-tables/swaps.md
View File

@ -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 %}

18
data/archive/tables/flow-tables/token-transfers.md
View File

@ -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 %}

28
data/archive/tables/flow-tables/topshot-metadata.md
View File

@ -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 %}

23
data/archive/tables/flow-tables/transactions.md
View File

@ -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 %}

13
data/archive/tables/flow-tables/validator-labels.md
View File

@ -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 %}

31
data/archive/tables/gnosis-tables.md
View File

@ -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)`.&#x20;
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)
* &#x20;[`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)

11
data/archive/tables/near-tables.md
View File

@ -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/" %}

45
data/archive/tables/optimism-tables.md
View File

@ -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).

75
data/archive/tables/osmosis-tables/README.md
View File

@ -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.&#x20;
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.&#x20;
[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)&#x20;
[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)&#x20;
[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.&#x20;
* Labels for all available tokens and liquidity pools on the Osmosis app and Osmosis validators.
#### What we don't have:&#x20;
* Data related to pool APY, as this is not available on chain.&#x20;
* Some labels & decimals for LP tokens and low market cap tokens.&#x20;

16
data/archive/tables/osmosis-tables/osmosis-daily-balances.md
View File

@ -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.&#x20;
| 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. |

16
data/archive/tables/osmosis-tables/osmosis-dim-labels.md
View File

@ -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. |

13
data/archive/tables/osmosis-tables/osmosis-dim-liquidity-pools.md
View File

@ -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 |

16
data/archive/tables/osmosis-tables/osmosis-dim-prices.md
View File

@ -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.&#x20;
| 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. |

18
data/archive/tables/osmosis-tables/osmosis-dim-tokens.md
View File

@ -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. |

12
data/archive/tables/osmosis-tables/osmosis-dim-vote-options.md
View File

@ -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. |

15
data/archive/tables/osmosis-tables/osmosis-ez-icns.md
View File

@ -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. |

15
data/archive/tables/osmosis-tables/osmosis-ez-prices.md
View File

@ -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. |
| | | |

20
data/archive/tables/osmosis-tables/osmosis-fact-airdrops.md
View File

@ -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. |

15
data/archive/tables/osmosis-tables/osmosis-fact-blocks-table.md
View File

@ -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. |

21
data/archive/tables/osmosis-tables/osmosis-fact-governance-proposal-deposits.md
View File

@ -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.&#x20;
| 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. |

17
data/archive/tables/osmosis-tables/osmosis-fact-governance-submit-proposal.md
View File

@ -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. |

18
data/archive/tables/osmosis-tables/osmosis-fact-governance-votes.md
View File

@ -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. |

21
data/archive/tables/osmosis-tables/osmosis-fact-liquidity-provider-actions.md
View File

@ -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. |

18
data/archive/tables/osmosis-tables/osmosis-fact-msg-attributes-table.md
View File

@ -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. |

Some files were not shown because too many files have changed in this diff Show More