Liquid Collective ETH
Liquid Collective DocsGithub
  • ETH Liquid Staking Documentation
  • Overview
    • Roles & Staking Infrastructure
    • Architecture
    • Staking Amounts
    • Slashing Coverage
    • Permissioning
    • Protocol Metadata
  • Tokenomics
    • LsETH (cToken)
    • Rewards, Fees, & Socialization
    • Deposits & Redemptions
  • Node Operations
    • Validator Infrastructure
    • Operate Validator Nodes
  • Oracles
    • Oracle Infrastructure
    • Operate an Oracle
  • Platforms
    • Platform Operations
  • 💻Technical Reference
    • Deployment Addresses
    • Smart Contracts
      • RiverV1
      • RedeemManagerV1
      • CoverageFundV1
      • TLCV1
      • ELFeeRecipientV1
      • Administrable
      • AllowlistV1
      • Firewall
      • WithdrawV1
      • WLSETHV1
      • Initializable
      • OperatorsRegistryV1
      • TUPProxy
      • OracleV1
      • ProtocolMetrics
      • Components
        • OracleManagerV1
        • SharesManagerV1
        • ERC20VestableVotesUpgradeableV1
        • ConsensusLayerDepositManagerV1
        • UserDepositManagerV1
      • Interfaces
        • IFirewall
        • IAllowlistV1
        • IAdministrable
        • IConsensusLayerDepositManagerV1
        • IRedeemManagerV1
        • IOracleManagerV1
        • ISharesManagerV1
        • IUserDepositManagerV1
        • IERC20VestableVotesUpgradeableV1
        • IOperatorsRegistryV1
        • IOracleV1
        • ITLCV1
        • IWLSETHV1
        • IWithdrawV1
        • IRiverV1
        • ICoverageFundV1
        • IDepositContract
        • IELFeeRecipientV1
        • IProtocolVersion
      • Libraries
        • LibBytes
        • LibErrors
        • LibBasisPoints
        • LibSanitize
        • LibAdministrable
        • LibUnstructuredStorage
        • LibAllowlistMasks
        • LibUint256
      • 🌊State
        • OperatorsRegistry
          • OperatorsV2
          • CurrentValidatorExitsDemand
          • ValidatorKeys
          • TotalValidatorExitsRequested
        • AllowList
          • AllowerAddress
          • DenierAddress
          • Allowlist
        • Oracle
          • LastEpochId
          • OracleMembers
          • Quorum
          • ReportsPositions
          • ReportsVariants
        • RedeemManager
          • BufferedExceedingEth
          • RedeemDemand
          • RedeemQueueV2
          • WithdrawalStack
        • River
          • AllowlistAddress
          • BalanceToDeposit
          • BalanceToRedeem
          • CLSpec
          • CLValidatorCount
          • CLValidatorTotalBalance
          • CollectorAddress
          • CommittedBalance
          • CoverageFundAddress
          • DailyCommittableLimits
          • DepositContractAddress
          • DepositedValidatorCount
          • ELFeeRecipientAddress
          • GlobalFee
          • KeeperAddress
          • LastConsensusLayerReport
          • LastOracleRoundId
          • MetadataURI
          • OperatorsRegistryAddress
          • OracleAddress
          • RedeemManagerAddress
          • ReportBounds
          • Shares
          • SharesPerOwner
          • WithdrawalCredentials
        • Shared
          • AdministratorAddress
          • ApprovalsPerOwner
          • PendingAdministratorAddress
          • RiverAddress
          • Version
        • SlashingCoverage
          • BalanceForCoverage
        • TLC
          • IgnoreGlobalUnlockSchedule
          • VestingSchedulesV2
        • WLSETH
          • BalanceOf
    • CLI
      • operators
        • operators count
        • operators add
        • operators get
        • operators list
      • validators
        • validators count
        • validators add
        • validators remove
        • validators get
      • oracle
        • oracle specs
        • oracle report
          • oracle status
        • oracle quorum
        • oracle members
          • oracle list
        • oracle epochs
          • oracle epochs current
          • oracle epochs last-completed
          • oracle epochs expected
        • oracle current-frame
        • oracle run
      • eth1keys
        • eth1keys generate
        • eth1keys import
      • withdrawal
        • withdrawal address
        • withdrawal credentials
      • el-fee-recipient
        • el-fee-recipient address
      • allowlist
        • allowlist is-allowed
        • allowlist allow
        • allowlist remove
      • eth-cl
        • eth-cl get-spec
        • eth-cl get-validator
      • eth-el
        • eth-el blocknumber
        • eth-el chain-id
  • FAQ
Powered by GitBook
On this page
  • Protocol Service Fee
  • Network reward collection & Conversion Rate variation
  • Calculating rewards and fees
  • Network reward computation
  • EL Fee Recipient Contract
  • Network reward distribution
  • Reward and penalty socialization
Export as PDF
  1. Tokenomics

Rewards, Fees, & Socialization

The collection and socialization of Ethereum network rewards and Liquid Collective protocol fees

PreviousLsETH (cToken)NextDeposits & Redemptions

