Hugging Face's logo

Datasets:
mriusero
/
DeFi-Protocol-Data-on-Ethereum-2023-2024

Modalities:
Tabular
Text
Formats:
parquet
Size:
1M - 10M
Tags:
finance
blockchain
Libraries:
Datasets
pandas
License:
Dataset card Data Studio Files Community
1
DeFi-Protocol-Data-on-Ethereum-2023-2024 / README.md
mriusero's picture
mriusero
Update README.md
ed288cc verified
preview code
|
raw
history blame contribute delete
9.76 kB
metadata
license: mit
tags:
  - finance
  - blockchain
size_categories:
  - 1M<n<10M

Decentralized finance (DeFi) has emerged as a significant sector within the blockchain and cryptocurrency space. DeFi protocols enable users to access financial services without traditional intermediaries, offering a wide range of applications such as lending, borrowing, trading, and yield farming. Understanding user behavior, protocol interactions, and market trends is crucial for analyzing the DeFi ecosystem's dynamics and identifying opportunities for innovation and growth.

About Dataset

This dataset encompasses several steps involved in preparing data to analyze decentralized finance (DeFi) protocols and transactions. The process of building the dataset involves collecting data from various DeFi protocols, extracting relevant contract data, gathering transaction information, and aggregating market data.

Specifically, the scope focuses on the following types of DeFi protocols on the Ethereum blockchain:

  • Decentralized Exchanges (DEX): Uniswap, Curve DAO, Balancer
  • Lending Platforms: Aave, Maker
  • Stablecoins: Tether, USD Coin (USDC), Dai
  • Yield Farming: Yearn Finance, Harvest Finance
  • Non-Fungible Token (NFT): NFTfi

Four files serves a distinct purpose and is carefully structured to facilitate deeper insights into the DeFi landscape:

├── contracts.parquet               # Contains contract details for selected DeFi protocols.
├── transactions.parquet            # Contains transaction data for Ethereum-based contracts.
├── market.parquet                  # Contains enriched market data with aggregated transaction metrics.
└── users.parquet                   # User profiles based on transaction data.

Also, features have been aggregated to capture users behaviors and protocols interactions, and the documentation is available here.

Metrics

The metrics associated with the dataset are as follows:

  • First Date: December 31, 2022, at 22:59:59 UTC
  • Last Date: December 30, 2024, at 23:00:11 UTC
  • Number of Protocols: 11
  • Number of Protocol Types: 5
  • Number of Unique Transactions: 22,682,739
  • Number of Unique Users/Addresses: 6,876,845
  • Total Market Hours: 177,955

Source

Tools used in this process:
1. CoinGecko API - For contract data related to DeFi protocols and their market details.
2. Etherscan API - For transaction data extraction on Ethereum smart contracts.
3. Yahoo Finance API - For market data including OHLC values of tokens and trading volume.
4. MongoDB - For managing and storing large volumes of transaction and protocol data in a structured format.
5. Ethereum Blockchain - For the decentralized financial infrastructure that powers these protocols and transactions.

Code is available on GitHub and ETL process documentation is explained here.

Subsets

users.parquet

This file focuses on user-level data and is aimed at answering questions related to user behavior, activity trends, and protocol interactions.
Potential use cases include:
- Analyzing the lifecycle of user activity in DeFi.
- Identifying power users or dormant users.
- Mapping the interaction between users and various protocols.

  • address (string): The wallet address of the user.
  • first_seen (datetime): The first recorded activity of the user.
  • last_seen (datetime): The most recent activity of the user.
  • protocol_types (list/string): Types of protocols the user interacted with.
  • protocols_used (list/string): Specific protocols the user interacted with.
  • received_count (integer): The total number of transactions received by the user.
  • total_received (ETH) (float): The total amount of ETH received by the user.
  • sent_count (integer): The total number of transactions sent by the user.
  • total_sent (ETH) (float): The total amount of ETH sent by the user.
  • transactions (integer): The total number of transactions the user participated in.

market.parquet

