Skip to content

Latest commit

 

History

History
19 lines (11 loc) · 2.71 KB

constellation-vs-others.md

File metadata and controls

19 lines (11 loc) · 2.71 KB
description
Understand the differences in risks, returns, and responsibilities

Constellation vs Others

LST Comparison

TokenFee on Ethereum RewardsProsCons
xrETH0%No fee, high decentralizationSee Risks and Mitigations
osETH5%+ (depends on chosen vault, network average otherwise)Slashing protection, some decentralizationComplex UX, minimum fee sacrifices decentralization
stETH10%High liquidity depthHighly centralized, higher fees, no slashing protection
rETH14%Slashing protection, high decentralizationHigh fee

Constellation vs Running a Node

Most xrETH depositors can expect similar returns and lower risks compared to running a basic Ethereum node (AKA "solo staking") on your own. In addition, xrETH is a liquid token, which allows for its usage in DeFi, boosting its potential even further.

When comparing to other node operation options, the landscape is more complex. Generally, using xrETH as a Constellation Node Operator allows for improved returns and full liquidity, and other solutions are available for users that wishing to maximize returns even at the cost of liquidity or utility.

MethodEstimated Returns*ProsCons
xrETH100% of solo stakingUsable in DeFi, which may boost returns dramaticallySee Risks and Mitigations
xrETH + Constellation Node Operation121% of solo stakingUsable in DeFi, which may boost returns dramaticallySee Risks and Mitigations
Solo staking100% of solo stakingNo SC riskFully locked, must run a node, risk and returns dependent upon individual performance
Rocket Pool (LEB8)ETH: 130-142% of solo staking
RPL: ~6% APR
Higher returns than solo stakingFully locked, must run a node, risk and returns dependent upon individual performance
Lido CSM237% of solo stakingHighest returnsFully locked, must run a node, risk and returns dependent upon individual performance

Limited to 16 ETH

*Estimated Returns are sourced from external data and are not guaranteed. NodeSet is not responsible for the creation of or any inaccuracy in this data.