Lenders deposit funds into Venus and receive interest payments from borrowers (supply-side fees).

Venus is a non-custodial lending protocol built on BNB chain. Venus was founded by Joselito Lizarondo and launched in 2020.

XVS tokenholders own and govern the protocol. They currently take a cut of the total interest paid by borrowers (revenue).

governance

github

twitter

discord

etherscan

website

Lending

Venus

Venus | Data breakdown

# Venus Active users (daily) Methodology

## 1. Overview

Venus Daily Active Users (DAU) measures the number of unique wallet addresses that interact with Venus protocol lending contracts each day. This metric captures user engagement across Venus's multi-chain lending platform by tracking distinct users who perform any lending-related activity (borrowing, depositing, withdrawing, or repaying) within each 24-hour period. The calculation aggregates user activity across 8 blockchain networks where Venus operates, providing a comprehensive view of protocol usage.

## 2. Data sources

The calculation relies on the following raw blockchain data sources:

- **Venus protocol event logs**: Parsed event logs from Venus lending contracts across 8 blockchain networks (BSC, Ethereum, Arbitrum, Base, opBNB, Optimism, Unichain, zkSync Era)
- **Core lending events**: Four types of protocol events - `Borrow`, `Mint` (deposits), `Redeem` (withdrawals), and `RepayBorrow` events
- **Contract-specific events**: BSC network includes events from VBep20Delegate contracts, vBNB contracts, and VToken contracts; other networks use VToken contract events
- **Block timestamp data**: Blockchain timestamp information for daily aggregation boundaries

## 3. Step-by-step calculation

### Component A: User event collection
- **Purpose**: Identifies all user interactions with Venus lending protocols across supported chains
- **Logic**: Extracts user addresses from four core Venus lending event types. For `Borrow` events, captures the `borrower` address; for `Mint` events, captures the `minter` address (users depositing assets); for `Redeem` events, captures the `redeemer` address (users withdrawing assets); for `RepayBorrow` events, captures the `payer` address (users repaying loans). Each chain uses its specific Venus contract structure - BSC includes VBep20Delegate, vBNB, and VToken contracts while other chains use VToken contracts exclusively.
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for transaction identification, `user_address` extracted from event-specific fields, `chain` identifier, and derived `user_type` classification

### Component B: User classification and normalization
- **Purpose**: Standardizes user data across chains and classifies users by activity type
- **Logic**: Maps each event type to a corresponding user classification - Borrow events create "Borrower" users, Mint events create "Depositor" users, Redeem events create "Withdrawer" users, and RepayBorrow events create "Repayer" users. All users are assigned to the "lending" market sector and business segment since Venus is a lending protocol. The `product_id` field is set to null as Venus doesn't have distinct product differentiation within lending.
- **Key fields**: `user_type` classification based on event mapping, standardized `market_sector_id` and `business_segment_id` values, `chain` identification for multi-chain tracking

### Final aggregation
- **Combining components**: All user events from different chains and event types are combined into a single dataset through union operations
- **Time aggregation**: Block timestamps are truncated to daily boundaries using day-level granularity, creating consistent 24-hour measurement periods across all chains
- **User deduplication**: Applies distinct counting on `user_address` within each day, chain, and user type combination to ensure users who perform multiple actions of the same type on the same day are only counted once
- **Data quality filtering**: Applies chain availability filters to ensure consistent data coverage and exclude periods where blockchain data might be incomplete or unreliable
- **Final calculation**: The result is a daily count of unique user addresses per chain and user type, with each record representing one distinct active user for that specific day and activity type

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

Unique revenue-generating users over a fixed 24-hour window.

VenusXVS

Active users (daily)

Active users (daily)

Competitive landscape

Chain breakdown