Rocket Pool
Rocket Pool
Overview
Guides
Website
简体中文
English
Overview
Guides
Website
简体中文
English
Rocket Pool

Guides

Overview
The Saturn 0 Upgrade

rETH Staker Guide

Overview
Staking directly via Rocket Pool
Staking via a Decentralised Exchange on the Ethereum Network (Layer 1)
Staking via a Decentralised Exchange on Layer 2
Staking on behalf of a node

Node Operator Guide

A Node Operator's Responsibilities
Node Requirements & Choosing a Platform

Preparing a Local Node

Overview
Selecting Staking Hardware
Preparing a PC, Mini-PC or NUC
Preparing a Mac
Intro to Secure Shell (SSH)

Preparing a Server Node

Overview
Selecting a Hosting Provider
Preparing the Operating System

Securing Your Node

Securing Your Node
Tailscale

Installing Rocket Pool

Overview
Choosing your ETH Clients
Selecting a Rocket Pool Mode
Creating a Standard Rocket Pool Node with Docker
Creating a Native Rocket Pool Node without Docker

Configuring Rocket Pool

Overview
Configuring the Smartnode Stack (Docker/hybrid mode)
Configuring the Smartnode Stack (native)
Advanced Smartnode Configuration for Docker Mode

Provisioning your Node

Overview
Starting Rocket Pool
Creating a New Wallet
Importing/Recovering an Existing Wallet
Preparing your Node for Operation
Intro to the Command Line Interface
Specifying a Fallback Node
Fee Distributors and the Smoothing Pool
MEV, MEV-Boost & MEV Rewards

Creating or Migrating Minipools

Overview
Creating a new Minipool (Validator)
The Minipool Delegate
Converting a Solo Validator into a Minipool
Migrating a 16-ETH Minipool to 8-ETH
The Deposit Credit System

Monitoring & Maintenance

Overview
Monitoring your Node's Performance
Setting up the Grafana Dashboard
Smartnode Stack Alert Notifications
Checking for Updates
Backing Up Your Node
Masquerading as Another Node Address
Expiring Pre-Merge History
Pruning the Execution Client
Changing Execution or Consensus Clients
Moving from One Node to Another

Claiming Rewards

Overview
Claiming Node Operator Rewards
Distributing Skimmed Rewards

Participating in pDAO governance

Overview
The Protocol DAO
Participating in on-chain pDAO Proposals
Setting your Snapshot Signalling Address
Delegating Voting Power
Viewing the State of a Proposal
Voting on a Proposal
Creating a Proposal
Executing a successful proposal
Claiming Bonds and Rewards
Creating and Claiming a recurring treasury spend

Exiting your Minipools

Shut Down a Minipool
Rescuing a Dissolved Minipool
FAQ (WIP)

Testing Rocket Pool with the Hoodi Test Network

Practicing with the Test Network
Migrating from the Test Network to Mainnet

Running an Oracle DAO Node

The Rocket Pool Oracle DAO
Setting up an Oracle DAO Node
Testing your Oracle DAO Node
Monitoring your Oracle DAO Node
Oracle DAO Proposals

Legacy Guides

Upgrading to Smartnode v1.3.x
Migrating the Smartnode from Previous Beta Tests
The Atlas Update
Lower ETH Bond Minipools

Redstone & The Merge

The Rocket Pool Redstone Update
[Docker Mode] Guide to the Redstone Update and the Merge
[Hybrid Mode] Guide to the Redstone Update and the Merge
[Native Mode] Guide to the Redstone Update and the Merge

The Houston Upgrade

Overview
Getting Started with Houston
The Protocol DAO
Participating in Proposals
Stake ETH on Behalf of Node
RPL Withdrawal Address
Preparing a Raspberry Pi
📝 Edit this page on GitHub
Previous PageShut Down a Minipool
Next PageFAQ (WIP)

#Rescuing a Dissolved Minipool

In the unlikely event your minipool does not stake within the dissolve window, it will be "dissolved" by the oDAO and user funds provided will be returned to the deposit pool for use by another minipool. In this scenario, you will need to perform the below process to retrieve your ETH and unlock your RPL to be unstaked.

#Update your Minipool Delegate

It is highly recommended that you use the latest minipool delegate when performing this process. Older delegates contain a selfdestruct operation when they are closed which means, if the process is not completed correctly in the specified order, funds may be locked forever. You can check that your minipool is on the latest delegate by attempting to Upgrade your Delegate. If your minipool does not appear in the list of minipools that can be upgraded then you can continue on below.

#Retrieve Your Unused Deposit Balance

NOTE

If your minipool was dissolved prior to Atlas, you may skip this step and head straight to Increase Your Beaconchain Balance to 32 ETH. You do not need to retrieve your unused deposit balance because the entire bond amount was deposited to the beaconchain prior to Atlas.

1 ETH from your initial bond deposit is used as an initial deposit to the beaconchain to secure your validator's withdrawal credentials. The remaining amount is deposited to your minipool when it is assigned ETH from the deposit pool.

When your minipool is dissolved, the user ETH is returned to the deposit pool and your ETH remains in the minipool ready to be returned to you. Use the Manual Distribution of rewards feature to retrieve this ETH that can then be used in the next step to activate your validator.

#Increase Your Beaconchain Balance to 32 ETH

You must top up your validator's balance to the minimum required for activation on the beaconchain. This amount is 32 ETH. If you have a 16 ETH bonded minipool, you will require an additional 16 ETH and if you have an 8 ETH bonded minipool you will need an additional 24 ETH during this step.

Deposit the required amount of ETH into your node address and then issue the following command to begin the process:

rocketpool minipool rescue-dissolved

You will be presented with a list of minipools that meet the criteria for a manual deposit:

Please select a minipool to rescue:
1: All available minipools
2: 0x7E5700bcd65B1770bA68abB288D3f53814d376aC (dissolved since 2023-02-08, 06:33 +0000 UTC)
3: 0x7E570195026dC29f4B2DfF08B56c3b5D0FF988Ef (dissolved since 2023-02-08, 06:33 +0000 UTC)

After selecting the minipool you want to rescue, you will be asked what amount you want to manually deposit:

1. All 16.000000 ETH required to rescue it
2. 1 ETH
3. A custom amount

Option 1 will be used in most circumstances. It is the amount required to bring your beaconchain balance up to the required 32 ETH amount. The other options are provided for advanced use cases.

NOTE

Bringing your beaconchain balance up to 32 ETH means your validator will be able to actively participate in Ethereum validation duties. The smartnode may not have had a chance to restart your validator since the dissolution. Therefore, it is a good idea to manually restart your validator to ensure it has loaded your validator keys and can perform validation duties to avoid any penalties during the rescue process.

If you are running the standard Docker mode, this can be done with docker restart rocketpool_validator.

Once this step is complete, your validator will enter the entry queue and you will need to wait for the following events to occur:

  1. 2048 execution layer blocks need to pass for your deposit to be accepted (~8 hours)
  2. Up to 32 epochs need to pass for validators to vote you in (0.5 - 3.5 hours)
  3. A variable amount of time in the validator queue (6.4 minutes per 4 validators in the queue)
  4. 256 epochs minimum validating before an exit is allowed (27 hours)

#Exiting your Validator

Once your validator has been active for a minimum of 256 epochs, you may exit your minipool via the same process as any other minipool by following the Exiting your Validator guide.

The full 32 ETH balance will be returned to your minipool and dissolved minipools distribute 100% of their balance to the node operator's withdrawal address.