This file aggregates market-related data over time intervals, offering insights into protocol performance and market dynamics.
Objectives include:
- Understanding market trends across DeFi protocols and tokens.
- Analyzing trading volumes, transaction activity, and price fluctuations.
- Identifying periods of high or low activity for specific tokens or protocols.

  • timestamp (datetime): The time when the data was recorded.
  • blockchain (string): The blockchain network (e.g., Ethereum, Binance Smart Chain).
  • protocol_name (string): The name of the protocol associated with the data.
  • symbol (string): The symbol of the cryptocurrency or token.
  • type (string): The type of asset (e.g., token, NFT).
  • contract_address (string): The contract address associated with the asset.
  • open (usd) (float): The opening price in USD during the interval.
  • high (usd) (float): The highest price in USD during the interval.
  • low (usd) (float): The lowest price in USD during the interval.
  • close (usd) (float): The closing price in USD during the interval.
  • volume (float): The total trading volume during the interval.
  • nb_tx_1h, nb_tx_24h (integer): The number of transactions in the last 1 hour and 24 hours, respectively.
  • total_value_eth_1h, total_value_eth_24h (float): The total value transferred in ETH in the last 1 hour and 24 hours.
  • total_gas_used_1h, total_gas_used_24h (float): The total gas used in the last 1 hour and 24 hours.
  • nb_unique_receivers_1h, nb_unique_receivers_24h (integer): The number of unique receiving addresses in the last 1 hour and 24 hours.
  • nb_unique_senders_1h, nb_unique_senders_24h (integer): The number of unique sending addresses in the last 1 hour and 24 hours.
  • std_value_eth_1h, std_value_eth_24h (float): The standard deviation of transaction values in ETH in the last 1 hour and 24 hours.
  • std_gas_used_1h, std_gas_used_24h (float): The standard deviation of gas used in the last 1 hour and 24 hours.
  • avg_gas_used_1h, avg_gas_used_24h (float): The average gas used in the last 1 hour and 24 hours.
  • avg_value_eth_per_tx_1h, avg_value_eth_per_tx_24h (float): The average ETH value per transaction in the last 1 hour and 24 hours.
  • max_gas_used_1h, max_gas_used_24h (float): The maximum gas used in the last 1 hour and 24 hours.
  • max_value_eth_1h, max_value_eth_24h (float): The maximum ETH value transferred in the last 1 hour and 24 hours.
  • median_value_eth_1h, median_value_eth_24h (float): The median transaction value in ETH in the last 1 hour and 24 hours.
  • min_gas_used_1h, min_gas_used_24h (float): The minimum gas used in the last 1 hour and 24 hours.
  • min_value_eth_1h, min_value_eth_24h (float): The minimum ETH value transferred in the last 1 hour and 24 hours.
  • num_errors_1h, num_errors_24h (integer): The number of errors in the last 1 hour and 24 hours.
  • error_rate_1h, error_rate_24h (float): The rate of errors in the last 1 hour and 24 hours.

transactions.parquet

This file provides granular transaction-level data, which is crucial for understanding the flow of assets within the DeFi ecosystem.
Applications include:
- Tracing the movement of funds between addresses.
- Analyzing transaction costs (gas) and failure rates.
- Identifying anomalous or fraudulent transactions.

  • timestamp (datetime): The time when the transaction occurred.
  • transaction_hash (string): The unique hash identifying the transaction.
  • from (string): The sender's wallet address.
  • to (string): The receiver's wallet address.
  • value (ETH) (float): The value transferred in ETH.
  • gas (integer): The gas limit specified for the transaction.
  • gas_used (integer): The actual gas used by the transaction.
  • is_error (boolean): Indicates if the transaction resulted in an error.
  • error_code (string): The error code, if applicable.
  • metadata (json/object): Additional metadata related to the transaction.

contracts.parquet

This file documents details about the smart contracts associated with various DeFi protocols.
It supports:
- Categorizing contracts by protocol, type, and use case.
- Analyzing the adoption of specific contract standards (e.g., ERC-20, ERC-721).
- Exploring the relationship between contract attributes and protocol performance.

  • contract_address (string): The unique address of the smart contract.
  • blockchain (string): The blockchain network where the contract is deployed.
  • type (string): The type of contract (e.g., ERC-20, ERC-721).
  • protocol_name (string): The name of the protocol the contract belongs to.
  • protocol_symbol (string): The symbol of the protocol or token.
  • description (string): A description of the contract's purpose or functionality.
  • website_url (string): The URL of the contract or protocol's official website.

license: mit