Last updated 3 months ago

Every 24 hours, Oracles report the new balance of staked ETH from accrued network rewards or fees. The is computed as the total balance of staked ETH over the total supply of LsETH. If accrued network rewards are greater than penalties and fees, the protocol Conversion Rate increases to reflect the net Ethereum network rewards collected by the protocol.

Because of LsETH's cToken design, the Conversion Rate may fluctuate. In contrast to other token models, such as aTokens, that issue new net network reward tokens on a unit basis, stakers on the Liquid Collective protocol will not receive more or less tokens as they receive network rewards or penalties.

Instead, the Conversion Rate for each unit of LsETH owned by the depositor will increase or decrease (i.e., the LsETH will evidence legal and beneficial ownership of more or less ETH) in an amount that reflects accrued network rewards.

Protocol Service Fee

The Liquid Collective protocol charges a Protocol Service Fee set at 10.0% of network rewards. Liquid Collective’s service fee is split amongst split amongst Node Operators, Platforms, Wallet & Custody Providers, Service Providers, the protocol’s , and the Liquid Collective DAO, which comprises a broad and dispersed community of protocol participants. All service fees are distributed in LsTokens, which are the native receipt tokens of the protocol (e.g. LsETH).

Network reward collection & Conversion Rate variation

Every day the Liquid Collective protocol accounts for Ethereum network rewards including consensus layer network rewards and execution layer fees minus possible penalties, which results in updating the data reflecting the total supply of ETH.

If network rewards have been earned on a given day, then the protocol collects the Protocol Service Fee as a percentage of the earned network rewards. The Protocol Service Fee is collected by minting LsETH, which results in an increase in the total supply of LsETH.

Under normal validator operations, the protocol earns network rewards; as such the total supply of ETH increases and the Conversion Rate increases accordingly.

In a scenario where validators are penalized or slashed, depending on the magnitude of the incurred penalties, the total ETH supply could decrease, and the Conversion Rate would decrease accordingly.

Example

Assuming

  • totalETHSupply = 125 ETH

  • totalLsETHSupply = 100

  • protocolFee = 10%

So conversionRate = 125 / 100 = 1.25

Today the protocol earns 10 ETH thus the protocol fee is 10% * 10 ETH / 1.25 = 0.8 LsETH

And the new conversionRate = (125+10) / (108+0.8) = 1.58

Note: Figures above are just examples and do not reflect reality or projections.

Calculating rewards and fees

Each time the Oracle contract reports consensus layer data to the River contract, the protocol programmatically distributes network rewards including consensus layer network rewards and execution layer fees.

Fees received by validators for the execution of transactions are distributed on the execution layer directly. The Liquid Collective protocol automatically stakes the execution layer fees to increase the protocol’s overall potential reward rate by increasing the number of validators in the protocol's active set.

Network reward computation

Each time the Oracle reports consensus layer data, the River smart contract:

  • Pulls execution layer fees from the EL Fee Recipient contract

  • Updates consensus layer data including the Liquid Collective active validators count and total Liquid Collective active validators balance

The network reward is computed as:

reward=(activeValidatorsCountold−activeValidatorsCountnew)∗32 ETH+(totalActiveValidatorsBalancenew−totalActiveValidatorsBalanceold)+pulledExecLayerFeesreward = \\(activeValidatorsCount_{old} - activeValidatorsCount_{new})*32 \, ETH \\ + (totalActiveValidatorsBalance_{new} - totalActiveValidatorsBalance_{old}) \\ + pulledExecLayerFeesreward=(activeValidatorsCountold​−activeValidatorsCountnew​)∗32ETH+(totalActiveValidatorsBalancenew​−totalActiveValidatorsBalanceold​)+pulledExecLayerFees

EL Fee Recipient Contract

The EL Fee Recipient Contract receives all of the execution layer fees including transaction fees and MEV priority fees. The River contract periodically pulls that ETH on every Oracle report.

Network reward distribution

If the earned reward is positive, it is distributed between:

  • LsETH holders receive 85% of the network rewards, proportional to their LsETH holdings, through an accrual of the Conversion Rate

  • Collector that receives the Protocol Service Fee via minting LsETH, which is currently set at 10%

Reward and penalty socialization

Liquid Collective socializes network rewards and penalties between holders proportionally to their LsETH balance. The protocol aims to enforce fairness between participants, making sure that no participant gets treated favorably compared to others.

This means that stakers on Liquid Collective are exposed to the performance of all validators across Liquid Collective as a whole.

Examples:

  • If a validator receives a massive MEV network reward, then this network reward is socialized amongst every LsETH holder.

  • If a validator gets slashed, then the penalty is socialized amongst every LsETH holder.

This socialization of network rewards and penalties is realized by the LsETH Conversion Rate which applies to every LsETH holder equally. Every 24 hours, Oracle reports the new balance of staked ETH across the protocol accounting for accrued network rewards and penalties, resulting in updating the Conversion Rate, which applies to every LsETH holder.

Conversion Rate
Slashing Coverage Treasury