> For the complete documentation index, see [llms.txt](https://docs.nodeset.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodeset.io/constellation/constellation-vs-others.md).

# Constellation vs Others

## LST Comparison

<table><thead><tr><th width="123">Token</th><th width="236">Fee on Ethereum Rewards</th><th width="161">Pros</th><th>Cons</th></tr></thead><tbody><tr><td>xrETH (NodeSet)</td><td>0%</td><td>No fee, high decentralization</td><td>See <a href="/pages/fBYG2WnuD0HIFwxVnwW0">Risks and Mitigations</a></td></tr><tr><td>osETH</td><td>5%+ (depends on chosen vault,  network average otherwise)</td><td>Slashing protection, some decentralization</td><td>Complex UX, minimum fee  sacrifices decentralization</td></tr><tr><td>stETH</td><td>10%</td><td>High liquidity depth</td><td>Highly centralized, higher fees, no slashing protection</td></tr><tr><td>rETH</td><td>14%</td><td>Slashing protection, high decentralization</td><td>High fee</td></tr></tbody></table>

## 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.&#x20;

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.

<table><thead><tr><th>Method</th><th width="186">Estimated Returns*</th><th width="179">Pros</th><th>Cons</th></tr></thead><tbody><tr><td>xrETH<br>(NodeSet)</td><td>100% of solo staking</td><td>Usable in DeFi, which may boost returns dramatically</td><td>See <a href="/pages/fBYG2WnuD0HIFwxVnwW0">Risks and Mitigations</a></td></tr><tr><td>xrETH + Constellation Node Operation<br>(NodeSet)</td><td>121% of solo staking</td><td>Usable in DeFi, which may boost returns dramatically</td><td>See <a href="/pages/fBYG2WnuD0HIFwxVnwW0">Risks and Mitigations</a></td></tr><tr><td>Solo staking</td><td>100% of solo staking</td><td>No SC risk</td><td>Fully locked, must run a node, risk and returns dependent upon individual performance</td></tr><tr><td>Rocket Pool (LEB8)</td><td>ETH: 130-142% of solo staking<br>RPL: ~6% APR</td><td>Higher returns than solo staking</td><td>Fully locked, must run a node, risk and returns dependent upon individual performance</td></tr><tr><td>Lido CSM</td><td>237% of solo staking</td><td>Highest returns</td><td>Fully locked, must run a node, risk and returns dependent upon individual performance<br><br>Limited to 16 ETH</td></tr></tbody></table>

*\*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.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nodeset.io/constellation/constellation-vs-others.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.