Stakers use Liquid Collective to deposit funds into Ethereum’s deposit contract and mint a liquid staking token, LsETH. In return stakers receive staking rewards (supply-side fees).

Liquid Collective is a non-custodial staking protocol launched on Ethereum. Liquid Collective is built and run by a collective of leading web3 teams. The protocol was initially launched in 2023.

Liquid Collective is stewarded by an independent industry consortium, with initial members that include The Liquid Foundation, Alluvial, Kiln, Figment, Coinbase, Coinbase Cloud, Kraken, Staked, and other web3 participants. Liquid Collective will be governed in a decentralized manner by a broad and dispersed community of industry participants.

github

twitter

etherscan

website

Liquid staking

Liquid Collective

# Active addresses (weekly) Methodology

## Overview

Active addresses (weekly) measures the number of unique addresses that make a transaction with a project, i.e. An application or a blockchain. Weekly active addresses are measured on a 7-day rolling basis.

## Data sources

- On-chain transaction records (sender addresses, receiver addresses, and timestamps)
- Program instructions and transaction metadata
- Asset metadata for chain and project identification

## Common calculation approaches

### Transaction sender identification
Sender addresses are extracted from transaction records across blockchains including Ethereum, BNB Chain, and Polygon. Unique initiators are identified from sender address fields and aggregated over a rolling 7-day period to measure network activity.

### Signer and instruction tracking
On Solana, active accounts are identified by extracting unique signers from program instructions. Data is aggregated from both successful and failed transactions to provide a comprehensive view of account activity and network demand.

### Delegated action handling
For networks with specific account abstraction features, such as NEAR Protocol, transaction initiators are identified by distinguishing between standard actions and delegate actions. For meta transactions on NEAR Protocol, the receiver account is identified as the active user to accurately represent user engagement.

**Note:** The calculation approaches and protocol examples above are representative patterns. Individual protocol implementations may vary.

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

Unique active addresses over a rolling 7-day window.

Liquid Collective

Active addresses (weekly)

Active addresses (weekly)

Competitive landscape