# Overview Constellation aims to extend Rocket Pool's capabilities by providing more benefits and optionality to users, improving capital efficiency and scalability, and reducing asset concentration risk. Constellation introduces liquid staking tokens, xrETH and xRPL, which offer unique properties compared to traditional liquid staking tokens (LSTs).\ \ **The Problem**\ \ To be maximally trustless, Rocket Pool requires naode operators to post a bond for each validator. This restricts growth by requiring a constant supply of NOs who can afford this bond and leads to an uneven distribution of assets across nodes. **The Solution** Constellation liquidizes the NO bond, opening it up to external investors via tokens called xrETH and xRPL. The ETH and RPL deposits used to mint these tokens are used by the Constellation smart contracts to create new minipools on Rocket Pool which are operated non-custodially by NodeSet operators.\ \ This allows to: 1. **Increase capital efficiency:** By enabling more ETH to be staked through a liquid staking token, xrETH, without requiring individual node operators (NOs) to lock large amounts of collateral. 2. **Minimize asset concentration risk:** By distributing assets across a large network of decentralized node operators. 3. **Enable external investors to participate in node bonding:** By tokenizing node operator bonds through xrETH and xRPL, Constellation enables external investors to fund the bonds that would normally be provided by the NOs themselves. This allows for more validators to be spun up, expanding the supply of rETH and xrETH.

Constellation + Rocket Pool Architecture (simplified)

There are four main user roles in this system: 1\) Depositors ([xrETH](https://docs.nodeset.io/constellation/xreth) or [xRPL](https://docs.nodeset.io/constellation/xrpl) holders) 2\) [Node operators](https://docs.nodeset.io/constellation/node-operators) 3\) [Administrator](https://docs.nodeset.io/constellation/administrator) 4\) [Treasurer](https://docs.nodeset.io/constellation/treasurer) --- # Agent Instructions: 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: ``` GET https://docs.gravitaprotocol.com/gravita-docs/constellation/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.