--- url: /liquid-staking/overview.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Staking Overview This guide will introduce you to how staking with Rocket Pool works (how your ETH is put to work and your rewards are generated) and summarize the ways in which you can stake. ::: tip NOTE If you're not interested in how staking works and just want to learn how to stake, [**click here to skip to that section.**](#how-to-stake-with-rocket-pool) ::: ## How Ethereum Staking Works Before getting into Rocket Pool, let's talk about staking on Ethereum in general. Since [the Merge](https://ethereum.org/en/upgrades/merge/) on September 15th, 2022, Ethereum now comprises two blockchains in parallel: the Execution layer (formerly ETH1), which contains all of Ethereum's transaction data, and the Consensus layer (also known as the [Beacon Chain](https://ethereum.org/en/roadmap/beacon-chain/), formerly ETH2) which consists of a network of **validators** that collectively determine the validity of each transaction and each block broadcast to the network. **Staking** is the process of creating and maintaining one (or more) of these validators on the Beacon Chain to help the network maintain the consistency and security of the Ethereum blockchain. Validators do this by listening for transactions and new block proposals, and **attesting** that the proposed block contains legal, valid transactions by doing some number crunching and verification behind the scenes. Occasionally, they get to propose new blocks themselves. To ensure that the network is resilient against malicious validators that lie about the current state of the chain, each validator is required to lock exactly 32 ETH up as a "stake" in the networks. Performing their duties correctly and agreeing with the majority of the other validators will earn them rewards; performing incorrectly and attacking the chain will cost them some of their locked 32 ETH balance. The amount taken depends on the severity of the attack and the number of validators that participated in it. Validators in Ethereum are assigned attestations and block proposals **on a schedule**. This is very different from the old Proof of Work (PoW) system, where everyone is constantly trying to race each other and come up with the next block before everyone else. This means that unlike PoW where a miner isn't guaranteed to earn a block reward unless they find the next block, Proof of Stake validators are guaranteed to have slow, steady income as long as they perform their duties. Initially, validator rewards simply accrued on the Beacon Chain against each validator and were inaccessible by their operator. As of the "Shapella" hard fork, validator rewards are routinely ["skimmed"](/node-staking/skimming.md) to the Execution Layer address defined by the validator's withdrawal credentials. Additionally, now that the Execution and Consensus layers have merged, validators are _also_ awarded with **priority fees** for transactions included in blocks they propose. These priority fees are paid **directly on the Execution layer** according the "Fee Recipient" set by the block proposer. If the validator is participating in [a MEV network](https://ethereum.org/en/developers/docs/mev/) to propose a block built by someone else, that builder will provide a supplemental tip to the validator known as a **MEV reward**. This is _also_ available directly on the Execution layer and is provided at the same time as priority fees. ## How Rocket Pool Works Unlike solo stakers, who are required to put 32 ETH up for deposit to create a new validator, Rocket Pool nodes only need to deposit 4 ETH per validator (called "bonded ETH"). This will be coupled with 28 ETH from the staking pool (called "borrowed ETH", which comes from liquid staker deposits in exchange for rETH) to create a new megapool validator. To the Beacon chain, a megapool validator looks exactly the same as a normal validator. It has the same responsibilities, same rules it must follow, same rewards, and so on. The only difference is in how the megapool validator was created on the execution layer, and how withdrawals work when the node operator decides to voluntarily exit the megapool validator. All of the creation, withdrawing, and rewards delegation is handled by Rocket Pool's **smart contracts** on the Ethereum chain. This makes it completely decentralized. ## The rETH Token As a Rocket Pool staker, your role is to deposit ETH into the deposit pool which will enable a node operator to create a new Beacon Chain validator. You can stake as little as **0.01 ETH**. In doing so, you will be given a token called **rETH**. rETH represents both **how much** ETH you deposited, and **when** you deposited it. The ratio includes rewards that Rocket Pool node operators earn from: - The Beacon Chain itself - Priority fees from block proposals - MEV rewards from block proposals More specifically, the value of rETH is determined by the following ratio: ``` rETH:ETH ratio = (total rETH supply) / (total ETH staked + total rETH contract balance + total rETH share of priority fees + total rETH share of MEV rewards) ``` Since the Beacon Chain rewards, priority fees, and MEV rewards will constantly accumulate, this means that **rETH's value effectively always increases relative to ETH**. The rETH/ETH exchange rate is updated approximately every 24 hours based on the Beacon Chain rewards earned by Rocket Pool node operators. To illustrate this point, here is a chart of rETH's value (relative to ETH) over time - as expected, it demonstrates slow but steady growth: ![rETH/ETH exchange rate over time](/static/image/reth_rate.3f861400e8.png) Let's do a simple example as a demonstration. Say you stake at the very beginning when 1 ETH = 1 rETH. You deposit 10 ETH and receive 10 rETH back. After a few years, the balances on the Beacon Chain grow due to validator rewards. Say 128 ETH had been staked with Rocket Pool and the sum of all validator balances on the Beacon Chain was 160 ETH. Then 1 ETH would be worth (128/160) = 0.8 rETH; conversely, 1 rETH would be worth (160/128) = 1.25 ETH. At this point, you could trade your 10 rETH back to Rocket Pool's smart contracts and receive 12.5 ETH in return. This means **as long as you are holding rETH**, you are staking with Rocket Pool! **You do not need to get it from Rocket Pool directly.** For example, you can purchase rETH on an exchange; as every rETH token is exactly the same, you will **automatically receive the benefits of staking just by holding the token!** ::: warning NOTE Trading rETH back for ETH directly with Rocket Pool is only possible when the staking pool has enough ETH in it to handle your trade. ETH in this pool comes from two sources: 1. ETH that other stakers have deposited, which hasn't been used by a node operator to create a new validator yet 2. ETH that was returned by a node operator after they exited one of their validators and received their rewards from the Beacon Chain It's possible that if node operators have put all of the staking pool to work on the Beacon chain, then the liquidity pool won't have enough balance to cover your unstaking. In this scenario, you may find other ways to trade your rETH back to ETH (such as a decentralized exchange like [Uniswap](https://app.uniswap.org/#/swap)) - though they will likely come with a small premium. ::: As an alternative to holding onto and eventually returning your rETH to the Rocket Pool, you are also free to **use it in DeFi applications**. You can trade it, lend it, use it as collateral... as rETH is a standard ERC20 token, you can use it in any way you could use any other token. ## Tax Implications Each country has its own tax laws, and it would be impossible to document them all here.\ In some countries, depositing ETH for rETH may be considered **a taxable event**. However, because rETH inherently accumulates value while the actual amount of the token you hold remains constant, simply holding it usually **does not generate any taxable events**. This may make rETH **a preferable staking token for long-term holding** if your country separates short-term and long-term capital gains taxes. Tax laws related to cryptocurrencies are in their infancy; each user should do their own research and consider speaking with a tax professional. Below are some helpful sites that offer tax assistance to users related to Ethereum. **This is not an official endorsement - users are advised to do their own research regarding tax implications and strategies**: - [https://koinly.io/](https://koinly.io/) - [https://cryptotaxcalculator.io/](https://cryptotaxcalculator.io/) - [https://rotki.com/](https://rotki.com/) ## How to Stake with Rocket Pool As described above, as long as you are holding the rETH token, you are a **Rocket Pool Staker**. We will summarize several common ways to acquire it here. ::: warning NOTE All of the methods described here rely on the usage of an Ethereum wallet such as [MetaMask](https://metamask.io/). If you have never used an Ethereum wallet before, we strongly encourage you to learn more about them and practice using them before staking with Rocket Pool. The sections below include some steps that are demonstrated with MetaMask as an example; they should translate to your wallet of choice easily enough for you to follow along. ::: ### Via Rocket Pool Directly With this method, you will use a web3 wallet (such as MetaMask) and interact with Rocket Pool's website to swap ETH for rETH and vice-versa. This method is **guaranteed** to provide you with the exact amount of rETH that your ETH is worth, since it's coming directly from Rocket Pool's smart contracts, but it can be somewhat expensive if the network's gas prices are high and you're staking a relatively small amount of ETH. ::: tip NOTE If you are practicing staking on the Hoodi Testnet, the direct method above is the only option currently supported. ::: [Click here to learn how to stake via Rocket Pool directly.](/liquid-staking/via-rp.md) ### Via a Decentralized Exchange on Ethereum (Layer 1) With this method, you will access a decentralized exchange such as [Balancer](https://docs.balancer.fi/) or [Uniswap](https://docs.uniswap.org/protocol/introduction) and purchase rETH using your token of choice, just like you would do any other token swap. Rocket Pool has officially created a [Balancer composable stable pool](https://docs.balancer.fi/products/balancer-pools/composable-stable-pools). Composable stable pools are ideal for tokens like rETH, because **they honor the true exchange rate reported by the Oracle DAO** - this means exchanging with it will have **much lower slippage** and **lower fees** than a conventional decentralized exchange, so you get a much better deal when buying or selling rETH. Because of this, and because it has a **smaller transaction fee** than swapping directly via Rocket Pool's website, we **strongly recommended** using Balancer if you want to stake via this route. If Balancer doesn't work for you, there is also an ETH-rETH liquidity pool on Uniswap. Note that this is a conventional pool, so **you will be affected by slippage and higher fees** if you use it, but the gas fee will still be lower than staking directly via Rocket Pool's website. [Click here to learn how to swap ETH for rETH via a decentralized exchange on Layer 1.](/liquid-staking/via-l1.md) ### Via a Decentralized Exchange on a Layer 2 Network With this method, you will start by bridging your existing ETH (or other tokens of choice) onto an Ethereum Layer 2 network such as [Optimism](https://www.optimism.io/) or [Arbitrum](https://arbitrum.io/) and then use a decentralized exchange on the network to purchase rETH. If you already have tokens on a Layer 2 network, this method is compelling because **the transaction fees are \~10x smaller than on the Ethereum mainnet**. However, if you have not used a Layer 2 network before, it does require a few additional steps to get set up. [Click here to learn how to swap ETH for rETH via a decentralized exchange on a Layer 2 network.](/liquid-staking/via-l2.md) ### Video Demonstration Community member **Kevster** has put together a helpful video that demonstrates each of these options step-by-step: For a more detailed writeup, select which method you would like to use from the links above and follow the guide for that section. --- url: /node-staking/responsibilities.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # A Node Operator's Responsibilities ## How Ethereum Staking Works As a reminder, staking in Proof of Stake is done via **validators**. A validator is essentially a single Beacon Chain address to which 32 ETH was deposited on the Execution layer. Validators are responsible for maintaining the consistency and security of the Beacon Chain. They do this by listening for transactions and new block proposals and **attesting** that the proposed block contains legal, valid transactions by doing some number crunching and verification behind the scenes. Occasionally, they get to propose new blocks themselves. Validators are assigned attestations and block proposals **on a randomized schedule**. This is very different from the old Proof of Work system, where everyone was constantly trying to race each other and come up with the next block before everyone else. This means that unlike Proof of Work where miners weren't guaranteed to earn a block reward unless they found the next block, Proof of Stake validators _are_ guaranteed to have slow, steady income as long as they perform their duties. If a validator is offline and misses an attestation or a block proposal, it will be **slightly penalized**. The penalties are quite small though; as a rule of thumb, if a validator is offline for X hours, it will make all of its lost ETH back after the same X hours of being back online. ### Rewards Validators earn consensus layer rewards from Attestation, Block Proposals, Sync Committees (rare), and Slashing Rewards (vanishingly rare). They also earn execution layer rewards from Priority Fees and MEV. As of 5/2026, overall APR is \~2.84%, with 2.63% being consensus layer APR, and 0.22% being execution layer APR. One place to find this info is the [rated explorer](https://explorer.rated.network/network?network=mainnet\&timeWindow=30d\&rewardsMetric=average\&geoDistType=all\&hostDistType=all\&soloProDist=stake). ### Penalties Validators are penalized for small amounts of ETH if they are offline and fail to perform their assigned duties. This is called **leaking**. If a validator violates one of the core rules of the Beacon chain and appears to be attacking the network, it may get **slashed**. Slashing is a forceful exit of your validator without your permission, accompanied by a relatively large fine that removes some of your validator's ETH balance. Realistically, the only condition that can cause a slashing is if you run your validator's keys on two nodes at the same time (such as a failover / redundancy setup, where your backup node accidentally turns on while your main node is still running). Don't let this happen, and **you won't get slashed**. Slashing _cannot occur_ from being offline for maintenance. Below is a table that shows the penalties that can happen to a validator: | Type | Layer | Amount | | --------------------- | --------- | --------------------------------------------------------------------------------- | | Missed Attestation | Consensus | -0.000011 ETH\* per attestation (-9/10 the value of a normal attestation reward) | | Missed Proposal | Consensus | 0 | | Missed Sync Committee | Consensus | -0.00047 ETH\* per epoch (-0.1 ETH total if offline for the whole sync committee) | | Slashing | Consensus | At least 1/32 of your balance, up to your entire balance in extreme circumstances | \*_Varies based on the total number of validators in the network. Approximated for 435,000 active validators._ ::: tip TIP As a rule of thumb, if you're offline for X hours (and you aren't in a sync committee), then you'll make all of your leaked ETH back after X hours once you're back online and attesting. ::: ## How Rocket Pool Nodes Work Unlike solo stakers, who are required to put 32 ETH up for deposit to create a new validator, Rocket Pool nodes only need to deposit 4 ETH per validator (called "bonded ETH"). This will be coupled with 28 ETH from the staking pool (called "borrowed ETH", which comes from liquid staker deposits in exchange for rETH) to create a new megapool validator. To the Beacon chain, a megapool validator looks exactly the same as a normal validator. It has the same responsibilities, same rules it must follow, same rewards, and so on. The only difference is in how the megapool validator was created on the execution layer, and how withdrawals work when the node operator decides to voluntarily exit the megapool validator. All of the creation, withdrawing, and rewards delegation is handled by Rocket Pool's **smart contracts** on the Ethereum chain. This makes it completely decentralized. A Rocket Pool **Node** is a single computer with an Ethereum wallet that was registered with Rocket Pool's smart contracts. The node can then create as many megapool validators as it can afford, all running happily on the same machine together. **A single Rocket Pool node can run many, many megapool validators.** Each megapool validator has a negligible impact on overall system performance; some people have been able to run hundreds of them on a single node. A megapool validator's upfront cost is 4 ETH. In addition, a node operator may optionally stake RPL to their node to qualify for additional rewards and to gain voting power within the protocol DAO. ## Rocket Pool Node Operators **Node operators** are the heart and soul of Rocket Pool. They are the individuals that run Rocket Pool nodes. ### Responsibilities They put ETH from the staking pool to work by running megapool validators with it, which earn staking rewards for the Rocket Pool protocol (and thus, increase rETH's value). Their job is straightforward, but crucially important: _run validators with the highest quality possible, and maximize staking rewards_. Node operators are responsible for: - Setting up a computer (either physical or virtual) - Configuring it correctly, including their home network if applicable - Installing Rocket Pool on it and setting up validators to perform validation - Securing it, both from outside and inside threats - Maintaining it for the life of their validators It's a big responsibility, and not a simple set-it-and-forget-it kind of job; you need to care for your node for as long as it's staking. With great responsibility, however, comes great rewards. ### Rewards Here are the major benefits of running a Rocket Pool node: - You earn your portion of each validator's ETH rewards, plus commission. - You run a validator with only 4 ETH of your own capital, with the remaining 28 ETH sourced from liquid stakers. - Each megapool validator earns 5% commission on rewards generated from the 28 protocol ETH. This comes to 35% more than solo staking (`(4 bonded + 28 borrowed * 0.05) / 4 = 1.35`). - By joining the [Smoothing Pool](/node-staking/fee-distrib-sp.md#the-smoothing-pool), you share execution layer rewards (priority fees and MEV) with other participants, providing more consistent returns instead of relying on the luck of block proposals. - Staking RPL earns you additional rewards. - RPL stakers earn a [share of protocol commission](/node-staking/megapools/staking-and-claiming-rewards.md#how-voter-share-is-distributed-to-megapool-rpl-stakers) (paid in ETH) proportional to their staked RPL. - You also earn issuance rewards (paid in RPL) on the RPL you stake. - At the end of a period (every 28 days), there's a snapshot of your RPL. - You can earn max yield on RPL **up to 15%** of the value of your total borrowed ETH. - You will earn yield on RPL beyond 15%, at a decreasing level. - You will get vote power based on the square root of your staked RPL, up to 150% of your bonded ETH. ### Limitations There are some limitations that come along with the rewards above: - If your node performs poorly and you actually end up losing ETH by the time you decide to exit your megapool validator, all of the lost ETH is coming out of your share. - For example: if you exit with a balance of 31 ETH, then your megapool validator lost 1 ETH from its initial 32 ETH deposit. You will receive 3 ETH, and 28 ETH will be returned to the staking pool. - Your staked RPL will be less liquid: - There's no limit on how much megapool staked RPL you can unstake, but you must wait 28 days after initiating unstaking before withdrawal. This prevents users from gaming the rewards system by staking RPL just in time for the 28-day rewards period, then withdrawing it immediately after the period. ### You've got this If you're fairly new to using the command line or computer maintenance, this can seem like a scary challenge. Luckily, one of Rocket Pool's most core principles is _decentralization_ - the fact that anyone, anywhere, can run a node if they have the determination and knowledge. While we can't help with determination, we _can_ help with knowledge. This section is packed with guides, walkthroughs, and information that will help you understand how to run a great Rocket Pool node. --- url: /index.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Rocket Pool Guides & Documentation > Decentralised Ethereum Liquid Staking Protocol [Get Started →](/protocol/) | [Contribute](https://github.com/rocket-pool/docs.rocketpool.net) ## Features - [**Overview**](/protocol/): Learn all about what Rocket Pool is, how it works, and how to use it with an easy-to-read series of articles. - [**Liquid Staking**](/liquid-staking/overview): Follow our detailed walkthroughs to practice using Rocket Pool on the Hoodi test network, from staking ETH to earning rewards. - [**Run a node**](/node-staking/responsibilities): Get started running a node with our detailed walkthroughs. Learn how to secure, maintain, monitor and upgrade your node. --- url: /legacy/atlas/lebs.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # 8-ETH Bonded Minipools When Rocket Pool was first launched, it supported two types of minipools: 1. A **16-ETH bond**, where the node operator provided 16 ETH and the remaning 16 ETH would come from the staking pool to create a complete (32 ETH) validator. 2. A **32-ETH temporary bond**, where the node operator would provide all 32 ETH so they could skip the initialization process and start validating on the Beacon Chain right away, then be given a refund of 16 ETH once the deposit pool had enough ETH to cover it. At this point it would turn into a normal 16-ETH bonded minipool. The latter was removed by a community vote several months into the protocol's life due to it no longer being necessary and resulting in long refund delays. The former represented the protocol's lowest bond amount because it guaranteed that if a node operator used Rocket Pool to attack the Ethereum protocol and had their _entire bond_ slashed, they would stand to lose just as much as the rETH stakers and would not come out ahead. Since Rocket Pool's launch, the community has done [significant research](https://dao.rocketpool.net/t/leb8-discussion-thread/899) on the security provided by this bond and found that it was very conservative. For all intents and purposes, a slashing of 16 ETH was deemed unrealistic and a 16-ETH bond effectively provided the same security benefits as a bond of only 8 ETH (plus the supplemental RPL requirement). Thus, backed by this research, the Atlas upgrade introduces a new type of minipool to the list: the **8-ETH bond**, colloquially referred to by the Rocket Pool community as a "LEB8" (Lower ETH Bond - 8 ETH). To create an 8-ETH minipool, the node operator only needs to provide **8 of their own ETH** (plus enough RPL to cover the collateral requirement - more on this in [RPL Collateral](#rpl-collateral)). It will then pull **24 ETH** from the deposit pool in order to complete the validator and get to work on the Beacon Chain. This **opens the door to new prospective node operators** that want to run a node but don't quite have 16 ETH. Further, it lets larger node operators **put more pool staker ETH to work** on the Beacon Chain earning rewards. As this works without meaningfully compromising security, everybody wins! In this guide, we'll cover three topics: - How 8-ETH bonded minipools actually work, and the reward numbers behind them - How to create a new 8-ETH minipool - How to migrate an _existing_ 16-ETH minipool down to an 8-ETH minipool without exiting Read on to learn more about each topic. ## How 8-ETH Bonded Minipools Work Mechanically, 8-ETH bonded minipools behave **identically** to every other minipool in the protocol. They still "own" a validator on the Beacon Chain (they represent that validator's withdrawal credentials), they still come with a commission (though the commission with Atlas **will be fixed at 14%** for all new minipools), and they provide all the same functionality that a 16-ETH bonded minipool does. The difference lies entirely in the numbers. ### Rewards From a profitability perspective (looking _purely_ at ETH rewards and ignoring RPL), 8-ETH bonded minipools with a 14% commission provide _more rewards_ to the node operator than even _16-ETH bonded minipools at 20% commission_ (which, as of Redstone, is the highest possible reward configuration). At the same time, they also provide more rewards to the _rETH holders_ as well due to the fact that the node operators are more efficiently putting the capital of the rETH holders to work. Let's walk through a simple example to illustrate. Say we are a node operator with 16 ETH available to stake (plus the required RPL bond). Say we've earned 1 ETH of rewards on the Beacon Chain per validator. Here's how the math works out for a single 16-ETH minipool with a 20% commission, versus two 8-ETH minipools at 14% commission: ``` 1x 16 ETH Minipool @ 20%: Rewards: 1 ETH Node Share = (16/32) + (16/32 * 0.2) = 0.5 + (0.5 * 0.2) = 0.5 + 0.1 = 0.6 ETH rETH Share = 1 - 0.6 = 0.4 ETH 2x 8 ETH Minipools @ 14%: Rewards: 2 ETH Node Share = ((8/32) + (24/32 * 0.14)) * 2 = (0.25 + (0.75 * 0.14)) * 2 = (0.25 + 0.105) * 2 = 0.71 ETH rETH Share = 2 - 0.71 = 1.29 ETH ``` In other words, a node operator will earn **18% more ETH** via two 8-ETH minipools than they would with a single 16-ETH minipool at 20% commission. ### RPL Collateral In order to create an 8-ETH minipool, node operators still need to stake enough RPL to cover the minimum collateral requirements for their node (accounting for all of its minipools of all bond sizes). These rules have been clarified with Atlas: - The **minimum RPL** per minipool is **10% of the _borrowed_ amount** - The **maximum RPL** per minipool is **150% of the _bonded_ amount** For a 16-ETH minipool, this remains unchanged; the minimum is 1.6 ETH worth of RPL, and the maximum is 24 ETH worth of RPL. For an 8-ETH minipool, this becomes a **minimum of 2.4 ETH worth of RPL** (10% of the borrowed amount, which is 24 ETH) and a **maximum of 12 ETH worth of RPL** (150% of the bonded amount). These numbers were selected by the Rocket Pool community [as part of a governance vote](https://vote.rocketpool.net/#/proposal/0x7426469ae1f7c6de482ab4c2929c3e29054991601c95f24f4f4056d424f9f671). ## Creating a New 8-ETH Minipool The process to create a new minipool with an 8-ETH bond is identical to the process for creating a 16-ETH minipool. Simply run the following command: ```shell rocketpool node deposit ``` When prompted for your bond amount, select `8 ETH`: ``` Your eth2 client is on the correct network. NOTE: by creating a new minipool, your node will automatically claim and distribute any balance you have in your fee distributor contract. If you don't want to claim your balance at this time, you should not create a new minipool. Would you like to continue? [y/n] y Please choose an amount of ETH to deposit: 1: 8 ETH 2: 16 ETH 1 Your minipool will use the current fixed commission rate of 14.00%. You currently have 8.00 ETH in your credit balance. This deposit will use 8.000000 ETH from your credit balance and will not require any ETH from your node. ... ``` ::: tip NOTE This example also shows usage of the [**new Deposit Credit System**](/node-staking/credit.md). Since the node operator has 8 ETH in credit, creating this 8-ETH minipool is free! ::: That's all there is to it! The rest of the process is the same as [the usual minipool creation instructions](/node-staking/create-validator.md). --- url: /legacy/atlas/whats-new.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # The Atlas Update ::: tip NOTE Atlas was deployed on `18 April 2023, 00:00 UTC`. Please visit [here](/legacy/houston/whats-new.md) to read about Houston, the latest protocol upgrade. ::: This page describes the major changes that Rocket Pool's next major update, titled **Atlas**, brings to the protocol including updates to both the Smart Node stack and to the Rocket Pool protocol in general. Please read through this page thoroughly to understand all of the differences between the previous version of Rocket Pool (Redstone) and Atlas. ## New Protocol Features Atlas brings about some exciting new features that are based on both community feedback and changes to the Ethereum protocol itself. Below is a brief list of these changes - click on any of them to learn more about it. ### Shapella and Withdrawals The Ethereum protocol is preparing to undergo its next major upgrade: **Shanghai** on the Execution layer, and **Capella** on the Consensus layer - since these are now interconnected, both will occur at the same time. Ethereum users have affectionately come to call the combined upgrade [**"Shapella"**](https://blog.ethereum.org/2023/02/21/sepolia-shapella-announcement) accordingly. Shapella introduces **withdrawals** to the Beacon Chain, meaning node operators are now able to access the ETH that is currently locked on the Beacon Chain. This comes in two flavors: - Partial withdrawals (**skimming**), where your rewards (your excess Beacon Chain balance over 32 ETH) are sent to your minipool on the Execution Layer. This is done _automatically by the protocol itself_ every so often (about once every four or five days on Mainnet). - **Full withdrawals**, where you exit your validator from the Beacon Chain and its entire balance is sent to your minipool on the Execution Layer. This is done _automatically by the protocol itself_ once your validator has been exited from the chain long enough. Atlas introduces a new delegate contract for minipools that allows node operators to **distribute** the minipool's ETH balance, splitting it evenly between the node operator and the rETH holders (plus commission, of course) at any time. This gives node operators **immediate access** to their Beacon Chain rewards! It also puts the rETH holders's share back into the deposit pool, so it can be used to unstake rETH for ETH at the protocol's exchange rate (or to create new minipools). ### 8-ETH Bonded Minipools One of the most anticipated changes made in Atlas is the introduction of the ability to only provide 8 ETH to make a minipool instead of 16 ETH. Minipools with only 8 ETH bonded by their owning node operator are matched with **24 ETH** from the staking pool (provided by rETH holders) in order to make a validator. This significantly reduces the capital requirement for running your own validator _and_ results in greater returns for both the node operator and the rETH stakers! In fact, running two 8-ETH minipool instead of one 16-ETH minipool will provide **over 18% more rewards** - even if the 16-ETH minipool has a commission rate of 20%. Creating an 8 ETH minipool requires that you stake a **minimum of 2.4 ETH worth of RPL** and a **maximum of 12 ETH worth of RPL**. These represent 10% of the amount you're _borrowing_ from the protocol, and 150% of the amount you're _bonding_ (staking) yourself. New minipools can be created with either 8 ETH or 16 ETH. 16 ETH minipools are unchanged from how they work today, and are available for users that want to minimize their exposure to the RPL token. To learn how to make new minipools using an 8 ETH bond, please visit the [minipool creation guide](/node-staking/create-validator.md). Also, once Atlas has been applied, node operators can **migrate existing 16-ETH minipools directly into 8-ETH minipool without needing to exit**. This will give them 8 ETH back in [deposit credit](/node-staking/credit.md), which can be used to create a **new 8-ETH minipool for free**! To learn more about 8-ETH bond minipools, please visit the [bond reduction guide](/node-staking/leb-migration.md). ### Solo Validator Conversion Part of the Shapella upgrade involves the ability for solo validators to [change their validators' withdrawal credentials](https://notes.ethereum.org/@launchpad/withdrawals-faq) from the original (now unused) BLS-based withdrawal key to an address on the Execution layer. This address will be the recipient for all of that validator's rewards and its full ETH balance once it exits the Beacon Chain. Regular Rocket Pool node operators don't need to worry about any of this, as the protocol automatically set this up for your minipools when you created them. _However_, as part of this new requirement for solo validators, Atlas brings an exciting opportunity: the ability to **create a special minipool** that will become the withdrawal address for your **existing solo validator**. In other words, this will allow you to **directly convert a solo validator into a Rocket Pool minipool without needing to exit it!** This means you will get all the benefits of Rocket Pool minipools, including: - The ability to convert your one validator (with a 32 ETH bond) into **four minipools** (each with an 8 ETH bond), effectively **quadrupling** your presence on the Beacon Chain - Commission on the portion of those minipools provided by rETH stakers - Access to Rocket Pool's [Smoothing Pool](/node-staking/fee-distrib-sp.md#the-smoothing-pool) to pool and evenly distribute rewards from block proposals and MEV To learn more about converting a solo validator into a minipool, please visit the [Converting a Solo Validator into a Minipool](/node-staking/solo-staker-migration.md) guide. ## New Smart Node Features In addition to core changes to the Rocket Pool protocol, Atlas also brings some exciting upgrades to the Smart Node stack itself which are present in v1.9.0. ### Automatic Rewards Distributions If you're already an active Rocket Pool node operator, you may be familiar with the `rocketpool_node` process that handles certain automated processes. For example, it ensures you have the correct fee recipient and automatically runs the second `stake` transaction for you after `prelaunch` minipools pass the 12-hour scrub check. Starting with Atlas, the `node` has a new duty: **automatic distribution of minipool rewards!** This is due to the way [the Shapella upgrade works](/node-staking/skimming.md), by skimming your rewards from the Beacon Chain into your minipool every few days. Whenever one of your minipools reaches a balance larger than a user-specified threshold (default of 1 ETH), the node will automatically run `distribute-balance` on it. This will send your portion of the rewards to your withdrawal address, and the pool staker's portion back to the deposit pool. Changing the threshold can be done in the `Smartnode and TX Fees` section of the `service config` TUI, under the `Auto-Distribute Threshold` setting. ### Unified Grafana Dashboard By popular demand, we have created a new [**Grafana dashboard**](https://grafana.com/grafana/dashboards/24900-rocket-pool-dashboard-v1-4-0/) to help node operators track and assess the status, progress, and overall health of their nodes: ![](/static/image/grafana-1.3.b0fda448f5.jpg) It comes with the following highly requested features: - Support for all Execution and Consensus clients in a single dashboard - no more changing dashboards based on which clients you're using! - Execution client stats, including CPU and RAM usage, and peer count - Attestation accuracy tracking which follows how "correct" your attestations were for the previous epoch, so you know how far off from optimal rewards you're getting - Tracking of the Smoothing Pool's balance - Tracking of claimed and unclaimed rewards, now including ETH from the Smoothing Pool - Stats about Rocket Pool's Snapshot-based governance votes - Room for tracking a second SSD's used space and temperature if you have one for your OS and a different one for your chain data - And more! You can import the new dashboard from the official Grafana service using ID `21863` by following our [Grafana guide](/node-staking/grafana.md). This new dashboard was a labor of love that involved extensive help from community member **0xFornax** - thank you for all of your hard work! ### Nimbus Changes Smart Node v1.9.0 introduces **split mode support** for Nimbus! Instead of running the Beacon Node and Validator Client inside a single process / container, the Smart Node will now run them in separate containers like the other clients. This has the following benefits: - Nimbus now supports **fallback clients** (a secondary Execution client and Beacon Node that Nimbus's Validator Client can connect to when your primary clients are down for maintenance, such as resyncing). - Nimbus is now supported in **Externally-Managed (Hybrid) Mode**, so you can couple the Validator Client that the Smart Node manages to an external Beacon Node that you maintain on your own. - The Beacon Node no longer needs to be restarted after the addition of new minipools, meaning you don't lose attestations while it reconnects to its peers. ### Lodestar Support [Lodestar](https://chainsafe.github.io/lodestar/) is now supported as an option for your Consensus Client of choice! This is the newest addition to be officially accepted onto [Ethereum's Launchpad](https://launchpad.ethereum.org/en/lodestar), and it's ready for validation. Lodestar supports many of the great features you've come to love from the other clients, including Doppelganger Detection, MEV-Boost, externally-managed clients (Hybrid Mode), and more! ### New Network Snapshot System On a slightly more technical note, v1.9.0 introduces a brand new system for quickly capturing a snapshot of the state of **everything about your node** on both the Execution and the Consensus layers. Under the hood, this system leverages [MakerDAO's multicall contract](https://github.com/makerdao/multicall) and Will O'Beirne's [Ethereum Balance Checker contract](https://github.com/wbobeirne/eth-balance-checker) to batch thousands of individual Execution client queries up into a single request. This makes the `node` process much less taxing on the Execution client for node operators with a large number of validators, and should significantly reduce its CPU load which will improve attestations and overall rewards. This new system hasn't made its way into the CLI itself yet, so any commands you run there (such as `rocketpool minipool status`) will still use the old single-query setup. Over time we'll introduce it into the CLI too, which will make all of its commands lightning fast (_except for waiting for transactions to be validated, that still takes a while_). --- url: /legacy/houston/getting-started.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Houston Quick-Start Whether you're a seasoned Node Operator, rETH holder or curious onlooker, this page will help you get started with exploring the new features included in Houston. ## ### Initializing Voting Power First and foremost, the most important step if you are **Node Operator** is to [initialize voting](/legacy/houston/participate.md#initializing-voting) to unlock your voting power. Nodes who've initialized voting are included when the network's total voting power is calculated. At the genesis of Houston, pDAO voting is disabled until a sufficient number of nodes have initialized voting. This is to prevent rogue proposals from passing while total voting power and quorum is low. After enough nodes have initialized voting, a switch will be flipped and pDAO will have the helm. To initialize voting power, use this command in the smartnode: ```shell rocketpool pdao initialize-voting ``` You only need to do this once. Initializing voting will ensure that your node's voting power is included in future on-chain proposals and allow you to vote on them. ### Setting your Snapshot Signalling Address Secondly, you'll want to set your snapshot signalling address. This allows node operators to participate in Snapshot votes in their browser or mobile device without having to expose their node keys to a hot wallet. Setting this up involves a handful of steps, so you'll want to follow this guide: [Setting your Snapshot Signalling Address](/legacy/houston/participate.md#setting-your-snapshot-signalling-address). ### Delegating on-chain Voting Power If you want to delegate on-chain voting power to a community member of your choosing, click [here](/legacy/houston/participate.md#delegating-voting-power) to learn how. ## # Guides [Full Houston Overview](/legacy/houston/whats-new.md) presents the fully on-chain Protocol DAO and introduces new features such as staking ETH on behalf of a node, setting an RPL withdrawal address, and time based balance and RPL submissions. Houston smart contract audits can be found here as well. [The Protocol DAO](/legacy/houston/pdao.md) discusses who and how the pDAO governs Rocket Pool. This page will fill you in on how pDAO duties such as treasury spends can be executed on-chain, along with the role of the all new Security Council. It'll also walk you through the lifecycle of a pDAO proposal and explain some of the measures taken to prevent spam and gun down malicious proposals. [Participating in Proposals](/legacy/houston/participate.md) includes a detailed step-by-step guide on how Node Operators can participate in pDAO proposals. If you're keen on raising an on-chain proposal, voting or delegating voting power, this is the guide for you. [Stake Eth on Behalf of a Node](/legacy/houston/stake-eth-on-behalf.md) goes over the steps for staking ETH on behalf of a node. It's a new feature introduced in Houston to facilitate single depositor scenarios. We'll walk through how to do this on a testnet if you want to try it out before staking real ETH on mainnet. [RPL Withdrawal Address](/legacy/houston/rpl-withdrawal-address.md) shows you how to set an RPL withdrawal address for your node. This is useful if you want to enable a separate entity to supply the RPL insurance collateral for a node. --- url: /legacy/houston/nonsmartnode-setup.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Voting setup for non-smartnode users Some users (eg, Allnodes users) don't use the smartnode and may need to set up voting using direct contract interaction. This guide contains both a minimal and a complete setup guide for such users. ::: tip Your node address should be loaded onto a hardware wallet for this. ::: ## Minimal setup guide This allows your delegate to vote for you on-chain and offchain. You'll be able to override your delegate on-chain, but not off-chain. - Use etherscan to initialize vote power ("Connect to Web3" with node address) with a delegate [https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F2](https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F2) - You can find delegates at [https://delegates.rocketpool.net/](https://delegates.rocketpool.net/) ## Full setup guide Use etherscan to initialize vote power ("Connect to Web3" with node address) - \[recommended for most] Initialize voting with a different node as the delegate [https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F2](https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F2) - You can find delegates at [https://delegates.rocketpool.net/](https://delegates.rocketpool.net/) - Remember you will always be able to override your delegates - Initialize voting with your own node as the delegate [https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F1](https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F1) - Here you'll be responsible for voting every time - I would mostly suggest this option for folks that wish to be delegates since they _do_ need to vote every time. - If your node was registered after Houston: - You will already have your vote power initialized with your own node as the delegate - You can set a new delegate with [https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F3](https://etherscan.io/address/0xA9d27E1952f742d659143a544d3e535fFf3Eebe1#writeContract#F3) Set snapshot signalling address: - Go to [https://node.rocketpool.net/signalling-address](https://node.rocketpool.net/signalling-address) and connect your node address - Put in your desired snapshot signalling address and sign the message to get the r, s, and v arguments you'll need - Note: your snapshot signalling address MUST NOT be your node address - In a new tab, go to [https://etherscan.io/address/0xc1062617d10Ae99E09D941b60746182A87eAB38F#writeContract#F2](https://etherscan.io/address/0xc1062617d10Ae99E09D941b60746182A87eAB38F#writeContract#F2) - "Connect to Web3" with node address - Fill in the arguments with your signalling address and the r, s, v parameters given in the previous step --- url: /legacy/houston/participate.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Participating in on-chain pDAO Proposals Any node with a non-zero voting power may raise or participate in a pDAO proposal at any time. Proposals can be one of the following types: - Changing pDAO settings - One-time treasury spends - Repeat treasury spends (management committees) - Security council membership For greater detail and rationale, refer to [proposal types](https://rpips.rocketpool.net/RPIPs/RPIP-33#proposal-types). It's important to understand that a pDAO proposal is an on-chain entity that exists to execute changes at the protocol level. ## Governance Process A proposal should be forecasted by the governance process before it ends up on-chain. Changes to the Rocket Pool protocol and proposed, voted, and executed using a strict, yet transparent governance process. The process begins with an informal discussion of an idea within the Discord community. This idea then progresses to formal discussions in the [#governance](https://discordapp.com/channels/405159462932971535/774497904559783947) channel on Discord and the [DAO Forum](https://dao.rocketpool.net/), where it undergoes thorough research, modeling, and scrutiny in preparation for a [Rocket Pool Improvement Proposal (RPIP)](https://rpips.rocketpool.net/). Following this, a draft RPIP is prepared and reviewed by designated RPIP reviewers to ensure its quality and readiness for presentation to the DAO. The draft proposal is then presented to the DAO on the forum for further review, feedback, and incorporation of any necessary changes. Once the proposal has been refined based on community input, a poll is raised on the DAO forum to gauge readiness for finalizing the RPIP text. If the poll passes, indicating community approval, the RPIP is marked final and ready for a Protocol DAO vote, which is conducted via Snapshot to determine whether the proposal should be implemented. From here, the Oracle DAO will raise an on-chain proposal. There is a window in which the Protocol DAO, Oracle DAO and community can review the proposal. If consensus is reached, the proposal is executed and changes are applied to the protocol. A handy dandy visual representation of this process can be found on the [Rocket Pool website](https://rocketpool.net/governance/process). ## Prerequisite Please read the [lifecycle of a proposal](/legacy/houston/pdao.md#lifecycle-of-a-pdao-proposal) before proceeding. It'll explain the differences between all the voting periods and the actions that can be taken during each period. The rest of this page will walk you through the steps required for participating in on-chain pDAO proposals. ## Initializing Voting If you are a node operator who registered before the Houston upgrade, you need to initialize voting to unlock voting power. Keep in mind that having at least one minipool is a requirement for having voting power. ```shell rocketpool pdao initialize-voting ``` This command will raise the prompt below. Please read it carefully: ``` Thanks for initializing your voting power! You have two options: 1. Vote directly (delegate vote power to yourself) This will allow you to vote on proposals directly, allowing you to personally shape the direction of the protocol. 2. Delegate your vote This will delegate your vote power to someone you trust, giving them the power to vote on your behalf. You will have the option to override. You can see a list of existing public delegates at https://delegates.rocketpool.net, however, you can delegate to any node address. Learn more about how this all works via: /en/legacy/houston/participate#participating-in-on-chain-pdao-proposals Please type `direct` or `delegate` to continue: ``` - If you respond with `direct`, voting power will be initialized to your node and you'll be able to vote directly on Protocol DAO proposals. - If you respond with `delegate`, you'll have the opportunity to save a bit of gas by initializing voting and [setting a delegate](/legacy/houston/participate.md#delegating-voting-power) within the same transaction. You only need to do this once. It configures the initial snapshot information for a node. After you initialize voting, every action taken will update your node's snapshot information. Once your voting power is initialized, you can check how much you have using the following smartnode command: ```shell rocketpool pdao status ``` :::tip NOTE Whenever a new proposal is created, a voting tree representing a snapshot of the network's voting power and delegate info is created in conjunction with the new proposal. This means your node's voting power won't be included in a proposal if it was raised before you initialized voting. `rocketpool pdao status` will display your node's voting power at the latest block, which may or may not be representative of your voting power on a particular proposal. ::: ## Auto Initialize Vote Power Smart Node version `1.13.8` introduces a new feature **Auto Initialize Vote Power**, which is designed to automatically initialize voting power on nodes who have not yet done so. Automatically initialized voting power is self-delegated. This feature can be configured in the Smart Node settings by running `rocketpool service config` and navigating to the \* \*Smart Node and TX Fees\*\* section. ![](/static/image/auto_init_vp.969ac645c7.png) The **Auto-Init Vote Power Gas Threshold** is a limit (in gwei) on this automatic transaction. You can opt out of this task by setting the threshold to 0. Feel free to opt out if your node was registered after the Houston upgrade or if voting power is already enabled. ## Setting your Snapshot Signalling Address Setting your Snapshot signalling address will allow you to participate in Snapshot votes on a browser or mobile device without having to expose node keys to a hot wallet. There are a few things to prepare: - Your node's address - An address you want to use for snapshot voting (signalling address) You'll be signing a message saying that your node's address can delegate to the new address. This message states your intent to use your wallet address as a Snapshot signalling address. Select which network you're using from one of the tabs below. **Hoodi Testnet** If you're trying this out on Hoodi testnet, you can sign on this page: [https://testnet.node.rocketpool.net/signalling-address](https://testnet.node.rocketpool.net/signalling-address) **Mainnet** If you're ready to configure this on mainnet, go here instead: [https://node.rocketpool.net/signalling-address](https://node.rocketpool.net/signalling-address) :::danger WARNING Do not load your node's private key onto a hot wallet. Please choose another account to be your signalling address. After setting the signalling address, you can use it to vote on Snapshot with your node's voting power. ::: Start by **connecting the address you want to use as a signalling address** to the website using MetaMask, WalletConnect, or any of the other methods the website supports. You will then be presented with this dialog to look up your node address. Next, you'll enter your node address then click the orange "Find" button. This will check if the address is a registered node and then bring you to the next step. :::tip TIP **Make sure you have the correct node address before doing this!** if you need to confirm your node's address, you can quickly retrieve it via the CLI using the `rocketpool node status` command. ::: Once you've signed in and confirmed your node address, you'll see your **Snapshot signalling address**. It should be the same as the account you've signed into the site with. Double check that this is correct before proceeding. Once you're confident that you're signed into the desired account, click the orange "Sign Message" button. You'll see a prompt in your wallet extension app to sign the following message: ``` `snapshot signalling address` may delegate to me for Rocket Pool governance ``` Signing won't cost you any gas but setting will. After you sign, the frontend will give you a command to paste into the smartnode. Go ahead and paste it into your smartnode's CLI and follow the prompted steps. The command should look something like this: ```shell rocketpool pdao set-signalling-address `snapshot signalling address` `EIP712 signature` ``` If you see this message in your CLI, you're all set! ``` The node's signalling address was successfully set to `snapshot signalling address` ``` :::tip TIP Don't worry if you accidentally close the site or lose track of the command. You can simply repeat the steps and **sign again using the same node address and signalling address**. The frontend uses `signer.Signmessage()` from the ethers library, which means your signature is deterministic given the same input. Click [here](https://docs.ethers.org/v6/api/providers/#cid_865) to learn more. ::: Clearing your signalling address is pretty easy, just use this command in the CLI: ```shell rocketpool pdao clear-signalling-address ``` ## Allowing RPL Locking You may ignore this step if you are only interested in voting on a proposal. Allowing RPL locking is only required for those who wish to propose or challenge a proposal. RPL locking is required for proposing and challenging. By default, locking RPL for any purpose, will be disabled. Node operator's will opt-in to performing governance activities by enabling the locking of RPL from their node or primary withdrawal address. You can do so using this command in the Smart Node: ```shell rocketpool node allow-rpl-locking ``` This will prompt you to allow the locking of RPL when creating or challenging governance proposals. Conversely you can use the following command to opt-out of RPL locking: ```shell rocketpool node deny-rpl-locking ``` ::: tip NOTE Locked RPL acts the same way as regular staked RPL for the purposes of rewards, voting, and collateral requirements. Locked RPL is not counted towards thresholds for withdrawing RPL. ::: ## Delegating Voting Power A node operator can elect to delegate their voting power to another node operator. The only requirement is that your delegate is a registered node. To delegate on-chain voting power to another node, use the following command: ```shell rocketpool pdao set-voting-delegate `address` ``` ::: tip NOTE If you've delegated your voting power to another node operator, you can reset this by setting the delegate address to your own node's address. ::: - During phase 1 of a proposal: **Voters** and **Delegates** may cast their vote on a proposal. - During phase 2 of a proposal: **Node Operators** who have delegated their vote get the opportunity to overturn their Delegate's vote, if they disagree. If you are a node operator with delegated voting power, you must vote during voting phase 1 for the delegated voting power to count towards the proposal. Your vote in phase 1 will be worth your **local voting power + delegated voting power**. Your vote in phase 2 is worth your **local voting power** only. ## Creating a Proposal In order to be eligible to propose, a node must meet a few requirements: - Included in snapshotting (either by [initializing voting](/legacy/houston/participate.md#initializing-voting) or by registering post Houston) - Must have at least one minipool - Has non-zero voting power - Has allowed [RPL locking](/legacy/houston/participate.md#allowing-rpl-locking) - Has an RPL stake (minus any already locked RPL) greater than the proposal bond Proposals exist to change parameters and execute code at the protocol level! There should be discussion and consensus through the [governance](/legacy/houston/participate.md#governance-process) process before a proposal is created on chain. Use the command `rocketpool pdao propose` to bring up a menu of options ``` COMMANDS: rewards-percentages, rp Propose updating the RPL rewards allocation percentages for node operators, the Oracle DAO, and the Protocol DAO one-time-spend, ots Propose a one-time spend of the Protocol DAO's treasury recurring-spend, rs Propose a recurring spend of the Protocol DAO's treasury recurring-spend-update, rsu Propose an update to an existing recurring spend plan security-council, sc Modify the security council setting, s Make a Protocol DAO setting proposal ``` Each of these commands will prompt you with a list of inputs to create your desired proposal. In this guide, we'll invite a node to the security council to serve as an example. To raise a proposal to invite a node to the security council, you would use the command: ```shell rocketpool pdao propose security-council invite ``` Keep in mind that this step will have some slight variation depending on the type of proposal. This particular command: `rocketpool pdao propose security-council invite` will prompt you to enter an ID followed by a member address. ``` Please enter an ID for the member you'd like to invite: (no spaces) test-member Please enter the member's address: 0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145 ... gas estimations ... Are you sure you want to propose inviting test-member (0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145) to the security council? [y/n] ``` After this is included in a block, a pDAO proposal will be created! The proposal will enter the [vote delay period](/legacy/houston/pdao.md#vote-delay-period) upon creation. ## Viewing the State of a Proposal Every proposal is assigned a `proposalID`. In this case, our proposal to invite `0xBdbc...` to the security council is represented with `ID 71`. There are a few ways to view the state of the proposal. One method will display a list of every pdao proposal along with their state (pending, succeeded, executed, etc). The second method displays in-depth details about a specific proposal. **Viewing a List of Proposals** To list all proposals, use the following command: ```shell rocketpool pdao proposals list ``` This will display a list of all proposals and their state ``` 1 Pending proposal(s): 71: invite test-member (0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145) to the security council - Proposed by: 0x681B8BBf08708e64694005c7Dc307b381b4D1A7D Succeeded proposal(s): Executed proposal(s): Destroyed proposal(s): Quorum not Met proposal(s): Defeated proposal(s): Expired proposal(s): ``` Here we can see that our proposal `invite test-member` has an ID of 71 and is in the pending state. In this state, [challengers](/legacy/houston/pdao.md#challenge-process) can dispute the validity of the merkle pollard (used to calculate voting power) supplied by the proposer. When `proposal.vote.delay.time` ends, the proposal will transition into active voting phases. Feel free to review [lifecycle of a proposal](/legacy/houston/pdao.md#lifecycle-of-a-pdao-proposal) for a refresher. **Viewing Proposal Details** Now that you have the proposal ID, you can view the status of your proposal using this command: ```shell rocketpool pdao proposals details `proposal-id` ``` This is where you can view all the information in regards to a specific proposal. For example, the execution payload, what phase the proposal is in, and vote direction. ``` Proposal ID: 71 Message: invite test-member (0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145) to the security council Payload: proposalSecurityInvite(test-member,0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145) Payload (bytes): f944c19f0000000000000000000000000000000000000000000000000000000000000040000000000000000000000000bdbcb42dd8e39323a395b2b72d2c8e7039f1f145000000000000000000000000000000000000000000000000000000000000000b746573742d6d656d626572000000000000000000000000000000000000000000 Proposed by: 0x681B8BBf08708e64694005c7Dc307b381b4D1A7D Created at: 12 Mar 24 06:15 UTC State: Pending Voting start: 12 Mar 24 06:20 UTC Challenge window: 30m0s Voting power required: 90943818825 Voting power for: 0 Voting power against: 0 Voting power abstained: 0 Voting power against: 0 Node has voted: no ```

NOTE

The state of this sample proposal is `Pending`. This indicates that the proposal can be challenged, before moving onto `Active (Phase 1)`. No voting can take place during the `Pending` state. ## Voting on a Proposal During a voting period, **Node Operators** and **Delegates** can cast a vote with one of four options: ``` 1. Abstain: The voter's voting power is contributed to quorum but is neither for nor against the proposal. 2. For: The voter votes in favor of the proposal being executed. 3. Against: The voter votes against the proposal being executed. 4. Veto: The voter votes against the proposal as well as indicating they deem the proposal as spam or malicious. ``` Their voting power will be applied to the option of their choosing. Voting power is a function of "effective RPL stake." A more detailed reading can be found in the [rocketpool-research repo](https://github.com/rocket-pool/rocketpool-research/blob/master/Protocol%20DAO/kane/pDAO%20Replacement/pDAO.md#overview-of-on-chain-voting). ::: tip NOTE If you are a node operator with delegated voting power, you must vote during voting phase 1 for the delegated voting power to count towards the proposal. Your vote in phase 1 will be worth your local voting power + delegated voting power. Your vote in phase 2 is worth your local voting power only. Please keep in mind that a node may vote once and only once on a proposal, so choose carefully. ::: Use this command to cast a vote: ```shell rocketpool pdao proposals vote ``` You'll be prompted to select a proposal to vote on if there is at least one proposal in an active voting phase. The menu should display all of the proposals your node is eligible to vote on: ``` 1: proposal 71 (message: 'invite test-member', payload: proposalSecurityInvite(test-member,0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145), phase 1 end: 14 Mar 24 05:40 UTC, vp required: 0.00, for: 0.00, against: 0.00, abstained: 0.00, veto: 0.00, proposed by: 0x681B8BBf08708e64694005c7Dc307b381b4D1A7D) 2: proposal 72 (message: 'replace langers-not-his-eoa (0xaC1396c21Eaf6630113516C69d63b7CB59B98b3E) on the security council with tpan (0x6E9E4Cc0A8172349E049128574E1fb85B8D3CE9E)', payload: proposalSecurityReplace(0xaC1396c21Eaf6630113516C69d63b7CB59B98b3E,tpan,0x6E9E4Cc0A8172349E049128574E1fb85B8D3CE9E), phase 1 end: 14 Mar 24 05:40 UTC, vp required: 0.00, for: 0.00, against: 0.00, abstained: 0.00, veto: 0.00, proposed by: 0xe2fC31d61E28BB16c0857D4682AB3616FA7A793d) 3: proposal 73 (message: 'set proposal.vote.delay.time', payload: proposalSettingUint(rocketDAOProtocolSettingsProposals,proposal.vote.delay.time,60), phase 1 end: 14 Mar 24 05:41 UTC, vp required: 0.00, for: 0.00, against: 0.00, abstained: 0.00, veto: 0.00, proposed by: 0x681B8BBf08708e64694005c7Dc307b381b4D1A7D) ``` After selecting an option, you'll be asked how you want to cast your vote. ``` How would you like to vote on the proposal? 1: Abstain 2: In Favor 3: Against 4: Veto ``` Selecting an option will then display your voting power, and then prompt you to send the transaction: ``` Your current voting power: 20123617964 +============== Suggested Gas Prices ==============+ | Avg Wait Time | Max Fee | Total Gas Cost | | 15 Seconds | 76 gwei | 0.0176 to 0.0265 ETH | | 1 Minute | 56 gwei | 0.0127 to 0.0190 ETH | | 3 Minutes | 56 gwei | 0.0127 to 0.0190 ETH | | >10 Minutes | 56 gwei | 0.0127 to 0.0190 ETH | +==================================================+ These prices include a maximum priority fee of 2.00 gwei. Please enter your max fee (including the priority fee) or leave blank for the default of 56 gwei: ``` You've successfully voted on the proposal once the transaction is included in the block! At this point, you may use `rocketpool pdao proposal details ` to view the state of the proposal. A proposal needs to reach `proposal.quorum` **voting power required** and a majority **voting power for** for it to be successful. ``` Voting power required: 140970562215 Voting power for: 197980809837 Voting power against: 0 Voting power abstained: 0 Voting power against: 0 Node has voted: In Favor ``` For the example above to pass, the voting power needs to exceed a quorum of `140970562215` voting power. There is `197980809837` voting power in favor and no votes against or abstained. The proposal is poised for success and ready for execution by the end of `proposal.vote.phase2.time`. ## Executing a Successful Proposal Congrats! Your proposal has passed! Now all that's left to do is to execute the proposal. Keep in mind that anybody can be the executor to a proposal. To execute a successful proposal, type in the command: ```shell rocketpool pdao execute ``` Selecting an option will prompt you to send a transaction. Once this transaction is included in a block, the change will be applied to the Rocket Pool protocol! ``` Please select a proposal to execute: 1: All available proposals 2: proposal 71 (invite test-member (0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145) to the security council)', proposalSecurityInvite(test-member,0xBdbcb42DD8E39323a395B2B72d2c8E7039f1F145) ``` ## Claiming Bonds and Rewards Proposers or Challengers may claim their bonds upon conclusion of a proposal. Depending on the outcome of a proposal, a Proposer or Challenger may or may not be able to claim their `proposal.bond` and `proposal.challenge.bond`. Here are some rules that dictate the conditions in which bonds can be claimed: - If a proposal is defeated, the proposer forfeits their bond which is divided proportionally amongst the challengers who contributed to the proposal's defeat. All other challengers receive their bond back only. - Contributing to the defeat of a proposal means a challenger submitted an index which was later proven to be incorrect by the proposers inability to reply to a challenge. It is possible that there are multiple incorrect indices but only those that resulted in the defeat of the proposal share the reward. All other challengers receive their bond back only. - If a challenger challenges a node, the proposer responds, and the proposal does not get defeated. The proposer can claim the challenge bonds from the invalid challenges. - If a proposal is defeated, the proposer forfeits their bond which is divided proportionally amongst the challengers who contributed to the proposal's defeat. Use this command to claim bonds: ```shell rocketpool pdao claim-bonds ``` This will display every proposal you're eligible to claim bonds from. You can either claim bonds from a specified proposal, or you can claim bonds and rewards from all eligible proposals. ``` Please select a proposal to unlock bonds / claim rewards from: 1: All available proposals 2: Proposal 42 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) 3: Proposal 43 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) 4: Proposal 44 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) 5: Proposal 46 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) 6: Proposal 47 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) 7: Proposal 48 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) 8: Proposal 49 (proposer: true, unlockable: 21.00 RPL, rewards: 0.00 RPL) ``` Once you've selected an option, you'll be prompted with the network's current gas costs recommendations; confirm your gas price selection and follow the rest of the prompts. ``` +============== Suggested Gas Prices ==============+ | Avg Wait Time | Max Fee | Total Gas Cost | | 15 Seconds | 26 gwei | 0.1591 to 0.2387 ETH | | 1 Minute | 21 gwei | 0.1261 to 0.1891 ETH | | 3 Minutes | 21 gwei | 0.1261 to 0.1891 ETH | | >10 Minutes | 21 gwei | 0.1261 to 0.1891 ETH | +==================================================+ These prices include a maximum priority fee of 2.00 gwei. Please enter your max fee (including the priority fee) or leave blank for the default of 21 gwei: Using a max fee of 21.00 gwei and a priority fee of 2.00 gwei. Are you sure you want to claim bonds and rewards from 7 proposals? [y/n] ``` Note that if you select the first option to claim all available proposals, they will each execute individually and not as one transaction. ## Creating a Recurring Treasury Spend You'll need to prepare a few inputs to create a recurring treasury spend: - A contract name - The recipient's address - Amount of RPL to send per period - The start time for the recurring payment (as a UNIX timestamp) - The length of each payment period in hours / minutes / seconds (e.g., 168h0m0s) - Number of payment periods ::: tip INFO The recipient will need to keep note of the contract name in order to claim payments. Don't worry though, as this information is stored and can be retrieved using the command `rocketpool pdao proposals details ` ::: To raise a proposal to set up a recurring treasury spend, use the following smartnode command and follow the prompts: ```shell rocketpool pdao propose recurring-spend ``` Here's what it looks like all together: ``` Please enter a contract name for this recurring payment: test-recurring-spend Please enter a recipient address for this recurring payment: 0x681B8BBf08708e64694005c7Dc307b381b4D1A7D Please enter an amount of RPL to send to 0x681B8BBf08708e64694005c7Dc307b381b4D1A7D per period: 1 Your value will be multiplied by 10^18 to be used in the contracts, which results in: [1000000000000000000] Please make sure this is what you want and does not have any floating-point errors. Is this result correct? [y/n] y Please enter the time that the recurring payment will start (as a UNIX timestamp): 1717935233 The provided timestamp corresponds to 2024-06-09 12:13:53 +0000 UTC - is this correct? [y/n] y Please enter the length of each payment period in hours / minutes / seconds (e.g., 168h0m0s): 720h Please enter the total number of payment periods: 24 ``` Once you've entered all the required inputs, a proposal to create a recurring payment will be raised. When the pDAO passes and executes this proposal, the recipient is allocated `1 RPL` starting at `2024-06-09 12:13:53 +0000 UTC` every `720 hours` for a total of `24 payments`. ## Claiming a Recurring Treasury Spend Claiming recurring payments should be pretty simple! Navigate to our frontend tool [here](https://node.rocketpool.net/claim-recurring-payments) to do so. If you're trying this out on Hoodi testnet, use [this](https://testnet.node.rocketpool.net/stake-rpl-on-behalf-of-node) link instead. Once you're on the site, click the **connect wallet** button. Please read through and accept the Terms of Service & Privacy Policy, this will enable different ways to connect, then click connect **metamask**. MetaMask will prompt you to select an account to connect to the website. After you've signed in, you'll need to enter the **contract name**. Doing so will display all the relevant details. Make sure you double check the recipient's address. Anybody can call the claim function, but each payment contract will have a designated recipient to disperse RPL towards. ![](/static/image/claim_recurring1.d9e111503e.png) You can claim your payments at any time, you'll just get the total unclaimed RPL up until the most recent period. Alternatively you can wait until all periods have passed to collect all at once and save on gas. Just hit the big orange claim button when you're ready and review the transaction in metamask (or your preferred wallet). Once that's done, you're all set! --- url: /legacy/houston/pdao.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # The Protocol DAO (pDAO) The Rocket Pool Protocol DAO (pDAO) is responsible for shaping the direction of the protocol and is run by RPL governance. Its members and their voting power are made up of node operators, big and small, all of which are directly participating in the protocol. It serves the Rocket Pool community at large, including rETH holders, Node Operators, and RPL holders. The pDAO prioritizes the safety of the Rocket Pool protocol and the health of the Ethereum Network. For an explicit definition of who and what the pDAO is, feel free to take a look at the [pDAO charter](https://rpips.rocketpool.net/RPIPs/RPIP-23). ## New pDAO features in Houston ### On-chain execution of pDAO responsibilities The Houston Upgrade introduces an on-chain replacement for the pDAO governance system's execution process. It uses an optimistic fraud-proof system that allows any node operator to raise proposals and vote on proposals to adjust "pDAO protocol parameters" and spend treasury funds. To see a comprehensive list of pDAO controllable parameters, click [here](https://rpips.rocketpool.net/RPIPs/RPIP-33#parameter-table). Pre-Houston, the core team was responsible for executing pDAO duties at the behest of the community governance process. For example, the team carries out the monthly IMC and GMC payments as per the governance voted payment schedules. The plan was for this power to reside with the team temporarily until a new power structure is set up to take over these responsibilities. Houston removes this dependency on the team, making the protocol more decentralized and trustless. ### Security Council The Houston upgrade also includes a new security council to help react quickly in the event of any potential issues with the protocol. These members can be elected by the pDAO and have the ability to propose and execute changes without delay. The pDAO has the power to elect and remove members from the security council. It's a serious role and the pDAO should develop strong entry requirements and processes for flushing stale members. The pDAO guardian will be the security council's sole member at the start of Houston. ### Recurring Treasury Spends RPL has a 5% inflation rate. 22% of this inflation is directed towards the pDAO as defined in [RPIP-25](https://rpips.rocketpool.net/RPIPs/RPIP-25). The pDAO can use these funds for a variety of purposes. For example, incentives such as liquidity provider (LP) bonuses, grants and bounties for 3rd party improvements and projects, and funding the development of the Rocket Pool protocol. The Houston upgrade also introduces a new feature that enables recurring treasury payments made to a specified beneficiary each rewards period. ## Protocol DAO (pDAO) proposals Any node with a non-zero voting power may raise or participate in a pDAO proposal at any time. Proposals can be one of the following types: - Changing pDAO settings - One-time treasury spends - Repeat treasury spends (management committees) - Security council membership For greater detail and rationale, refer to [proposal types](https://rpips.rocketpool.net/RPIPs/RPIP-33#proposal-types). It's important to understand that a pDAO proposal is an on-chain entity that exists to execute changes at the protocol level. ## Lifecycle of a pDAO proposal A proposal should be forecasted by the [governance process](/legacy/houston/participate.md#governance-process) before it ends up on-chain. It consists of 4 Periods, all of which are pDAO [controllable parameters](https://rpips.rocketpool.net/RPIPs/RPIP-33#parameter-table): - Vote Delay Period: `proposal.vote.delay.time` - Vote Phase 1: `proposal.vote.phase1.time` - Vote Phase 2: `proposal.vote.phase2.time` - Execution: `proposal.execute.time ` ![](/static/image/proposal_diagram.3ec987f1be.png) ### Vote Delay Period In order to decide the outcome of a proposal, the protocol must know the quorum required. A proposer calculates this value off-chain and submits it alongside their proposal. The value is optimistically accepted, but in the case of fraud, verifiers can perform a challenge/response process to prove the value is incorrect. Invalid proposals are then discarded. A few reasons why proposers and challengers are required to lock RPL. - `proposal.bond` incentivizes valid proposals and disincentivizes spam. - `proposal.challenge.bond` incentivizes the takedown of invalid/malicious proposals. Challengers supply an index into the Merkle-sum tree that they are alleging is incorrect. Any node operator can participate in challenging fraudulent proposals (and earn a reward in doing so). Feel free to read about the [pDAO Challenge Process](/legacy/houston/pdao.md#challenge-process) if you're interested in opting in. A proposal not defeated in a challenge by the end of the vote delay period will enter voting stages. ::: tip NOTE When `proposal.vote.delay.time` expires, the proposal is no longer able to be challenged or defeated. ::: ### Vote Period 1 During a voting period, Node Operators and Delegates can cast a vote with one of four options: ``` 1. Abstain: The voter's voting power is contributed to quorum but is neither for nor against the proposal. 2. For: The voter votes in favor of the proposal being executed. 3. Against: The voter votes against the proposal being executed. 4. Veto: The voter votes against the proposal as well as indicating they deem the proposal as spam or malicious. ``` Their voting power will be included in the option of their choosing. This can be done using the command: ```shell rocketpool pdao proposals vote ``` If the veto quorum (as defined by the `proposal.veto.quorum` parameter) is met, the proposal is immediately defeated and the proposer loses their bond. This is to dissuade spam, low quality proposals, or proposals that have not gone through off-chain processes first. The smartnode command `rocketpool pdao proposals finalize` is used to finalize a vetoed proposal by burning the proposer's locked RPL bond. The duration of period 1 is determined by the `proposal.vote.phase1.time` parameter. The proposal will transition to phase 2 regardless of whether `proposal.quorum` is reached or not. ### Vote Period 2 Delegates can vote during vote period 2, but only their vote is only worth their **local voting power**. Voters who didn't vote in period 1 will still be able to cast a vote during period 2. Node operators who disagree with their delegate's choice will have the opportunity to overturn their delegate's vote. The process of overturning a vote is pretty simple, just call `rocketpool pdao proposals vote` during vote period 2 and follow the prompts. The delegate's voting power will be overturned by the delegatee's voting power. The result of a proposal is concluded when vote period 2 is over. In order for a result to be determined (and executed), `proposal.quorum` total voting power must be reached by the end of `proposal.vote.phase2.time`. If quorum is met and consensus is reached, the proposal will pass the voting periods and be marked as successful. ::: tip NOTE No further actions can be taken in the event that `proposal.quorum` is not met. A proposal is considered concluded and final if quorum is not met. ::: ### Execution Once both voting periods have passed and the proposal is successful, the proposal can be executed and the change (defined by the payload) is applied to the Rocket Pool protocol. To execute a proposal, use the command: ```shell rocketpool pdao proposals execute ``` You will be prompted to select a proposal to execute, the proposal will be applied to the protocol after this step! After the proposal has passed the voting periods, the proposer may [claim](/legacy/houston/participate.md#claiming-bonds-and-rewards) their locked RPL bond, unless the proposal was defeated by a challenge or vetoed. ::: tip NOTE There is a window `proposal.execute.time` where a proposal can be executed. A proposal will expire if this timer reaches its end. ::: And that's it! Keep in mind that all of the variables mentioned above are pDAO controllable parameters. Click [here](https://rpips.rocketpool.net/RPIPs/RPIP-33#parameter-table) for a comprehensive list of every parameter the pDAO has authority to change using on-chain proposals. ## Challenge Process The complete network voting power tree is stored off-chain due to gas limits. When a user submits a new proposal, they are responsible for constructing the network voting tree at target block number. This tree is generated off-chain but verifiable via Merkle roots that are submitted on-chain. The protocol relies on **verifiers** to check the details submitted by the proposer. Any node can participate in tracking and verifying the correctness of proposals. To opt into this responsibility, use the command `rocketpool service config`, navigate to the **Smart Node and TX Fee Settings** menu, and check the box `Enable PDAO Proposal Checker`. ![](/static/image/proposal_checker.8a91ab984e.png) When this setting is enabled, the node will check for new proposals, verify their correctness, and submit challenges to invalid proposals. The only prerequisite is that [RPL Locking](/legacy/houston/participate.md#allowing-rpl-locking) is enabled. This check runs every 5 minutes in conjunction with a few other node related duties. We'll run through an example of what challenging a fraudulent proposal looks like. We can use the smartnode command `rocketpool service logs node` to monitor the progress: ``` rocketpool_node | 2024/04/05 02:19:16 Checking for Protocol DAO proposal challenges to defend... rocketpool_node | 2024/04/05 02:19:26 Checking for Protocol DAO proposals to challenge... rocketpool_node | 2024/04/05 02:19:26 [Network Tree] Couldn't load network tree for block 1283202 from disk, so it must be regenerated. rocketpool_node | 2024/04/05 02:19:26 [PDAO Proposals] Network tree for block 1283202 didn't exist, creating one. rocketpool_node | 2024/04/05 02:19:26 [Voting Info Snapshot] Couldn't load network tree for block 1283202 from disk, so it must be regenerated. rocketpool_node | 2024/04/05 02:19:26 [PDAO Proposals] Voting info snapshot for block 1283202 didn't exist, creating one. rocketpool_node | 2024/04/05 02:19:26 Proposal 177 does not match the local tree artifacts and must be challenged. rocketpool_node | 2024/04/05 02:19:26 [Voting Info Snapshot] Loaded file [vi-1283202.json.zst]. rocketpool_node | 2024/04/05 02:19:26 [Network Tree] Loaded file [network-tree-1283202.json.zst]. rocketpool_node | 2024/04/05 02:19:26 Submitting challenge against proposal 177, index 5... rocketpool_node | 2024/04/05 02:19:26 This transaction will use a max fee of 16.067134 Gwei, for a total of up to 0.003252 - 0.004878 ETH. rocketpool_node | 2024/04/05 02:19:26 Transaction has been submitted with hash 0x327e59e398bf2141a0d9273947d1da5c255606c45afaca428ab092186300eac2. rocketpool_node | 2024/04/05 02:19:26 You may follow its progress by visiting: rocketpool_node | 2024/04/05 02:19:26 https://holesky.etherscan.io/tx/0x327e59e398bf2141a0d9273947d1da5c255606c45afaca428ab092186300eac2 ``` We can see that our node has caught a fraudulent proposal and started the process of challenging it. Block `1283202` is the block in which proposal 177 was raised, which means voting power for this proposal will be calculated at block `1283202`. If you're interested in seeing what these **Voting Info Snapshots** look like, you can locate them in this directory: `~/.rocketpool/data/voting` Because the proposer was caught submitting incorrect voting info, our node makes a contract call `Function: createChallenge` on proposal 177 at index 5 and waits for the proposer to respond to the challenge. ``` rocketpool3_node | 2024/04/05 02:56:51 Checking for Protocol DAO proposal challenges to defend... rocketpool3_node | 2024/04/05 02:57:01 Checking for Protocol DAO proposals to challenge... rocketpool3_node | 2024/04/05 02:57:01 [Network Tree] Loaded file [network-tree-1283202.json.zst]. rocketpool3_node | 2024/04/05 02:57:01 Proposal 177 does not match the local tree artifacts and must be challenged. rocketpool3_node | 2024/04/05 02:57:01 [Voting Info Snapshot] Loaded file [vi-1283202.json.zst]. rocketpool3_node | 2024/04/05 02:57:01 [Network Tree] Loaded file [network-tree-1283202.json.zst]. rocketpool3_node | 2024/04/05 02:57:01 Proposal 177 has been defeated with node index 20, submitting defeat... rocketpool3_node | 2024/04/05 02:57:01 This transaction will use a max fee of 19.078965 Gwei, for a total of up to 0.002061 - 0.003091 ETH. rocketpool3_node | 2024/04/05 02:57:01 Transaction has been submitted with hash 0x8cc01dff37205dc98e53f4e9fae7f3c802ecc1c69a01f53e734115a73401287e. rocketpool3_node | 2024/04/05 02:57:01 You may follow its progress by visiting: rocketpool3_node | 2024/04/05 02:57:01 https://holesky.etherscan.io/tx/0x8cc01dff37205dc98e53f4e9fae7f3c802ecc1c69a01f53e734115a73401287e rocketpool3_node | rocketpool3_node | 2024/04/05 02:57:01 Waiting for the transaction to be validated... rocketpool3_node | 2024/04/05 02:57:13 Successfully defeated proposal. ``` Since the proposer's voting info is incorrect, it won't be able to respond to the challenge in time (determined by `proposal.challenge.period`). The proposal is considered defeated at this point. When the proposal is defeated, our node automatically makes the contract call `defeatProposal` on proposal 177 at index 5 to end the proposal. ::: tip NOTE Challengers who participate in defeating the proposal are paid a proportional amount of the proposer's bond if they submit an index proven to be incorrect. All other challengers receive their bond back only. ::: Now that the proposal is defeated, our node (the challenger) can [claim](/legacy/houston/participate.md#claiming-bonds-and-rewards) their original RPL bond as well as the proposer's RPL bond as a reward for defeating a fraudulent proposal. If you're curious to dig into the details of the pDAO proposal and challenge system, take a look at the [technical specifications](https://github.com/rocket-pool/rocketpool-research/blob/houston/Protocol%20DAO/pdao-prop-challenge-spec.md#draft-protocol-dao-proposal-challenge-system-specification). Feel free to skip to this section on the [challenge process](https://github.com/rocket-pool/rocketpool-research/blob/houston/Protocol%20DAO/pdao-prop-challenge-spec.md#challenge-process) if you're interested in studying an example that goes into low level details. --- url: /legacy/houston/rpl-withdrawal-address.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Setting your RPL Withdrawal Address It's important to understand the difference between your [primary withdrawal address](/node-staking/prepare-node.md#setting-your-primary-withdrawal-address) and your RPL withdrawal address. By default, your RPL withdrawal address is unset and your Primary withdrawal address is where all of your RPL checkpoint rewards, your staked RPL, and Beacon Chain ETH will be sent to. You can set a [separate withdrawal address for your RPL](https://rpips.rocketpool.net/RPIPs/RPIP-31) if you wish. Your RPL withdrawal address if set will be able to trigger and claim RPL from inflation rewards and will have no effect on ETH consensus rewards or anything related to ETH. In this case, your Primary withdrawal address will no longer have any authority over RPL related actions. This creates some interesting opportunities where RPL can be supplied by an entity to a node operator that does not wish to have exposure to RPL. That entity can then claim RPL rewards for putting up the required insurance collateral for the node. In other words, this allows different actors to supply each collateral type. ::: warning NOTE Upon setting up your node for the first time, your RPL withdrawal address defaults to being unset. If you choose to set an RPL withdrawal address, **it is vitally important to set this to a different address controlled by a cold wallet.** A cold wallet could be a hardware wallet (such as a [Ledger](https://www.ledger.com/), [Trezor](https://trezor.io/), or [Grid+](https://gridplus.io/)), or a Smart Contract wallet (such as [Safe](https://app.safe.global/welcome)). We **strongly recommend** that you DO NOT use a hot wallet such as MetaMask as your RPL withdrawal address. This way, if your node wallet is compromised, the attacker doesn't get access to your staked RPL by forcing you to exit because all of those funds will be sent to your separate cold wallet (which they hopefully do not have). RPL withdrawal addresses are set at a node operator level. If you create multiple minipools, they will all refer to the same RPL withdrawal address so you only need to perform this setup once. [See here](https://ethereum.org/en/security/#wallet-security) for some basics on wallet security from the Ethereum Foundation. ::: There are two different ways to do this. Please read both options below to determine which one applies to you. **Method 1** _Use this method if your new RPL withdrawal address can be used to sign transactions via MetaMask or WalletConnect._\*

NOTE

This method will require you to **submit a transaction** from your new RPL withdrawal address, so **you must have a small amount of ETH in that address already.**

NOTE

For users of **Ledger** hardware wallets, note that Ledger Live does not yet support MetaMask or WalletConnect natively. You will need to use MetaMask and connect it to your Ledger instead. Follow [the official Ledger instructions](https://www.ledger.com/academy/security/the-safest-way-to-use-metamask) to do this. To work with the Rocket Pool website, you will need to have your Ledger connected, unlocked, and the ETH app open. You will also need to **enable "blind signing"** for the current session; you can find this within the Settings portion of the ETH app on the device. Bind signing will automatically be disabled after you close the session. If you are using Hoodi Testnet and want to use your Ledger as your RPL withdrawal address, **you must create a new Ethereum wallet on your Ledger** first to ensure you don't connect your live address to the test network, which tends to cause confusion. Make sure to select the **Hoodi Testnet** in the network selection dropdown when connecting your Ledger to MetaMask. Note that Ledger Live will not show your balance on the test network, but other applications which support the test network (such as MetaMask and Etherscan) will be able to display it. 1. Run `rocketpool node set-rpl-withdrawal-address 'your cold wallet address or ENS name'`. Your new RPL withdrawal address will be marked as "pending". Until you confirm it, **your old RPL withdrawal address will still be used**. 2. To confirm it, you must send a special transaction **from your new RPL withdrawal address** to the minipool contract to verify that you own the RPL withdrawal address. 3. The easiest way to do this is to navigate to the Rocket Pool RPL withdrawal address site (for the [Hoodi Testnet](https://testnet.node.rocketpool.net/rpl-withdrawal-address) or for [Mainnet](https://node.rocketpool.net/rpl-withdrawal-address)). 4. If you haven't already connected Metamask or WalletConnect to the Rocket Pool website, do this now. Click the **select wallet** button in the center of the screen, and choose MetaMask or WalletConnect based on which wallet you would like to use. You will then be prompted asking you to confirm the connection. For example, using MetaMask: Click **Next**, then click **Confirm** to enable the Rocket Pool website to use your wallet. 3. Select **RPL Withdrawal Address** from the top menu (or the hamburger menu on the left side if you're on a mobile device). 4. You will see this prompt: 4. Type your **node wallet address** here and click on the orange **Find** button to continue. ![](/static/image/node_address.6d1c2d3c82.png)1. You will be prompted to confirm a pending RPL withdrawal address. This should be the same address you used while running this command previously: `rocketpool node set-rpl-withdrawal-address` Select **Confirm Pending** when you're ready. 2. Now, there should be a new confirmation dialog in your wallet. Again, using MetaMask as an example, click the MetaMask icon to open it and you should see something like this: Click **Confirm** to send the transaction to the network. This will take some time until it gets included in a block, but once it does, you will see a confirmation dialog: ![](/static/image/rpl_withdrawal_confirmation.4f8817457e.png)5. Your new RPL withdrawal address will now be confirmed and activated. You can view this with `rocketpool node status`. **Method 2** **Use this method only if your RPL withdrawal address _cannot_ be used to sign transactions via MetaMask or WalletConnect.** In this method, you will run: ```shell rocketpool node set-rpl-withdrawal-address --force `your cold wallet address` ``` You will be offered the chance to send a test transaction before confirming this, to ensure that you have the right address. If you confirm this command when it prompts you, your new RPL withdrawal address will be set immediately. By doing this, you bypass the safety measure associated with Method 1, which requires you to prove that you own the new address. If you make a typo here, there is no way to undo it and **your minipool's rewards will be lost forever**. We **strongly** encourage you to use the test transaction mechanism before confirming this, and if possible, use Method 1 instead. Once this is done, you will **no longer be able to change your RPL withdrawal address using the `set-rpl-withdrawal-address` command**. To change it, you will need to send a signed transaction from your **active** RPL withdrawal address (the one you just switched to). The Rocket Pool website has a function to help you do this. If you'd like to unset your RPL withdrawal address, the process is pretty simple. First thing, you'll want to navigate back to the RPL Withdrawl Address page on the Rocket Pool website. **Hoodi Testnet** [https://testnet.node.rocketpool.net/rpl-withdrawal-address](https://testnet.node.rocketpool.net/rpl-withdrawal-address) **Mainnet** [https://node.rocketpool.net/rpl-withdrawal-address](https://node.rocketpool.net/rpl-withdrawal-address) If you're signed in with the node's RPL withdrawal address, you should be able to click the **unset** button on the right here: ![](/static/image/unset_rpl_withdrawal.8415469b06.png) Clicking **unset** will take you to a page where you can confirm the details. If you're happy with what you see, click the orange **unset** button to send the transaction to the network. That's all there is to setting your RPL withdrawal address! We hope you found the process quick and easy. Feel free to swing by [our Discord server](https://discord.gg/G46XgK264a) to let us know what you thought of it and keep tabs on the project as it evolves. --- url: /legacy/houston/stake-eth-on-behalf.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Stake ETH on behalf of node RPIP-32 allows an account to [stake ETH on behalf](https://rpips.rocketpool.net/RPIPs/RPIP-32) of a Rocket Pool node that is registered in the protocol. This supports a variety of situations where the node operator is not directly providing the ETH: - Enhanced security for node operators, as they can stake directly from their hardware wallet, eliminating the need to transfer funds to the node beforehand. - Staking as a Service providers where custody of funds are managed by a trusted custodian. - Protocol integrations where custody of funds are managed by smart contracts. - DAOs or organizations where custody of funds are managed by a treasury. While the primary aim of this feature is to facilitate single depositor scenarios, it’s worth noting that multiple independent depositors can also leverage this capability by creating smart contracts layered on top. Rocket Pool also introduced the ability to [stake RPL on behalf](/node-staking/create-validator.md#whitelisting-an-address-to-stake-on-behalf) of a node back in our previous Atlas release. ### Prerequisite Make sure that you've properly configured the [primary withdrawal address](/node-staking/prepare-node.md#setting-your-primary-withdrawal-address) of the node you intend on funding. Follow the link above for a guide on how withdrawal addresses act post houston. ::: tip NOTE Don't skip this step! All ETH bond/rewards will be withdrawn to the primary withdrawal address. In other words, the address that supplies ETH for a node should be used as the primary withdrawal address! Please make sure that the node's primary withdrawal address is set to a wallet you have custody over. ::: The process is slightly different for the Hoodi Testnet and Mainnet, so choose the network you are interested in from the tabs below. **Preparing on the Hoodi Testnet**

WARNING

When practicing staking on the test network, you **do not need to provide any of your real ETH** during this process. You will be given **fake test ETH** to use instead. **Do not attempt to move your real ETH on mainnet to the testnet or you will lose it permanently!** Start by installing [MetaMask](https://metamask.io/) if you haven't already. Follow the instructions on their site to install the extension, create an account, and sign in. Next, open the MetaMask panel using its icon in your browser toolbar. You will need to add the Hoodi Testnet to MetaMask. Click on the top left dropdown & click the "Add Network" button. You will see a list of networks, Hoodi is not in this list so click the "Add a network manually" button. Fill in the following details: ``` Network Name: Hoodi New RPC Url: https://rpc.hoodi.ethpandaops.io Chain ID: 560048 Currency Symbol: ETH Block Explorer Url: https://hoodi.etherscan.io ``` Then click Save. You should now see the Hoodi network in the top left dropdown. Click on the **network dropdown** in the top left of the Metamask extension & select **Hoodi Test Network**: ![](/static/image/mm_network.9e33ace5ec.png)Now that you have a wallet address in MetaMask, you need to fill it with some test ETH. Head over to the [Practicing with the Test Network](/node-staking/testnet/overview.md#getting-test-eth-on-hoodi) page for a quick guide on how to use a testnet faucet to get some test ETH on Hoodi. Once you have some Hoodi ETH to test with, head to [https://testnet.node.rocketpool.net/deposit-eth-on-behalf-of-node](https://testnet.node.rocketpool.net/deposit-eth-on-behalf-of-node). If you see a notice about a web3 browser being required, or the current network ID being unsupported, make sure you’ve completed the previous steps correctly before continuing. **Preparing on the Ethereum Mainnet** Start by installing [MetaMask](https://metamask.io/) if you haven't already. Follow the instructions on their site to install the extension, create an account, and sign in. Next, open the MetaMask panel using its icon in your browser toolbar. Click on the **network dropdown** in the toolbar at the top and ensure that **Ethereum Mainnet** is selected: ![](/static/image/mm_network_main.1536c3b585.png)Now that you have a wallet address in MetaMask, you need to transfer some ETH into it. You will need to supply this from an existing wallet or buy ETH on an exchange. Once you have some ETH to stake, head to [https://node.rocketpool.net/deposit-eth-on-behalf-of-node](https://node.rocketpool.net/deposit-eth-on-behalf-of-node). If you see a notice about a web3 browser being required, or the current network ID being unsupported, make sure you’ve completed the previous steps correctly before continuing. Once you're at the site, click on the **connect wallet** button. Please read through and accept the Terms of Service & Privacy Policy, this will enable different ways to connect, then click **connect metamask**. MetaMask will prompt you to select an account to connect to the website. Choose one, confirm a few permissions. You'll see an overview of your balances by clicking the wallet icon located at the top right of the window. From here, you'll want to enter the address of the node you'd like to deposit ETH on behalf of. The page should look like this: ![](/static/image/enter_node_address.c23b86ee7b.png) Go ahead and paste your desired address into this box and click find. In this example, we'll use `0xd3e317806456102d19db283b4c2201f0ef41a296` ![](/static/image/eth_on_behalf.cff0dfd649.png) In the first box, enter the amount of ETH you would like to deposit on behalf of the node. The second box indicates which address you'll be depositing ETH on behalf of. Please ensure that you've entered the correct address and deposit. Once you're satisfied, click Deposit and MetaMask will pop up with a window asking you to confirm your transaction. Once you confirm it, the transaction will begin. When it's been included in a block and added to the chain, your delegate will be able to use the command `rocketpool node status` in smartnode to see the new balance. This balance can also be viewed through the Rocket Pool staking site. ``` The node has 0.000000 ETH in its credit balance and 8.000000 ETH staked on its behalf. 8.000000 can be used to make new minipools. ``` ::: warning NOTE If a node operator deposits your ETH into a minipool, you won't be able to exit their minipool without access to their withdrawal credentials, so keep this in mind! You can use the Rocket Pool staking site to withdraw ETH staked on behalf of a node if it isn't being used in a minipool. ::: That's it! You're now staking with Rocket Pool. # Unstake ETH on behalf of node **Preparing on the Hoodi Testnet** When you're ready to withdraw ETH you've staked on behalf of a node, head over to [https://testnet.node.rocketpool.net/withdraw-eth](https://testnet.node.rocketpool.net/withdraw-eth). After signing in as the node's [primary withdrawal address](/node-staking/prepare-node.md#setting-your-primary-withdrawal-address), you should be greeted with a familiar menu. You'll be prompted to enter the node address you want to withdraw from: **Preparing on the Ethereum Mainnet** When you're ready to withdraw ETH you've staked on behalf of a node, head over to [https://node.rocketpool.net/withdraw-eth](https://node.rocketpool.net/withdraw-eth). After signing in as the node's [primary withdrawal address](/node-staking/prepare-node.md#setting-your-primary-withdrawal-address), you should be greeted with a familiar menu. You'll be prompted to enter the node address you want to withdraw from: ![](/static/image/enter_node_address.c23b86ee7b.png) After entering an address, clicking "Find" will take you to the next menu where you can withdraw ETH you've staked on behalf of that node. ![](/static/image/withdraw_eth_on_behalf.2439585a00.png) You'll be able to see how much ETH is available for withdrawal in the top right. After you input your desired quantity and confirm the node address, click the orange **Withdraw ETH** button to send the transaction to the network. Once the transaction is confirmed, you'll see the proper balances in your account! That's all there is to staking ETH on behalf of a node! We hope you found the process quick and easy. Feel free to swing by [our Discord server](https://discord.gg/G46XgK264a) to let us know what you thought of it and keep tabs on the project as it evolves. --- url: /legacy/houston/whats-new.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # The Houston Upgrade The Houston upgrade is largely aimed at introducing a fully on-chain DAO to govern the protocol, known as the Protocol DAO or pDAO. It is a DAO like no other and it does not require snapshot voting or any other 3rd party tools to function, it is truly on-chain and one of a kind, more on that below. This upgrade will also be introducing some other very exciting features that will allow new integrations and platforms to be built on the protocol. Some of these include the ability to stake ETH on behalf of node (not just from the node itself) and a new RPL withdrawal address feature, that allows one party to supply the ETH for staking and another party to provide the RPL without giving custody to the node operator" ## Protocol DAO The Rocket Pool Protocol DAO (pDAO) is responsible for shaping the direction of the protocol and is run by RPL governance. Its members and their voting power are made up of node operators, big and small, all of which are directly participating in the protocol. Typically DAO governance in the wider crypto space is done by token weight voting. Basically, the more tokens you hold for a protocol/project, the bigger your voting power. You also don’t need to be actively participating in the protocol, simply holding the tokens is enough. This style of governance we wanted to avoid. If you want to help direct and guide the future of Rocket Pool, you need to be actively involved, not just storing tokens in a cold wallet. From the biggest Venture Capitalist funds to your ordinary guy running a single minipool, you will need to be actively participating in the protocol to help govern it. Currently the protocol DAO has control over a variety of on-chain settings that are used in the protocol. New Rocket Pool Improvement Proposals (RPIP) can be made and voted on by these Node Operators within Rocket Pool. You can see the [**current RPIP registry here**](https://rpips.rocketpool.net/). If you’re a devil for the details, the current RPIP for the on-chain protocol DAO talked about now can be found here. ### What can the pDAO do? The pDAO has control over many settings of the protocol, it can spend treasury funds and in our Houston upgrade, it comes with a new security council to help react quickly in the event of any potential issues with the protocol. Lets talk about each of those a little more below. **Protocol Parameters:** These control certain facets of the protocol such as the setting that controls the minimum ETH amount that can be deposited for rETH (currently 0.01 ETH) or even controlling the maximum size of the deposit pool, this is how much max ETH that can be deposited into the protocol while waiting to be assigned to node operators for staking. You can find a full table of [these settings here](https://rpips.rocketpool.net/RPIPs/RPIP-33#parameter-table). **Treasury Funds:** RPL has a 5% inflation rate and a portion of that is allocated to the pDAO treasury. The pDAO have the ability to spend this treasury on a variety of protocol oriented endeavors, from funding development of the protocol directly, grants management for funding 3rd party improvements and projects that make use of Rocket Pool and more. Our Houston upgrade adds a new ability where these payments from the treasury can be done not just in a lump sum manner, but in a progressive manner to help track goals in relation to ongoing funding. **Security Council:** As the Houston upgrade moves the pDAO to a fully on-chain system, a new safety measure was introduced in the form of the [security council](https://rpips.rocketpool.net/RPIPs/RPIP-33#security-council). These members can be elected by the pDAO and they have the ability to pause the protocol quickly in the event any potential issues occur. Quorum must be met among members for any security response to be executed. The pDAO also has the power to remove members or disband the security council entirely if they need to. ### Proposals and Voting For any governance system to function, there needs to be proposals and voting. At the moment, snapshot voting is used for these settings and proposal changes, then some manual intervention is needed to execute the changes. With the introduction of the [Houston upgrade and RPIP-33](https://rpips.rocketpool.net/RPIPs/RPIP-33), this is moved to a new optimistic fraud-proof system that allows any node operator to raise, vote on or challenge proposals, directly on-chain without the need for any 3rd party tools. **Proposing:** Any node with a non-zero voting power may raise a proposal at any time. When doing so they must lock a proposal bond in the form of RPL for the entire proposal process. **Challenging:** If a node that created a proposal has been found to have done so with incorrect data required, they can be challenged and the challenger must provide a bond for the challenge. The node that makes the challenge can be rewarded with the proposers bond made when creating the proposal if successful, however if they have made an invalid challenge, the proposer can collect their challenge bond. **Voting**: If a proposal passes the period where it can be challenged, it enters the voting periods. Node operators can then choose to vote in one of the following flavors: 1. Abstain: The voter’s voting power is contributed to quorum but is neither for nor against the proposal. 2. For: The voter votes in favor of the proposal being executed. 3. Against: The voter votes against the proposal being executed. 4. Veto: The voter votes against the proposal as well as indicating they deem the proposal as spam or malicious. If the veto quorum is met, the proposal is immediately defeated and the proposer loses their bond. This is to dissuade spam, low quality proposals, or proposals that have not gone through off-chain processes first such as signaling by snapshot voting. There are **two voting periods** - Vote Period 1: For voters or delegates voting on behalf of others. - Vote Period 2: For voters who delegated their power and want to overturn their delegate's decision. Once both voting periods have passed and the proposal is successful, the proposal can be executed and the change is applied to the Rocket Pool protocol. After the proposal has passed the voting periods, the proposer may unlock their RPL bond, unless the proposal was defeated by a challenge or vetoed. ## Stake ETH on Behalf of a node [RPIP-32](https://rpips.rocketpool.net/RPIPs/RPIP-32) allows an account to [stake ETH on behalf](/legacy/houston/stake-eth-on-behalf.md) of a Rocket Pool node that is registered in the protocol. This supports a variety of situations where the node operator is not directly providing the ETH: - Enhanced security for node operators, as they can stake directly from their hardware wallet, eliminating the need to transfer funds to the node beforehand. - Staking as a Service providers where custody of funds are managed by a trusted custodian. - Protocol integrations where custody of funds are managed by smart contracts. - DAOs or organizations where custody of funds are managed by a treasury. While the primary aim of this feature is to facilitate single depositor scenarios, it’s worth noting that multiple independent depositors can also leverage this capability by creating smart contracts layered on top. Rocket Pool also introduced the ability to stake RPL on behalf of back in our previous Atlas release. ## RPL Withdrawal Address Rocket Pool currently allows node operators to specify a withdrawal address for their ETH and RPL. This could be an external hardware wallet or something similarly secure. With [RPIP-31](https://rpips.rocketpool.net/RPIPs/RPIP-31), you can set a withdrawal address for your ETH and [a new one for your RPL](/legacy/houston/rpl-withdrawal-address.md) if you wish. The RPL withdrawal address if set will be able to trigger and claim RPL from inflation rewards and will have no effect on ETH consensus rewards or anything related to ETH. This creates some interesting opportunities where RPL can be supplied by an entity to a node operator that does not wish to have exposure to RPL. That entity can then claim RPL rewards for putting up the required insurance collateral for the node. ## Time-based Balance and RPL Price Submissions Rocket Pool nodes need to have at least 10% collateral in RPL staked to be eligible for rewards, with their "effective stake" calculated based on the ETH:RPL ratio, which is reported by the Oracle DAO at the end of each rewards interval. Previously, this "top up window" (the time between the final RPL report and the end of the interval) had some uncertainty and fluctuated from interval to interval because it was being specified by number of blocks. This was valid pre-merge but didn't factor variability and randomness in the way blocks are added. To address this, the intervals for price and balance reporting will now be based on seconds rather than blocks. This change ensures predictability and has parity with the way rewards intervals are calculated today. If the interval is set to `86400` seconds (number of seconds in 24 hours), prices and balances are reported at the same time every day. The protocol now has a fixed and controllable "top up window," removing guesswork and providing users with a consistent 24-hour window for topping up after the final price update. Feel free to read more about this change in [RPIP-35](https://rpips.rocketpool.net/RPIPs/RPIP-35). ## Audits In preparation for the Houston Upgrade, Rocket Pool engaged with three of the most esteemed auditing teams in the Ethereum ecosystem. - [Consensys Diligence](https://consensys.io/diligence/audits/2023/12/rocket-pool-houston/) (Late November to Mid December 2023) - [Sigma Prime](https://rocketpool.net/files/audits/sigma-prime-audit-houston.pdf) x2 (Late November 2023, then a second round March 2024) - [Chainsafe](https://rocketpool.net/files/audits/chainsafe-audit-houston.pdf) (Mid January to April 2024) For a full history of audits plus details on the Immunefi bug bounty program, visit here: [https://rocketpool.net/protocol/security](https://rocketpool.net/protocol/security) --- url: /legacy/redstone/docker-migration.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # \[Docker Mode] Guide to the Redstone Update and the Merge This guide will cover everything you need to know in order to prepare your node for the Redstone Update and The Merge if you are using **Docker Mode**. ## Things to Do Before Upgrading to v1.5.0 Before upgrading to v1.5.0 and higher of the Smart Node, please go through the following checklist to make sure you're prepared: ### Switch to a Full Execution Client The Merge requires you to run your own Execution client, so you won't be able to use remote providers like Infura or Pocket anymore. v1.5.0 won't have them anymore, and won't let you start the stack until you select a full Execution client. Because of this change, you should switch to a full client while you're still on v1.4, let it sync to completion, and then upgrade to v1.5. Docker Mode makes switching clients very easy. [This guide](/node-staking/change-clients.md#changing-execution-clients) provides a walkthrough of the process. ## Upgrading to v1.5.0 Upgrading the Smart Node stack to v1.5.0 is no different than any other upgrade. Simply follow [the normal directions here](/node-staking/updates.md#updating-the-smart-node-stack). ## Things the Smart Node Handles Automatically In Docker mode, the Smart Node will take care of most of the changes needed to support Redstone and The Merge automatically once you update to v1.5.0. Here's a brief list of what it will do for you without any manual intervention: ### The Engine API The Merge changes the way your Execution client talks to your Consensus client. Instead of using the old HTTP or Websocket based RPC system, The Merge requires a new system exposed by your Execution client called the Engine API. This is a special connection that lets the Consensus client replace the old Proof-of-Work mining system with Proof-of-Stake; it's the heart of The Merge. It's also **authenticated** with a secret token, so only your Consensus client can connect to your Execution client - nothing else can. The Smart Node will handle the set up of the authentication token and the Engine API on both your Execution and Consensus clients automatically. ### Your Fee Recipient The **fee recipient** is the address on the Execution layer chain that will receive all of the priority fees for blocks you propose. It is a setting provided to your Validator client when it first starts. The Smart Node will handle setting it up to the correct address when you upgrade to v1.5, and will constantly check to make sure you're using the correct one so you don't get [penalized accidentally](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system). If you opted into the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool), it will make that your fee recipient. If you didn't, it will make your [fee distributor contract](/legacy/redstone/whats-new.md#fee-recipients-and-your-distributor) the fee recipient. ### MEV-Boost [MEV-boost](https://boost.flashbots.net/) is the system Flashbots provides to give MEV rewards to Proof-of-Stake validators after The Merge. Rocket Pool has MEV-Boost built into the Smart Node and automatically configures your node to use it, so your proposals get the maximum amount of rewards. ## Things You Should Do After Upgrading While the Smart Node handles most of the changes for you, there are a few additional things you should do manually: ### Ensure a Successful Upgrade The first thing to do is ensure that your node is working correctly. Consider taking the following steps: - Check the logs for errors with `rocketpool service logs eth1`, `rocketpool service logs eth2`, `rocketpool service logs validator`, and `rocketpool service logs node`. - Confirm with a Block Explorer (such as your Grafana dashboard and [https://beaconcha.in](https://beaconcha.in)) that you are still attesting properly - Remember that if you have Doppelganger protection enabled, you will miss a few attestations after the restart. This is normal! ### Set Up a Fallback Node Because The Merge is not compatible with remote providers like Infura and Pocket, you'll lose the ability to use them as fallback Execution clients when your primary goes offline. The Smart Node still has the ability to provide a fallback Execution client (and now a fallback Consensus client as well), but you will now need to use Execution and Consensus clients that you control. For more information on setting up a fallback node, see the [Fallback node guide](/node-staking/fallback.md). ### Initialize your Fee Distributor If you aren't planning to opt into the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool) and claim all of your priority fees and MEV rewards to your [fee distributor contract](/legacy/redstone/whats-new.md#fee-recipients-and-your-distributor), you will eventually have to initialize it (create the contract instance on the chain) in order to claim rewards from it to your withdrawal address. This is a fairly cheap operation and only needs to be done once. ::: tip TIP Initializing your fee distributor can be done at **any time**. You can let rewards accumulate in its address long before you initialize it, and your balance will remain after initialization. We recommend you do so when gas prices are low to minimize the overhead cost. Note that it **must be initialized in order to claim your rewards.** ::: ### Opt Into the Smoothing Pool If you plan on taking advantage of the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool) right away, you should opt in before the end of the first Redstone rewards period to maximize your "eligibility" amount. Opting in can be done via running the following command: ``` rocketpool node join-smoothing-pool ``` ### Claim Rewards The Redstone upgrade replaces the expensive, problematic old rewards system with a [brand new one](/legacy/redstone/whats-new.md#new-rewards-system) that's much cheaper, supports automatic restaking of RPL (both partial and full amounts), and - most importantly - **lets you claim your rewards whenever you want**. Because there is no longer a time limit on claiming rewards, and because it's cheaper to claim many rewards intervals at once, the automatic rewards claiming feature of the Smart Node **has been removed**. You will now be able to claim rewards via the following command: ``` rocketpool node claim-rewards ``` This will show you all of the rewards you've accumulated across all of the rewards intervals starting with the Redstone upgrade. ## Reverting to v1.4.3 If, for any reason, something isn't to your liking and you want to revert to the previous Smart Node release, you can do so easily. The Smart Node automatically backs up your settings from the previous version when you upgrade it, so simply get the previous version (here we're demonstrating **v1.4.3**) and replace the settings with the backup: 1. Stop the service: ```shell rocketpool service stop ``` 1. Download the v1.4.3 CLI: **Linux x64** `shell wget https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-linux-amd64 -O ~/bin/rocketpool ` **Linux arm64** `shell wget https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-linux-arm64 -O ~/bin/rocketpool ` **Mac x64** `shell curl -L https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool ` **Mac arm64** `shell curl -L https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-darwin-arm64 > /usr/local/bin/rocketpool ` 1. Install the v1.4.3 package: ```shell rocketpool service install -d ``` 1. Replace your old configuration with the v1.4.3 backup configuration: ```shell cp ~/.rocketpool/user-settings-backup.yml ~/.rocketpool/user-settings.yml ``` 1. Verify all of your old settings are now being used: ```shell rocketpool service config ``` 1. If it looks good, start the Smart Node stack: ```shell rocketpool service start ``` All set! You're now back on the old version and should begin attesting shortly after starting the service. ::: danger WARNING v1.4.3 is **deprecated** and will no longer be usable after the Redstone update is deployed. If you do need to revert to it, please make plans to upgrade back to v1.5.0 before the contracts are updated! ::: --- url: /legacy/redstone/hybrid-migration.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # \[Hybrid Mode] Guide to the Redstone Update and the Merge This guide will cover everything you need to know in order to prepare your node for the Redstone Update and The Merge if you are using **Hybrid Mode**. ## Things to Do Before Upgrading to v1.5.0 Before upgrading to v1.5.0 and higher of the Smart Node, please go through the following checklist to make sure you're prepared: ### Switch to a Full Execution Client The Merge requires you to run your own Execution client, so you won't be able to use remote providers like Infura or Pocket anymore. Because of this change, if you're currently using a light Execution client, you should switch to a full client while you're still on v1.4, let it sync to completion, and then upgrade to v1.5. ### Ensure the EC and CC are Both Externally Managed Previous versions of the Smart Node stack allowed you to have one client locally managed, and the other externally managed. For example, you could have an Execution client that the Smart Node manages and connect it to a Consensus client that you manage externally. Starting with v1.5, this configuration is no longer supported. You'll have to switch to either a locally managed Execution and Consensus client (also known as [Docker Mode](/legacy/redstone/docker-migration.md)), or set up both an Execution and a Consensus client that you manage on your own. ::: tip TIP If you are interested in letting the Smart Node maintain its own Execution and Consensus client but want to keep control over your own Validator client (e.g., if you have your own solo staking validator keys attached to it), you may want to consider [Reverse Hybrid Mode](/node-staking/advanced-config.md#allowing-external-validator-clients-to-connect-to-the-smart-node) which does exactly this! ::: ### Set Up the Engine API The Merge changes the way your Execution client talks to your Consensus client. Instead of using the old HTTP or Websocket based RPC system, The Merge requires a new system exposed by your Execution client called the Engine API. This is a special connection that lets the Consensus client replace the old Proof-of-Work mining system with Proof-of-Stake; it's the heart of The Merge. It's also **authenticated** with a secret token, so only your Consensus client can connect to your Execution client - nothing else can. As you manage your own Execution and Consensus clients, you'll need to set up the Engine API manually. How to do it depends entirely on which clients you're running. CoinCashew has [a great and concise guide](https://www.coincashew.com/coins/overview-eth/ethereum-merge-upgrade-checklist-for-home-stakers-and-validators) on how to set up the Engine API on your Execution and Consensus clients. Give that a look, and test the new configuration out by making sure it still attests properly before upgrading. As always, Rocket Pool will manage its own Validator client so you don't need to worry about manually modifying it. ## Upgrading to v1.5.0 Upgrading the Smart Node stack to v1.5.0 is no different than any other upgrade. Simply follow [the normal directions here](/node-staking/updates.md#updating-the-smart-node-stack). ## Things the Smart Node Handles Automatically In Hybrid mode, the Smart Node will take care of some of the changes needed to support Redstone automatically once you update to v1.5.0, but you will need to handle others manually in Hybrid Mode. Here's a brief list of what it will do for you without any manual intervention: ### Your Fee Recipient The **fee recipient** is the address on the Execution layer (eth1) chain that will receive all of the priority fees for blocks you propose. It is a setting provided to your Validator client when it first starts. The Smart Node will handle setting it up to the correct address on the Validator client it manages when you upgrade to v1.5, and will constantly check to make sure you're using the correct one so you don't get [penalized accidentally](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system). If you opted into the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool), it will make that your fee recipient. If you didn't, it will make your [fee distributor contract](/legacy/redstone/whats-new.md#fee-recipients-and-your-distributor) the fee recipient. ## Things You Should Do After Upgrading While the Smart Node handles most of the changes for you, there are a few additional things you should do manually: ### Ensure a Successful Upgrade The first thing to do is ensure that your node is working correctly. Consider taking the following steps: - Check the logs for errors with `rocketpool service logs validator` and `rocketpool service logs node`. - Confirm with a Block Explorer (such as your Grafana dashboard and [https://beaconcha.in](https://beaconcha.in)) that you are still attesting properly - Remember that if you have Doppelganger protection enabled, you will miss a few attestations after the restart. This is normal! ### Set Up MEV-Boost [MEV-boost](https://boost.flashbots.net/) is the system Flashbots provides to give MEV rewards to Proof-of-Stake validators after The Merge. **Rocket Pool requires all nodes to use it to maximize their returns and thus keep the protocol competitive with other staking services.** You will need to make some adjustments to your Beacon Node / Consensus client to connect it to MEV-boost. MEV-boost is currently not available on Hoodi or Mainnet, so you do not need to set it up at this time. Of course, you will not be penalized for not using it during this transition period. Once it becomes available, we will announce a date at which it must be installed and connected to your node. Flashbots will provide instructions you can follow at that time, and we will link to them here. ::: danger NOTE Once we make the announcement that MEV-boost must be enabled by all node operators, you must ensure you have it properly installed and configured with your Beacon Node! Not doing so will result in your minipool being [penalized](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system). ::: ### Set Up a Fallback Node Because The Merge is not compatible with remote providers like Infura and Pocket, you'll lose the ability to use them as fallback Execution clients when your primary goes offline. The Smart Node still has the ability to provide a fallback Execution client (and now a fallback Consensus client as well), but you will now need to use Execution and Consensus clients that you control. For more information on setting up a fallback node, see the [Fallback node guide](/node-staking/fallback.md). ### Initialize your Fee Distributor If you aren't planning to opt into the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool) and claim all of your priority fees and MEV rewards to your [fee distributor contract](/legacy/redstone/whats-new.md#fee-recipients-and-your-distributor), you will eventually have to initialize it (create the contract instance on the chain) in order to claim rewards from it to your withdrawal address. This is a fairly cheap operation and only needs to be done once. ::: tip TIP Initializing your fee distributor can be done at **any time**. You can let rewards accumulate in its address long before you initialize it, and your balance will remain after initialization. We recommend you do so when gas prices are low to minimize the overhead cost. Note that it **must be initialized in order to claim your rewards.** ::: ### Opt Into the Smoothing Pool If you plan on taking advantage of the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool) right away, you should opt in before the end of the first Redstone rewards period to maximize your "eligibility" amount. Opting in can be done via running the following command: ```shell rocketpool node join-smoothing-pool ``` ### Claim Rewards The Redstone upgrade replaces the expensive, problematic old rewards system with a [brand new one](/legacy/redstone/whats-new.md#new-rewards-system) that's much cheaper, supports automatic restaking of RPL (both partial and full amounts), and - most importantly - **lets you claim your rewards whenever you want**. Because there is no longer a time limit on claiming rewards, and because it's cheaper to claim many rewards intervals at once, the automatic rewards claiming feature of the Smart Node **has been removed**. You will now be able to claim rewards via the following command: ```shell rocketpool node claim-rewards ``` This will show you all of the rewards you've accumulated across all of the rewards intervals starting with the Redstone upgrade. ## Reverting to v1.4.3 If, for any reason, something isn't to your liking and you want to revert to the previous Smart Node release, you can do so easily. The Smart Node automatically backs up your settings from the previous version when you upgrade it, so simply get the previous version (here we're demonstrating **v1.4.3**) and replace the settings with the backup: 1. Stop the service: ```shell rocketpool service stop ``` 1. Download the v1.4.3 CLI: **Linux x64** `shell wget https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-linux-amd64 -O ~/bin/rocketpool ` **Linux arm64** `shell wget https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-linux-arm64 -O ~/bin/rocketpool ` **Mac x64** `shell curl -L https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool ` **Mac arm64** `shell curl -L https://github.com/rocket-pool/smartnode/releases/download/v1.4.3/rocketpool-cli-darwin-arm64 > /usr/local/bin/rocketpool ` 1. Install the v1.4.3 package: ```shell rocketpool service install -d ``` 1. Replace your old configuration with the v1.4.3 backup configuration: ```shell cp ~/.rocketpool/user-settings-backup.yml ~/.rocketpool/user-settings.yml ``` 1. Verify all of your old settings are now being used: ```shell rocketpool service config ``` 1. If it looks good, start the Smart Node stack: ```shell rocketpool service start ``` All set! You're now back on the old version and should begin attesting shortly after starting the service. ::: danger WARNING v1.4.3 is **deprecated** and will no longer be usable after the Redstone update is deployed. If you do need to revert to it, please make plans to upgrade back to v1.5.0 before the contracts are updated! ::: --- url: /legacy/redstone/native-migration.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # \[Native Mode] Guide to the Redstone Update and the Merge This guide will cover everything you need to know in order to prepare your node for the Redstone Update and The Merge if you are using **Native Mode**. ## Things to Do Before Upgrading to v1.5.0 Before upgrading to v1.5.0 and higher of the Smart Node, please go through the following checklist to make sure you're prepared: ### Switch to a Full Execution Client The Merge requires you to run your own Execution client, so you won't be able to use remote providers like Infura or Pocket anymore. Because of this change, if you're currently using a light Execution client, you should switch to a full client while you're still on v1.4, let it sync to completion, and then upgrade to v1.5. ### Set Up the Engine API The Merge changes the way your Execution client talks to your Consensus client. Instead of using the old HTTP or Websocket based RPC system, The Merge requires a new system exposed by your Execution client called the Engine API. This is a special connection that lets the Consensus client replace the old Proof-of-Work mining system with Proof-of-Stake; it's the heart of The Merge. It's also **authenticated** with a secret token, so only your Consensus client can connect to your Execution client - nothing else can. As you manage your own Execution and Consensus clients, you'll need to set up the Engine API manually. How to do it depends entirely on which clients you're running. CoinCashew has [a great and concise guide](https://www.coincashew.com/coins/overview-eth/ethereum-merge-upgrade-checklist-for-home-stakers-and-validators) on how to set up the Engine API on your Execution and Consensus clients. Give that a look, and test the new configuration out by making sure it still attests properly before upgrading. We'll show you how to set up your Validator client so that it uses the correct fee recipient required by the Smart Node software automatically below. ## Upgrading to v1.5.0 Upgrading the Smart Node stack to v1.5.0 is no different than any other upgrade. Simply follow [the normal directions here](/node-staking/updates.md#updating-the-smart-node-stack). ## Things You Should Do After Upgrading In Native mode, there are several things you will need to do manually after upgrading: ### Ensure a Successful Upgrade The first thing to do is ensure that your node is working correctly. Consider taking the following steps: - Check your log scripts for the Execution client, the Consensus client, the Validator client, and the Smart Node daemon (the `rp-node` service) to ensure they're all functioning normally without errors. - Confirm with a Block Explorer (such as your Grafana dashboard and [https://beaconcha.in](https://beaconcha.in)) that you are still attesting properly - Remember that if you have Doppelganger protection enabled, you will miss a few attestations after the restart. This is normal! ### Set up the Fee Recipient in your Validator Client One of the **critical** details to set up prior to the Merge is the **fee recipient** specified by your validator client. As described in the [overview article](/legacy/redstone/whats-new.md#fee-recipients-and-your-distributor), this can be one of two values: - If you **are opted into** the Smoothing Pool, this must be the address of the **Smoothing Pool contract**. You can get the address from [the official contracts page](/protocol/contracts-integrations.md). - If you are **not** in the Smoothing Pool, this must be the address of your node's **fee distributor contract**. You can get the address by running `rocketpool node status`, under the `Fee Distributor and Smoothing Pool` section. In Native mode, you have the choice of letting the Smart Node manage this for you if you use the Smart Node daemon service, `rp-node`, or managing it yourself if you do not use the daemon. #### Automatic Management via the Daemon The Smart Node daemon will automatically determine the appropriate fee recipient for your node and manage it in case it changes (such as opting into and out of the Smoothing Pool). This is the **safest** option, because the Smart Node will always ensure it's set to a value that **prevents [penalization](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system)**. The way it does this is by maintaining a file with the correct fee recipient in it, and regularly refreshing it to ensure its correctness. When it needs to be updated, it modifies the file and restarts your Validator client automatically so it loads the new recipient - similarly to how it restarts your Validator client after staking a new minipool. Select your client below to learn how to set it up: **Lighthouse** Modify your Validator Client service by adding the following line _before_ the `ExecStart` line: ``` EnvironmentFile=`data dir`/validators/rp-fee-recipient-env.txt ``` For example: ``` EnvironmentFile=/srv/rocketpool/data/validators/rp-fee-recipient-env.txt ``` Next, add the following command line argument _to the end_ of your `ExecStart` line: ``` --suggested-fee-recipient ${FEE_RECIPIENT} ``` Your VC will now use the file managed by the Smart Node daemon, and will automatically be restarted whenever the fee recipient changes. **Nimbus** Modify your Validator Client service by adding the following line _before_ the `ExecStart` line: ``` EnvironmentFile=`data dir`/validators/rp-fee-recipient-env.txt ``` For example: ``` EnvironmentFile=/srv/rocketpool/data/validators/rp-fee-recipient-env.txt ``` Next, add the following command line argument _to the end_ of your `ExecStart` line: ``` --suggested-fee-recipient=${FEE_RECIPIENT} ``` Your VC will now use the file managed by the Smart Node daemon, and will automatically be restarted whenever the fee recipient changes. **Prysm** Modify your Validator Client service by adding the following line _before_ the `ExecStart` line: ``` EnvironmentFile=`data dir`/validators/rp-fee-recipient-env.txt ``` For example: ``` EnvironmentFile=/srv/rocketpool/data/validators/rp-fee-recipient-env.txt ``` Next, add the following command line argument _to the end_ of your `ExecStart` line: ``` --suggested-fee-recipient ${FEE_RECIPIENT} ``` Your VC will now use the file managed by the Smart Node daemon, and will automatically be restarted whenever the fee recipient changes. **Teku** Modify your Validator Client service by adding the following line _before_ the `ExecStart` line: ``` EnvironmentFile=`data dir`/validators/rp-fee-recipient-env.txt ``` For example: ``` EnvironmentFile=/srv/rocketpool/data/validators/rp-fee-recipient-env.txt ``` Next, add the following command line argument _to the end_ of your `ExecStart` line: ``` --validators-proposer-default-fee-recipient=${FEE_RECIPIENT} ``` Your VC will now use the file managed by the Smart Node daemon, and will automatically be restarted whenever the fee recipient changes. #### Manual Fee Recipient Management ::: danger WARNING By doing this, you assume full responsibility for ensuring your fee recipient is always set to the correct address. Please read the [penalty specification](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system) to understand what it must be set to given your configuration, and when you can safely change it from one value to another. Failure to do so could result in your minipools being penalized! ::: **Prior to Redstone being deployed**, you can simply use the rETH address for the network you're on (which can be found in [the official contracts page](/protocol/contracts-integrations.md)). The rETH address is always safe no matter what. **Once Redstone has been deployed**, you can see the exact address that you should set your fee recipient to via `rocketpool node status`. For example, if you are opted into the Smoothing Pool, it will show the Smoothing Pool's address and note that you must use it as your fee recipient: ![](/static/image/native-fee-rc-in.a5ed95c176.png) If you are _not_ opted into the Smoothing Pool, it will show your fee distributor address and note that you must use it as your fee recipient: ![](/static/image/native-fee-rc-out.569a030690.png) Select your Consensus client below to learn how to configure it. **Lighthouse** Add the following command line argument to your Validator Client's service definition file: ``` --suggested-fee-recipient `address` ``` Where `address` is: - The [rETH address](/protocol/contracts-integrations/index.md#token-contracts) **before** the Redstone update is deployed (e.g., `0xae78736Cd615f374D3085123A210448E74Fc6393` on Mainnet) - Your node's **fee distributor** after Redstone is deployed, which you can retrieve with `rocketpool node status` once the contract upgrade occurs - The [Smoothing Pool address](/protocol/contracts-integrations/index.md#key-protocol-contracts) if you opt into the Smoothing Pool As a reminder, `rocketpool node status` will show you the correct fee recipient to use at any time. **Please read the [penalty specification](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system) carefully to understand the conditions and expectations around the fee recipient.** **Nimbus** Add the following command line argument to Nimbus's service definition file: ``` --suggested-fee-recipient=`address` ``` Where `address` is: - The [rETH address](/protocol/contracts-integrations/index.md#token-contracts) **before** the Redstone update is deployed (e.g., `0xae78736Cd615f374D3085123A210448E74Fc6393` on Mainnet) - Your node's **fee distributor** after Redstone is deployed, which you can retrieve with `rocketpool node status` once the contract upgrade occurs - The [Smoothing Pool address](/protocol/contracts-integrations/index.md#key-protocol-contracts) if you opt into the Smoothing Pool As a reminder, `rocketpool node status` will show you the correct fee recipient to use at any time. **Please read the [penalty specification](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system) carefully to understand the conditions and expectations around the fee recipient.** **Prysm** Add the following command line argument to your Validator Client's service definition file: ``` --suggested-fee-recipient `address` ``` Where `address` is: - The [rETH address](/protocol/contracts-integrations/index.md#token-contracts) **before** the Redstone update is deployed (e.g., `0xae78736Cd615f374D3085123A210448E74Fc6393` on Mainnet) - Your node's **fee distributor** after Redstone is deployed, which you can retrieve with `rocketpool node status` once the contract upgrade occurs - The [Smoothing Pool address](/protocol/contracts-integrations/index.md#key-protocol-contracts) if you opt into the Smoothing Pool As a reminder, `rocketpool node status` will show you the correct fee recipient to use at any time. **Please read the [penalty specification](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system) carefully to understand the conditions and expectations around the fee recipient.** **Teku** Add the following command line argument to your Validator Client's service definition file: ``` --validators-proposer-default-fee-recipient=`address` ``` Where `address` is: - The [rETH address](/protocol/contracts-integrations/index.md#token-contracts) **before** the Redstone update is deployed (e.g., `0xae78736Cd615f374D3085123A210448E74Fc6393` on Mainnet) - Your node's **fee distributor** after Redstone is deployed, which you can retrieve with `rocketpool node status` once the contract upgrade occurs - The [Smoothing Pool address](/protocol/contracts-integrations/index.md#key-protocol-contracts) if you opt into the Smoothing Pool As a reminder, `rocketpool node status` will show you the correct fee recipient to use at any time. **Please read the [penalty specification](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system) carefully to understand the conditions and expectations around the fee recipient.** ### Set Up MEV-Boost [MEV-boost](https://boost.flashbots.net/) is the system Flashbots provides to give MEV rewards to Proof-of-Stake validators after The Merge. **Rocket Pool requires all nodes to use it to maximize their returns and thus keep the protocol competitive with other staking services.** You will need to make some adjustments to your Beacon Node / Consensus client to connect it to MEV-boost. MEV-boost is currently not available on Hoodi or Mainnet, so you do not need to set it up at this time. Of course, you will not be penalized for not using it during this transition period. Once it becomes available, we will announce a date at which it must be installed and connected to your node. Flashbots will provide instructions you can follow at that time, and we will link to them here. ::: danger NOTE Once we make the announcement that MEV-boost must be enabled by all node operators, you must ensure you have it properly installed and configured with your Beacon Node! Not doing so will result in your minipool being [penalized](https://github.com/rocket-pool/rocketpool-research/blob/master/Penalties/penalty-system). ::: ### Set Up a Fallback Node Because The Merge is not compatible with remote providers like Infura and Pocket, you'll lose the ability to use them as fallback Execution clients when your primary goes offline. The Smart Node still has the ability to provide a fallback Execution client (and now a fallback Consensus client as well), but you will now need to use Execution and Consensus clients that you control. For more information on setting up a fallback node, see the [Fallback node guide](/node-staking/fallback.md). ### Initialize your Fee Distributor If you aren't planning to opt into the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool) and claim all of your priority fees and MEV rewards to your [fee distributor contract](/legacy/redstone/whats-new.md#fee-recipients-and-your-distributor), you will eventually have to initialize it (create the contract instance on the chain) in order to claim rewards from it to your withdrawal address. This is a fairly cheap operation and only needs to be done once. ::: tip TIP Initializing your fee distributor can be done at **any time**. You can let rewards accumulate in its address long before you initialize it, and your balance will remain after initialization. We recommend you do so when gas prices are low to minimize the overhead cost. Note that it **must be initialized in order to claim your rewards.** ::: ### Opt Into the Smoothing Pool If you plan on taking advantage of the [Smoothing Pool](/legacy/redstone/whats-new.md#smoothing-pool) right away, you should opt in before the end of the first Redstone rewards period to maximize your "eligibility" amount. Opting in can be done via running the following command: ```shell rocketpool node join-smoothing-pool ``` ### Claim Rewards The Redstone upgrade replaces the expensive, problematic old rewards system with a [brand new one](/legacy/redstone/whats-new.md#new-rewards-system) that's much cheaper, supports automatic restaking of RPL (both partial and full amounts), and - most importantly - **lets you claim your rewards whenever you want**. Because there is no longer a time limit on claiming rewards, and because it's cheaper to claim many rewards intervals at once, the automatic rewards claiming feature of the Smart Node **has been removed**. You will now be able to claim rewards via the following command: ```shell rocketpool node claim-rewards ``` This will show you all of the rewards you've accumulated across all of the rewards intervals starting with the Redstone upgrade. --- url: /legacy/redstone/whats-new.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # The Rocket Pool Redstone Update Rocket Pool's next major update, titled **Redstone**, has been released for beta testing on the Ropsten and Holesky test networks. This page describes the major changes that Redstone brings, including updates to both the Smart Node stack and to the Rocket Pool protocol in general. Please read through this page thoroughly to understand all of the differences between the previous version of Rocket Pool and Redstone. ::: tip ATTENTION For detailed information on how to prepare your node for the upgrade and what to do after the upgrade, please look at the following guides: - [Guide for Docker Mode](/legacy/redstone/docker-migration.md) - [Guide for Hybrid Mode](/legacy/redstone/hybrid-migration.md) - [Guide for Native Mode](/legacy/redstone/native-migration.md) ::: ## Client Changes and The Merge Ropsten (and shortly, Holesky) have successfully undergone **The Merge of the Execution and Consensus Layers**. It no longer uses Proof-of-Work; instead, validators on Ropsten are now responsible for creating and proposing blocks on both chains. While this comes with some exciting financial benefits (which will be discussed later), it also comes with some important changes to the way validators operate. Below is a brief summary of the changes to client behavior as part of The Merge: - Your Execution client now uses three API ports: - One for HTTP access to its API (**default 8545**) - One for Websocket access to its API (**default 8546**) - One for the new **Engine API** used by Consensus clients after The Merge (**default 8551**) - Execution clients now require a Consensus client to function, and Consensus clients now require an Execution client to function. - **Neither one can operate in isolation any longer.** - One Execution client must be linked to one, and only one, Consensus client (and vice versa). - You will not be able to link multiple Execution clients to a single Consensus client, or multiple Consensus clients to a single Execution client. - Because of this, **fallback execution clients are no longer available** for Rocket Pool node operators. - **Full execution clients** are required. - Remote providers (like Infura and Pocket) can no longer be used by any validators, Rocket Pool or otherwise. ## Fee Recipients and Your Distributor As validators are now responsible for creating blocks, that means they receive the **priority fees** (also known as **tips**) attached to each transaction. These fees are paid in ETH, and they are provided directly to you every time one of your minipool validators proposes a block. Unlike the ETH locked on the Beacon Chain, **you don't have to wait for withdrawals to access your priority fees**! They are simply awarded to you as part of the block proposal process. In order to know where to send the fees to, your Validator Client requires an extra parameter known as the `fee recipient`. This is the address on the Execution Layer (ETH1) that all of the priority fees earned by your node during block proposals will be sent to. Rocket Pool is designed to fairly distribute these rewards, the same way it fairly distributes your Beacon chain rewards: half of any priority fees your minipool validators earn will go to you (plus the average commission of all of your minipools), and the other half will go to the pool stakers (minus your average commission). To that end, the Smart Node will automatically set your Validator Client's `fee recipient` to a special address known as your node's **fee distributor**. Your fee distributor is a unique contract on the Execution Layer that's **specific to your node**. It will hold all of the priority fees you've earned over time, and it contains the logic required to fairly split and distribute them. This distribution process is controlled by you (the node operator), and can be done whenever you please. It does not have a time limit. The address for your node's fee distributor is **deterministically based on your node address**. That means it is known ahead of time, before the fee distributor is even created. **The Smart Node will use this address as your fee recipient.** ::: tip NOTE By default, your fee recipient will be set to the **rETH address** when you install Smart Node v1.5.0 (if the Redstone contract updates haven't been deployed yet). The Smart Node will automatically update this to your node's fee distributor address once the Redstone update has been deployed. One exception to this rule is if you are opted into the **Smoothing Pool** - see the section at the end of this page for more information on it. ::: New Rocket Pool nodes will automatically initialize their node's distributor contract upon registration. Existing nodes will need to do this process manually. This only needs to be run once. One interesting ramification of this is that your distributor's address may start accruing a balance **before** you've initialized your node distributor contract. This is okay, because your distributor will gain access to all of this existing balance as soon as you initialize it. You can view your fee distributor's balance as part of: ```shell rocketpool node status ``` The output will look like this: ![](/static/image/status-fee-distributor.ec05f77ee4.png) To initialize your node's distributor, simply run this new command: ```shell rocketpool node initialize-fee-distributor ``` ::: warning NOTE After the Redstone update, you must call this function before you can create any new minipools with `rocketpool node deposit`. ::: When your distributor has been initialized, you can claim and distribute its entire balance using the following command: ```shell rocketpool node distribute-fees ``` This will send your share of the rewards to your **withdrawal address**. ## Rocket Pool Protocol Changes In addition to the Execution and Consensus client changes and the new priority fees, the Rocket Pool protocol itself has undergone some important changes you should be aware of. ### New Rewards System One of the most significant changes introduced with the Redstone update is the **new rewards system**. This is a complete overhaul of the way node operators receive their RPL rewards (and ETH from the Smoothing Pool - discussed later). The _old_ rewards system had the following drawbacks: - Claiming cost approximately 400k gas, which is quite expensive. - Node operators had to claim the rewards at each interval (every 28 days), or would forfeit them. This meant the gas costs could become prohibitively expensive for node operators with small amounts of RPL. - Rewards were determined at the time of the _claim_, not at the time of the checkpoint. If a user staked a significant amount of RPL between the checkpoint and your claim, your rewards could be diluted and you'd receive less RPL than you were expecting. The _new_ claims system solves all of these problems. At every interval, the Oracle DAO will collectively create a **true snapshot** of the state of the node operators in the Rocket Pool network, including all of their effective stake amounts. This information is compiled into a [Merkle Tree](https://en.wikipedia.org/wiki/Merkle_tree) - an extremely efficient way to make all of the details available to smart contracts. The Merkle Tree is built into a JSON file and hosted on GitHub, and the root of the Merkle Tree is submitted to the contracts. This new system has the following features: - You can now **let rewards accumulate** for as long as you want. No more time limit on when you need to claim. - You can claim **multiple intervals** all at once. - Your first claim transaction uses about 85k gas. Each subsequent claim transaction costs about 55k gas. - If you're claiming multiple intervals at once, each supplemental interval costs **6k gas** so it's most cost-effective to claim as many of them at once as possible. - Your RPL rewards **no longer get diluted** - your RPL rewards are fixed at the time of the snapshot, and you are always eligible for that amount. - You can **restake some (or all) of your RPL rewards** as part of the claiming transaction, which further trims down gas requirements compared to today. - Currently, **all of your claims must be on Mainnet** but we have the infrastructure in place to build the ability to claim on Layer 2 networks at a later date. When your node detects a new rewards checkpoint, it will automatically download the JSON file for that interval. You can then review your rewards using the following command: ```shell rocketpool node claim-rewards ``` As intervals go by and you accumulate rewards, the output will look like this: ![](/static/image/claim-rewards-gb.bd6aec354a.png) Here you can quickly see how many rewards you've earned at each interval, and can decide which ones you want to claim. Note that **Ropsten's interval time is set to 1 day to facilitate testing.** You can also specify an amount you want to restake during this claim: ![](/static/image/autostake.4de0b52e8e.png) This will let you compound your RPL rewards in one transaction, using substantially less gas than you currently need to use today. ::: tip NOTE If you prefer to build the rewards checkpoint manually instead of downloading the one created by the Oracle DAO, you can change this setting from `Download` to `Generate` in the TUI: ![](/static/image/tui-generate-tree.9f862c08b7.png) As the tip implies, you will need access to an archive node to do this. If your local Execution client is not an archive node, you can specify a separate one (such as Infura or Alchemy) in the `Archive-Mode EC URL` box below it. This URL will only be used when generating Merkle trees; it will not be used for validation duties. ::: ::: danger WARNING If you are below 10% RPL collateral _at the time of the snapshot_, you will not be eligible for rewards for that snapshot. Unlike the current system, where you can simply "top off" before you claim in order to become eligible again, this will be locked in that snapshot forever and **you will never receive rewards for that period**. You **must** be above 10% collateral at the time of a snapshot in order to receive rewards for that period. ::: ### Smoothing Pool One final exciting new feature of the Redstone update is the **Smoothing Pool**. The Smoothing Pool is **an opt-in feature** that will collectively pool the priority fees of every member opted into it. During a rewards checkpoint, the total ETH balance of the pool is divided into a pool staker portion and a node operator portion. All of the rewards in the node operator portion are **distributed fairly to every member of the pool**. In essence, the Smoothing Pool is a way to effectively eliminate the randomness associated with block proposals on the Beacon Chain. If you've ever had a streak of bad luck and gone months without a proposal, you may find the Smoothing Pool quite exciting. ::: tip NOTE The Smoothing Pool rewards are built into the Merkle Tree used for RPL rewards, so you claim them at the same time you claim RPL using `rocketpool node claim-rewards`. ::: To help clarify the details, the Smoothing Pool uses the following rules: - Opting into the Smoothing Pool is done on a **node level**. If you opt in, all of your minipools are opted in. - The node operator's total share is determined by the average commission of every minipool in every node opted into the Smoothing Pool. - Anyone can opt in at any time. They must wait a full rewards interval (1 day on Ropsten, 28 days on Mainnet) before opting out to prevent gaming the system. - Once opted out, you must wait another full interval to opt back in. - The Smoothing Pool calculates the "share" of each minipool (portion of the pool's ETH for the interval) owned by each node opted in. - The share is a function of your minipool's performance during the interval (calculated by looking at how many attestations you sent on the Beacon Chain, and how many you missed), and your minipool's commission rate. - Your node's total share is the sum of your minipool shares. - Your node's total share is scaled by the amount of time you were opted in. - If you were opted in for the full interval, you receive your full share. - If you were opted in for 30% of an interval, you receive 30% of your full share. To opt into the Smoothing Pool, run the following command: ```shell rocketpool node join-smoothing-pool ``` This will record you as opted-in in the Rocket Pool contracts and automatically change your Validator Client's `fee recipient` from your node's distributor contract to the Smoothing Pool contract. To leave the pool, run this command: ```shell rocketpool node leave-smoothing-pool ``` ### The Penalty System To ensure that node operators don't "cheat" by manually modifying the fee recipient used in their Validator Client, Rocket Pool employs a penalty system. The Oracle DAO constantly monitors each block produced by Rocket Pool node operators. Any block that has a fee recipient other than one of the following addresses is considered to be **invalid**: - The rETH address - The Smoothing Pool address - The node's fee distributor contract (if opted out of the Smoothing Pool) A minipool that proposed a block with an **invalid** fee recipient will be issued **a strike**. On the third strike, the minipool will begin receiving **infractions** - each infraction will dock **10% of its total Beacon Chain balance, including ETH earnings** and send them to the rETH pool stakers upon withdrawing funds from the minipool. Infractions are at a **minipool** level, not a **node** level. The Smart Node software is designed to ensure honest users will never get penalized, even if it must take the Validator Client offline to do so. If this happens, you will stop attesting and will see error messages in your log files about why the Smart Node can't correctly set your fee recipient. ## Guides for Pre- and Post-Upgrade For detailed information on how to prepare your node for the upgrade and what to do after the upgrade, please look at the following guides: - [Guide for Docker Mode](/legacy/redstone/docker-migration.md) - [Guide for Hybrid Mode](/legacy/redstone/hybrid-migration.md) - [Guide for Native Mode](/legacy/redstone/native-migration.md) --- url: /legacy/upgrading.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Migrating the Smart Node from Previous Beta Tests If you've been a Rocket Pool node operator during our previous beta tests on Medalla or Pyrmont, thank you for helping us improve the protocol and welcome back! This brief guide will walk you through the process of purging your own beta build and setting up the newest build for either the Hoodi testnet, or for real staking on mainnet. **Hoodi Network**

NOTE

You will need to create a new node wallet to interact with the Hoodi test network. Re-using a wallet from a previous beta build may result in failures while creating new validators! There are three major steps towards upgrading from a beta build to the Hoodi test network. First, migrate any hoodi ETH you have to a separate wallet. You can then migrate it back to the new node wallet you create after you reinstall Rocket Pool, so you don't need to rely as much on a faucet for hoodi ETH. The easiest way to do this is via Metamask - see the [rETH staking guide](/liquid-staking/overview.md) for a walkthrough of how to set up a new wallet. You can do this using the following command: ```shell rocketpool node send XXX eth 0xabcd1234... ``` where `XXX` is the amount of hoodi ETH to send, and `0xabcd1234...` is the address of the new wallet you created. **Note that you'll need to leave a little bit of ETH behind to pay for the gas used in the transaction!** Next, remove all the old Docker images and chain data with the following command: ```shell rocketpool service terminate ``` Once this is done, remove the old Rocket Pool data and settings folder. **This will delete your old wallet and your old validators, so make sure you no longer need to save them for anything!** ```shell sudo rm -rf ~/.rocketpool ``` Once this is done, your old beta setup will be cleaned. You can follow the [Rocket Pool installation guide](/node-staking/eth-clients.md) for a walkthrough on installing and configuring Rocket Pool for the Hoodi testnet. **Mainnet Network** _Coming soon!_ --- url: /legacy/v1.3-update.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Upgrading to Smart Node v1.3.x Version 1.3.0 of the Smart Node stack brings some important changes that users should be aware of. They are designed to significantly improve your node operator experience and address many of the features that our users have requested since Rocket Pool's launch. In this guide, we'll walk you through the process of migrating from an older version of the Smart Node from an older version to v1.3.x and beyond. ## Configuration File Changes v1.3.0 introduces some significant changes in the way the Smart Node's configuration is managed. If you've manually modified the Smart Node configuration before, you should be aware of the following changes: - The `config.yml` file has been removed. All of its information is now baked directly into the Smart Node stack, so users can no longer accidentally modify the file in a way that prevented the Smart Node from working properly. - All of the user-configurable parameters that were previously part of it are now settings in the new `service config` Terminal UI. - The `settings.yml` file has been replaced with a new file called `user-settings.yml`. This contains all of your settings for every user-configurable portion of the Smart Node. - This file is **not meant to be modified directly**. Modification should be done through the new `service config` Terminal UI instead. - The `chains` folder has been removed. The scripts for launching the Execution Client (ETH1), the Beacon Node, and the Validator Client now reside in the `scripts` folder. - The `docker-compose` YAML files have been removed. Each container now gets its own file in the `templates` folder. Upon `rocketpool service start`, these templates are filled out with your settings and put into the `runtime` folder automatically. - Modifying the templates or runtime files is not recommended. Instead, fill in your container customizations using the **override** files for each container in the `override` folder. These files will overwrite the Docker files in `runtime`, so you are free to customize them as you see fit. - The files in `override` **will persist upon Smart Node upgrades and reinstallation** so you only need to create them once. - If you are interested in modifying the `docker-compose` files via this override mechanic, please see [this section](/node-staking/advanced-config.md#customizing-the-docker-compose-definition-files) ## Installing the New Version Installing the new version should feel very familiar. Start by stopping the services and downloading the new CLI as usual: **Docker or Hybrid Mode** Stop the Rocket Pool services: ``` rocketpool service stop ``` Download the new Smart Node CLI for your system (choose from the tabs below): **Linux x64** For `x64` systems (most normal machines): ```shell wget https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-linux-amd64 -O ~/bin/rocketpool ``` **Linux arm64** For `arm64` systems: ```shell wget https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-linux-arm64 -O ~/bin/rocketpool ``` **macOS x64** For `x64` systems (most Macs): ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool ``` **macOS arm64** For `arm64` systems, such as the Mac mini with M1: ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-darwin-arm64 > /usr/local/bin/rocketpool ``` Now run the install command: ``` rocketpool service install -d ``` The `-d` flag tells it to ignore system dependencies like Docker, since you already have them.

NOTE

As of v1.3.0, you **no longer have to specify which network you want to install for!** The new Smart Node will know which network you're already using, and it will let you change your network dynamically using the new Terminal UI. **Native Mode**

NOTE

This will only update the Smart Node stack itself - it **will not** update your Execution and Consensus clients. You will have to do this manually (see [the manual update guide](/node-staking/updates.md#manually-updating-the-execution-or-consensus-client) to learn how to do it). Stop the Rocket Pool services: ```shell sudo systemctl stop rp-node rp-watchtower ``` Download the new Smart Node CLI and daemon binaries: **Linux x64** For `x64` systems (most normal machines): ```shell sudo wget https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-linux-amd64 -O /usr/local/bin/rocketpool sudo wget https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-daemon-linux-amd64 -O /usr/local/bin/rocketpoold ``` **Linux arm64** For `arm64` systems: ```shell sudo wget https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-linux-arm64 -O /usr/local/bin/rocketpool sudo wget https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-daemon-linux-arm64 -O /usr/local/bin/rocketpoold ``` **macOS x64** For `x64` systems (most Macs): ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool curl -L https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-daemon-darwin-amd64 > /usr/local/bin/rocketpoold ``` **macOS arm64** For `arm64` systems, such as the Mac mini with M1: ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-cli-darwin-arm64 > /usr/local/bin/rocketpool curl -L https://github.com/rocket-pool/smartnode-install/releases/latest/download/rocketpool-daemon-darwin-arm64 > /usr/local/bin/rocketpoold ```

NOTE

As of v1.3.0, `config.yml` has been removed. **You no longer need to download the installer package and extract it.** Next, create a backup folder called `old_config_backup` in your Smart Node directory and move your old configuration files into it (`config.yml` and `settings.yml`). The Smart Node will use these to migrate your settings to the new system. For example, if you followed the Native setup guide and your Smart Node directory is `/srv/rocketpool`: ```shell cd /srv/rocketpool mkdir old_config_backup mv config.yml old_config_backup mv settings.yml old_config_backup ``` Now, modify the service definition files for `rp-node`: ```shell sudo nano /etc/systemd/system/rp-node.service ``` Replace the `ExecStart` line with the following: ``` ExecStart=/home/ubuntu20/bin/rocketpoold --settings /srv/rocketpool/user-settings.yml node ``` Note that the `--config` flag has been removed, and `--settings` now points to `user-settings.yml`. **Don't worry that this file doesn't exist yet; it will be generated automatically in the next step.**

NOTE

If you are an Oracle DAO member, you _must_ repeat the above process for the `rp-watchtower` service as well. Finally, reload the service definitions: ```shell sudo systemctl daemon-reload ``` After the installation, all of your old configuration files will be moved to a folder named `old_config_backup` in your Smart Node directory (by default `~/.rocketpool/old_config_backup`). You can find them there if you ever need to refer to them for any reason. **If you are looking for instructions on reverting to v1.2.4 from this backup, please scroll to the [Reverting to Your Previous Configuration](#reverting-to-your-previous-configuration) section at the end of this page.** ## Configuring the Smart Node with the Terminal UI Now that you have the new CLI and package installed, all of your previous settings have been preserved and migrated to the new system. In the next step, you should run `rocketpool service config`. This will look quite different compared to previous versions of this function; v1.3.0 introduces the **Terminal UI**: a terminal-based dynamic user interface for configuring your Smart Node. You must run it before starting the Docker containers after the migration process to view the configuration, verify that all of your changes were migrated successfully, and update any other settings that you desire. When you first run it, you will be prompted with this greeting screen (if you were using **Docker or Hybrid mode**): ![](/static/image/tui-migrate.1aa6d01ae7.png) :::tip NOTE **Native Mode users** will see this screen with slightly different wording, which states the Smart Node is operating in Native mode. ::: The TUI will begin with **the Wizard**, which allows you to quickly and easily change the most important parameters of the Smart Node (such as client mode and selection). **All of your previous settings should already be highlighted as you traverse through each page of the wizard so you don't have to remember what your previous configuration was off the top of your head.** :::warning NOTE **For a detailed walkthrough of this Wizard, please visit the following pages:** - For **Docker Mode**, please visit [the new Docker configuration guide](/node-staking/config-docker.md). - **Hybrid Mode** users: Hybrid Mode is now a **first-class feature** of the Smart Node and configuring it is _much_ easier than it used to be. Please visit [the new Docker configuration guide](/node-staking/config-docker.md) and follow it. When you are prompted to choose an Execution client mode and Consensus client mode, choose **Externally Managed** for them accordingly. - For **Native Mode**, please visit [the new Native configuration guide](/node-staking/config-native.md). ::: Navigate through this wizard and confirm that all of your settings are correct. Once you are done, you will have the option of **reviewing all of the settings before saving** if you desire. This includes settings that the Wizard didn't cover, such as the **RPL claim gas threshold** or your **max number of Geth peers** as examples. The **main settings screen**, which you should also look at to confirm your previous settings, will look like this (for Docker and Hybrid mode users): ![](/static/image/tui-settings-home.952239333f.png) :::tip NOTE **Native Mode users** will see a slightly different screen that is unique to Native mode and only presents the settings that are relevant for it. ::: Feel free to explore this new UI and adjust any settings you see fit. Use the `Arrow Keys` to navigate, and press `Enter` to enter a category or confirm any changes to a setting that you make. Press `Esc` when you're finished editing a category to return to this home screen. When you're ready to save your changes and start the Smart Node stack, simply press `Tab` to move down to the buttons at the bottom of the screen, select `Review Changes and Save` (by making it green via the arrow keys). Press `Enter` to be brought to the **Review Page**, where you can see everything you've changed since the last time you ran `rocketpool service config`. Confirm all of your change are present, and then press `Enter` again to save them. The screen will show you which containers need to be restarted for the changes to apply, though since you're migrating, you've already turned the containers off and they will all be restarted anyway. ## Starting the Smart Node Stack Once you've saved your configuration, the terminal will ask if you want to restart the containers automatically (unless you're using Native mode). If you do not / cannot allow them to start automatically, you can start them up manually with the following commands: **Docker or Hybrid Mode** `shell rocketpool service start ` **Native Mode** `shell sudo systemctl start rp-node rp-watchtower ` Once they're up, you can verify that everything is working as intended. Use the `rocketpool service version` command to check that you have the correct version of the Smart Node and client containers: ``` $ rocketpool service version Your Smartnode is currently using the Hoodi Test Network. Rocket Pool client version: 1.3.0-rc1 Rocket Pool service version: 1.3.0-rc1 Selected Eth 1.0 client: Geth (Locally managed) Image: ethereum/client-go:v1.10.16 Selected Eth 2.0 client: Nimbus (Locally managed) Image: statusim/nimbus-eth2:multiarch-v22.3.0 ``` Use the `rocketpool service logs eth1` and `rocketpool service logs eth2` commands to watch the logs for your Execution client (formerly ETH1 client) and your Consensus client (formerly ETH2 client). Look out for any errors and [please visit our Discord server for help](https://discord.com/invite/rocketpool) if you encounter them. ## Reverting to your Previous Configuration If, for any reason, you need to revert back to v1.2.4 of the Smart Node stack, don't worry! All of your old configuration files have been preserved in a backup directory and can easily be retrieved to restore your previous setup. Select which mode you use from the tabs below and follow the instructions. **Docker or Hybrid Mode** Start by replacing the CLI with the v1.2.4 CLI for your system: **Linux x64** For `x64` systems (most normal machines): ```shell wget https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-linux-amd64 -O ~/bin/rocketpool ``` **Linux arm64** For `arm64` systems: ```shell wget https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-linux-arm64 -O ~/bin/rocketpool ``` **macOS x64** For `x64` systems (most Macs): ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool ``` **macOS arm64** For `arm64` systems, such as the Mac mini with M1: ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-darwin-arm64 > /usr/local/bin/rocketpool ``` Next, copy all of your old configuration files from the `old_config_backup` folder back into the Smart Node's folder: ```shell cd ~/.rocketpool cp -r old_config_backup/* ``` Now, all you need to do is restart the Docker containers: ```shell rocketpool service start ``` Done! Your old configuration is back. **Native Mode** Stop the Rocket Pool services: **Linux x64** For `x64` systems (most normal machines): ```shell sudo wget https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-linux-amd64 -O /usr/local/bin/rocketpool sudo wget https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-daemon-linux-amd64 -O /usr/local/bin/rocketpoold ``` **Linux arm64** For `arm64` systems: ```shell sudo wget https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-linux-arm64 -O /usr/local/bin/rocketpool sudo wget https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4rocketpool-daemon-linux-arm64 -O /usr/local/bin/rocketpoold ``` **macOS x64** For `x64` systems (most Macs): ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool curl -L https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-daemon-darwin-amd64 > /usr/local/bin/rocketpoold ``` **macOS arm64** For `arm64` systems, such as the Mac mini with M1: ```shell curl -L https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-cli-darwin-arm64 > /usr/local/bin/rocketpool curl -L https://github.com/rocket-pool/smartnode-install/releases/download/v1.2.4/rocketpool-daemon-darwin-arm64 > /usr/local/bin/rocketpoold ``` Copy the previous settings files back into your Smart Node directory: ```shell cd /srv/rocketpool cp old_config_backup * ``` Now, revert the service definition files for `rp-node`: ```shell sudo nano /etc/systemd/system/rp-node.service ``` Replace the `ExecStart` line with the following: ``` ExecStart=/usr/local/bin/rocketpoold --config /srv/rocketpool/config.yml --settings /srv/rocketpool/settings.yml node ```

NOTE

If you are an Oracle DAO member, you _must_ repeat the above process for the `rp-watchtower` service as well. Finally, reload the service definitions and restart the services: ```shell sudo systemctl daemon-reload sudo systemctl start rp-node rp-watchtower ``` Done! Your old configuration is back. --- url: /liquid-staking/via-l1.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Staking via a Decentralized Exchange on the Ethereum Network (Layer 1) As a reminder, you do not have to swap ETH for rETH directly via Rocket Pool in order to enjoy the benefits of decentralized staking. All you need to do is hold rETH as it inherently grows in value - how you get it doesn't matter! rETH is available for trade on several decentralized exchanges, such as [Balancer](https://docs.balancer.fi/) and [Uniswap](https://docs.uniswap.org/protocol/introduction). The **Balancer** pool is a special kind of pool known as a [metastable pool](https://docs.balancer.fi/concepts/pools/composable-stable.html). Metastable pools are ideal for tokens like rETH, because **they honor the true exchange rate reported by the Oracle DAO**. This means exchanging with this pool will have **much lower slippage** and **lower fees** than a conventional decentralized exchange, so you get a much better deal when buying or selling rETH. Other decentralized exchanges don't have this property, so you may find that their exchange rate is slightly lower. Regardless of which pool you use, they all **tend to have lower gas fees** than staking via the official Rocket Pool website. This makes them a great choice for users that want to stake a small amount of ETH, though it's always a good idea to compare the rate you would receive on an exchange with the exchange rate according to Rocket Pool. In the following examples, we will show how to swap ETH for rETH using both Balancer and Uniswap. ::: warning NOTE Currently this method is only available on Mainnet. If you want to practice on the Hoodi Testnet, you must [swap with Rocket Pool directly](/liquid-staking/via-rp.md). **The rest of this guide will assume you are on Mainnet.** ::: This process can be completed with any web3-compatible wallet. For demonstration purposes, we're going to use [MetaMask](https://metamask.io/) as it is one of the more popular wallet choices. **You should be able to follow along using similar steps with a different wallet if you choose - just find the comparable function in your wallet for each step.** ## Setting up MetaMask Start by installing [MetaMask](https://metamask.io/) if you haven't already. Follow the instructions on their site to install the extension, create an account, and sign in. Next, open the MetaMask panel using its icon in your browser toolbar. Click on the **network dropdown** in the toolbar at the top and ensure that **Ethereum Mainnet** is selected: ![](/static/image/mm_network_main.1536c3b585.png) Finally, add the rETH token to MetaMask so you can see your balance and access it for trading. Click the **Assets** tab, then click **Add Token**: ![](/static/image/mm_add_token.565f58b7f4.png) Ensure that **Custom Token** is selected in this dialog. In the **Token Contract Address** box, put the following value: ``` 0xae78736Cd615f374D3085123A210448E74Fc6393 ``` The **Token Symbol** should automatically be populated with `rETH`, and the **Decimals of Precision** should automatically be populated with `18`. Accept the rest of the prompts, and then you will see the rETH token appear in your list. Now that you have a wallet address in MetaMask, you need to transfer some ETH into it. **You will need to supply this from an existing wallet or buy ETH on an exchange.** ## Swapping for rETH via Balancer Now that your wallet is set up and funded, head to this URL which will open Balancer and automatically show swapping ETH for rETH: [https://app.balancer.fi/#/trade/ether/0xae78736Cd615f374D3085123A210448E74Fc6393](https://app.balancer.fi/#/trade/ether/0xae78736Cd615f374D3085123A210448E74Fc6393) The page will look like this initially: ![](/static/image/balancer.6b22623ba6.png) Click on the `Connect wallet` button in the top-right corner. You will be prompted with a screen that asks you which wallet provider you want to use. For this example, select **MetaMask**. ::: tip NOTE If you're not using MetaMask, one of the other providers such as WalletConnect will likely be compatible with your wallet. ::: Upon clicking that button, MetaMask will pop up with a prompt asking you to select which accounts you want to use. Assuming you only have one, your account should already be selected. Click **Next**. It will then ask if you would like to give Balancer access to view the addresses of your accounts: ![](/static/image/bal_connect.9ef2e405eb.png) Click **Connect** and after a brief pause window, your wallet will be connected to Balancer. You should now see its ETH balance in the top left side of the screen. Now, enter the amount of ETH you want to swap and Balancer's UI will show you the amount of rETH you will receive in return: ![](/static/image/bal_swap.d9fb0c3a40.png) ::: warning NOTE Notice that the amount of rETH you receive will be **less than** the amount of ETH you put in. This is normal, because **rETH is worth more than ETH** and continuously appreciates over time. You can see this in the exchange rate highlighted at the right of the screenshot. ::: Click **Preview** to see the details of the trade, including the minimum amount you could receive due to slippage. If you're satisfied, click **Confirm trade**. This will send the request to MetaMask, where you can review the total transaction cost before confirming it: ![](/static/image/mm_gas.b762180de7.png) ::: warning NOTE Pay **close attention** to the estimated gas fee here, highlighted in red. If it's a significant amount of your overall transaction (here it's over 17%), then it will take a **very long time** before you break even on staking rewards. If this is the case, you should either wait for the network's average gas price to drop, or [consider using a Layer 2 solution instead](/liquid-staking/via-l2.md). ::: If you are happy with the gas fees relative to the total amount of rETH you'll be receiving, click **Confirm** to submit the transaction. After a short period, you should see a notification from MetaMask that it completed successfully, and you will now see the rETH token in your wallet. That's it! You're now staking with Rocket Pool. All you need to do is hold onto your rETH, and you'll automatically gain your staking rewards as the value of the rETH token increases. ## Swapping for rETH via Uniswap While we recommend you stake through Balancer because it has lower fees and a more accurate ETH-rETH rate, you can also swap for rETH via Uniswap if the need arises. Head to this URL which will open Uniswap and automatically show swapping ETH for rETH: [https://app.uniswap.org/#/swap?inputCurrency=eth\&outputCurrency=0xae78736cd615f374d3085123a210448e74fc6393](https://app.uniswap.org/#/swap?inputCurrency=eth\&outputCurrency=0xae78736cd615f374d3085123a210448e74fc6393) ::: warning NOTE You may initially be prompted with a warning that looks like this: ![](/static/image/unknown_token.aee8d8c3f9.jpg) This is just a temporary warning until Uniswap adds rETH to its canonical token list. As long as the token address is `0xae78736cd615f374d3085123a210448e74fc6393`, you can add it safely. ::: The page will look like this initially: ![](/static/image/uni_connect.cd51433cd5.png) Click on one of the `Connect Wallet` buttons such as the highlighted one in the top-right corner. You will be prompted with a screen that asks you which wallet provider you want to use. For this example, select **MetaMask**. ::: tip NOTE If you're not using MetaMask, one of the other providers such as WalletConnect will likely be compatible with your wallet. ::: Upon clicking that button, MetaMask will pop up with a prompt asking you to select which accounts you want to use. Assuming you only have one, your account should already be selected. Click **Next**. It will then ask if you would like to give Uniswap access to view the addresses of your accounts: ![](/static/image/mm_connect.746bb044e5.png) Click **Connect** and after a brief pause window, your wallet will be connected to Uniswap. You should now see its ETH balance in the top right corner of the screen. Now, enter the amount of ETH you want to swap and Uniswap's UI will show you the amount of rETH you will receive in return: ![](/static/image/uni_swap.b37de8975f.png) ::: warning NOTE Notice that the amount of rETH you receive will be **less than** the amount of ETH you put in. This is normal, because **rETH is worth more than ETH** and continuously appreciates over time. You can see this in the exchange rate highlighted at the bottom of the screenshot. ::: Click **Swap** to see the details of the trade, including the minimum amount you could receive due to slippage. If you're satisfied, click **Confirm Swap**. This will send the request to MetaMask, where you can review the total transaction cost before confirming it: ![](/static/image/mm_gas.b762180de7.png) ::: warning NOTE Pay **close attention** to the estimated gas fee here, highlighted in red. If it's a significant amount of your overall transaction (here it's over 17%), then it will take a **very long time** before you break even on staking rewards. If this is the case, you should either wait for the network's average gas price to drop, or [consider using a Layer 2 solution instead](/liquid-staking/via-l2.md). ::: If you are happy with the gas fees relative to the total amount of rETH you'll be receiving, click **Confirm** to submit the transaction. After a short period, you should see a notification from MetaMask that it completed successfully, and you will now see the rETH token in your wallet. That's it! You're now staking with Rocket Pool. All you need to do is hold onto your rETH, and you'll automatically gain your staking rewards as the value of the rETH token increases. --- url: /liquid-staking/via-l2.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Staking via a Decentralized Exchange on Layer 2 As a reminder, you do not have to swap ETH for rETH directly via Rocket Pool in order to enjoy the benefits of decentralized staking. All you need to do is hold rETH as it inherently grows in value - how you get it doesn't matter! That being said, one of the main concerns (especially in recent times) is the cost of gas associated with staking or swapping ETH for rETH. To help reduce this, the Ethereum network has started adopting the use of [rollups](https://www.youtube.com/watch?v=7pWxCklcNsU) - also known as **Layer 2**. Layer 2 comprises several separate networks that live underneath Ethereum, executing lots of transactions like Ethereum normally would, but rolling all of them up into one single "mega" transaction and posting _that_ to the main Ethereum chain instead. Ideally, this means you'd get all of the security benefits associated with Ethereum's decentralized nature, but enjoy **much lower gas fees** for your transactions since execution and storage costs on Layer 2s can be much lower and only a portion of your transactions must be stored on Layer 1 where state is much more expensive. Rocket Pool currently supports two Layer 2 networks: [Optimism](https://www.optimism.io/) and [Arbitrum](https://arbitrum.io/). Both of them have running versions of [Uniswap](https://docs.uniswap.org/protocol/introduction), the most widely-used decentralized exchange protocol. With Uniswap, you can quickly and easily exchange ETH for rETH. The advantage of using this approach is that **gas fees will be substantially lower** than with other methods. If this is important to you because you want to stake a small amount of ETH, then using a Layer 2 network is likely going to be your option of choice. The disadvantage is that you might not get the best deal on rETH. Uniswap requires a small fee that's given to its liquidity providers, and large transactions will require large liquidity pools in order to get good deals without too much price impact. Layer 2 networks tend to have lower rETH liquidity than the main Ethereum network. Therefore, we recommend you compare the total rETH you would get on a Layer 2 network with what you'd get via the other methods to determine if it makes sense for you to pursue this path. You can view the current ETH and rETH balances of the [Optimism pool](https://info.uniswap.org/#/optimism/pools/0xaefc1edaede6adadcdf3bb344577d45a80b19582) and the [Arbitrum pool](https://info.uniswap.org/#/arbitrum/pools/0xaac7de2b91293ba1791503d9127d2bdf2159db65) to determine if they have enough rETH to cover your swap. In the following example, we will demonstrate how to interact with Layer 2 networks and use Uniswap to swap ETH for rETH. ::: warning NOTE Currently this method is only available on Mainnet. If you want to practice on the Hoodi Testnet, you must [swap with Rocket Pool directly](/liquid-staking/via-rp.md). **The rest of this guide will assume you are on Mainnet.** ::: This process can be completed with any web3-compatible wallet. For demonstration purposes, we're going to use [MetaMask](https://metamask.io/) as it is one of the more popular wallet choices. **You should be able to follow along using similar steps with a different wallet if you choose - just find the comparable function in your wallet for each step.** ## Setting up MetaMask on Mainnet Start by installing [MetaMask](https://metamask.io/) if you haven't already. Follow the instructions on their site to install the extension, create an account, and sign in. Next, open the MetaMask panel using its icon in your browser toolbar. Click on the **network dropdown** in the toolbar at the top and ensure that **Ethereum Mainnet** is selected: ![](/static/image/mm_network_main.1536c3b585.png) The address directly below that is your **Ethereum wallet address**. Before going any further, you will need to supply this wallet with ETH. If you don't already have ETH in the account from prior usage, you can do this by transferring ETH from an existing account to this wallet address. ## Transferring ETH from Layer 1 to Layer 2 via Hop There are several ways to bridge ETH from the Ethereum Mainnet to a Layer 2 network. In this demonstration, we're going to use the [Hop](https://docs.hop.exchange/faq) protocol - a simple and reliable way to move ETH (and a few other coins) from Layer 1 to several Layer 2 networks, or between Layer 2 networks. Navigate to the Hop exchange website here: [https://app.hop.exchange/send?token=ETH](https://app.hop.exchange/send?token=ETH) The home screen should look like this: ![](/static/image/hop.76bac0190a.png) Start by clicking on the **Connect a Wallet** button in the top right corner. You will be prompted with a screen that asks you which wallet provider you want to use. For this example, select **MetaMask**. ::: tip NOTE If you're not using MetaMask, one of the other providers such as WalletConnect will likely be compatible with your wallet. ::: Upon clicking that button, MetaMask will pop up with a prompt asking you to select which accounts you want to use. Assuming you only have one, your account should already be selected. Click **Next**. It will then ask if you would like to give Hop access to view the addresses of your accounts: ![](/static/image/hop_connect.9b54fd9588.png) Click **Connect** and after a brief pause, your wallet will be connected to Hop. You should now see its ETH balance in the top right corner of the screen. Now, you can use the two dropdowns in the **From** and **To (estimated)** boxes to select your networks, and enter the amount of ETH you want to send in the **From** box. For example, this is what it would look like to send 0.1 ETH from Layer 1 to Arbitrum: ![](/static/image/hop_send.06f661016a.png) ::: warning NOTE As a reminder, Uniswap (and thus Rocket Pool staking) is currently **only supported on Optimism and Arbitrum**. You must select one of those networks. ::: When you're ready, click the **Send** button. Metamask will pop up with a confirmation dialog that shows you the gas fee associated with the transaction: ![](/static/image/hop_confirm.2c546072d8.png) If you are comfortable with those gas fees, click **Confirm** to begin the transaction. After a few moments, MetaMask will pop up with a successful transaction confirmation message, and your ETH will now be available on your Layer 2 network of choice! ## Connecting to Uniswap on Layer 2 Now that your wallet is set up and funded, head to this URL which will open Uniswap and automatically show swapping ETH for rETH: [https://app.uniswap.org/#/swap?inputCurrency=eth](https://app.uniswap.org/#/swap?inputCurrency=eth) The page will look like this initially: ![](/static/image/uni_connect.cd51433cd5.png) Click on one of the `Connect Wallet` buttons such as the highlighted one in the top-right corner. You will be prompted with a screen that asks you which wallet provider you want to use. For this example, select **MetaMask**. ::: tip NOTE If you're not using MetaMask, one of the other providers such as WalletConnect will likely be compatible with your wallet. ::: Upon clicking that button, MetaMask will pop up with another prompt asking you to select which accounts you want to use, just like it did with Hop. Leave your account selected, click **Next**, and then click **Connect** as you did with Hop before. After a brief pause, your wallet will be connected to Uniswap. You should now see its ETH balance in the top right corner of the screen. The first thing to do is change your network from the Ethereum mainnet to the Layer 2 you just swapped to. Click on the network dropdown at the top right of the screen (highlighted in red here): ![](/static/image/uni_network.4a59c0a71b.png) Once you do, MetaMask will prompt you to confirm that you want to add a custom network: ![](/static/image/uni_net_confirm.051418902b.png) Click **Approve** and then click **Switch Network**. This will change MetaMask to use the new Layer 2 network instead of Ethereum's mainnet for transactions. ::: warning NOTE Before you do any transactions with MetaMask, _always_ verify which network it's currently using by opening MetaMask and looking at the network dropdown on the top! It's easy to accidentally switch to a different network and forget! ::: ## Adding rETH to MetaMask The next step is to add the rETH token to MetaMask so you can see your balance and access it for trading. Click the **Assets** tab, then click **Add Token**: ![](/static/image/mm_add_token.565f58b7f4.png) Ensure that **Custom Token** is selected in this dialog, and select the appropriate tab for the Layer 2 network you chose below: **Optimism** In the **Token Contract Address** box, put the following value: ```shell 0x9bcef72be871e61ed4fbbc7630889bee758eb81d ``` The **Token Symbol** should automatically be populated with `rETH`, and the **Decimals of Precision** should automatically be populated with `18`. Accept the rest of the prompts, and then you will see the rETH token appear in your list. **Arbitrum** In the **Token Contract Address** box, put the following value: ```shell 0xec70dcb4a1efa46b8f2d97c310c9c4790ba5ffa8 ``` The **Token Symbol** should automatically be populated with `rETH`, and the **Decimals of Precision** should automatically be populated with `18`. Accept the rest of the prompts, and then you will see the rETH token appear in your list. ## Swapping ETH for rETH with Uniswap The final step of the process is to do the swap! Click on the **Select a token** dropdown and enter the address for rETH that you just added to MetaMask (you can also just type rETH, but **make sure it is the correct token and not an impostor or scam token** by verifying its address first). ::: warning NOTE You may initially be prompted with a warning that looks like this: ![](/static/image/unknown_token.aee8d8c3f9.jpg) This is just a temporary warning until Uniswap adds rETH to its canonical token list on the Layer you're using. As long as the token address is `0x9bcef72be871e61ed4fbbc7630889bee758eb81d` on Optimism or `0xec70dcb4a1efa46b8f2d97c310c9c4790ba5ffa8` on Arbitrum, you can add it safely. ::: Next, enter the amount of ETH you want to swap and Uniswap's UI will show you the amount of rETH you will receive in return: ![](/static/image/arb_swap.013fc85d11.png) ::: warning NOTE Notice that the amount of rETH you receive will be **less than** the amount of ETH you put in. This is normal, because **rETH is worth more than ETH** and continuously appreciates over time. You can see this in the exchange rate highlighted at the bottom of the screenshot. ::: Now click **Swap** to see the details of the trade, including the minimum amount you could receive due to slippage. If you're satisfied, click **Confirm Swap**. This will send the request to MetaMask, where you can review the total transaction cost before confirming it: ![](/static/image/arb_gas.00e057e0b3.png) ::: tip NOTE Pay **close attention** to the estimated gas fee here. You will likely notice that it is **approximately 10x cheaper** in terms of gas fees to do this swap on a Layer 2 network than it is on the Ethereum Mainnet! ::: If you are happy with the gas fees relative to the total amount of rETH you'll be receiving, click **Confirm** to submit the transaction. After a short period, you should see a notification from MetaMask that it completed successfully, and you will now see the rETH token in your wallet. That's it! You're now staking with Rocket Pool. All you need to do is hold onto your rETH, and you'll automatically gain your staking rewards as the value of the rETH token increases. --- url: /liquid-staking/via-rp.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Staking Directly via Rocket Pool ## Overview Rocket Pool's staking interface now offers two distinct routes for converting between ETH and rETH: 1. **Protocol Route** - Direct interaction with Rocket Pool smart contracts 2. **CoW Swap Route** - Decentralized exchange aggregator with MEV protection (Mainnet only) The interface automatically recommends the best route based on current market conditions and liquidity availability. ## Routing Options Explained ### Protocol Route **How it works:** Direct interaction with Rocket Pool's deposit pool and smart contracts on-chain. **Advantages:** - Instant execution - Predictable exchange rate based on current rETH/ETH ratio - No intermediary tokens required (direct ETH ↔ rETH conversion) - Lower complexity - Always get exactly as much rETH as your ETH is worth (minus a 0.05% deposit fee) - No slippage, no liquidity issues, no sandwiching or front-running **Limitations:** - Subject to deposit pool limits when staking - Subject to liquidity availability when unstaking - Requires gas fees for transaction - Gas fees might be expensive for small amounts ### CoW Swap Route (Mainnet Only) ::: danger WARNING The CoW Swap route is not part of the Rocket Pool protocol. Quotes & solvers are determined by **third party** systems that are outside the control or visibility of the Rocket Pool protocol. Users should note that using CoW Swap may expose them to additional risks such as slippage, price impact, solvers that route funds incorrectly, etc. For fine grain control we highly recommend that you use CoW Swap directly. ::: **How it works:** Uses CoW Protocol's batch auction system to find the best price across multiple DEXs. **Advantages:** - MEV (Maximum Extractable Value) protection against sandwich attacks - Gasless execution - you only sign the order - Often provides better rates through DEX aggregation - Always available regardless of protocol deposit pool limits - No gas fees for the swap itself **Limitations:** - Requires WETH wrapping/unwrapping steps (handled automatically) - Orders may take 2-5 minutes to execute - Orders can expire if not matched within the time limit - Requires one-time token approvals ## Key Concepts ### WETH (Wrapped ETH) When using CoW Swap, the interface automatically handles WETH conversions: - WETH is an ERC-20 token representing ETH in a standardized format - 1 WETH always equals 1 ETH - The interface wraps ETH to WETH before trading and unwraps after - You only pay gas for the initial wrap (one-time) ### Slippage Tolerance For CoW Swap orders: - Default: 0.5% - Adjustable based on your preference - Higher slippage = more likely to execute - Lower slippage = better price protection ### Order Expiry CoW Swap orders have a time limit: - Default: 30 minutes - Adjustable from 5 minutes to 24 hours - Orders automatically cancel if not executed ### Better Rate Indicator The interface shows which route offers better value: - Green badge with "X% better" indicates the optimal route - Automatically pre-selects the best option - Updates in real-time as market conditions change ### Protocol Liquidity When unstaking rETH: - Protocol route requires available ETH in the deposit pool - Shows "Insufficient liquidity" when pool is empty - Automatically routes through CoW Swap when protocol liquidity is unavailable ## Getting Started **Preparing on the Hoodi Testnet**

WARNING

When practicing staking on the test network, you **do not need to provide any of your real ETH** during this process. You will be given **fake test ETH** to use instead. **Do not attempt to move your real ETH on mainnet to the testnet or you will lose it permanently!** Start by installing [MetaMask](https://metamask.io/) if you haven't already. Follow the instructions on their site to install the extension, create an account, and sign in. Next, open the MetaMask panel using its icon in your browser toolbar. You will need to add the Hoodi Testnet to MetaMask. Click on the top left dropdown & click the "Add Network" button. You will see a list of networks, Hoodi is not in this list so click the "Add a network manually" button. Fill in the following details: ``` Network Name: Hoodi New RPC Url: https://rpc.hoodi.ethpandaops.io Chain ID: 560048 Currency Symbol: ETH Block Explorer Url: https://hoodi.etherscan.io ``` Then click Save. You should now see the Hoodi network in the top left dropdown. Click on the **network dropdown** in the top left of the Metamask extension & select **Hoodi Test Network**. Finally, add the rETH token to MetaMask so you can see your balance and access it for trading. Click the **Assets** tab, then click **Add Token**: ![](/static/image/mm_add_token.565f58b7f4.png)Ensure that **Custom Token** is selected in this dialog. In the **Token Contract Address** box, put the following value: ``` 0x7322c24752f79c05ffd1e2a6fcb97020c1c264f1 ``` The **Token Symbol** should automatically be populated with `rETH`, and the **Decimals of Precision** should automatically be populated with `18`. Accept the rest of the prompts, and then you will see the rETH token appear in your list. Now that you have a wallet address in MetaMask, you need to fill it with some test ETH. Head over to the [Practicing with the Test Network](/node-staking/testnet/overview.md#getting-test-eth-on-hoodi) page for a quick guide on how to use a testnet faucet to get some test ETH on Hoodi. Once you have some Hoodi ETH to test with, head to [https://testnet.rocketpool.net/](https://testnet.rocketpool.net/). **Note:** Testnet only supports Protocol routing. CoW Swap is available on mainnet only. **Preparing on Ethereum Mainnet** Start by installing [MetaMask](https://metamask.io/) if you haven't already. Follow the instructions on their site to install the extension, create an account, and sign in. Next, open the MetaMask panel using its icon in your browser toolbar. Click on the **network dropdown** in the toolbar at the top and ensure that **Ethereum Mainnet** is selected: ![](/static/image/mm_network_main.1536c3b585.png)Finally, add the rETH token to MetaMask so you can see your balance and access it for trading. Click the **Assets** tab, then click **Add Token**: ![](/static/image/mm_add_token.565f58b7f4.png)Ensure that **Custom Token** is selected in this dialog. In the **Token Contract Address** box, put the following value: ``` 0xae78736Cd615f374D3085123A210448E74Fc6393 ``` The **Token Symbol** should automatically be populated with `rETH`, and the **Decimals of Precision** should automatically be populated with `18`. Accept the rest of the prompts, and then you will see the rETH token appear in your list. Now that you have a wallet address in MetaMask, you need to transfer some ETH into it. You will need to supply this from an existing wallet or buy ETH on an exchange. Once you have some ETH to stake, head to [https://stake.rocketpool.net/](https://stake.rocketpool.net/). ## Staking ETH for rETH Once you're at the staking site, click on the **connect wallet** button. Please read through and accept the Terms of Service & Privacy Policy, this will enable different ways to connect, then click **connect metamask**. MetaMask will prompt you to select an account to connect to the website. Choose one, confirm a few permissions, and you'll see your balances update in the UI. ### Step 1: Enter Amount Enter the amount of ETH you want to stake in the **Stake ETH** input field. \[Image placeholder: Input field with amount being entered] ### Step 2: Review Routing Options The interface will display two routing options (mainnet only): - **Protocol Card**: Shows if deposit pool is available or full - **CoW Swap Card**: Shows estimated output and rate comparison The better option will be highlighted with a green "X% better" badge and automatically selected. \[Image placeholder: Routing cards showing comparison] ### Step 3: Configure Settings (CoW Swap Only) If using CoW Swap, you can optionally: - Adjust slippage tolerance (default 0.5%) - Set order expiry time (default 30 minutes) ### Step 4: Execute Transaction **Via Protocol** Click **Stake via Protocol** button. MetaMask will prompt you to: 1. **Approve the transaction** with gas fees shown 2. **Confirm the transaction** ::: danger IMPORTANT Check the total gas cost before approving - if it's very expensive relative to your stake amount, consider using CoW Swap instead! ::: Once confirmed, the transaction will be mined and you'll receive your rETH immediately. **Via CoW Swap** Click **Stake via CoW Swap** button. The process involves several automated steps: 1. **WETH Wrapping** (if needed) - Approve ETH to WETH conversion - One-time gas fee required 2. **WETH Approval** (first time only) - Approve CoW Protocol to use your WETH - One-time gas fee required 3. **Sign Order** - Review order details - Sign with MetaMask (gasless) - No gas fees 4. **Order Execution** - Monitor progress in modal - Typical wait: 2-5 minutes - Can close modal and continue browsing 5. **Completion** - rETH automatically appears in wallet - View on Etherscan if needed ::: tip NOTE It's **completely normal** to receive less rETH than the ETH you put in. rETH and ETH have a **dynamic exchange rate**: as the Rocket Pool network earns rewards, 1 rETH becomes worth more than 1 ETH. ::: ## Unstaking rETH for ETH When you're ready to unstake and trade your rETH back for ETH, head back to the staking website and click on the **swap direction button** to switch to unstaking mode: ### Step 1: Enter Amount Enter the amount of rETH you want to unstake in the **Unstake rETH** field. ### Step 2: Check Routing Availability The interface will show: - **Protocol liquidity** available in the deposit pool - **Protocol card** status (available or "Insufficient liquidity") - **CoW Swap card** with estimated ETH output ### Step 3: Execute Unstaking **Via Protocol** If protocol liquidity is available: 1. Click **Unstake via Protocol** 2. Confirm transaction in MetaMask 3. Pay gas fees 4. Receive ETH immediately ::: warning NOTE Protocol unstaking is only possible when the deposit pool has enough ETH. If you see "Insufficient liquidity", use CoW Swap instead. ::: **Via CoW Swap** CoW Swap is always available for unstaking: 1. **rETH Approval** (first time only) - Approve rETH for CoW Protocol - One-time gas fee 2. **Sign Order** - Review details - Sign order (gasless) 3. **Order Execution** - Monitor in modal - 2-5 minute wait 4. **WETH Unwrapping** (automatic) - Receives WETH from swap - Automatically unwraps to ETH - ETH appears in wallet ## Troubleshooting ### Common Issues #### Order Expired (CoW Swap) Your order didn't execute within the time limit. **Solutions:** - Increase order expiry time (up to 24 hours) - Adjust slippage tolerance higher - Try again with current market prices - Use Protocol route if available #### Insufficient Balance Not enough ETH/rETH for the transaction. **Solutions:** - Check wallet balance - Account for gas fees (Protocol route) - Reduce stake/unstake amount #### Pool Full (Protocol Staking) Deposit pool has reached its limit. **Solution:** - Use CoW Swap route (automatically selected) - Wait for node operators to pull ETH from pool - Check back later for availability #### Insufficient Liquidity (Protocol Unstaking) Not enough ETH in deposit pool for unstaking. **Solution:** - Use CoW Swap route (automatically selected) - Always available regardless of pool state ### Manual WETH Conversion If you have WETH that wasn't automatically unwrapped: 1. Visit [swap.cow.fi](https://swap.cow.fi) 2. Connect your wallet 3. Swap WETH → ETH (1:1 ratio, gasless) Or use Etherscan: 1. Go to WETH contract: `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2` 2. Connect wallet to "Write Contract" 3. Use `withdraw` function 4. Enter amount in Wei 5. Execute transaction ## Best Practices ### For Optimal Rates - Let the interface auto-select the best route - Check during low network activity for better protocol availability - For large amounts, CoW Swap often provides better rates - Adjust slippage carefully to balance execution likelihood vs price ### For Security - Verify you're on the correct website: [https://stake.rocketpool.net](https://stake.rocketpool.net) - Start with small test amounts - Review all transaction details before confirming - Keep some ETH for gas fees - Only approve trusted contracts ### For Gas Optimization - Compare gas costs between routes - Batch transactions when possible - Use CoW Swap for small amounts to avoid high gas fees - Monitor gas prices at [etherscan.io/gastracker](https://etherscan.io/gastracker) ## Tax Implications ::: warning IMPORTANT This section provides general educational information only. Tax laws vary significantly by jurisdiction and individual circumstances. **Always consult with a qualified tax professional** for advice specific to your situation. ::: ### Understanding rETH and Taxes When staking with Rocket Pool, it's crucial to understand potential tax implications: #### The Staking Transaction (ETH → rETH) **Potential Tax Events:** - **Token Swap**: Converting ETH to rETH may be considered a taxable event in many jurisdictions - **Capital Gains/Losses**: If your ETH has appreciated since acquisition, you may owe capital gains tax - **Cost Basis**: The value of rETH received becomes your new cost basis for future transactions **Example Scenario:** ``` Bought 1 ETH at $1,000 Stake when ETH is worth $2,000 Potential taxable gain: $1,000 Your rETH cost basis: $2,000 ``` #### Holding rETH (Earning Rewards) **How rETH Appreciates:** - rETH increases in value relative to ETH automatically - No new tokens are received - the token itself appreciates - This appreciation represents your staking rewards **Tax Treatment Varies:** - **Some jurisdictions**: Tax on appreciation only when realized (upon sale/swap) - **Other jurisdictions**: May tax unrealized gains annually - **Income vs. Capital Gains**: Classification affects tax rates #### The Unstaking Transaction (rETH → ETH) **Tax Considerations:** - Converting rETH back to ETH is typically a taxable event - Calculate gain/loss based on: - **Cost basis**: Value when you acquired rETH - **Disposal value**: Value when converting back to ETH - The difference is your capital gain or loss ### Routing Method Tax Implications #### Protocol Route - Single taxable event per transaction - Clear timestamp and value for tax records - On-chain transaction provides permanent record #### CoW Swap Route - WETH wrapping/unwrapping typically not taxable (1:1 conversion) - Main swap (ETH/WETH ↔ rETH) is the taxable event - Order execution provides clear tax documentation ### Record Keeping Best Practices **Essential Records to Maintain:** 1. **For Each Stake:** - Date and time of transaction - Amount of ETH staked - Amount of rETH received - ETH price at time of staking - Transaction hash - Gas fees paid 1. **While Holding:** - Periodic snapshots of rETH/ETH exchange rate - Your rETH balance over time - Market values on key dates (year-end, etc.) 1. **For Each Unstake:** - Date and time of transaction - Amount of rETH unstaked - Amount of ETH received - ETH price at time of unstaking - Transaction hash - Gas fees paid **Tools for Tracking:** - Export transactions from Etherscan - Use portfolio tracking apps that support rETH - Maintain a spreadsheet with all transactions - Consider using crypto tax software ### Tax Optimization Strategies **Timing Considerations:** - **Tax-Loss Harvesting**: Unstake during market downturns if you have losses to offset gains - **Long-term vs. Short-term**: Many jurisdictions favor long-term holdings (typically >1 year) - **Year-end Planning**: Consider timing of transactions around tax year boundaries **Cost Basis Methods:** - **FIFO (First In, First Out)**: Default in many jurisdictions - **LIFO (Last In, First Out)**: May be available in some regions - **Specific Identification**: Track specific rETH portions if allowed ### Common Tax Scenarios #### Scenario 1: Regular Staking ``` Action: Stake 10 ETH for 9.5 rETH Tax Event: Disposal of ETH, acquisition of rETH Report: Capital gain/loss on ETH disposal Track: 9.5 rETH with new cost basis ``` #### Scenario 2: Partial Unstaking ``` Action: Unstake 5 rETH for 5.3 ETH Tax Event: Disposal of rETH, acquisition of ETH Report: Capital gain/loss on rETH disposal Track: Remaining rETH balance and cost basis ``` #### Scenario 3: DeFi Integration ``` Action: Use rETH in DeFi protocols Tax Event: Each protocol interaction may be taxable Report: Track all movements and value changes Track: Yields, swaps, and liquidity provisions ``` ### Jurisdiction-Specific Considerations **United States:** - IRS treats crypto-to-crypto swaps as taxable - Staking rewards may be taxable when received or when sold (evolving guidance) - Form 8949 and Schedule D for reporting **European Union:** - Tax treatment varies by member state - Some countries tax upon realization, others annually - Consider local crypto tax regulations **United Kingdom:** - HMRC treats staking rewards as income or capital gains depending on circumstances - Detailed record keeping required - Consider "bed and breakfasting" rules **Other Jurisdictions:** - Research your local tax authority's crypto guidance - Many countries are still developing frameworks - Professional advice strongly recommended ### Using Tax Software **Popular Crypto Tax Tools:** - Most support rETH tracking - Can import from Etherscan - Calculate gains/losses automatically - Generate tax reports for your jurisdiction **Integration Tips:** 1. Import all wallet addresses 2. Verify rETH/ETH transactions are correctly classified 3. Ensure exchange rates are accurate 4. Review calculated gains/losses 5. Export reports for tax filing ### Red Flags to Avoid **Common Mistakes:** - Not tracking cost basis - Forgetting to report staking transactions - Ignoring small transactions - Missing DeFi interactions - Incorrect exchange rate data **Audit Preparation:** - Keep all transaction records - Document your calculation methods - Save exchange rate sources - Maintain wallet ownership proof - Store records for required retention period ## FAQs **Q: Which route should I choose?** A: The interface automatically recommends the best route with a green "better rate" badge. Generally, use the recommended option. **Q: Why does CoW Swap sometimes offer better rates?** A: CoW Swap aggregates liquidity from multiple DEXs and uses batch auctions to find optimal prices, often beating the fixed protocol rate. **Q: Is CoW Swap really gasless?** A: Order creation and signing are gasless. You only pay gas for initial WETH wrapping and token approvals (one-time setup). **Q: How long do CoW Swap orders take?** A: Typically 2-5 minutes, but can vary based on market conditions. **Q: What happens if my CoW Swap order expires?** A: Nothing is lost. Your tokens remain in your wallet. You can place a new order with adjusted parameters. **Q: Why is the Protocol route sometimes unavailable?** A: **For staking:** Deposit pool is full. **For unstaking:** Insufficient ETH liquidity. These are temporary states that change as users interact with the protocol. **Q: Are staking transactions taxable?** A: In most jurisdictions, yes. Converting ETH to rETH and back are typically taxable events. Consult a tax professional for your specific situation. **Q: How do I track my rETH cost basis?** A: Record the value of ETH when you stake it - this becomes your rETH cost basis. Use transaction hashes, timestamps, and prices for accurate records. **Q: Is moving between Protocol and CoW Swap routes different for taxes?** A: The tax treatment is typically the same - both involve exchanging ETH for rETH. The route chosen doesn't usually affect tax obligations, though record keeping may differ slightly. ## Additional Resources - [Rocket Pool Documentation](https://docs.rocketpool.net) - [CoW Swap Documentation](https://docs.cow.fi) - [Rocket Pool Discord](https://discord.gg/rocketpool) - [Etherscan Gas Tracker](https://etherscan.io/gastracker) ## Contract Addresses ### Mainnet - **rETH Token:** `0xae78736Cd615f374D3085123A210448E74Fc6393` - **WETH Token:** `0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2` - **Rocket Storage:** `0x1d8f8f00cfa6758d7bE78336684788Fb0ee0Fa46` - **CoW Protocol VaultRelayer:** `0xC92E8bdf79f0507f65a392b0ab4667716BFE0110` ### Hoodi Testnet - **rETH Token:** `0x7322c24752f79c05ffd1e2a6fcb97020c1c264f1` - Check [Rocket Pool Documentation](https://docs.rocketpool.net) for other Hoodi testnet addresses. *** That's all there is to staking with Rocket Pool! We hope you find the new routing options helpful in getting the best value for your stake. Feel free to swing by [our Discord server](https://discord.gg/rocketpool) to let us know what you thought of it and keep tabs on the project as it evolves. --- url: /node-staking/addons/addons.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # How to Write Add-ons for Rocket Pool Smart Node ## Introduction Rocket Pool Smart Node add-ons are extensions that provide additional features to the Smart Node stack. They can be implemented as Docker containers that integrate with the Ethereum clients or the Smart Node service. Add-ons can be enabled and configured through the Smart Node's terminal user interface (TUI) via the `rocketpool service config` command. Add-on development can be based on two existing examples: - **Graffiti Wall Writer**: Enables node operators to contribute to community drawings on the Beaconcha.in graffiti wall by dynamically setting block proposal graffiti. It uses a decentralized drawing tool to determine which pixels to "paint" with each proposal. - **Rescue Node**: Provides a fallback beacon node service using credentials from the Rocket Rescue Node project. This helps prevent missed attestations during node maintenance, syncing, or outages by routing requests to a shared remote beacon node. Add-ons are part of the Smart Node source code and must be contributed via pull request to the repository. They implement a standardized interface for configuration and integration. ## Prerequisites - Familiarity with Go programming, as add-ons are written in Go. - Understanding of Docker, as add-ons can run as containers. - Knowledge of the Rocket Pool Smart Node architecture, including its Docker compose setup and configuration system. - Access to the Smart Node repository for local development and testing. ## Steps to Create an Add-on To create a new add-on, you will need to add code in specific locations within the Smart Node repository. The process involves implementing the add-on logic, configuring its UI, registering it, and handling integration with the Docker stack. ### 1. Implement the Add-on Logic Create a new subdirectory in `addons/` named after your add-on (use snake_case, e.g., `my_addon`). In this directory, create a Go file (e.g., `my_addon.go`) that defines the add-on struct and implements the `SmartnodeAddon` interface from `github.com/rocket-pool/smartnode/shared/types/addons`. ``` type MyAddon struct { cfg *MyAddonConfig `yaml:"config,omitempty"` } func NewMyAddon() addons.SmartnodeAddon { return &MyAddon{ cfg: NewConfig(), } } ``` Key methods to implement: - `GetName()`: Returns the display name of the add-on. - `GetDescription()`: Returns a brief description. - `GetConfig()`: Returns the configuration object with parameters (e.g., enabled flag, API keys, URLs). - `GetEnabledParameter()`: Returns the parameter controlling whether the add-on is enabled. - Methods for starting/stopping the add-on, generating Docker compose sections, or interacting with other services. If the add-on runs a Docker container: - Define the Docker image (e.g., a custom image or external one). - Specify volumes, ports, or environment variables needed. For example, the Graffiti Wall Writer add-on runs a container that periodically updates the validator client's graffiti file based on a JSON configuration for the image to draw. The Rescue Node add-on configures the validator client to use a remote fallback beacon node via a proxy, requiring username and password parameters. ### 2. Create the Configuration UI Add a file in `rocketpool-cli/service/config/` named `addon-myaddon.go`. This file defines the TUI page for configuring the add-on using the `tview` library. Key elements: - Define a struct `AddonMyAddonPage` with fields for the layout, master config, and form items. - Constructor `NewAddonMyAddonPage` that initializes the page and calls `createContent()`. - `createContent()`: Sets up the form with checkboxes (e.g., enabled) and input fields for other parameters. - Event handlers like `handleEnableChanged()` to show/hide parameters based on the enabled state. Example snippet: ```go package config import ( "fmt" "github.com/rivo/tview" "github.com/rocket-pool/smartnode/shared/services/config" "github.com/rocket-pool/smartnode/shared/types/addons" cfgtypes "github.com/rocket-pool/smartnode/shared/types/config" ) // The page wrapper for the add-on config type AddonMyAddonPage struct { addonsPage *AddonsPage page *page layout *standardLayout masterConfig *config.RocketPoolConfig addon addons.SmartnodeAddon enabledBox *parameterizedFormItem otherParams []*parameterizedFormItem } // Creates a new page for the add-on settings func NewAddonMyAddonPage(addonsPage *AddonsPage, addon addons.SmartnodeAddon) *AddonMyAddonPage { configPage := &AddonMyAddonPage{ addonsPage: addonsPage, masterConfig: addonsPage.home.md.Config, addon: addon, } configPage.createContent() // ... (additional code for page setup) } // Creates the content for the settings page func (configPage *AddonMyAddonPage) createContent() { // Setup layout and form items // ... } ``` ### 3. Register the Add-on Update `addons/constructors.go` to include a constructor for your add-on. This file contains functions to instantiate all add-ons. Example: ``` func NewMyAddon() addons.SmartnodeAddon { return my_addon.NewMyAddon() } ``` Then add it to the list of available addons within the`NewRocketPoolConfig` in `shared/services/config/rocket-pool-config.go`. ``` // Addons cfg.GraffitiWallWriter = addons.NewGraffitiWallWriter() cfg.RescueNode = addons.NewRescueNode() cfg.MyAddon = addons.MyAddon() ``` ### 4. Integrate with Docker Compose Add-ons often require modifications to the Docker compose files. - Add templates in the `shared/services/rocketpool/assets/install/templates/addons` directory for your add-on's compose section (e.g., `my_addon.tmpl`). - The add-on code generates the compose YAML when enabled, including services, volumes, and dependencies. The `composeAddons` function inside the `services/rocketpool/client` folder is responsible for provisioning Docker Compose containers based on the Rocket Pool configuration, setting up runtime, template and override assets for the add-on. For installation: - Update the installer script (`install.sh`) if the add-on needs files copied (e.g., default config files). ### 5. Optional Integrations - **Node Status Command**: If the add-on has status info (e.g., credential expiration for Rescue Node), update `rocketpool-cli/node/status.go` to display it. - **Metrics or Logs**: Integrate with Prometheus/Grafana if applicable. - **External Dependencies**: If using an external repo (e.g., Rescue Node proxy), ensure it's documented. ### 6. Testing and Submission - Build and test locally: Use the Makefile to build the Smart Node, install, and enable your add-on. - Verify in the TUI, check Docker containers, and test functionality. - Submit a pull request to [https://github.com/rocket-pool/smartnode](https://github.com/rocket-pool/smartnode) with your changes. ## Example: Graffiti Wall Writer - **Purpose**: Draws community images on the Beaconcha.in graffiti wall using block proposals. - **Implementation**: Runs a Docker container that fetches wall state and updates the validator's graffiti file. - **Config**: Enabled flag and parameter for image JSON URL (default: Rocket Pool logo). - **Integration**: The container mounts the validator's data directory to write the graffiti file. Enabled via TUI; contributes to decentralized drawing. ## Example: Rescue Node - **Purpose**: Fallback beacon node to avoid penalties during downtime. - **Implementation**: Configures the validator client to use a remote proxy with authentication. - **Config**: Enabled flag, username, and password from Rescue Node website. - **Integration**: Modifies validator config to point to the rescue proxy. Shows credential status in `rocketpool node status`. For more details, review the source code in the repository or contribute to improve add-on development docs. --- url: /node-staking/advanced-cli.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # \[NYI] Advanced CLI Usage As a node operator, the command-line interface (CLI) is the tool that you will use to interface with nearly every aspect of Rocket Pool. In this section, we'll go through a detailed walkthrough of how to use it. ## Wallet Control --- url: /node-staking/advanced-config.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Advanced Smart Node Configuration for Docker Mode In this section, we will cover a few techniques that expand the Smart Node's customization and functionality. ## Allowing External Validator Clients to Connect to the Smart Node Because the Smart Node manages the Execution client and Beacon Node, it handles much of their configuration (including updates) automatically. One common request from users is for the ability to attach an externally-managed Validator client to the Smart Node's Execution and Consensus clients. Essentially, this acts as a sort of **"Reverse Hybrid" mode**; instead of the Smart Node managing its own Validator client and connecting to an external Execution and Consensus client, it manages all three things and an external Validator client can use its own clients instead. Enabling this is trivial using the [Settings Manager](/node-staking/config-docker.md#configuring-via-the-settings-manager). ### Execution Client To enable access to the Execution client, go to the **Execution Client (ETH1)** category and check the **Expose RPC Ports** box: ![](/static/image/tui-ec-expose-ports.7f4af29767.png) This will open the RPC ports (default 8545 for HTTP and 8546 for Websockets) on your node, so other machines on your local network can connect to them. For example, if your node's local IP address were `192.168.1.45`, then by enabling this option you could use `http://192.168.1.45:8545` as the Execution client URL for your other services. ### Beacon Node (Consensus Client) To enable access to the Consensus client's Beacon Node, go to the **Consensus Client (ETH2)** category and check the **Expose API Port** box: ![](/static/image/tui-cc-expose-ports.5222cda507.png) This will open the HTTP API port (default 5052) on your node, so other machines on your local network can connect to it. ::: warning Note: Ports opened via iptables, not ufw When you expose RPC and API endpoints in using the Rocketpool configurator, ports are opened via `iptables` and therefore will not show up as a `ufw` firewall rule. To see which ports are open you can use `sudo lsof -i -P -n | grep LISTEN` or similar command. ::: For example, if your node's local IP address were `192.168.1.45`, then by enabling this option you could use `http://192.168.1.45:5052` as the Beacon Node URL for your other services. ::: warning NOTE FOR PRYSM USERS **Prysm** has a second box called `Expose RPC Port` that must be checked if you want to attach an externally-managed Prysm Validator Client to your Beacon Node. This is because Prysm's Validator Client cannot currently connect to a Beacon Node via the standard Beacon HTTP API. In the future, this will be fixed and there will only be one checkbox like the other clients. ::: ### MEV-Boost To enable access to MEV-Boost, go to the **MEV-Boost** category and check the **Expose API Port** box: ![](/static/image/tui-mev-expose-ports.cf5e978835.png) This will open the HTTP API port (default 18550) on your node, so other machines on your local network can connect to it. For example, if your node's local IP address were `192.168.1.45`, then by enabling this option you could use `http://192.168.1.45:18550` as the MEV-Boost URL for your other services. ## Customizing the Docker-Compose Definition Files While the Settings Manager contains many options you can use to customize your node, it doesn't wrap all of the features that `docker-compose` provides. Some users require supplemental customizations to the Smart Node's `docker-compose` files. Because the `docker-compose` files are regenerated (into the `runtime` directory) from their templates (in the `templates` directory) each time `rocketpool service start` is called, modifying the runtime files is not advised. Instead, we leverage `docker-compose`'s [inherent override functionality](https://docs.docker.com/compose/extends/#adding-and-overriding-configuration) to let you make any modifications you need to which will be preserved upon restarts. Furthermore, this system _also_ **preserves your modifications after an upgrade to or reinstallation of the Smart Node stack**. To do this, simply open the file for the container of your choice in the `override` folder, and add your customizations to it there. Anything you put in these files will **override** whatever the corresponding settings are in the `docker-compose` files from the `runtime` folder. For example, say you wanted to [add AWS credentials to Grafana for CloudWatch support](https://grafana.com/docs/grafana/latest/administration/configure-docker/#configure-aws-credentials-for-cloudwatch-support). You could do it by modifying `override/grafana.yml` like so: ```yaml # Enter your own customizations for the Grafana container here. These changes will persist after upgrades, so you only need to do them once. # # See https://docs.docker.com/compose/extends/#adding-and-overriding-configuration # for more information on overriding specific parameters of docker-compose files. version: "3.7" services: grafana: x-rp-comment: Add your customizations below this line environment: - GF_AWS_PROFILES=default - GF_AWS_default_ACCESS_KEY_ID=YOUR_ACCESS_KEY - GF_AWS_default_SECRET_ACCESS_KEY=YOUR_SECRET_KEY - GF_AWS_default_REGION=us-east-1 ``` This will merge the four environment variables listed here to the existing array of environment variables in the Grafana container. Alternatively, if you wanted to save eth1 client data to a non-default path on your filesystem, you would modify `override/eth1.yml` to contain volume parameters like: ```yaml # Enter your own customizations for the eth1 container here. These changes will persist after upgrades, so you only need to do them once. # # See https://docs.docker.com/compose/extends/#adding-and-overriding-configuration # for more information on overriding specific parameters of docker-compose files. version: "3.7" services: eth1: x-rp-comment: Add your customizations below this line volumes: eth1clientdata: driver: local driver_opts: type: none o: bind device: "/data/eth/eth1" ``` This will merge the parameters into the `eth1clientdata` volume specification, causing `/data/eth/eth1` to be the location of the eth1 client data rather than the default (`/var/lib/docker/volumes/rocketpool_eth1clientdata` if using default Docker configuration). For more information on how `docker-compose` overrides work, please visit [https://docs.docker.com/compose/extends/#adding-and-overriding-configuration](https://docs.docker.com/compose/extends/#adding-and-overriding-configuration). ## Custom and override networks Smart Node loads official network definitions from YAML instead of hard-coding them. - Official networks ship in `networks-default.yml`. On every `rocketpool service install`, Smart Node overwrites `~/.rocketpool/networks-default.yml` with the packaged file, so do not edit that file for lasting changes. - To add a network or override an official one without rebuilding, create `~/.rocketpool/networks-extra.yml` using the same schema (`version` plus a `networks` list). Same-name entries replace the official ones; new names are appended and appear in `rocketpool service config`. - Extra networks may omit Rocket Pool contract addresses. Use that when you only need your execution and consensus clients to sync a chain that has no Rocket Pool deployment. ::: tip NOTE After you change `networks-extra.yml`, run `rocketpool service config`, select the network you want, save, and restart the affected containers so the new definition is picked up. ::: Example — append a sync-only chain with no Rocket Pool contracts: ```yaml version: 1 networks: - name: plataberget label: Platåberget description: | Platåberget is the public Glamsterdam / Gloas testnet (ethpandaops glamsterdam-devnet-8). It launched 13 August 2026 (chain ID 7091047534) with the Gloas fork at epoch 1536. There are no Rocket Pool contracts on this network; use it to run execution and consensus clients. chainID: 7091047534 txWatchUrl: https://dora.plataberget.ethpandaops.io beaconExplorerUrl: https://dora.plataberget.ethpandaops.io beaconNetwork: plataberget commitBoostChainName: plataberget clientTagSet: test customChainConfigDir: plataberget supportsMevBoost: false allowNonBlsWithdrawalCredentials: false isProduction: false nethermindPruneThresholdMb: 51200 ``` ::: warning NOTE If you pick a network with no Rocket Pool storage address, Smart Node node/protocol commands that need Rocket Pool contracts will not work on that network. Client syncing can still proceed. ::: ## Docker image pins Smart Node pins official client and Smart Node images by digest so a retagged image cannot be pulled. - Defaults live in `~/.rocketpool/mainnet.env` as `repo:tag@sha256:…`. `rocketpool service install` always overwrites this file (and `testnet.env` / `devnet.env`). - To pin a different image for one network only, put that key in the matching `{network}.env` file. Keys you omit inherit the mainnet pin. - TUI tag fields still override the pins. They win over both env files until you restore the default. ## Node Daemon HTTP API The node daemon serves an HTTP API (default port **8280**) used by the local `rocketpool` CLI and by custom tooling. Configure it in `rocketpool service config` under the **API** category. Native mode uses the same category. | Setting | Purpose | | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **API Port** | Listen port. Default `8280`. | | **Expose API Port** | **Closed** — not published; the host CLI cannot reach the API in Docker. **Open to Localhost** (default) — `127.0.0.1:8280`. **Open to External hosts** — published on all interfaces. | Changing these settings requires a node container restart. The Settings Manager flags that for you. ::: warning Do not expose the API without TLS The API can export your wallet, send funds, and change node settings. Do not publish it to the public internet without TLS. Put it behind a reverse proxy, or keep it on a trusted LAN. ::: If you run multiple nodes on the same machine, each instance needs its own API port and its own api-tokens.json file. ### API authentication Starting with Smart Node v1.22.0, API routes require a bearer token. Clients send: ``` Authorization: Bearer ``` Query-string tokens are ignored. The `rocketpool` CLI on this machine loads the write token from the data directory and sends it automatically. If the CLI returns `unauthorized`, point `-c` at the same config directory the daemon is using, or copy that install's `data/api-tokens.json`. | Setting | Purpose | | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **API Token** | Write-scoped secret. Format is `rpsn_` followed by 64 hex characters. Treat it like a password. Clearing the field and saving regenerates it. It is stored in `api-tokens.json`, not in `user-settings.yml`. | | **API Token Comment** | Non-secret label stored with the token. Default `rocketpool CLI`. | | **Unauthenticated Reads** | Server policy, not a per-token privilege. Default is **Require a token for read routes**: every route except `/healthz` needs a valid bearer token. Choosing **Allow unauthenticated reads** lets status, balances, and `can-*` estimates run without a token. Wallet operations, transactions, and other write routes still need a write-scoped token. | | **API Rate Limit** | Maximum requests per second. `0` disables the limit (this is the default). Burst equals one second of quota. Over the limit, the API returns HTTP 429 with `Retry-After: 1`. | `/healthz` never requires a token. Tokens live in `/api-tokens.json` (host default `~/.rocketpool/data/api-tokens.json`). The Docker daemon sees the same file at `/.rocketpool/data/api-tokens.json` on the data-directory bind mount. The file is mode `0600`. Each record has a scope: - `write` — all routes. - `read` — read routes only. Write routes return HTTP 403 `forbidden`. Add extra tokens by appending records to `api-tokens.json`, then restart the node: ```json { "tokens": [ { "token": "rpsn_…", "comment": "rocketpool CLI", "scope": "write" }, { "token": "rpsn_…", "comment": "monitoring", "scope": "read" } ] } ``` Copy the token from the **API Token** field or from `api-tokens.json`. Do not put it in logs or screenshots. ### Calling the API Read-only query (GET). A token is required unless unauthenticated reads are enabled: ```shell curl -s -H "Authorization: Bearer $RP_API_TOKEN" \ http://127.0.0.1:8280/api/node/sync | jq ``` ```json { "status": "success", "error": "", "ecStatus": { "primaryEcStatus": { "isWorking": true, "isSynced": true, "syncProgress": 1, "networkId": 560048 } }, "bcStatus": { "primaryEcStatus": { "isWorking": true, "isSynced": true, "syncProgress": 1 } } } ``` Transaction (POST). Always requires a write-scoped token: ```shell curl -s -X POST \ -H "Authorization: Bearer $RP_API_TOKEN" \ -d "timezoneLocation=America/Los_Angeles" \ http://127.0.0.1:8280/api/node/set-timezone | jq ``` ```json { "status": "success", "error": "", "txHash": "0x0bab800962146f3e41c701601be6d636f9bec261ef6cabe667bc560ed19dfffb" } ``` | Status | Body | When | | ------ | --------------------------------------------------------------------------- | -------------------------------- | | 401 | `{"status":"error","error":"unauthorized"}` plus `WWW-Authenticate: Bearer` | Missing or invalid token | | 403 | `{"status":"error","error":"forbidden"}` | Read token used on a write route | | 429 | `{"status":"error","error":"too many requests"}` plus `Retry-After: 1` | Rate limit exceeded | ## (Experimental) Enabling Dual-Stack (IPv4 + IPv6) networking This option is for users running Docker mode configurations with locally managed clients. Starting with Smart node v1.20.2, Rocket Pool supports dual-stack (IPv4 + IPv6) networking for your Ethereum clients. When enabled, your consensus client can connect to both IPv4 and IPv6 peers, potentially improving peer discovery. If you use the Besu (v1.22.0 and newer) or Reth (v1.24.4 and newer) execution client, it connects to IPv6 peers too. This feature is also useful if your network is behind a CGNAT and struggles to peer using IPv4. ::: tip TIP The following site gives a rundown on the status of Ethereum IPv6 Support. [ipv6eth.info](https://ipv6eth.info/) ::: ::: warning EXPERIMENTAL FEATURE IPv6 support is currently experimental. While it has been tested with all supported consensus clients, you may encounter issues depending on your network configuration. If you experience problems, you can disable IPv6 and restart your clients to return to IPv4-only mode. If you encounter any issues with IPv6 support, please report them in the **#support** channel on the [Rocket Pool Discord](https://discord.gg/rocketpool). ::: When you enable IPv6 support: - Your Docker network will be configured for dual-stack (IPv4 + IPv6) - Your consensus client will listen on both IPv4 and IPv6 addresses - If you use Besu or Reth, your execution client will listen on both IPv4 and IPv6 addresses on its usual P2P port (default `30303`) - Your node will be able to discover and connect to IPv6 peers in addition to IPv4 peers - Your node will advertise its IPv6 address in its ENR (Ethereum Node Record), making it discoverable by other IPv6 nodes (depends on your consensus client; see the table below) - Changing the setting (on or off) recreates the Docker network, so all Rocket Pool containers are stopped, removed and recreated. The Smart Node asks you to confirm first. Your chain data and wallet/validator keys are not affected, but your clients will be offline briefly while they restart. ### Client-Specific Behavior Different consensus clients handle IPv6 with varying levels of support: | Client | IPv6 Listening | IPv6 Broadcasting (ENR) | Peering Behavior | Notes | | -------------- | -------------- | ----------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------ | | **Teku** | Full | Full | Prioritizes IPv6 | Prefers IPv6 connections when available. Uses separate IPv6 ports (default: 9090, and 8002 for QUIC). | | **Lighthouse** | Full | Full | No preference | Connects to whichever address (IPv4 or IPv6) responds first. Typically sees \~1-2% IPv6 peers. | | **Lodestar** | Full | Full | Prioritizes IPv4 | Listens and broadcasts on both IPv4 and IPv6, but only peers via IPv6 if the other node has IPv4 disabled. | | **Nimbus** | Full | IPv4 only\* | Primarily IPv4 | Can accept inbound IPv6 connections, but broadcasts only IPv4 in ENR. | | **Prysm** | IPv4 only\* | IPv4 only\* | Primarily IPv4 | Listens and broadcasts on IPv4 only, so IPv6 peers can't reach it. Can still connect out to some IPv6 peers. | \* By default, uses IPv4. On IPv6-only hosts, uses IPv6 instead. ### Prerequisites Before enabling IPv6, ensure that: 1. Your ISP/host provides IPv6 connectivity - Test this with [ipv6test.google.com/](https://ipv6test.google.com/) or by running this command in your CLI: `curl -6 https://icanhazip.com`. If the command returns an IPv6 address in this format: `xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx`, you are good to go. 2. Your firewall allows IPv6 traffic on the consensus client P2P ports. The defaults are `9001` (TCP and UDP) and `8001` (UDP, for QUIC). Teku requires additional dedicated ports for IPv6. The default Teku IPv6 ports are `9090` (TCP and UDP) and `8002` (UDP, for QUIC). If you use Besu or Reth, also allow IPv6 traffic on the execution client P2P port (default `30303`). 3. You're using locally managed clients in Docker mode (not externally managed clients) ### How to Enable IPv6 To enable IPv6, go to the Smart Node and TX Fees category and check the **Enable IPv6** box then save and restart the Smart Node stack. ![](/static/image/tui-enable-ipv6.d0fe8c3ba0.png) ::: warning NOTE If you enable IPv6 but don't have a public IPv6 address, the Smart node will display a warning during startup: ``` Warning: IPv6 is enabled but no public IPv6 address was detected. Your node will not be reachable by IPv6 peers. ``` Your node will continue to work normally using IPv4. ::: ### Verifying that IPv6 is Working After enabling IPv6 and restarting your services, you can verify it's working correctly: 1. Check Docker Network Configuration ```shell docker inspect rocketpool_net | grep -i ipv6 ``` You should see `"EnableIPv6": true` and each container should have an `IPv6Address`. 2. Verify Port Binding ```shell sudo nsenter -t $(docker inspect -f '{{.State.Pid}}' rocketpool_eth2) -n ss -tlnp | grep 9001 ``` This checks the port inside your consensus client's container. You should see `*:9001` or `[::]:9001`. If you see an IPv4 address instead (such as `172.18.0.x:9001`), your consensus client isn't listening on IPv6 (expected for Prysm, see the table above). 3. Confirm Your Public IPv6 Address ```shell curl -6 https://icanhazip.com ``` Should return your public IPv6 address (e.g., `xxx:xxx:xxxx:...`). 4. Check Consensus Client Logs View your consensus client logs to confirm IPv6 listening: ```shell docker logs rocketpool_eth2 2>&1 | grep -iE "listen|ipv6|::" | head -20 ``` **What to look for:** - **Lighthouse** - `Listening on /ip6/` or `listen_addr: /ip6/` - **Lodestar** - `Multiaddrs` showing both `/ip4/` and `/ip6/` addresses - **Teku** - `p2p-interface` showing both `0.0.0.0` and `::` - **Nimbus** - `Listening to incoming network requests` (does not explicitly mention IPv6) - **Prysm** - `Beacon chain gRPC server listening` (does not explicitly mention IPv6) 5. Check for IPv6 Peers Check your beacon node's peer list via the API: ```shell curl -s http://localhost:5052/eth/v1/node/peers | grep -o '/ip6/[^"]*' | head -10 ``` This will show up to 10 IPv6 peer addresses if any are connected. Depending on which consensus client you are using, it may take a while for any IPv6 peers to connect. In our testing, we found that Teku was the only client to immediately connect to IPv6 peers. --- url: /node-staking/backups.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Backing Up Your Node ::: tip NOTE This is currently written for **Docker Mode** installations. Some locations may vary for Hybrid or Native users. ::: In general, if you created your node wallet and minipools via the Smart Node, the only thing you truly need on hand to recover your node from a complete failure is the **mnemonic for your node wallet** Everything else can be recovered from that quite easily. If you have minipools that have externally-generated validator keys (e.g. you migrated from **Allnodes** to your own self-hosted node), you will need the private keystore files for your validators as well since they cannot be recovered from the node wallet. That being said, once the Merge takes place, you will no longer be able to use a light Execution client (e.g. Pocket or Infura) as a fallback if you ever need to resync the Execution layer chain. Furthermore, you will be required to have an active and healthy Execution client to attest correctly. Having a fast, reliable way to recover from an Execution client failure (such as a corrupt database, SSD malfunction, or compromised / stolen hardware) will be critical, as it can take hours or even days to sync from scratch. In this guide, we'll show you how to back up some of these things to help improve your node's resilience and minimize unnecessary downtime. ::: warning NOTE This guide assumes you have installed the Smart Node to the default directory (`~/.rocketpool`). If you specified a different installation directory, substitute it accordingly in the instructions below. ::: ## Items That Can Be Backed Up ### Smart Node Configuration The Smart Node's configuration is stored in `~/.rocketpool/user-settings.yml`. You can save this and replace it to restore all of your Smart Node settings (i.e., the things you specified in `rocketpool service config`). ### Execution Client / ETH1 Client Chain Data The Execution client's chain data is likely the most important thing to back up. As mentioned, it can take several days to re-sync your EC chain data. After The Merge, this means hours to days of downtime and lost profits! The chain data is stored within the `rocketpool_eth1clientdata` Docker volume, which by default is located at `/var/lib/docker/volumes/rocketpool_eth1clientdata`. Note this folder is typically not accessible by unprivileged user accounts; you will need to elevate to the `root` user to see it. ::: tip NOTE If you changed Docker's storage location during the initial Smart Node installation (such as people that run Docker on a second SSD), you will find the volume in `//docker/volumes/rocketpool_eth1clientdata` If you don't recall which installation path you use, you can check `/etc/docker/daemon.json` for its location. If the file doesn't exist, you use the default location. ::: For detailed instructions on how to efficiently back up your Execution chain data, please see the [Backing up your Execution Chain Data](#backing-up-your-execution-chain-data) section below. ### Monitoring & Metrics Data This data is stored within the `rocketpool_grafana-storage` Docker volume, which by default is located at `/var/lib/docker/volumes/rocketpool_grafana-storage` (or `//docker/volumes/rocketpool_prometheus-data` if you customized your Docker storage location). ## Items That Should **Not** Be Backed Up ### Private Keys and Passwords Your node wallet's private key and the password file used to encrypt it are stored in `~/.rocketpool/data/wallet` and `~/.rocketpool/data/password` respectively. These files don't generally need to be backed up, as they can be recovered from your mnemonic using `rocketpool wallet recover`. If, for some reason, you _do_ decide to back up these files, you will need to be **extremely careful** about how you store them. Anyone who gains access to these files will gain access to your node wallet, its validators, and any funds you have stored on it for things like gas. We **strongly recommend** you do not back up these files and just use your wallet mnemonic to recover them if necessary. ### Consensus Client Chain Data Unlike the Execution layer data, the Consensus layer data is not nearly as important to your node thanks to [Checkpoint Sync](/node-staking/config-docker.md#beacon-chain-checkpoint-syncing). Consensus clients can easily use this technique to immediately resync to the head of the Beacon chain and resume validation duties. ## Backing up your Execution Chain Data The Smart Node comes with the ability to back up your Execution chain data via the `rocketpool service export-eth1-data` command. Under the hood, this utilizes `rsync`, a powerful backup/copy tool within Linux. `rsync` compares the files in the source directory (your Docker volume) and the target directory (your backup location). If a source file doesn't exist in the target directory, it will be copied entirely. However, if it _does_ exist, `rsync` will only copy the _changes_ between the two files. This means the first backup will take a good amount of time as it must copy all of the data initially. Subsequent backups will only copy the changes between your previous backup and now, making the process much faster. As part of a backup strategy, you may want to plan to run `export-eth1-data` on a regular basis. To ensure the integrity of the chain data, running this command will **safely shut down the Execution client before backing up its data**. If you elect to schedule it every week, your Execution client will only be down for a few minutes while it updates the backup. This is certainly better than the days it would take to resync the data from scratch. To trigger a backup, start by **mounting the storage medium you want to export the data to**. For example, this could be an external hard drive. ::: tip HINT If you don't know how to mount external devices on Linux, it's easy! Plug the device into your node, and follow [a guide like this](https://www.addictivetips.com/ubuntu-linux-tips/mount-external-hard-drives-in-linux/) to learn how to mount it. ::: Once you have it mounted, note its mount path. For this example, let's assume that we want to store the chain data in a folder called `/mnt/external-drive` which the external device is mounted to. Replace this with your actual mount path wherever you see it below. Now, run the following command: ```shell rocketpool service export-eth1-data /mnt/external-drive ``` This will check that your target folder is reachable and has enough free space to store the chain data. The output will look like this: ``` This will export your execution client's chain data to an external directory, such as a portable hard drive. If your execution client is running, it will be shut down. Once the export is complete, your execution client will restart automatically. You have a fallback execution client configured (http://:8545). Rocket Pool (and your consensus client) will use that while the main client is offline. Chain data size: 87 GiB Target dir free space: 287 GiB Your target directory has enough space to store the chain data. NOTE: Once started, this process *will not stop* until the export is complete - even if you exit the command with Ctrl+C. Please do not exit until it finishes so you can watch its progress. Are you sure you want to export your execution layer chain data? [y/n] ``` As you can see, the chain data will be under 100 GB (for the Hoodi testnet; the Ethereum mainnet will be an order of magnitude larger) and the external folder has 287 GiB free so exporting can continue. When you're ready, enter `y` here and press `Enter`. This will stop your Execution client and begin copying its chain data to your target folder. You will see the progress of each individual file go past the screen as it runs. ::: warning NOTE It's important that you _do not_ exit the terminal while this is running. If you do, the copy will continue to run in the background but you won't be able to follow its progress! ::: Once it's finished, it will automatically restart your Execution client container. **Note that your existing chain data is not deleted from your node after the export is complete!** ### Restoring Your Execution Chain Data If you ever need to restore your backed up chain data, simply run the following command. ```shell rocketpool service import-eth1-data /mnt/external-drive ``` ::: danger WARNING This will automatically delete any existing Execution client data in your `rocketpool_eth1clientdata` volume! ::: Once it's done, your Execution client will be ready to go. --- url: /node-staking/change-clients.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Changing Execution or Consensus Clients Under normal circumstances, you will likely just select an Execution and Consensus client when you first create your Rocket Pool node and will let them happily run for the life of your Node. However, there are a few situations where you may want to change your client selection. Here are a few examples: - Your client gains a [supermajority](https://clientdiversity.org/) share on the Execution or Beacon chains, and you want to change for the overall health of the network - A bug causes your client to stop functioning correctly, and you need to get back online quickly to resume validation duties - You want to try a new feature that a different client offers - A different client is better suited to your node's hardware (e.g. some clients are better on ARM systems than others) Luckily, the Smart Node stack makes changing clients extremely easy. All it takes is a few changes in the Configuration TUI, and some optional extra commands to back up your existing client data before changing clients. ## Changing Execution Clients Prior to changing your Execution client, it's worth noting the following points: - Chain data **is not shared** between clients. Your new client will need to resync the Mainnet chain data, which can take some time (though each client supports snap sync, which the Smart Node uses to speed up resyncing). - By default, the Smart Node will leave your old client's chain data on your drive in case you want to revert back to your old Execution client and pick up where you left off. You may want to **export it to a different location** and delete it to free up space prior to changing clients, since Execution clients can use hundreds of gigabytes. We have steps below on how to do this. - While your new client is resyncing, most of the Smart Node CLI functions will be offline since they rely on the Execution client. **You should have a fallback Execution client available before doing this to mitigate the downtime on your Smart Node.** ### (Optional) Export your Execution Client's Database The first step in the process is an optional one: if you like, you can export your existing chain data for your current Execution client. This will let you free up valuable disk space on your node for your new Execution client, and you can keep the old chain data around in case you want to revert back to the old client and pick up where you left off. Please refer to the [Backing Up Your Node](/node-staking/backups.md#backing-up-your-execution-chain-data) guide for details. ### Change your Selected Execution Client To change your selected client, run `rocketpool service config` to enter the configuration UI. Navigate to the `Execution Client (ETH1)` section, and select the `Execution Client` dropdown: ![](/static/image/tui-select-ec.b83d6b57eb.png) Open the dropdown with `Enter`, use the arrow keys to navigate to your client of choice, and press `Enter` again to confirm the selection. Note that each client has its own unique options, so you may see some additional settings appear in this screen after you select a different client. Feel free to explore through them to see how they affect things. When you're happy with your choice, press `Esc` to return to the main menu, then `Tab` to highlight the `Review Changes and Save` button. You will be presented with the review screen, which will show your client selection change: ![](/static/image/tui-confirm-ec.d93fb5e923.png) Press `Enter` to accept the changes, and you're done! Your new Execution client will begin syncing immediately. As usual, you can follow it with `rocketpool service logs eth1`. **We recommend you do this to verify there are no errors, and that it works properly.** ::: danger NOTE Now that the Execution and Consensus layers have merged, taking down your Execution client will _also_ take down your Consensus client until your Execution client has finished resyncing. This means your node will **stop attesting and proposing blocks, and it will leak ETH instead of earning it!** To avoid this and continue validating while your Execution client resyncs, **please set up a [fallback node](/node-staking/fallback.md)**. ::: ### (Recommended) Remove your Old Chain Data This is not a required step, but we **strongly recommend** you remove the chain data from your old client now that you've switched to a new one so you can free up disk space for it. To do this, simply run the following command: ```shell rocketpool service resync-eth1 ``` This will delete all of your Execution client data and start it over. ::: tip TIP Since you just selected a new Execution client, it won't be affected by this - essentially, all it will do is delete your old chain data. You should do this as soon as possible after switching clients to prevent unnecessary loss of progress on your new client. ::: ## Changing Consensus Clients Changing Consensus clients is even easier than Execution clients, thanks to [Checkpoint Sync](/node-staking/config-docker.md#beacon-chain-checkpoint-syncing). This feature lets you immediately sync a new Consensus client with the network, so there's no need to preserve your old chain data. Start by using the `rocketpool service config` UI and navigating to the `Consensus Client (ETH2)` section. Next, select the `Consensus Client` dropdown: ![](/static/image/tui-select-cc.eb3271e1d0.png) Open the dropdown with `Enter`, use the arrow keys to navigate to your client of choice, and press `Enter` again to confirm the selection. Note that each client has its own unique options, so you may see some additional settings appear in this screen after you select a different client. Feel free to explore through them to see how they affect things. Next, verify that you're using a Checkpoint Sync provider: ![](/static/image/tui-checkpoint-sync.3609828bb3.png) If you don't have a Checkpoint Sync provider configured, [you can easily use instructions from here to do it for free](/node-staking/config-docker.md#beacon-chain-checkpoint-syncing)! When you're happy with your choice, press `Esc` to return to the main menu, then `Tab` to highlight the `Review Changes and Save` button. You will be presented with the review screen, which will show your client selection change: ![](/static/image/tui-confirm-cc.3e8f4000c2.png) Press `Enter` to accept the changes, and you're done! Your new Consensus client will begin syncing immediately. As usual, you can follow it with `rocketpool service logs eth2`. **We recommend you do this to verify there are no errors, and that it works properly.** --- url: /node-staking/cli-intro.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Intro to the Command Line Interface As a node operator, the CLI is your primary tool for interacting with Rocket Pool. You will use it to create new megapool validators, check on the status of everything, claim periodic RPL rewards, exit and withdraw from your minipools when you're ready, and a host of other activities. Once you've finished syncing the Execution and Beacon chains, all of the commands will be available for you to use. In this section, we'll go over a brief tour of some of the more common ones and some other tricks that the CLI can do. ## Learning About the Commands To list all of the available commands, type: ```shell rocketpool help ``` The output will look like this: ``` ______ _ _ ______ _ | ___ \ | | | | | ___ \ | | | |_/ /___ ___| | _____| |_ | |_/ /__ ___ | | | // _ \ / __| |/ / _ \ __| | __/ _ \ / _ \| | | |\ \ (_) | (__| < __/ |_ | | | (_) | (_) | | \_| \_\___/ \___|_|\_\___|\__| \_| \___/ \___/|_| Authored by the Rocket Pool Core Team A special thanks to the Rocket Pool community for all their contributions. NAME: rocketpool - Rocket Pool CLI USAGE: rocketpoolcli [global options] command [command options] [arguments...] VERSION: 1.24.2 COMMANDS: auction, a Manage Rocket Pool RPL auctions claims, l View and claim all available rewards and credits across the node minipool, m Manage the node's minipools megapool, g Manage the node's megapool network, e Manage Rocket Pool network parameters node, n Manage the node odao, o Manage the Rocket Pool oracle DAO pdao, p Manage the Rocket Pool Protocol DAO queue, q Manage the Rocket Pool deposit queue security, c Manage the Rocket Pool security council service, s Manage Rocket Pool service wallet, w Manage the node wallet update Update the cli binary help, h Shows a list of commands or help for one command GLOBAL OPTIONS: --allow-root, -r Allow rocketpool to be run as the root user --config-path path, -c path Rocket Pool config asset path (default: "~/.rocketpool") --daemon-path path, -d path Interact with a Rocket Pool service daemon at a path on the host OS, running outside of docker --maxFee value, -f value The max fee (including the priority fee) you want a transaction to cost, in gwei (default: 0) --maxPrioFee value, -i value The max priority fee you want a transaction to use, in gwei (default: 0) --gasLimit value, -l value [DEPRECATED] Desired gas limit (default: 0) --nonce value Use this flag to explicitly specify the nonce that this transaction should use, so it can override an existing 'stuck' transaction --debug Enable debug printing of API commands --secure-session, -s Some commands may print sensitive information to your terminal. Use this flag when nobody can see your screen to allow sensitive data to be printed without prompting --help, -h show help --version, -v print the version COPYRIGHT: (c) 2026 Rocket Pool Pty Ltd ``` The `pdao` group is for Protocol DAO voting and proposals. Voting is done with `rocketpool pdao proposals vote`. To change **several** Protocol DAO settings in a single proposal, write them to a JSON file using the `--to-json` flag on the setting propose commands, then submit with: ```shell rocketpool pdao propose submit-batch ``` Governance walkthrough: [Participating in on-chain pDAO Proposals](/pdao/participate.md). ## Service Commands The service group involves managing the various services the smart node manages for you. Here is what the `rocketpool service help` output will show: ``` NAME: rocketpool service - Manage Rocket Pool service USAGE: rocketpool service [global options] command [command options] [arguments...] VERSION: 1.24.2 COMMANDS: install, i Install the Rocket Pool service config, c Configure the Rocket Pool service status, u View the Rocket Pool service status start, s Start the Rocket Pool service pause, p Pause the Rocket Pool service stop, o Pause the Rocket Pool service (alias of 'rocketpool service pause') reset-docker, rd Cleanup Docker resources, including stopped containers, unused images and networks. Stops and restarts Smart Node. prune-docker, pd Cleanup unused Docker resources, including stopped containers, unused images, networks and volumes. Does not restart smartnode, so the running containers and the images and networks they reference will not be pruned. logs, l View the Rocket Pool service logs compose View the Rocket Pool service docker compose config version, v View the Rocket Pool service version information prune-eth1, n Shuts down the main ETH1 client and prunes its database, freeing up disk space, then restarts it when it's done. migrate-geth Shuts down Geth and migrates its database from Pebble v1 to Pebble v2, then restarts it when it's done. install-update-tracker, d Install the update tracker that provides the available system update count to the metrics dashboard get-config-yaml Generate YAML that shows the current configuration schema, including all of the parameters and their descriptions resync-eth1 Deletes the main ETH1 client's chain data and resyncs it from scratch. Only use this as a last resort! resync-eth2 Deletes the ETH2 client's chain data and resyncs it from scratch. Only use this as a last resort! terminate, t Deletes all of the Rocket Pool Docker containers and volumes, including your ETH1 and ETH2 chain data and your Prometheus database (if metrics are enabled). Also removes your entire `.rocketpool` configuration folder, including your wallet, password, and validator keys. Only use this if you are cleaning up the Smart Node and want to start over! GLOBAL OPTIONS: --compose-file value, -f value Optional compose files to override the standard Rocket Pool docker compose YAML files; this flag may be defined multiple times --help, -h show help ``` ### `status` This command shows you the current running status of each of the Docker containers managed by Rocket Pool. For example, the default Docker install's output looks like this: ``` Your Smart Node is currently using the Hoodi Testnet network. NAME IMAGE COMMAND SERVICE CREATED STATUS PORTS rocketpool_eth1 ghcr.io/paradigmxyz/reth:v2.8.1@sha256:… "sh /setup/start-ec.…" eth1 2 days ago Up 2 days 0.0.0.0:30303->30303/tcp, [::]:30303->30303/tcp, 0.0.0.0:30303->30303/udp, [::]:30303->30303/udp rocketpool_eth2 consensys/teku:26.10.2@sha256:… "sh /setup/start-bn.…" eth2 2 days ago Up 2 days 0.0.0.0:8001->8001/udp, [::]:8001->8001/udp, 0.0.0.0:9001->9001/tcp, [::]:9001->9001/tcp, 0.0.0.0:9001->9001/udp, [::]:9001->9001/udp rocketpool_exporter prom/node-exporter:v1.12.1@sha256:… "/bin/node_exporter …" node-exporter 2 days ago Up 2 days rocketpool_grafana grafana/grafana:13.2.4@sha256:… "/run.sh" grafana 2 days ago Up 2 days 3000/tcp, 0.0.0.0:3100->3100/tcp, [::]:3100->3100/tcp rocketpool_node rocketpool/smartnode:v1.25.1@sha256:… "/go/bin/rocketpool …" node 2 days ago Up 2 days 127.0.0.1:8280->8280/tcp rocketpool_prometheus prom/prometheus:v3.15.1@sha256:… "/bin/prometheus --w…" prometheus 2 days ago Up 2 days 9090/tcp rocketpool_validator consensys/teku:26.10.2@sha256:… "sh /setup/start-vc.…" validator 2 days ago Up 2 days 5051/tcp, 8008/tcp, 9000/tcp, 9000-9001/udp rocketpool_watchtower rocketpool/smartnode:v1.25.1@sha256:… "/go/bin/rocketpool …" watchtower 2 days ago Up 2 days Volume sizes: rocketpool_alertmanager-data 0B rocketpool_eth1clientdata 156.6GB rocketpool_eth2clientdata 429.3GB rocketpool_grafana-storage 3.279MB rocketpool_prometheus-data 2.133GB ``` You can use it to quickly check if any of the Docker containers are having trouble, or to make sure that a `start` or `stop` command worked correctly. Starting with Smart Node v1.25.1, the command also lists how much disk space each Smart Node Docker volume uses, below the container table. For example, `rocketpool_eth1clientdata` holds your Execution client's chain data and `rocketpool_eth2clientdata` holds your Consensus client's. This is a quick way to see what is filling up your disk. Measuring the volumes can take a while on a node with a large database, so the list may show up a little later than the table. ### `start` and `stop` These two commands you are already familiar with. They simply start all of the Rocket Pool containers, or stop them. ::: tip The `pause` command does the same thing as `stop`. It's just left over as a legacy command from earlier versions of Rocket Pool. ::: ### `logs` This command is another one you should have already seen. You can use it to look at the output logs of each Docker container. This can be useful for troubleshooting or getting a more detailed status report from them. If you simply do `rocketpool service logs` without any other arguments, it will aggregate all of the logs together and show them to you at once. If you want to focus on one container's output, you can add an argument to the end to specify the container. Valid values are `eth1`, `eth2`, `validator`, `api`, `node`, `watchtower`, `prometheus`, `grafana`, and `node-exporter`. By default, it shows the last 100 lines and keeps following new output until you press `Ctrl+C`. To look at a specific time window instead, add `--since`, `--until`, or both. Both accept a timestamp (such as `2026-10-20T10:00:00Z`) or a relative time (such as `30m` for 30 minutes ago): ```shell # Everything from the last 30 minutes, then keep following rocketpool service logs --since 30m eth2 # A 5-minute window that started 3 hours ago, using relative times rocketpool service logs --since 3h --until 2h55m node # The same kind of window, using timestamps rocketpool service logs --since 2026-10-20T10:00:00Z --until 2026-10-20T10:05:00Z node ``` With either flag, you get every line in the window rather than only the last 100. With `--until`, the command prints the logs and exits instead of following them. Logs only go back to when the container was last created, which happens on every Smart Node update, and the oldest lines are removed once the logs grow large. A window further back than that shows nothing. These flags require Smart Node v1.25.1 or newer. ### `config` This command runs through the configuration interview again. You can use it if you want to change your selection of Execution or Consensus client, or change some of the parameters that you initially specified when you selected them (such as your validator's graffiti message, the max number of peers to connect to, and so on). You can call this command at any time, but the changes won't take effect until you call `rocketpool service stop` and `rocketpool service start`. ### `migrate-geth` Geth operators who still have a Pebble v1 database can migrate it in place with: ```shell rocketpool service migrate-geth ``` This **shuts Geth down**, migrates the database from Pebble v1 to Pebble v2, then restarts it. Plan for Execution-client downtime (a [fallback node](/node-staking/fallback.md) keeps you attesting). Confirm with `y`, or pass `--yes` to skip the prompt. ### `terminate` This command will shut down the Docker containers, then delete them, delete the Rocket Pool virtual network, and delete the ETH1 and ETH2 chain data volumes and your Prometheus metrics database. It then deletes your entire Smart Node configuration folder (`~/.rocketpool` by default). Use it only when you want to remove the Smart Node completely and start over. ::: warning This is irreversible. It removes your chain data, which means you'll need to sync ETH1 and ETH2 again. It **also deletes your node wallet, password, and validator keys**, along with your configured settings. Before running it, make sure you have your node's recovery mnemonic written down and have verified it (for example with `rocketpool wallet test-recovery`), or you will lose access to your node wallet and validator keys. ::: ## Update Command To replace the CLI binary (and optionally stop, upgrade, and restart the stack), run: ```shell rocketpool update ``` This is the usual way to update a Docker or Hybrid node. The walkthrough lives on [Checking for Updates](/node-staking/updates.md). ## Node Commands The `node` group involves operations on your Rocket Pool node. We'll cover these more in-depth in the next section where we create a megapool validator, but it may be helpful to see them all at a glance. Here is what the `rocketpool node help` output will show: ``` NAME: rocketpool node - Manage the node USAGE: rocketpool node command [command options] [arguments...] COMMANDS: status, s Get the node's status sync, y Get the sync progress of the eth1 and eth2 clients register, r Register the node with Rocket Pool rewards, e Get the time and your expected RPL rewards of the next checkpoint set-primary-withdrawal-address, w Set the node's primary withdrawal address, which will receive all ETH rewards (and RPL if the RPL withdrawal address is not set) confirm-primary-withdrawal-address, f Confirm the node's pending primary withdrawal address if it has been set back to the node's address itself set-rpl-withdrawal-address, srwa Set the node's RPL withdrawal address, which will receive all RPL rewards and staked RPL withdrawals confirm-rpl-withdrawal-address, crwa Confirm the node's pending rpl withdrawal address if it has been set back to the node's address itself allow-rpl-locking, arl Allow the node to lock RPL when creating governance proposals/challenges deny-rpl-locking, drl Do not allow the node to lock RPL when creating governance proposals/challenges set-timezone, t Set the node's timezone location swap-rpl, p Swap old RPL for new RPL stake-rpl, k Stake RPL against the node add-address-to-stake-rpl-whitelist, asw Adds an address to your node's RPL staking whitelist, so it can stake RPL on behalf of your node. remove-address-from-stake-rpl-whitelist, rsw Removes an address from your node's RPL staking whitelist, so it can no longer stake RPL on behalf of your node. claim-rewards, c Claim available RPL and ETH rewards for any checkpoint you haven't claimed yet withdraw-rpl, i Withdraw RPL staked against the node withdraw-eth, h Withdraw ETH staked on behalf of the node withdraw-credit, wc (Saturn) Withdraw ETH credit from the node as rETH send, n Send ETH or tokens from the node account to an address. ENS names supported. Use 'all' as the amount to send the entire balance. can be 'rpl', 'eth', 'fsrpl' (for the old RPL v1 token), 'reth', or the address of an arbitrary token you want to send (including the 0x prefix). initialize-fee-distributor, z Create the fee distributor contract for your node, so you can withdraw priority fees and MEV rewards after the merge distribute-fees, b Distribute the priority fee and MEV rewards from your fee distributor to your withdrawal address and the rETH contract (based on your node's average commission) join-smoothing-pool, js Opt your node into the Smoothing Pool leave-smoothing-pool, ls Leave the Smoothing Pool sign-message, sm Sign an arbitrary message with the node's private key send-message Send a zero-ETH transaction to the target address (or ENS) with the provided hex-encoded message as the data payload claim-unclaimed-rewards, cur Sends any unclaimed rewards to the node's withdrawal address provision-express-tickets, pet Provision the node's express tickets OPTIONS: --help, -h show help ``` Below is a summary of some of the commands you'll tend to need during typical node operation. ### `status` This command will give you a high-level view of your entire node at a glance. It includes how much ETH and RPL you have staked, how many minipools you have and their statuses, your RPL collateral ratio, and more. This is an example of what `rocketpool node status` shows once you have your node registered and some minipools set up: ``` === Account and Balances === The node 0x4d19DE4A5a1B1B36EBaB3D5c32C01061fbDE328d has a balance of 49.402553 ETH and 0.000000 RPL. The node has 0.000000 ETH in its credit balance and 0.000000 ETH staked on its behalf. 0.000000 can be used to make new validators. The node is registered with Rocket Pool with a timezone location of America/Los_Angeles. === Megapool === The node has a megapool deployed at 0xCf3576c5A6e5a25AC00C9adb6751924BAe1680B1. The megapool has 9 validators. The node has 0 express queue ticket(s). === Penalty Status === The node does not have any penalties for cheating with an invalid fee recipient. === Signalling on RocketDash === The node does not currently have an offchain signalling address set. To learn more about offchain signalling, please visit https://docs.rocketpool.net/pdao/participate#setting-your-snapshot-signalling-address. Rocket Pool has no RocketDash governance proposals being voted on. === Onchain Voting === The node doesn't have a delegate, which means it can vote directly on onchain proposals. You can have another node represent you by running `rocketpool p svd
`. The node is NOT allowed to lock RPL to create governance proposals/challenges. === Primary Withdrawal Address === The node's primary withdrawal address has not been changed, so ETH rewards and minipool withdrawals will be sent to the node itself. Consider changing this to a cold wallet address that you control using the `set-withdrawal-address` command. === RPL Withdrawal Address === The node's RPL withdrawal address has not been set. All RPL rewards will be sent to the primary withdrawal address. === Fee Distributor and Smoothing Pool === The node's fee distributor 0x84c1f488CDecb2E335c40901E3Fe58925f4cC9A7 has a balance of 0.004897 ETH. NOTE: You are in Native Mode; you MUST ensure that your Validator Client is using this address as its fee recipient! The node is not opted into the Smoothing Pool. To learn more about the Smoothing Pool, please visit https://docs.rocketpool.net/upgrades/redstone/whats-new#smoothing-pool. === RPL Stake === NOTE: The following figures take *any pending bond reductions* into account. The node has a total stake of 20000.000000 RPL. This is currently 3.74% of its borrowed ETH and 30.06% of its bonded ETH. The node has 0.000000 megapool staked RPL. The node has 20000.000000 legacy staked RPL. The node has a total stake (legacy minipool RPL plus megapool RPL) of 20000.000000 RPL. You have 0.000000 RPL staked on your megapool and can request to unstake up to 0.000000 RPL === Minipools === The node has a total of 3 active minipool(s): - 3 staking ``` ### `sync` This command will show you the current sync status of your Execution and Consensus clients. You'll probably use it a lot when you first set the node up, then never need it again (unless you change or reset your clients). The output of `rocketpool node sync` will look like this: ``` Your Smartnode is currently using the Hoodi Test Network. Your eth1 client hasn't synced enough to determine if your eth1 and eth2 clients are on the same network. To run this safety check, try again later when eth1 has made more sync progress. Your primary execution client is still syncing (67.12%). You do not have a fallback execution client enabled. Your primary consensus client is still syncing (99.94%). You do not have a fallback consensus client enabled. ``` Note that **Prysm** currently doesn't provide its completion percent - you'll need to look in the `eth2` logs if you use it. ### `stake-rpl` This command is what you'll use when you want to stake more RPL on your node. RPL staked on your megapool earns a share of the protocol's ETH revenue and gives your node voting power; see [Staking RPL and Claiming Rewards](/node-staking/megapools/staking-and-claiming-rewards.md) for details. Unlike the other commands so far, this one is actually _interactive_ because it will trigger a transaction - it isn't simply informational. It will first ask you how much RPL you'd like to stake, with some pre-defined options for convenience or the ability to specify a custom amount: ``` NOTE: By staking RPL, you become a member of the Rocket Pool pDAO. Stay informed on governance proposals by joining the Rocket Pool Discord. Please choose an amount of RPL to stake: 1: 5% of borrowed ETH (733.993926 RPL) for one validator? 2: 10% of borrowed ETH (1467.987852 RPL) for one validator? 3: 15% of borrowed ETH (2201.981778 RPL) for one validator? 4: Your entire RPL balance (20000.000000 RPL)? 5: A custom amount ``` Once you select an option, you will be shown some information about the suggested gas price and estimated amount to be used, along with a confirmation dialog. If it's your first time staking RPL on the node, you'll need to give the staking contract approval to interact with your RPL: ``` Before staking RPL, you must first give the staking contract approval to interact with your RPL. This only needs to be done once for your node. +============== Suggested Gas Prices ==============+ | Avg Wait Time | Max Fee | Total Gas Cost | | 15 Seconds | 4 gwei | 0.0001 to 0.0001 ETH | | 1 Minute | 4 gwei | 0.0001 to 0.0001 ETH | | 3 Minutes | 4 gwei | 0.0001 to 0.0001 ETH | | >10 Minutes | 4 gwei | 0.0001 to 0.0001 ETH | +==================================================+ These prices include a maximum priority fee of 2.00 gwei. Please enter your max fee (including the priority fee) or leave blank for the default of 4 gwei: Using a max fee of 4.00 gwei and a priority fee of 2.00 gwei. Do you want to let the staking contract interact with your RPL? [y/n] y Approving RPL for staking... Transaction has been submitted with hash . You may follow its progress by visiting: https://hoodi.etherscan.io/tx/ Waiting for the transaction to be included in a block... you may wait here for it, or press CTRL+C to exit and return to the terminal. Successfully approved staking access to RPL. RPL Stake Gas Info: +============== Suggested Gas Prices ==============+ | Avg Wait Time | Max Fee | Total Gas Cost | | 15 Seconds | 4 gwei | 0.0005 to 0.0007 ETH | | 1 Minute | 4 gwei | 0.0005 to 0.0007 ETH | | 3 Minutes | 4 gwei | 0.0005 to 0.0007 ETH | | >10 Minutes | 4 gwei | 0.0005 to 0.0007 ETH | +==================================================+ These prices include a maximum priority fee of 2.00 gwei. Please enter your max fee (including the priority fee) or leave blank for the default of 4 gwei: Using a max fee of 4.00 gwei and a priority fee of 2.00 gwei. Are you sure you want to stake 733.993925 RPL? You may request to unstake your staked RPL at any time. The unstaked RPL will be withdrawable after an unstaking period of 672h0m0s. [y/n] ``` If you confirm, you will be shown the transaction hash and given a link to [Etherscan](https://etherscan.io) so you can follow its progress: ``` Staking RPL... Transaction has been submitted with hash . You may follow its progress by visiting: https://hoodi.etherscan.io/tx/ Waiting for the transaction to be included in a block... you may wait here for it, or press CTRL+C to exit and return to the terminal. Successfully staked 733.993925 RPL. ``` Most operations only require one transaction, so the CLI will wait until it has been included in a block and then exit. However, stake-rpl is one of the few commands that requires two transactions, so this dialog will appear twice. ### `claim-rewards` When your node detects a new rewards checkpoint, it will automatically download the rewards tree file with the information for that interval (if you're using the default of Download Mode - see below for information on generating your own trees instead of downloading them). You can then review your rewards using the following command: ``` rocketpool node claim-rewards ``` As intervals go by and you accumulate rewards, the output will look like this: ![](/static/image/claim-rewards-gb.bd6aec354a.png) Here you can quickly see how many rewards you've earned at each interval, and can decide which ones you want to claim. You can also specify an amount you want to restake during this claim: ![](/static/image/autostake.4de0b52e8e.png) This will let you compound your RPL rewards in one transaction, using substantially less gas than you currently needed to use with the legacy claim system. ::: tip NOTE If you prefer to build the rewards checkpoint manually instead of downloading the one created by the Oracle DAO, you can change this setting from `Download` to `Generate` in the TUI: ![](/static/image/tui-generate-tree.9f862c08b7.png) As the tip implies, you will need access to an Execution client archive node to do this. If your local Execution client is not an archive node, you can specify a separate one (such as Infura or Alchemy) in the `Archive-Mode EC URL` further down in the same menu. This URL will only be used when generating Merkle trees; it will not be used for validation duties. ::: ### `join-smoothing-pool` ```shell rocketpool node join-smoothing-pool ``` This will record you as opted-in in the Rocket Pool contracts and automatically change your Validator Client's `fee recipient` from your node's distributor contract to the Smoothing Pool contract. Note that once you opt in, there is a **28 day cooldown** (one full rewards interval length) until you can opt out. ### `leave-smoothing-pool` ```shell rocketpool node leave-smoothing-pool ``` This will opt you out of the Smoothing Pool if you're currently opted in, and have waited at least 28 days after opting in. Once **the next epoch after the current epoch** is finalized, it will automatically change your node's `fee recipient` from the Smoothing Pool back to your node's distributor contract. This is to ensure you don't get penalized for front-running the exit process when you see that you have a proposal coming up. ### `distribute-fees` Once you've earned rewards on your fee distributor, you can claim and distribute its entire balance using the following command: ```shell rocketpool node distribute-fees ``` This will send your share of the rewards to your **withdrawal address**. ### `send` This command lets you send ETH, RPL, or other Rocket Pool-related tokens from the node wallet to a different address. This might be useful if you want to move your funds on the wallet elsewhere. The syntax for using the `send` command is like this: ```shell rocketpool node send
``` The arguments are as follows: - `` is the amount of the token to send. - `` is the token to send - this can be `eth`, `rpl`, `fsrpl` (the old legacy RPL token), or `reth`. - `
` is the Ethereum address (or ENS name) to send the tokens to. For example: ```shell rocketpool node send 1 eth ``` would send 1 ETH to my friend. ## Megapool Commands The `megapool` group is where you can access all the commands used to manage your megapool and megapool validators. Here's what `rocketpool megapool help` will show: ``` NAME: rocketpool megapool - Manage the node's megapool USAGE: rocketpool megapool [global options] command [command options] [arguments...] VERSION: 1.24.2 COMMANDS: deposit, d Make a deposit and create a new validator on the megapool. Optionally specify count to make multiple deposits. status, s Get the node's megapool status validators, v Get a list of the megapool's validators repay-debt, r Repay megapool debt reduce-bond, e Reduce the megapool bond claim, c Claim any megapool rewards that were distributed but not yet claimed stake, k Stake a megapool validator exit-queue, x Exit the megapool queue dissolve-validator, i Dissolve a megapool validator exit-validator, t Request to exit a megapool validator notify-validator-exit, n Notify that a validator exit is in progress notify-final-balance, f Notify that a validator exit has completed and the final balance has been withdrawn distribute, b Distribute any accrued execution layer rewards sent to this megapool GLOBAL OPTIONS: --help, -h show help ``` Below is a summary of the commands that you'll typically use during normal operation: ### `deposit` This command lets you create new validators on your megapool. We'll go more into it later. Feel free to jump ahead to [Creating a Megapool Validator](/node-staking/megapools/create-megapool-validator.md) if you'd like a preview. ### `status` This command gives you some information on the state of your megapool and the validators managed by your megapool. You'll be able to see your megapool's address, number of express queue tickets, your megapool's delegate address, ETH balance on the execution and consensus layer, and lots of other useful information. Here's an example of the `rocketpool megapool status` output: ``` === Megapool === The node has a megapool deployed at 0xCf3576c5A6e5a25AC00C9adb6751924BAe1680B1 The node has 0 express ticket(s). The megapool has 9 validators. === Megapool Delegate === The megapool is using the latest delegate. The megapool's effective delegate address is 0x138602A95956995280f1146aA9477d6B4E481B3c The megapool has automatic delegate upgrades disabled. You can toggle this setting using 'rocketpool megapool set-use-latest-delegate'. === Megapool Balance === The megapool has 4.000000 node bonded ETH. The megapool has 28.000000 RP ETH for a total of 32.000000 bonded ETH. Megapool balance (EL): 32.051883 ETH The megapool has 1 validators exiting. You'll be able to see claimable rewards once the exit process is completed. Beacon balance (CL): 0.000000 ETH Your portion: 0.000000 ETH Current network commission: 5.000000% ``` ### `validators` The `rocketpool megapool validators` command will show you the status of each and every validator managed by your node's megapool. You'll be able to see information such as the validator pubkeys, beacon chain state, and queue position of prestaking validators: ``` There are 8 validator(s) on the express queue. There are 2 validator(s) on the standard queue. The express queue rate is 2. 1 Staking validator(s): Megapool Validator ID: 1 Validator pubkey: Validator active: no Validator index: Beacon status: pending_queued Express Ticket Used: no 1 Initialized validator(s): -------------------- Megapool Validator ID: 2 Expected pubkey: Validator active: no Validator Queue Position: 10 Express Ticket Used: no 1 Exiting validator(s): -------------------- Megapool Validator ID: 0 Validator pubkey: Validator active: no Validator index: Beacon status: withdrawal_done Express Ticket Used: yes ``` ### `exit-validator` This command allows you to select a validator to voluntarily exit on the Beacon Chain. Use this when you want to close a validator and withdraw its final ETH balance. Note that this cannot be undone - once you trigger an exit, the validator will shut down permanently. ## Minipool Commands The `minipool` group involves commands that affect your minipools. As with the `node` group, we'll cover these more in-depth in the next section but it may be helpful to see them all now. Here is what the `rocketpool minipool help` output will show: ``` NAME: rocketpool minipool - Manage the node's minipools USAGE: rocketpool minipool command [command options] [arguments...] COMMANDS: status, s Get a list of the node's minipools stake, t Stake a minipool after the scrub check, moving it from prelaunch to staking. set-withdrawal-creds, swc Convert the withdrawal credentials for a migrated solo validator from the old 0x00 value to the minipool address. Required to complete the migration process. import-key, ik Import the externally-derived key for a minipool that was previously a solo validator, so the Smart Node's VC manages it instead of your externally-managed VC. refund, r Refund ETH belonging to the node from minipools distribute-balance, d Distribute a minipool's ETH balance between your withdrawal address and the rETH holders. exit, e Exit staking minipools from the beacon chain close, c Withdraw any remaining balance from a minipool and close it delegate-upgrade, u Upgrade a minipool's delegate contract to the latest version rescue-dissolved, rd Manually deposit ETH into the Beacon deposit contract for a dissolved minipool, activating it on the Beacon Chain so it can be exited. OPTIONS: --help, -h show help ``` ::: warning NOTE The `set-withdrawal-creds` and `import-key` commands only apply to minipools that were created from solo validator migrations before Saturn 1. [Solo validator migration](/node-staking/solo-staker-migration.md) is no longer possible, and the corresponding `create-vacant-minipool` and `promote` commands have been removed from the CLI. ::: Below is a summary of the commands that you'll typically use. ### `status` This command simply provides a summary of each of your minipools. This includes its current status, the eth1 address of the minipool, the commission on it (called the `node fee`), the public key of the corresponding ETH2 validator, and some other things: ``` $ rocketpool minipool status 1 Staking minipool(s): -------------------- Address: Penalties: 0 Status updated: 2025-07-15, 08:31 +0000 UTC Node fee: 5.000000% Node deposit: 8.000000 ETH RP ETH assigned: 2025-07-14, 20:26 +0000 UTC RP deposit: 24.000000 ETH Minipool Balance (EL): 0.064202 ETH Your portion: 0.018458 ETH Available refund: 0.000000 ETH Total EL rewards: 0.018458 ETH Validator pubkey: Validator index: Validator active: yes Beacon balance (CL): 32.000347 ETH Your portion: 8.000099 ETH Use latest delegate: no Delegate address: 0x56903694d881282D33ed0643EAe14263880Dd47F Rollback delegate: Effective delegate: 0x56903694d881282D33ed0643EAe14263880Dd47F ``` ### `refund` This command lets you pull 16 ETH back from a minipool if you deposited 32 ETH to create one, once Rocket Pool was able to contribute 16 ETH from the rETH staking pool. ### `exit` This command submits a voluntary exit for your validator on the Beacon Chain. Use this when you want to close a validator and withdraw its final ETH balance. Note that **this cannot be undone** - once you trigger an exit, the validator will shut down permanently. ## Useful Flags There are some useful global flags that you can add to some of the above commands, which you may want to take advantage of. ### Setting a Custom Max Fee or Priority Fee (Gas Price) Starting with [the London ETH1 hardfork](https://coinquora.com/ethereum-london-hard-fork-all-you-need-to-know/) in July of 2021, Ethereum transactions no longer use a single gas price for their transactions. Instead, modern Ethereum transactions use two values: - The **max fee**, which describes the absolute maximum gas price you're willing to accept on a transaction - The **max priority fee**, which describes the maximum amount you're willing to "tip" the miner for including your transaction in a block ::: tip TIP The way these two values work can be a bit convoluted, so here are some simple examples. Let's say the current network fee, called the **base fee**, is at 50 gwei. You submit a transaction with an **80 gwei** max fee, and a priority fee of **2 gwei**. Because the network's base fee is lower than your max fee, this transaction could get picked up in the current block. It would cost you **50 gwei** for the base fee and **2 gwei** for the priority fee; even though you set your max fee to 80, **it would only cost you 52 gwei total**. As another example, say you have that same transaction, but now the network's base fee is **100 gwei**. Since 100 gwei is larger than your 80 gwei max fee, your transaction **will not** be included in this block. Instead, it will simply sit in the transaction pool until the base fee is low enough to include it. Now, let's say the current base fee is **50 gwei** again, and your transaction has a max fee of **80** gwei and a priority fee of **4 gwei**. It would execute with a total cost of **54 gwei**. The 4 gwei priority fee would ensure that it was included in front of all of the transactions with a lower priority fee. If you **really** want the transaction to go through at all costs, you can set the priority fee to be the same as the max fee. This emulates the legacy gas behavior, so your transaction will use all of the gas you give it - regardless of whether or not the network's base fee is lower than your max fee or not. ::: By default, Rocket Pool will use an oracle to look at the current transaction pool and suggest a reasonable max fee for any transactions you trigger. It uses [EtherChain](https://etherchain.org/tools/gasnow) for its primary suggestion oracle, and [Etherscan](https://etherscan.io/gastracker) as a backup. If you prefer, you can set a custom max fee (in gwei) you'd be willing to pay with the `-f` flag. You can also set a custom priority fee with the `-i` flag. To do this, add them after `rocketpool` and before the other command information. For example, calling `node set-timezone` with this flag would provide the following output: ``` $ rocketpool -f 10 node set-timezone Would you like to detect your timezone automatically? [y/n] n Please enter a timezone to register with in the format 'Country/City': Australia/Brisbane You have chosen to register with the timezone 'Australia/Brisbane', is this correct? [y/n] y Using the requested max fee of 10.00 gwei (including a max priority fee of 2.00 gwei). Total cost: 0.0005 to 0.0007 ETH Are you sure you want to set your timezone? [y/n] ``` This shows that regardless of what max fee the network recommends, it will use your custom max fee of 10 gwei (and priority fee if you specify it) instead when submitting this transaction. ::: warning NOTE If you set a manual max fee, we strongly encourage you to use a third-party gas price oracle such as [EtherChain](https://etherchain.org/tools/gasnow) to determine if that fee is high enough for the current network conditions before submitting the transaction. ::: ### Canceling / Overwriting a Stuck Transaction Sometimes, you might run into a scenario where you sent a transaction to the network but you used a gas price that is far too low for the network conditions, and it will take a prohibitively long time to execute. Since all of your subsequent transactions will wait until that one goes through, that transaction essentially blocks all of the operations on your Rocket Pool node. To deal with this situation, we've added a global flag that lets you "cancel" such a transaction by replacing it with something else. Every Ethereum wallet, including your node wallet, sends transactions sequentially. Each transaction you send has a number called a `nonce` that identifies where it lives in that sequence. The very first transaction you send will have a `nonce` of 0, the next one you send will have a `nonce` of 1, and so on. This overwriting technique involves sending a _new_ transaction that uses the same `nonce` as your existing _stuck_ transaction, but will ideally include a higher gas price than the stuck one. This means that the new one will be mined first. As soon as it's mined into a block, the old one will be discarded from the network as though it was never sent in the first place. To use this flag, you first need to find the `nonce` of your stuck transaction: 1. Go to an ETH1 block explorer like [https://etherscan.io](https://etherscan.io). 2. Navigate to the address of your wallet, and look at the list of transactions. 3. Go through them, starting with the most recent, until you find the furthest one down the list that has the `Pending` state. 4. Mark the `nonce` of that transaction. That's what you'll need. Once you have it, simply call any transaction with the CLI using the `--nonce -i 2.2` flags after `rocketpool` and before the rest of the command. ::: warning NOTE You **must** include the `-i` (priority fee) flag in order to overwrite a previous transaction. This number must be at least 10% higher than whatever priority fee your old transaction used. The Smart Node uses a priority fee of 2 gwei by default, so a value of `2.2` is usually sufficient for an override. If your old transaction used a custom fee (say, 10 gwei), you will need to set it at least 10% higher in the overriding transaction (so in this example, 11 gwei). ::: As an example, say I submitted a transaction with a `nonce` of 10 and a max fee of 20 gwei, but the current network fee is 100 gwei so my transaction is stuck. To fix it, I will submit a transaction where I send a small amount of ETH from myself back to myself with a higher max fee (say, 150 gwei) and a higher priority fee. I'll burn a little gas doing it, but it will unstick the broken transaction: ``` $ rocketpool --nonce 10 -f 150 -i 2.2 node send 0.0001 eth Using the requested max fee of 150.00 gwei (including a max priority fee of 2.20 gwei). Total cost: 0.0032 to 0.0032 ETH Are you sure you want to send 0.000100 eth to ? This action cannot be undone! [y/n] ``` The Smart Node stack will automatically check to make sure that the `nonce` you have provided is valid (it refers to a pending transaction) before sending it and wasting your gas accidentally. If not, it will return an error message. Otherwise, it will go through and provide you with the transaction details so you can monitor it to confirm that it did, in fact, overwrite your old stuck transaction. That's it for the common CLI commands. In the next section, we'll walk through how to create a megapool validator and start validating on the Beacon Chain. --- url: /node-staking/commit-boost.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Commit-Boost Commit-Boost is an open-source and community-driven validator sidecar that serves as an alternative to MEV-Boost for handling Proposer-Builder Separation (PBS). In addition to block building, Commit-Boost also supports proposer commitments protocols, such as preconfirmations and inclusion lists. The Smart Node currently runs only Commit-Boost's PBS (block building) module, so these extra protocols aren't available through the Smart Node yet. If you're new to MEV and PBS, we recommend reading the [MEV, MEV-Boost & MEV Rewards](/node-staking/mev.md) page first for background information. ## What is Commit-Boost? Commit-Boost is a drop-in alternative for MEV-Boost with additional capabilities. The main purpose is to standardize communication between Ethereum validators and third-party protocols. - Uses the same Builder API as MEV-Boost (default port 18550), so your Beacon Node talks to it the same way it talks to MEV-Boost. - Connects to MEV relays and handles block building, just like MEV-Boost. - Supports a modular plugin system for upcoming commitment protocols. - For developers, it provides a single API to interact with validators. Commit-Boost is [open source](https://github.com/Commit-Boost/commit-boost-client) and was [audited](https://github.com/Commit-Boost/commit-boost-client/blob/main/audit/Sigma_Prime_Commit_Boost_Client_Security_Assessment_Report_v2_0.pdf) by Sigma Prime in Dec 2024. ## Commit-Boost vs MEV-Boost Both Commit-Boost and MEV-Boost handle PBS using the builder marketplace and MEV relay infrastructure. Here's how they differ: | Feature | MEV-Boost | Commit-Boost | | ------------------------------ | --------- | ---------------------------------------------------------------------------------- | | **Purpose** | PBS only | PBS + extensible and modular platform | | **Maintainer** | Flashbots | Community / Commit-Boost team | | **Future protocols** | Static | Plugin system for third-party protocols (not available through the Smart Node yet) | | **Available relays (mainnet)** | 8 relays | 5 relays (OFAC-filtering only) | From the Smart Node's perspective, both connect to your Beacon Node identically. Commit-Boost is forward-looking as Ethereum adds new proposer commitment features like preconfirmations. :::tip NOTE You cannot run both MEV-Boost and Commit-Boost simultaneously. The Smart Node enforces this when saving your config within the TUI. ::: ## Available Relays Here are the relays available in Commit-Boost: | Name | Regulation | Networks | MEV Types | | ------------------------------------------------------------------------------------------------------------ | ------------------------------ | -------------- | --------- | | [Flashbots](https://boost.flashbots.net/) | Complies with OFAC Sanctions\* | Mainnet, Hoodi | All types | | [bloXroute Regulated](https://docs.bloxroute.com/eth/block-builders-and-validators/mev-relay-for-validators) | Complies with OFAC Sanctions\* | Mainnet, Hoodi | All types | | [Titan Regional](https://docs.titanrelay.xyz/) | Complies with OFAC Sanctions\* | Mainnet only | All types | | [Ultra Sound Filtered](https://relay-filtered.ultrasound.money/) | Complies with OFAC Sanctions\* | Mainnet only | All types | | BTCS OFAC+ | Complies with OFAC Sanctions\* | Mainnet only | All types | | [AESTUS](https://aestus.live/) | Unregulated | Hoodi only | All types | | [Titan Global](https://docs.titanrelay.xyz/) | Unregulated | Hoodi only | All types | :::warning NOTE \*Relays that comply with OFAC sanctions follow the blacklist of addresses that the United States Office of Foreign Assets Control (OFAC) maintains. We **strongly encourage** you to read more about OFAC sanctions, network censorship, and make a carefully-informed decision about which relays you are comfortable using. More information can be found in the [MEV page](/node-staking/mev.md#block-builders-and-relays). ::: :::warning IMPORTANT On mainnet, Commit-Boost supports **fewer relays** than MEV-Boost in the Smart Node. Specifically, Commit-Boost on mainnet does **not** include: - Ultra Sound (non-filtering) - Aestus - Titan Global (non-filtering) All relays available in Commit-Boost on mainnet are regulated/filtered versions that comply with OFAC sanctions. If you need access to unregulated relays, you should continue using MEV-Boost instead of Commit-Boost. ::: ## Rewards and APY Commit-Boost provides similar rewards to MEV-Boost. Since Commit-Boost only supports regulated relays on mainnet, you may see slightly different MEV rewards compared to MEV-Boost if you were previously using unregulated relays. In the future, proposer commitment protocols such as preconfirmations and inclusion lists could add additional yield on top of standard MEV rewards. ## Configuring Commit-Boost in the Smart Node To learn how to configure Commit-Boost, select your mode below: **Docker Mode** Configuring Commit-Boost is easy with the Smart Node's configuration TUI. Start by running `rocketpool service config` and select the `ePBS` category: ![](/static/image/tui-epbs.0ee1adc3e1.png)Then select `Commit-Boost`: ![](/static/image/tui-commit-boost.0abccc18f4.png)Check the box labeled `Enable Commit-Boost` to enable it. ![](/static/image/tui-enable-commit-boost.7a39eda76f.png):::tip NOTE If MEV-Boost is currently enabled, you'll need to disable it before saving and exiting the TUI. The Smart Node will not allow both to be enabled simultaneously. ::: Once enabled, you'll see several configuration options: **Commit-Boost Mode** - **Locally Managed** (recommended): The Smart Node runs and manages the Commit-Boost container for you. - **Externally Managed**: Use a Commit-Boost instance that you manage yourself. Enter its address in the **External URL** field (e.g., `http://192.168.1.10:18550`). None of the settings below apply in this mode. :::warning NOTE If you run your own Commit-Boost instance, you **must** only register with the trusted relays listed above. Using untrusted relays may result in penalties from the Oracle DAO. ::: **If using Locally Managed mode:** **Relay Selection Mode** - **Use All Relays**: Automatically enables all relays available for your current network (mainnet or testnet). This is the simplest option. - **Manual Mode**: Shows individual checkboxes for each available relay, letting you pick exactly which relays to use. **Custom Relays**: Add custom relay URLs (comma-separated) if you want to use relays not in the default list. Only add relays from the trusted list above; using untrusted relays may result in penalties from the Oracle DAO. **Port**: Default `18550` (same as MEV-Boost). You typically don't need to change this. **Expose API Port**: - **Closed** (recommended): API is only accessible within the Docker network - **Open to Localhost**: API is accessible on localhost - **Open to External hosts**: API is accessible from external machines. Only select this if you need external access _and_ you've followed the proper steps to secure your node from unwanted traffic: [Securing Your Node](/node-staking/securing-your-node.md) **Container Tag**: The Docker image tag for Commit-Boost. The Smart Node sets the default and updates it with each release. You can change it manually if a new version is released before the Smart Node is updated. Once you've configured Commit-Boost and selected your relays, save and exit. The Smart Node will restart the relevant containers and automatically configure your Beacon Node and Validator Client to use Commit-Boost. See below for instructions on verifying it's working correctly. **Hybrid Mode** Configuring Commit-Boost is easy with the Smart Node's configuration TUI. Start by running `rocketpool service config` and select the `ePBS` category: ![](/static/image/tui-epbs.0ee1adc3e1.png)Then select `Commit-Boost`: ![](/static/image/tui-commit-boost.0abccc18f4.png)Check the box labeled `Enable Commit-Boost` to enable it. ![](/static/image/tui-enable-commit-boost.7a39eda76f.png):::tip NOTE If MEV-Boost is currently enabled, you'll need to disable it before saving and exiting the TUI. The Smart Node will not allow both to be enabled simultaneously. ::: Once enabled, you'll see several configuration options: **Commit-Boost Mode** This determines whether the Smart Node manages Commit-Boost for you, or if you're running your own instance: - **Locally Managed** (recommended): The Smart Node runs and manages the Commit-Boost container for you. Some users prefer to let Rocket Pool manage its own instance of Commit-Boost and connect their externally-managed Beacon Nodes to it. - **Externally Managed**: Use this if your externally-managed Beacon Node already connects to its own Commit-Boost (or MEV-Boost) instance. There is no URL to enter: the Smart Node only enables the builder flags on its Validator Client, and you must enable the builder endpoint in your Beacon Node's own configuration. If you don't, you may not be able to publish blocks and will miss significant rewards. :::warning NOTE If you run your own Commit-Boost instance, you **must** only register with the trusted relays listed above. Using untrusted relays may result in penalties from the Oracle DAO. ::: **If using Locally Managed mode** (recommended for most users): **Relay Selection Mode** - **Use All Relays**: Automatically enables all relays available for your current network (mainnet or testnet). This is the simplest option. - **Manual Mode**: Shows individual checkboxes for each available relay, letting you pick exactly which relays to use. **Custom Relays**: Add custom relay URLs (comma-separated) if you want to use relays not in the default list. Only add relays from the trusted list above; using untrusted relays may result in penalties from the Oracle DAO. **Port**: Default `18550` (same as MEV-Boost). You typically don't need to change this. **Expose API Port**: This setting **should be changed from the default** so that your externally-managed Beacon Node can communicate with the Commit-Boost instance Rocket Pool will manage. - **Closed** (default): API is only accessible within the Docker network - **Open to Localhost**: API is accessible on localhost. Select this if your externally-managed BN is running on the same machine. - **Open to External hosts**: API is accessible from external machines. Only select this if your externally-managed BN is running on a different machine _and_ you've followed the proper steps to secure your node from unwanted traffic: [Securing Your Node](/node-staking/securing-your-node.md) **Container Tag**: The Docker image tag for Commit-Boost. The Smart Node sets the default and updates it with each release. You can change it manually if a new version is released before the Smart Node is updated. **If using Externally Managed mode**: There are no other settings to fill in. Relay selection, port, and the other options don't apply since you're managing Commit-Boost (and your Beacon Node's connection to it) yourself. Once you've configured Commit-Boost and selected your relays, save and exit the TUI. **Configuring your Beacon Node (Locally Managed mode)**: You'll need to manually configure your externally-managed Beacon Node to connect to the Smart Node's Commit-Boost instance. Set your Beacon Node's builder endpoint to `http://localhost:18550` (or use the appropriate IP if your BN runs on a different machine). Refer to your Beacon Client's documentation for the specific flag to enable the builder endpoint. The Smart Node will automatically configure your Validator Client with the necessary builder flags when you enable Commit-Boost. :::tip NOTE You **may need to permit this in your UFW configuration** if you have the firewall enabled. ::: See below for instructions on verifying it's working correctly. **Native Mode** Native Mode users who want to use Commit-Boost must set it up manually outside the Smart Node: Refer to the [official Commit-Boost documentation](https://commit-boost.github.io/commit-boost-client/) for installation and configuration instructions. :::warning NOTE If you run your own Commit-Boost instance, you **must** only register with the trusted relays listed above. Using untrusted relays may result in penalties from the Oracle DAO. ::: ## Checking Logs and Verifying Operation After enabling Commit-Boost, you can verify it's running correctly by checking the logs: ```bash rocketpool service logs commit-boost ``` You should see log output similar to this, showing successful validator registrations with the relays: ``` rocketpool_commit-boost | 2026-05-21T03:06:11.039761Z INFO : new request ua="nim-presto/0.0.3 (amd64/linux)" num_registrations=7 method=/eth/v1/builder/validators req_id=dcbb5e96-709b-4e0f-b336-cca37eb81d6b rocketpool_commit-boost | 2026-05-21T03:06:11.587846Z INFO : register validator successful method=/eth/v1/builder/validators req_id=dcbb5e96-709b-4e0f-b336-cca37eb81d6b rocketpool_commit-boost | 2026-05-21T03:06:11.587862Z INFO : Responded with 200 OK in 548 ms method=/eth/v1/builder/validators req_id=dcbb5e96-709b-4e0f-b336-cca37eb81d6b rocketpool_commit-boost | 2026-05-21T03:12:35.037766Z INFO : new request ua="nim-presto/0.0.3 (amd64/linux)" num_registrations=7 method=/eth/v1/builder/validators req_id=b47edad9-be4d-4a7f-b0d0-6c7ef4808629 rocketpool_commit-boost | 2026-05-21T03:12:35.642706Z INFO : register validator successful method=/eth/v1/builder/validators req_id=b47edad9-be4d-4a7f-b0d0-6c7ef4808629 rocketpool_commit-boost | 2026-05-21T03:12:35.642721Z INFO : Responded with 200 OK in 604 ms method=/eth/v1/builder/validators req_id=b47edad9-be4d-4a7f-b0d0-6c7ef4808629 ``` Key things to look for in the logs: - `new request` entries showing your Validator Client connecting to Commit-Boost - `register validator successful` confirming your validators are registered with the relays - `200 OK` responses indicating successful communication You can also verify Commit-Boost is running with: ```bash rocketpool service version ``` Near the end of the output, you should see: ``` MEV-Boost client: Disabled Commit-Boost client: Enabled (Local Mode) Image: ghcr.io/commit-boost/commit-boost: ``` If you use an externally-managed instance, it shows `Enabled (External Mode)` instead. ## Switching from MEV-Boost to Commit-Boost Switching from MEV-Boost to Commit-Boost is straightforward: 1. Run `rocketpool service config` 2. Select the **ePBS** category, then **MEV-Boost**, and uncheck `Enable MEV-Boost` 3. Go back to the **ePBS** category, select **Commit-Boost**, and check `Enable Commit-Boost` 4. Configure your relay preferences 5. Save and exit The Smart Node will handle the rest. Your Beacon Node will be updated automatically to use Commit-Boost instead of MEV-Boost. :::tip NOTE Switching restarts your Beacon Node, so your validators may miss an attestation or two while it comes back up. Avoid switching right before a scheduled proposal. ::: ## Additional Resources - [Official Commit-Boost Documentation](https://commit-boost.github.io/commit-boost-client/) - [Commit-Boost GitHub Repository](https://github.com/Commit-Boost/commit-boost-client) - [Understanding MEV and PBS](/node-staking/mev.md) --- url: /node-staking/config-docker.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Configuring the Smart Node Stack (Docker / Hybrid Mode) Running complete Execution layer and Consensus layer clients can be daunting; there are several options to choose from and each of them has a plethora of different settings. Luckily, the Smart Node is designed to hide all of that complexity so it's quick and easy to configure, while still giving you the freedom to customize everything if you so desire. In this section, we'll go over the various methods for configuring the Smart Node if you're using the **Docker-based setup** or a **Hybrid setup** where you connect to externally managed Execution or Consensus clients (e.g., clients you manage outside of the Smart Node for solo staking). ::: warning NOTE If you're using Native mode without Docker, please visit the [Native configuration guide](/node-staking/config-native.md) instead. ::: There are three ways to configure it: - Via the [Wizard UI](#configuring-via-the-wizard) - this is the easiest way. It only asks you a few basic questions and uses well-tested defaults for the test. This will be what you are presented with when you run `rocketpool service config` for the first time. - Via the [Settings Manager UI](#configuring-via-the-settings-manager) - this gives you access to all of the Smart Node's settings so you can customize everything as much as you want. - Headlessly via the [Command Line](#configuring-via-the-command-line) - this is an option for people who run the Smart Node in a headless (non-interactive) environment and need to configure it automatically. Choose which mode you'd like to learn more about from the list above, or simply scroll through each option below. ## Configuring via the Wizard To start the configuration process, run the following command: ```shell rocketpool service config ``` This will launch a terminal-based UI that will allow you to quickly and easily configure your node, as well as provide optional fine-grained control over every setting for advanced customization. ::: tip NOTE If you've already configured the Smart Node, you will instead be greeted with the [Settings Manager](#configuring-via-the-settings-manager). You can choose to re-open the Wizard from there if you prefer it, and all of your existing settings will be pre-selected for you. ::: When you run the config UI for the first time (or if you choose to run the Wizard again later), you will be presented with a screen that looks like this: ![](/static/image/tui-first-time.6aed10bb81.png) ::: tip TIP To use the Wizard, **press the `Arrow Keys` (up/down/left/right) to navigate between things such as buttons (choices) or text boxes**. You can also use `Tab` and `Shift+Tab` if you prefer - it will do the same thing. For buttons, **the one that's currently selected will be highlighted in green**. The ones in black are not selected. In the screenshot above, `Next` is currently selected and `Quit` is not. **Press `Enter` or `Space` to select a button**, analogous to clicking on it with the mouse. **Press `Escape` to go back to the previous dialog** if you changed your mind about something. This will come in handy as you progress through the various Wizard pages. **Hold `Ctrl` and press `C` at any time to exit the Wizard without saving anything**. For example, on the screen above, you could press the `left` and `right` arrow keys to move between the `Next` and `Quit` buttons. Pressing `Enter` while `Next` is selected will proceed to the next screen. Pressing `Enter` while `Quit` is selected will quit the Wizard without saving. ::: When you're ready to begin, press `Next`. ### Choosing a Network In the next screen, you will be asked to choose which network you want to use: ![](/static/image/tui-network.a56ca695c9.png) You can highlight the different choices with the `Up` and `Down` arrow keys (or `Tab` and `Shift+Tab`). When you change choices, the **Description** box on the right will show you a brief description of each option. This is true for all choice-based pages in the Wizard, not just the network selection, so you will see this style of page frequently. If you want to practice running a Rocket Pool node on the Hoodi test network with fake ETH and RPL you can get for free, select **Hoodi Testnet**. If you're ready to create a real Rocket Pool node on Mainnet to earn real rewards, select **Mainnet**. ::: tip NOTE Official networks (Mainnet, Hoodi Testnet, and Devnet) come from `networks-default.yml`. You can add or override networks in `~/.rocketpool/networks-extra.yml` without rebuilding Smart Node. See [Custom and override networks](/node-staking/advanced-config.md#custom-and-override-networks) for details. ::: ### Client Mode You will be presented with two options for client mode: ![](/static/image/tui-client-mode.d053419038.png) **Locally Managed** (also known as **"Docker Mode"**) is the default choice. Use it if you don't already have a client pair and you want the Smart Node to manage one for you. By choosing this, the Smart Node will create, configure and manage an Execution & Consensus Client pair as Docker containers. Don't worry, you'll get to choose _which_ client you want to run next. **Externally Managed** (also known as **"Hybrid Mode"**) is a convenient choice for users that already have an Execution & Consensus client pair running elsewhere that they manage manually. By choosing this, the Smart Node will simply connect to your existing clients and will not run one of its own. For example, users can use this to plug into the clients that they currently use for solo staking; that way, they don't need to have two separate copies of the clients. :::warning NOTE Since the Execution-Consensus Layer Merge, you _cannot_ mix and match these modes (e.g., you cannot have a local Execution client but an externally-managed Consensus client). You must either choose all locally-managed or all externally-managed. ::: ### Execution Client Setup Choose which mode you'd like to use for managing your Execution client and follow the steps in the corresponding tab below: **Locally Managed** If you want the Smart Node to manage an Execution client for you, the next screen will ask you to pick a client: ![](/static/image/tui-ec-selection.4c8afc9ccd.png)Please refer to the [Choosing your ETH clients](/node-staking/eth-clients.md#execution-clients) section for a description of each option. Once you've made your choice, click on the appropriate tab below to learn how to configure it: If you choose **Geth**, **Besu**, **Nethermind**, **Reth**, or **Erigon**, the Wizard will handle all of the configuration for you. You can manually adjust some of its parameters at the end of this process, but the defaults that it uses are completely appropriate for node operation. You can proceed to the next section. If you choose **Erigon**, also forward its **Torrent Port** (default **42069**, TCP and UDP) as well as P2P port **30303**, so snapshot sync and peering work. The Wizard still uses sensible defaults for everything else.

NOTE

**Open up the P2P port in your router's port forwarding setup**. Configure it to forward **port 30303** on both TCP and UDP to your machine's local IP address. This way, other Execution clients can discover it and communicate with it from the outside. This will help your Execution client sync quickly and improve performance (and thus rewards). Each router has a different way of doing this, so **you'll need to check out your router's manual on how to set up port forwarding**.

NOTE

Because the Smart Node will run in its own Docker container, it will use Docker's internal network. You won't be able to use hostnames like `localhost` or `127.0.0.1` here; if your Execution client is running on the same machine as the Smart Node, you will need to provide the machine's LAN IP address instead. And with that, your Execution client is all set! **External** For an externally managed Execution client, the next screen will prompt you for the URLs of its HTTP-based RPC (web3) API and its Websocket-based RPC API: ![](/static/image/tui-external-ec.eec1569b62.png)The Smart Node will use the HTTP URL to communicate with it and perform blockchain activities, such as querying the chain's state and submitting transactions. **If you don't already have your client's API port enabled and accessible from your Smart Node machine, you will need to set it up now.** Instructions on this vary from client to client; consult your client's documentation to learn how to set up the HTTP RPC endpoint. The Websocket URL is only relevant if you need it for your own usage; the Smart Node does not use it. You can leave it blank if you do not need it.

NOTE

Because the Smart Node will run in its own Docker container, it will use Docker's internal network. You won't be able to use hostnames like `localhost` or `127.0.0.1` here; if your fallback Execution client is running on the same machine as the Smart Node, you will need to provide the machine's LAN IP address instead. When you're happy with your fallback Execution client choices, proceed to the next step. ### Consensus Client Setup Now that you have an Execution client ready, the next task is to set up the Consensus client. The "mode" (local or external) will be inherited from the choice you used for your Execution client earlier. Choose which mode you selected earlier from the tabs below: **Locally Managed** If you want the Smart Node to manage a Consensus client for you, the next screen will ask you to pick a client: ![](/static/image/tui-local-cc.10454c4dc3.png)**The preferred choice** for the overall health and diversity of the network is the **Random (Recommended)** choice, which will randomly choose among one of the four supported Consensus clients for you. If you would prefer to choose an explicit client, please refer to the [Choosing your ETH clients](/node-staking/eth-clients.md#consensus-clients) section for a description of each option so you can make an educated decision.

NOTE

There are two conditions that will prompt you with warnings based on client selection: - The selected client is currently [a supermajority client](https://clientdiversity.org/), meaning that an unhealthy majority of validators on the Beacon Chain use it which threatens the stability of the network - The selected client is **too resource-heavy** for the hardware you're currently using If either of those cases is true for your chosen client, you will be warned and asked to choose a different client. You have the option of continuing to use the one you selected, but you must be aware of the risks in doing so. Once you've made your choice or have been assigned a random client, click on the appropriate tab below to learn how to configure it: **Lighthouse** The first option in Lighthouse's configuration will ask about your validator's **graffiti** message: ![](/static/image/tui-local-graffiti.2e7579a04c.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). Next up is an option to enable or disable **Checkpoint Sync**: ![](/static/image/tui-local-checkpoint.40bc50ca11.png)Lighthouse has the ability to instantly sync to the latest block on the Beacon Chain network by connecting to an existing Beacon Node that you trust. This is preferred over conventional syncing because it doesn't require any time (whereas conventional syncing can take days) and comes with some security benefits. Take a look at [their documentation on checkpoint syncing](https://lighthouse-book.sigmaprime.io/checkpoint-sync.html) for more information if you are curious. You can enter the URL of any Beacon Node that provides access to its REST API here. See [the section below on Checkpoint Syncing](#beacon-chain-checkpoint-syncing) if you'd like to use it. The final question will ask if you want to enable Doppelgänger Protection: ![](/static/image/tui-local-dd.a61e766403.png)Lighthouse supports a feature called [Doppelgänger Detection](https://lighthouse-book.sigmaprime.io/validator-doppelganger.html). In a nutshell, this feature will **intentionally** miss a few attestations after Lighthouse's Validator Client restarts; while doing this, it will listen to see if attestations are still being sent to the network using your validator keys. Ideally, there would not be any attestations (which means no other machine is running with your validator keys attached). After its short waiting period, Lighthouse would start validating normally. _However_, if there _is_ another machine running with your validator keys attached, then Lighthouse will immediately shut down and issue an error message in its log files. The reason for this is that if it were to start attesting as well, then you would start **double attesting** which is a **slashable offense**. When slashed, your validator would be forcibly exited from the Beacon chain and you would be penalized a significant amount of ETH. Most of the time, doppelgänger detection will result in nothing but a few missed attestations after a client restart. In situations where you are moving your validator to a new machine or you are changing to a new Beacon client, however, **doppelgänger detection can prevent you from being slashed by double attesting accidentally**. Think of it as cheap insurance for your minipools; you'll miss a trivial bit of profit every time you restart, but you can be fairly confident that you won't accidentally run your keys in two places and get slashed for it. Lighthouse also establishes P2P connections over the [QUIC protocol](https://en.wikipedia.org/wiki/QUIC), which the Smart Node always enables. It uses the **P2P QUIC Port** in the ETH2 settings (default 8001, UDP), so forward that port to your node in your router's port forwarding setup. Make sure to avoid collisions with ports already in use by your node (or fallback/testnet nodes). Also make sure the same port is open if you're using a firewall on your node (check `ufw status`). To check if the QUIC configuration is working you should see a 2-digit number after `libp2p_quic_peers` when running `docker run --network rocketpool_net curlimages/curl http://eth2:9100/metrics | grep libp2p_peers_multi`. **Nimbus** The first option in Nimbus's configuration will ask about your validator's **graffiti** message: ![](/static/image/tui-local-graffiti.2e7579a04c.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). Next up is an option to enable or disable **Checkpoint Sync**: ![](/static/image/tui-local-checkpoint.40bc50ca11.png)Nimbus has the ability to instantly sync to the latest block on the Beacon Chain network by connecting to an existing Beacon Node that you trust. This is preferred over conventional syncing because it doesn't require any time (whereas conventional syncing can take days) and comes with some security benefits. Take a look at [their documentation on checkpoint syncing](https://nimbus.guide/trusted-node-sync.html) for more information if you are curious. You can enter the URL of any Beacon Node that provides access to its REST API here. See [the section below on Checkpoint Syncing](#beacon-chain-checkpoint-syncing) if you'd like to use it. The final question will ask if you want to enable Doppelgänger Protection: ![](/static/image/tui-local-dd.a61e766403.png)Nimbus supports a feature called [Doppelgänger Protection](https://nimbus.guide/faq.html#why-does-my-validator-miss-two-epochs-of-attestations-after-restarting). In a nutshell, this feature will **intentionally** miss a few attestations after Nimbus restarts; while doing this, it will listen to see if attestations are still being sent to the network using your validator keys. Ideally, there would not be any attestations (which means no other machine is running with your validator keys attached). After its short waiting period, Nimbus would start validating normally. _However_, if there _is_ another machine running with your validator keys attached, then Nimbus will immediately shut down and issue an error message in its log files. The reason for this is that if it were to start attesting as well, then you would start **double attesting** which is a **slashable offense**. When slashed, your validator would be forcibly exited from the Beacon chain and you would be penalized a significant amount of ETH. Most of the time, doppelgänger detection will result in nothing but a few missed attestations after a client restart. In situations where you are moving your validator to a new machine or you are changing to a new Beacon client, however, **doppelgänger detection can prevent you from being slashed by double attesting accidentally**. Think of it as cheap insurance for your minipools; you'll miss a trivial bit of profit every time you restart, but you can be fairly confident that you won't accidentally run your keys in two places and get slashed for it. Nimbus supports P2P gossip over the [QUIC protocol](https://en.wikipedia.org/wiki/QUIC), which the Smart Node always enables. It uses the **P2P QUIC Port** under Nimbus settings (default **8001**, UDP), so forward that port to your node in your router's port-forwarding setup, and open it in the host firewall if you use one (`ufw status`). Avoid collisions with other nodes on the same machine (or fallback / testnet nodes). **Prysm** The first option in Prysm's configuration will ask about your validator's **graffiti** message: ![](/static/image/tui-local-graffiti.2e7579a04c.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). Next up is an option to enable or disable **Checkpoint Sync**: ![](/static/image/tui-local-checkpoint.40bc50ca11.png)Prysm has the ability to instantly sync to the latest block on the Beacon Chain network by connecting to an existing Beacon Node that you trust. This is preferred over conventional syncing because it doesn't require any time (whereas conventional syncing can take days) and comes with some security benefits. Take a look at [their documentation on checkpoint syncing](https://docs.prylabs.network/docs/prysm-usage/checkpoint-sync) for more information if you are curious. You can enter the URL of any Beacon Node that provides access to its REST API here. See [the section below on Checkpoint Syncing](#beacon-chain-checkpoint-syncing) if you'd like to use it. The final question will ask if you want to enable Doppelgänger Protection: ![](/static/image/tui-local-dd.a61e766403.png)Prysm supports a feature called Doppelgänger Protection. In a nutshell, this feature will **intentionally** miss a few attestations after Prysm's Validator Client restarts; while doing this, it will listen to see if attestations are still being sent to the network using your validator keys. Ideally, there would not be any attestations (which means no other machine is running with your validator keys attached). After its short waiting period, Prysm would start validating normally. _However_, if there _is_ another machine running with your validator keys attached, then Prysm will immediately shut down and issue an error message in its log files. The reason for this is that if it were to start attesting as well, then you would start **double attesting** which is a **slashable offense**. When slashed, your validator would be forcibly exited from the Beacon chain and you would be penalized a significant amount of ETH. Most of the time, doppelgänger detection will result in nothing but a few missed attestations after a client restart. In situations where you are moving your validator to a new machine or you are changing to a new Beacon client, however, **doppelgänger detection can prevent you from being slashed by double attesting accidentally**. Think of it as cheap insurance for your minipools; you'll miss a trivial bit of profit every time you restart, but you can be fairly confident that you won't accidentally run your keys in two places and get slashed for it. **Teku** The first option in Teku's configuration will ask about your validator's **graffiti** message: ![](/static/image/tui-local-graffiti.2e7579a04c.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). The final question is an option to enable or disable **Checkpoint Sync**: ![](/static/image/tui-local-checkpoint.40bc50ca11.png)Teku has the ability to instantly sync to the latest block on the Beacon Chain network by connecting to an existing Beacon Node that you trust. This is preferred over conventional syncing because it doesn't require any time (whereas conventional syncing can take days) and comes with some security benefits. Take a look at [their documentation on checkpoint syncing](https://docs.teku.consensys.net/en/latest/HowTo/Get-Started/Checkpoint-Start/) for more information if you are curious. You can enter the URL of any Beacon Node that provides access to its REST API here. See [the section below on Checkpoint Syncing](#beacon-chain-checkpoint-syncing) if you'd like to use it. **Lodestar** The first option in Lodestar's configuration will ask about your validator's **graffiti** message: ![](/static/image/tui-local-graffiti.2e7579a04c.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). Next up is an option to enable or disable **Checkpoint Sync**: ![](/static/image/tui-local-checkpoint.40bc50ca11.png)Lodestar has the ability to instantly sync to the latest block on the Beacon Chain network by connecting to an existing Beacon Node that you trust. This is preferred over conventional syncing because it doesn't require any time (whereas conventional syncing can take days) and comes with some security benefits. Take a look at [their documentation on checkpoint syncing](https://chainsafe.github.io/lodestar/run/beacon-management/starting-a-node#checkpoint-sync) for more information if you are curious. You can enter the URL of any Beacon Node that provides access to its REST API here. See [the section below on Checkpoint Syncing](#beacon-chain-checkpoint-syncing) if you'd like to use it. The final question will ask if you want to enable Doppelgänger Protection: ![](/static/image/tui-local-dd.a61e766403.png)Lodestar supports a feature called Doppelgänger Detection. In a nutshell, this feature will **intentionally** miss a few attestations after Lodestar's Validator Client restarts; while doing this, it will listen to see if attestations are still being sent to the network using your validator keys. Ideally, there would not be any attestations (which means no other machine is running with your validator keys attached). After its short waiting period, Lodestar would start validating normally. _However_, if there _is_ another machine running with your validator keys attached, then Lodestar will immediately shut down and issue an error message in its log files. The reason for this is that if it were to start attesting as well, then you would start **double attesting** which is a **slashable offense**. When slashed, your validator would be forcibly exited from the Beacon chain and you would be penalized a significant amount of ETH. Most of the time, doppelgänger detection will result in nothing but a few missed attestations after a client restart. In situations where you are moving your validator to a new machine or you are changing to a new Beacon client, however, **doppelgänger detection can prevent you from being slashed by double attesting accidentally**. Think of it as cheap insurance for your minipools; you'll miss a trivial bit of profit every time you restart, but you can be fairly confident that you won't accidentally run your keys in two places and get slashed for it.

NOTE

**Open up the P2P port in your router's port forwarding setup**. Configure it to forward **port 9001** on both TCP and UDP, and **port 8001** on UDP (used for P2P over QUIC), to your machine's local IP address. This way, other Consensus clients can discover it and communicate with it from the outside. This will help your Consensus client sync quickly and improve performance (and thus rewards). Each router has a different way of doing this, so **you'll need to check out your router's manual on how to set up port forwarding** **Externally Managed** Because each Consensus client has slightly different behavior, the Smart Node needs to know which one you're using externally so it can adapt its own behavior accordingly. Start by choosing which client you have from the list in the next screen: ![](/static/image/tui-external-cc.667fa98457.png)

NOTE

At this time, **Nimbus** is not compatible with External mode because it cannot run as a standalone Validator Container (VC) yet. When the client supports this feature, it will be added to the list here. Select your client from the tabs below to learn how to finish configuring it. **Lighthouse** Start by specifying the URL for your Lighthouse Beacon Node's API: ![](/static/image/tui-external-lh.3bcee5bbce.png)The Smart Node will use the HTTP URL to communicate with it and perform blockchain activities, such as querying the chain's state and submitting messages. **If you don't already have the API port enabled and accessible from your Smart Node machine, you will need to set it up now.** See [Lighthouse's documentation](https://lighthouse-book.sigmaprime.io/api-bn.html) for instructions on how to do this.

NOTE

Because the Smart Node will run in its own Docker container, it will use Docker's internal network. You won't be able to use hostnames like `localhost` or `127.0.0.1` here; if your client is running on the same machine as the Smart Node, you will need to provide the machine's LAN IP address instead. Next, it will ask about your validator's **graffiti** message: ![](/static/image/tui-external-graffiti.18aaa87487.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). The final question will ask if you want to enable Doppelgänger Protection: ![](/static/image/tui-external-dd.ec9ad6f568.png)Lighthouse supports a feature called [Doppelgänger Detection](https://lighthouse-book.sigmaprime.io/validator-doppelganger.html). In a nutshell, this feature will **intentionally** miss a few attestations after Lighthouse's Validator Client restarts; while doing this, it will listen to see if attestations are still being sent to the network using your validator keys. Ideally, there would not be any attestations (which means no other machine is running with your validator keys attached). After its short waiting period, Lighthouse would start validating normally. _However_, if there _is_ another machine running with your validator keys attached, then Lighthouse will immediately shut down and issue an error message in its log files. The reason for this is that if it were to start attesting as well, then you would start **double attesting** which is a **slashable offense**. When slashed, your validator would be forcibly exited from the Beacon chain and you would be penalized a significant amount of ETH. Most of the time, doppelgänger detection will result in nothing but a few missed attestations after a client restart. In situations where you are moving your validator to a new machine or you are changing to a new Beacon client, however, **doppelgänger detection can prevent you from being slashed by double attesting accidentally**. Think of it as cheap insurance for your minipools; you'll miss a trivial bit of profit every time you restart, but you can be fairly confident that you won't accidentally run your keys in two places and get slashed for it. **Prysm** Start by specifying the URL for your Prysm Beacon Node's API and the URL for its JSON-RPC API: ![](/static/image/tui-external-prysm.af45910cad.png)The Smart Node will use the HTTP URL to communicate with it and perform blockchain activities, such as querying the chain's state and submitting messages. It will prepare its Prysm Validator Client with the JSON-RPC URL so it can communicate with your Beacon Node, as _Prysm's Validator Client currently cannot work over the HTTP API._ **If you don't already have the API ports enabled and accessible from your Smart Node machine, you will need to set them up now.** See [Prysm's documentation](https://docs.prylabs.network/docs/prysm-usage/parameters) for instructions on how to do this. **You will need the `grpc-gateway` _and_ the `rpc-host` enabled.**

NOTE

Because the Smart Node will run in its own Docker container, it will use Docker's internal network. You won't be able to use hostnames like `localhost` or `127.0.0.1` here; if your client is running on the same machine as the Smart Node, you will need to provide the machine's LAN IP address instead. Next, it will ask about your validator's **graffiti** message: ![](/static/image/tui-external-graffiti.18aaa87487.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). The final question will ask if you want to enable Doppelgänger Protection: ![](/static/image/tui-external-dd.ec9ad6f568.png)Prysm supports a feature called Doppelgänger Protection. In a nutshell, this feature will **intentionally** miss a few attestations after Prysm's Validator Client restarts; while doing this, it will listen to see if attestations are still being sent to the network using your validator keys. Ideally, there would not be any attestations (which means no other machine is running with your validator keys attached). After its short waiting period, Prysm would start validating normally. _However_, if there _is_ another machine running with your validator keys attached, then Prysm will immediately shut down and issue an error message in its log files. The reason for this is that if it were to start attesting as well, then you would start **double attesting** which is a **slashable offense**. When slashed, your validator would be forcibly exited from the Beacon chain and you would be penalized a significant amount of ETH. Most of the time, doppelgänger detection will result in nothing but a few missed attestations after a client restart. In situations where you are moving your validator to a new machine or you are changing to a new Beacon client, however, **doppelgänger detection can prevent you from being slashed by double attesting accidentally**. Think of it as cheap insurance for your minipools; you'll miss a trivial bit of profit every time you restart, but you can be fairly confident that you won't accidentally run your keys in two places and get slashed for it. **Teku** Start by specifying the URL for your Teku Beacon Node's API: ![](/static/image/tui-external-teku.35c1ccfc9b.png)The Smart Node will use the HTTP URL to communicate with it and perform blockchain activities, such as querying the chain's state and submitting messages. **If you don't already have the API port enabled and accessible from your Smart Node machine, you will need to set it up now.** See [Teku's documentation](https://docs.teku.consensys.net/en/latest/Reference/CLI/CLI-Syntax/#rest-api-enabled) for instructions on how to do this.

NOTE

Because the Smart Node will run in its own Docker container, it will use Docker's internal network. You won't be able to use hostnames like `localhost` or `127.0.0.1` here; if your client is running on the same machine as the Smart Node, you will need to provide the machine's LAN IP address instead. Next, it will ask about your validator's **graffiti** message: ![](/static/image/tui-external-graffiti.18aaa87487.png)This is an optional custom message you can attach to any blocks you propose on the Beacon Chain. The message will be preserved forever, so think of it like a fun little way to leave your mark! **Note the maximum length of the graffiti is 16 characters.** If you'd like to see some examples of what validators are using for Graffiti today, [take a look here](https://beaconcha.in/blocks). #### Beacon Chain Checkpoint Syncing **Checkpoint syncing** is a very useful technique that some Beacon Chain clients support. It allows your Beacon client to instantly sync the entire Beacon chain without having to start from the beginning and catch up on every block. This means instead of taking **days**, your Beacon client can be ready in a matter of **minutes**. All it needs is access to an existing Beacon client that you trust. You can use any Beacon node that provides access to its HTTP API. Currently, many node operators are using the checkpoint-sync-endpoints - a service that allows Rocket Pool node operators to checkpoint sync easily. Both the Hoodi Testnet and Mainnet are supported. A list of checkpoint sync urls can be found via the following link: - [Checkpoint Sync Urls](https://eth-clients.github.io/checkpoint-sync-endpoints/) Choose a relevant checkpoint sync url and paste in the terminal during `rocketpool service config` when it prompts you for a Checkpoint Sync Provider. After that, your Beacon node will automatically connect to the checkpoint sync node when it first starts up and instantly pull down the latest state of the chain! ::: warning NOTE Checkpoint Sync will only occur if you _don't have any Beacon Chain data yet_. In other words, if you start syncing normally and decide to checkpoint sync later, you will have to remove your chain data first in order for checkpoint sync to work. This can easily be done with the following command: ```shell rocketpool service resync-eth2 ``` ::: ### Fallback Node Starting with 1.5.0 of the Smart Node stack, you can provide a "fallback" Execution client and Consensus client pair that can take over for your primary clients if they ever go offline (such as because you use Geth and need to prune it). In this situation, your primary node machine will still be responsible for attesting and proposing blocks with your minipools' validator keys, but it will connect to an external machine to interact with the Execution layer and Beacon chains. [To learn more about fall back nodes, see this section](/node-staking/fallback.md) and return here when you're done. ### Metrics Configuration Rocket Pool comes with the ability to display a detailed dashboard showing metrics about your node's hardware health, system updates, your validator performance, your rewards, information about the overall Rocket Pool network, and more: ![](/static/image/nimbus-dashboard.518741bcdb.png) The next question in the Wizard will ask you if you want to enable this: ![](/static/image/tui-metrics.e752a11861.png) If you choose to enable it, you will learn more about setting it up and how to use it in the [Setting up the Grafana Dashboard](/node-staking/grafana.md) section later in the process. ::: warning NOTE All of the data collected by this system **stays on your machine**. Rocket Pool does not collect any of the telemetry or send it to a separate service. It's purely there for you to use so you can monitor your own node! ::: ### MEV Configuration Since the Merge of the Execution and Consensus layers in September 2022, Ethereum validators now have the ability to earn priority fees and participate in Maximal Extractable Value (or MEV for short). Starting with Smart Node v1.7.0, MEV is now _opt-out_ so its configuration is presented as part of the initial setup, as you see in the next screen: ![](/static/image/tui-mev-mode.d793e5590e.png) [Please read our MEV guide to learn more about MEV, its configuration, and what to do in this section of the wizard.](/node-staking/mev.md) Return here when you're finished. ### Completion After this question, you've finished setting up the Smart Node! You will see the following dialog: ![](/static/image/tui-finished.42115de95c.png) If you're happy with your setup and are ready to start the Smart Node, click `Save and Exit` here and go to the [Securing your Node](/node-staking/securing-your-node.md) section next. If you would like to review all of the settings and customize many additional settings that weren't included in the Wizard, click `Review All Settings` and go to the [next section](#configuring-via-the-settings-manager). ## Configuring via the Settings Manager If you've already run `rocketpool service config`, instead of being greeted by the Wizard, you will see the **Settings Manager** screen: ![](/static/image/tui-settings-manager.42402b0b5a.png) There are three main features of this screen: 1. The **Category List**, which lets you drill down into the settings for each category of the Smart Node stack 2. The **Review Changes and Save** button, which you can use when you're ready to see what settings you've changed and save the updated configuration 3. The **Open the Config Wizard** button, which will bring you to the [Setup Wizard](#configuring-via-the-wizard) if you prefer that interface instead ::: tip TIP To use the Settings Manager, **press the `Arrow Keys` (up/down/left/right) to navigate between options in the home page**. Press `Tab` to go **between the category list (1) and the buttons (2 and 3)** at the bottom of the screen. The button that's currently selected will be **highlighted in green**. **Press `Enter` or `Space` to select a button**, analogous to clicking on it with the mouse. **Hold `Ctrl` and press `C` at any time to exit the Settings Manager without saving anything**. ::: As you scroll through the categories list, each option will have a helpful description appear in the **Description Box** to the right of the screen. Feel free to explore them; nothing you do will be saved until you go through the Review dialog via the **Review Changes and Save** button, and you can press **Ctrl+C** at any time to exit without saving, so you won't accidentally mess something up by playing with the settings here. ### Configuring the Settings From the home screen, select any one of the categories with the `Enter` key to view the settings for that category. For example, here is the screen for the **Smart Node and TX Fees** category: ![](/static/image/tui-smartnode.2748ca094b.png) Use the `Arrow Keys` to move up and down between the settings. The currently selected one will have a white square at the end of it (if it's a text box or a check box), or will be highlighted in white (if it's a drop down). Press `Escape` to go back to the home screen of the Settings Manager when you're done. As you scroll through the settings, each one will show a brief description of what it does in the **Description Box** on the right. It will also show the **default value** there in case you want to revert it to its stock setting. In this example, the **RPL Claim Gas Threshold** setting is currently selected (highlighted with a green box on the left-hand side of the screen). It has been changed to `40`, but you can see that it has a default of `150` in the top-right corner (the top of the **Description Box**). ::: tip TIP As a reminder, nothing will be saved to disk until you go through the Review dialog via the **Review Changes and Save** button. You are encouraged to explore all of the settings to learn about them and see what your Smart Node can do! ::: ### The Setting Types and How to Use Them The settings manager uses the following setting types and UI elements: #### Text Boxes Text boxes are used to enter arbitrary strings of text or numbers. They look like this: ![](/static/image/tui-textbox.f99e293310.png) Enter your desired values into them, then **press `Enter` or use the `Arrow Keys` to navigate to a different setting in order to preserve your changes.** If you don't, the Settings Manager will assume you're still updating that setting and won't mark it as changed yet. #### Drop Downs Drop downs are used to select an option from a list of choices. They look like this (when they're open): ![](/static/image/tui-dropdown-open.d5dc147082.png) The **green** item is the one that is currently selected. Use the `Arrow Keys` to change options - as you do, the **Description Box** on the right will update to tell you more about the currently selected option. When you're happy with your choice, press `Enter` to choose the selected option and the drop down will close, revealing the option that is currently selected: ![](/static/image/tui-dropdown-closed.c9f39e80ae.png) #### Check Boxes Check boxes are used for simple Yes/No questions. They look like this: ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPAAAAAgCAIAAACjCWLqAAABg2lDQ1BJQ0MgcHJvZmlsZQAAKJF9kT1Iw0AcxV/TSkUqgnYo4pChOlkQFXHUKhShQqgVWnUwufQLmhiSFBdHwbXg4Mdi1cHFWVcHV0EQ/ABxdHJSdJES/5cUWsR4cNyPd/ced+8AoVFlmhUaAzTdNjOppJjLr4jhVwQRQz9CEGRmGbOSlIbv+LpHgK93CZ7lf+7P0asWLAYEROIZZpg28Trx1KZtcN4njrKyrBKfE4+adEHiR64rHr9xLrks8Myomc3MEUeJxVIHKx3MyqZGPEkcVzWd8oWcxyrnLc5atcZa9+QvjBT05SWu0xxCCgtYhAQRCmqooAobCVp1UixkaD/p4x90/RK5FHJVwMgxjw1okF0/+B/87tYqTox7SZEk0PXiOB/DQHgXaNYd5/vYcZonQPAZuNLb/o0GMP1Jer2txY+Avm3g4rqtKXvA5Q4QezJkU3alIE2hWATez+ib8sDALdCz6vXW2sfpA5ClrtI3wMEhMFKi7DWfd3d39vbvmVZ/P+79cnJWu3nHAAAACXBIWXMAAC4jAAAuIwF4pT92AAAAB3RJTUUH5gMZAzY2IpiKTwAAABl0RVh0Q29tbWVudABDcmVhdGVkIHdpdGggR0lNUFeBDhcAAApFSURBVHja7ZtpVJPXFoZ3JgIBAwQIyCRJRBkEqxigjKFItYq3aCFOF+WCtDUd1NpaahetSm2p1F60igqltQ6I0cqyiq0oQ6CAioBCmASCgLACISGEKQwh9wcUq/2CpEtdbe95/uWsL+c9e3/v2mefsxJcWJgaEIh/CniUAgQyNAKBDI1AIEMjEMjQCGRoBAIZGoFAhkYgniFElALEXxM+H2OQy0UV+p/AiL6R3Eh/5P9S/e/ccliExPD5XD6fy09PZE85CGaX4vnc1OjKPytVsjWdy4+9pv+3eEuEW7zk15N5NwjPN/PPTf0ZGlqXE8/nc7d7q56GaSapfPM4dyJffC6fz01ccx/zuZ6ysKSkKMGDJw8+RzMVfsB/ZPFxy6XPTs17O5fP38vRfdZRDbKWHN19MOp0Wnjqgd0rWM8wyX82ojFh3EIizjzySi8AwIOjARTcjFdSlX+hHloxR1DMGF+QvJ6KneYWt7yWfpJvqr/lEwafN13O10utVQAAIL6v+7zVVd4JXO+nOJ9JQOInUeW6/VYVZZY6s4RMMxi8oTnJT1t9mqV23vv7o5Jf+vaD+C1LYpp37sobdolL+E/Fnqdk6BnOF3gRV50s+3CDtLab6+JTXuwBINsINkRmuDO7QW53K2PTiTyboak8sYifGiJ5+Ll//uqD6/waLI2GRhQza3LCU865yrWN2kC4Pu6bpdYkkSDiwA9smVrDnATpgte+W+NfbUnFy0Repw9G3XpYZHvc39653W+oPHl3wnUrlSahNp8TqYGT5YFge+Hz+HSbxg1bYl+hbdwat7y39PDXXwpo2An5o7oyO/b7Y85F761J9LQJ274/rP/Sx0fT6PvPbLkJAAB3eSe4PCDnfH7y6J0RTsx63sLxLumdtQm+4yskWws2bLrgwZCPShwFp6P55SYqKNmanuDV6PuzquolO1VLNi/+hwW9GoIJXFGup2ac/WTvj61EIEhNDDR2z9jqGGFiqA94Y0Y07ZerF7Bn74ozG/+77a329lMd1tEnt8/Db3xKPXRjCC99oY5z2qF3Uvj+LWqlDgCQhREfH15sRcs/x80Vdy3mxa91nPLcYFqyNjolOjolOvrsIhMAGLCbK+m8teJEctTVVgU7LJHrOqa1nz1zHNq8b3f1Oi47FO4+qGFOtU3Ivg9Db9Nki37ODKhVtTBpkxMMzV4d/67fQNWJ2P1TuBkArAsiJhZ/2ZEMqpZXD59nwdwMbtDltS939JdvTBbQNCRkCvVHt9j6pUlJvGuNAGCTk8JLSno9twUACLWZvKQjQU2/f5RU8++dh4PsKKW/vNxArFy5IyHY8rffADNFur+uvdaitF+eHmCuIRZyA8sKQOSV30oEAFCZSHs09lsY6lO890fVNUSkBebhCR+6jeQeO15n8MrePUF6T+/abpRIBByxh6ZLriv5V0GWDgDgXHP9aFB7MvpCLhVKwOGbH3x9ao/XuGicg1rvE1Q/vs7ea6tvS42u7ku4qCTgSUM68sagF7IYDAlUmGsXcXVowtElCls95lfnXV0b4KYD1pwD/gFNeHnggT1vCEcAQEWYPN2wzm9zGejL2bnv8qwnnOFNql8KqgYAAKf76cE1Q4SWi7wf3T/kbkrDKecfSQ7o1pgQAwx1rJ5F3emc1wkjbklBLFptASdvYjvAiys5YgKJvfkaY/JRp3x/U2g4te3IT3Rc2eiRuEyOb8vFs+OVJzA9yx9Puh4854E5HaADKxbKAAUHoKAqprHv/1FdQ5gY6upKzIi0ATc3MsI7tlRAWRa5enrWeNzQY2N4rJG5l75dZheZHbL5i5VqveZs3ufJHmM0GQnAMXzL9+GTNw8SMoDGrkO07q2Y37UcBIlH+LFQrwa6/ghufO/XGdY2XmUnXQEAHeZigBeoChz2nFITE4C6Wc0TniWoJksxZRQGCDTXEhb5haqhKZXuvrFhb+Ajb0Rlkyew5zJrhio4N6QAAFTshAxpVP+zUEykuoDr6KADgFps0Qkwiyb77cChNwigqyIAjBI03UoMUAYAgKqgAki0V9cQ5ozpqmt3YVjy1cF8NUB/xtdHRaFbmNobelhuNAhgYiIFoBPMJMYAcrkRAHSVRHxasp5qU+u/7lD44rSgXzzOyWijgGvM+Ci9gjTx5T7L0Wkvlex55s2gmr67YYmZTnLLKzERJZMXLUolDvBDZBLAw7KJOQi6pl0GAH1mEjpAn4Kqgz2niVQKMLPVlghVowAwhsfjx8a7mwbuR6e6Ptl1NXJl4I50pnZOMyyMDK1R9uvreJxe77Lw20o9BXZC5Bjqo0QVAI6gwgHo6Q0+Wj5wAIDDTaU8IKMpQU2nSwDMcBZiOoBMRgPonO7Kh1iiNljALPaxCs5oIwCh29jAuLtHY5IfP9tjh9mg8bZiGhFp7HQPbTtUb/jaZ5tbd3+xJ4a/gc/V2tDQ6FI5eN2dG/epva3u3FJjMC0UWgA0hbz/E6XGtalLhwh4AJ3hYVALfQu7C3z9LrkPLewYGTRjlpvVba1qnv5uogaAPjGz6YGBI0f0u/aI0NZmDuyqZRFXdOop0nved9tJGIPjGXf68b3ILol9lhXoFVXOBuJVrDnt8vPsgrnX340dyxFSDefU9fB3na2fqGeK6tD0UsFbK1KX5n2WKcZN2UOLJm45itddEo76bPqOrc9I+2iD2Y7dQW+eKn4vugo7IZjqZpJewM0tDPaWO7zYBfCwre7uNgYQ+ay6Bm267RW+dcpmtnuTPq7eFABMa/w4KnW/3a07fgXSnKBVX2/Wn0fxyKKpGKd/tdXC0GCdfXn+8jfurtmzw0FoSbKr7Dlz/MANrMzL2zHUtXzvj0ckm/YyZed2xBWCx74vP94i7jrrkxjzWdGrAOQn3LI6O+96tMhb191Xz2SIZtu3Uvrtbp3fnFZsOgLD9Pl5izn5Af437fVMyy9EnSk1HR21EFbS9Rl32Z7FbOdmY5V1WaFXrUQHS6VzUUg+o8/lynWHgckdu22WzKxxvtfVZf61Y+1mxnYdyuolWdWGAND9wEJ/dtU8t2IvjxLj1uX5IjLGoPj+4uUVpJtLyyzzAqxJjTnRyZl2vQ+w5+ypW9CE77R3KnebL6L2OebnurUNtnuGFtlI3C7mOzU0g/tSgftMU8GvDIw2D9/qHXrTiiJhsEQslojFEuneX1pm9n1MqKg/++2D2S73+kQvcwpdKE45Ja53sBKCpW4q7m1zWXjHbQ6pshbmzBq9lxNcIQMAkHbMsJhT67SoyMvzDlSsuj2WvT32+GK2yBgAjEVsdgnb1kjwM+dGhSmVVcl2rzLud8o69vaFOn01tHuGFtl0LsooYBJn561Y0N1UsOq2WEONb3IT9iqsGI0O9m0G/cziXM69bsBIcl8BhnpmYBFGmBJN6o9HJJ6mnYdnlq3ckWf4ztmTa23Jtu5WwpTkU6WGNoZeOlPXSfQnWcRfE/RbDgQCGRrxzwK1HAhUoREIZGgEAhkagUCGRiBDIxDI0AgEMjQC8Sz5HzHpqShKad+YAAAAAElFTkSuQmCC) When they are checked, they will have an `X` in the middle as you see above. When they are _unchecked_, they will simply be blank like this: ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOgAAAAkCAIAAAAM4eHgAAABg2lDQ1BJQ0MgcHJvZmlsZQAAKJF9kT1Iw0AcxV/TSkUqgnYo4pChOlkQFXHUKhShQqgVWnUwufQLmhiSFBdHwbXg4Mdi1cHFWVcHV0EQ/ABxdHJSdJES/5cUWsR4cNyPd/ced+8AoVFlmhUaAzTdNjOppJjLr4jhVwQRQz9CEGRmGbOSlIbv+LpHgK93CZ7lf+7P0asWLAYEROIZZpg28Trx1KZtcN4njrKyrBKfE4+adEHiR64rHr9xLrks8Myomc3MEUeJxVIHKx3MyqZGPEkcVzWd8oWcxyrnLc5atcZa9+QvjBT05SWu0xxCCgtYhAQRCmqooAobCVp1UixkaD/p4x90/RK5FHJVwMgxjw1okF0/+B/87tYqTox7SZEk0PXiOB/DQHgXaNYd5/vYcZonQPAZuNLb/o0GMP1Jer2txY+Avm3g4rqtKXvA5Q4QezJkU3alIE2hWATez+ib8sDALdCz6vXW2sfpA5ClrtI3wMEhMFKi7DWfd3d39vbvmVZ/P+79cnJWu3nHAAAACXBIWXMAAC4jAAAuIwF4pT92AAAAB3RJTUUH5gMZAzk2pQCWgAAAABl0RVh0Q29tbWVudABDcmVhdGVkIHdpdGggR0lNUFeBDhcAAAmjSURBVHja7ZtpVJNnFsdvEsISMEI2kEUSAshSQMUABdkElBHsoANxGyhHpWpqq9UZ63JQW1uHkbFHraJCrYqKGBXHIlr2TUSMgrIjEBSEA4RACFuQhMwHFEXfUOkoPZ4+v295zpv7f+59/+fmPu95gwsJUQIC8aGBRyVAIOMiEMi4CAQyLgIZF4FAxkUgkHERyLgIBDIuAvGuUUMlQPzh8PkYi1wu6rgfPEPauhJd7aE/pfqHYFyDoG18PpfP5/ITD3LGXQR6chSfezKi7PdKCTYlcvmR6dofhG8Jd3mxn8Xy7hAmt/KTpv4ORgVNr6h4XnHRoQsHCghAT446epaeHrk6zu7/Uylbd3rvPNLLzy1J+zclMt+8rrs4JEbSYfvJSU/D31icRNMU/PPCoVfvZc2ZY5Ep1Pek5raFu9HZISZsZ47svWY1wF5wJixAYE57JhOZ//fw7oz3VuT3lNEkzrhSy9xC1sjmJbVk7HI2OuY09hHdx5QPc3Gy6bDNuG+sAACA1seak62ucIvmur3DeFTvg7tWl2j2GZUWG6qblpvRYeCO6iK/a/VJNe4U2yReeKqNYS9ugNJctCIq7uNuAA2T3LBVV53MukDCvHt1TXyOyeB4934O/2SQ6OXnPoelh1d41BnqDg5Jp1VlhcZdspdMdPs65Sv3/uhvTBTmhh86w+lUqohJEM/628/LPCsNyfhOoev5w6vvil82dKcNO7Z4DJbEfhOdYaRQJdQ8N/6kz2jLIExP2heVaFIftjHyL5RPN+0N6Ll/9Id/51KwC/Kmuiwz8tQJ29ublx10MQnZciCkL3nn8QTGgQsbiwAA4CEvnssDjax9Z48/GPLatpI3e2S6+WJ5tPvIDjWMc8PWJDmzJHKRde75CH4JVQGCTYnRrvXuNxUV85iKxkxe1JlZPSqS8VlUoqVkXdz1/ZUmNSCIqToqp1tsdYw0MdT73TAzmtQZtz6Ilzhb3TbhyBdxfM9GpUwdADTKw3ce9TWi5F3iZrd2+PKilluPO7/TBMsj4iIi4iIiLs6hAkA/c4ao/e6i+NjVqU1STshBrv3whH3rkmXV7Havo8d64ZFQpwEVMZUmQfu/Dr5H6ZxzM8W7WtFoRhkNMGi+NOpLj/6K+MgD47gWAIzzw59v/rq1Biga/3r0MhtmXOX6XV8+v62v5NPYXIqKgoyjPobhWv+YGF56PQCYZMXxYmI+y24EAEJ1Ci/mmF/Dq5cSq/6+46gfk3T/1/l1amWLt0YHGr54qdpMqHlreXqjzCIg0VtfRS4adWwjAKFrXpMaAICCKu5WOSdhqI9z38eqq8hoUjuuXE0NcGrdFE2NGsEn+WnqAICzz/agQPXZiKRsMgjA6scz7nOrT1epnobJtXP9agEAQL8nfek9sW7q/uhrMgKeOKguqfebmcZiiaBUf2LbrwyOPr5AOl3L7D+X7e3roMgKK2a/p3cDXuJz6Nu15UMAoCCMnjLYl7+y6+/N2rH/uulvnJmplfP8KgEAwOZxYmDVIKHxGu+K09fcNQk4mcOxWO8ulQXRwVDHmjWU7bY57TDkGOPHplTne72YCPGtZV6tBCJnfTpr9FKbPE8a1J376tgvDFyx/NjeFC/3xmsXRzqMT2KaJ56YEWj5VJ8B0IaVC6mfhAOQkqVv0dfeVFeRJoa6sgwzo/dj3OFhPNbKjOSfFjJXZQat/9dipdaTTN6+WOdhSicRwDp046nQ0ZO+SANA5bQgXPH5tldGBYLIOfREsGsdQ3sIN/Kbrf5soruXtTOkANCm3wowkyzFYccUU6kANaZPnnuToBhtrSQ59BMo9gK2xsyKwXGVHq4N+95nTOUVJjm5FlyzqsFSrztiAAAydkEGVar/XkhUsSbg2toYAKBsNWgHMKV0vjgQaA0AaCoIAHKCqqcA/aR+ACBLyQCiiaurSHPK26q/J+M+k+gOAFCpYgAGgS7SA5BIdAGgQxC+W7CSbFLtueJIqG+C36/OlzopcsDVX92eWEp8/uVeQ/lbC2u4XFjnV9X7MORgio3E8Ma2cMHogw2ZDAf4QQ0iwMs2iLkImrQOHYBeuogB0Cslq2PHpIrFANOapqtBhRwAhvF4/PDIVFLH3X6uY9ee1FWLfbYmmk3MUVMLVgVXyfq01Z3Pr7Sb/VOZlhS7IBIMdbmaAgBHUOAAtLQGxrYJHADgcOMp93dSZKBkMEQAdJxBKwOgs5MC0P62Ox9kC5thllnhXKPAq80EIHTp6eh1dass8utnbOw061Rd/zYZvYtRod6ubCDDibt3t8V0zRn39YBWUG4A0BD0j19IVfYNHepqgAdQf/YMlOXuBV357h7JToOz24YG6GYl9JpNFU/eWhmnBIDeVrOGpzrWXkKtV+aq5mZ94FQsDL+hXksSP3J72ELEWByprM2Vzas6RBZpRqB1u8wc1FKxYjLzcpiB3IwvI4ezyslTLWu6+Xsu1j7vT9LK4MT7uZ8vOumf811KK27cGVf4/KlC4YrkcvncNT9ztFkJ28PoW7/xW3eucHNEBXZBMNXpoh7AzSgIdJNYfdwB8HLs7erSAxDOXZIOzZotpe41siccpwZtXC0NAGhVHl4KZR/z7gOPfHGW35If1mt/RHJOoyhY529Nn4BxwTjzukPA2ofLvt1qVW5IZJZ1Xzh96A5W5SUtGOoTvO+vZ9T5jp5S2truGXuONK55rJzGEppbNJH6mHcvr08opA3BM4ZDjq9XnrdnkYUWrSRp9YX7NLncoLyMoc16yHEp5Ng+0VMYFxe4VovUsVTa5wTlsXrtbmRY9Y/+0jabdtLrHVxTF3pWD7fQ9ZhtssoFaZVTAaDrqYG2ecVHjoWuzgK9poA8oQbGYutj34BSYpF/sWGOtzGxPisiNoXZ8xQ7ZnfNrAZ8u4VNiaODkNxrnZft2DzQ4hJ820TkeC3Ppu4JOPnnOk2j5d5iYYxh+Ca34CIjkojFFrLZQjZbqPnYv5h+aluwsC9zw+FMu0e9wvleBXYkmyyB/QOsgmCp01p7mu1mP3C0JJZVg6Wp/FFWYGknAIC4bYqBZbXNnNuuLg+gdMm94cwtkad9OUI9ANATcjgCznTd3Jted0ppZHYZx6lCr88m7cSGpBptJbS4BN82aZ9zNd9MzTxn0ayuhvwl91pV9OwGx/IeqRGr3sqiWafPrDDb61EXYBS5Nx9DPcXnNkaaIlXqr2eEtaWQEIzFS5fG7XvoX76IPxz0rgLizwIyLuKDBI0KCNRxEQhkXAQCGReBjItAIOMiEMi4CGRcBAIZF4FAxkUgkHERHyz/AwOfWpJv0c3yAAAAAElFTkSuQmCC) To change the setting, simply select it and press `Enter`. ### Saving Changes When you're happy with your changes and you'd like to review them before saving, press the **Review Changes and Save** button on the home screen. As a reminder, to get to it, press the `Tab` key. You will be presented with a view that looks like this: ![](/static/image/tui-review.c54d1707e4.png) The **Review Box** here will present all of the settings you've changed, showing the old values and the new ones. For example, the first line here shows that the **RPL Claim Gas Threshold** used to be `150`, and it's been changed to `40`. It will also show you which containers are affected by the settings you've modified and will offer to restart them for you after you've saved your changes. ::: tip NOTE At this point, your changes **still haven't been saved yet**. If you want to go back and modify something, press `Escape` to return to the home screen. ::: When you are satisfied with the changes, press `Enter` to save the new configuration to disk. You will then exit the Terminal UI and be presented with something like this message: ``` Your changes have been saved! The following containers must be restarted for the changes to take effect: rocketpool_watchtower rocketpool_validator rocketpool_eth2 rocketpool_node Would you like to restart them automatically now? [y/n] ``` Press `y` and `Enter` if you want to automatically apply your new configuration changes and restart the affected containers. Press `n` and `Enter` if you have other things you want to do before restarting them, and will do it manually later. In either case, your configuration is done! ::: tip NOTE You may see an error message like the one below: ``` 2022/08/13 13:49:41 Error piping stdout: read |0: file already closed ``` This is not actually an error, it's simply a cosmetic glitch. You can safely ignore it. ::: ::: tip NOTE If you are running Mac OS, you may see an issue complaining about node_exporter. You will need to run these commands to fix. ```shell rocketpool service stop nano ~/.rocketpool/override/exporter.yml ``` Replace the entire contents of the file with: ``` # Enter your own customizations for the node exporter container here. These changes will persist after upgrades, so you only need to do them once. # # See https://docs.docker.com/compose/extends/#adding-and-overriding-configuration # for more information on overriding specific parameters of docker-compose files. version: "3.7" services: node-exporter: x-rp-comment: Add your customizations below this line volumes: ["/proc:/host/proc:ro","/sys:/host/sys:ro"] ``` then finally `rocketpool service start`. ::: ## Configuring via the Command Line If you use the Smart Node in a headless environment where you can't interact with the Terminal UI, you can configure your node via the command line instead. The `rocketpool service config` command accepts, as arguments, every setting that can normally be configured via the Terminal UI. Run the following command to see a list of them (note that it's quite long): ```shell rocketpool service config --help ``` The output will look like this: ``` NAME: rocketpool service config - Configure the Rocket Pool service USAGE: rocketpool service config OPTIONS: --executionClientMode value Choose which mode to use for your Execution client - locally managed (Docker Mode), or externally managed (Hybrid Mode). Type: choice Options: local, external (default: "local") --executionClient value Select which Execution client you would like to run. Type: choice Options: geth, infura, pocket (default: "geth") --useFallbackExecutionClient Enable this if you would like to specify a fallback Execution client, which will temporarily be used by the Smartnode and your Consensus client if your primary Execution client ever goes offline. Type: bool ... ``` Each option will have its name, its type, its default value, and (if it's a choice parameter) its options. Using this text, you can find the option(s) you want to set and specify them via the appropriate arguments. ::: tip NOTE This command builds on top of your existing configuration, so if you have some settings already saved and just want to modify others, you don't need to repeat them. It will only update settings that you include as arguments to this command. ::: ## Next Steps Once you've configured your node just the way you want it, you're ready to secure your operating system to protect your node. Move on to the [Securing your Node](/node-staking/securing-your-node.md) section next. --- url: /node-staking/config-native.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Configuring the Smart Node Stack (Native Mode) In this section, we'll go over the various methods for configuring the Smart Node if you're using the **Native setup** that doesn't use Docker at all. ::: warning NOTE If you're using a Docker-based setup, please visit the [Docker configuration guide](/node-staking/config-docker.md) instead. ::: There are three ways to configure it: - Via the [Wizard UI](#configuring-via-the-wizard) - this is the easiest way. It only asks you a few basic question and uses well-tested defaults for the test. This will be what you are presented with when you run `rocketpool service config` for the first time. - Via the [Settings Manager UI](#configuring-via-the-settings-manager) - this gives you access to all of the Smart Node's settings so you can customize everything as much as you want. - Headlessly via the [Command Line](#configuring-via-the-command-line) - this is an option for people who run the Smart Node in a headless (non-interactive) environment and need to configure it automatically. Choose which mode you'd like to learn more about from the list above, or simply scroll through each option below. ## Configuring via the Wizard To configure the Smart Node, run the configuration command: ```shell rp service config ``` This will launch a terminal-based UI that will allow you to quickly and easily configure your node, as well as provide optional fine-grained control over the settings that are relevant to Native mode. ::: tip NOTE If you've already configured the Smart Node, you will instead be greeted with the [Settings Manager](#configuring-via-the-settings-manager). You can choose to re-open the Wizard from there if you prefer it, and all of your existing settings will be pre-selected for you. ::: When you run the config UI for the first time (or if you choose to run the Wizard again later), you will be presented with a screen that looks like this: ![](/static/image/tui-native-welcome.e0ccb7b05e.png) ::: tip TIP To use the Wizard, **press the `Arrow Keys` (up/down/left/right) to navigate between things such as buttons (choices) or text boxes**. You can also use `Tab` and `Shift+Tab` if you prefer - it will do the same thing. For buttons, **the one that's currently selected will be highlighted in green**. The ones in black are not selected. In the screenshot above, `Next` is currently selected and `Quit` is not. **Press `Enter` or `Space` to select a button**, analogous to clicking on it with the mouse. **Press `Escape` to go back to the previous dialog** if you changed your mind about something. This will come in handy as you progress through the various Wizard pages. **Hold `Ctrl` and press `C` at any time to exit the Wizard without saving anything**. For example, on the screen above, you could press the `left` and `right` arrow keys to move between the `Next` and `Quit` buttons. Pressing `Enter` while `Next` is selected will proceed to the next screen. Pressing `Enter` while `Quit` is selected will quit the Wizard without saving. ::: When you're ready to begin, press `Next`. ### Choosing a Network In the next screen, you will be asked to choose which network you want to use: ![](/static/image/tui-native-network.76c6420120.png) You can highlight the different choices with the `Up` and `Down` arrow keys (or `Tab` and `Shift+Tab`). When you change choices, the **Description** box on the right will show you a brief description of each option. This is true for all choice-based pages in the Wizard, not just the network selection, so you will see this style of page frequently. If you want to practice running a Rocket Pool node on the Hoodi test network with fake ETH and RPL you can get for free, select **Hoodi Testnet**. If you're ready to create a real Rocket Pool node on Mainnet to earn real rewards, select **Mainnet**. ::: tip NOTE Official networks (Mainnet, Hoodi Testnet, and Devnet) come from `networks-default.yml`. You can add or override networks in `~/.rocketpool/networks-extra.yml` without rebuilding Smart Node. See [Custom and override networks](/node-staking/advanced-config.md#custom-and-override-networks) for details. ::: ### Execution Client Setup The next screen will prompt you for the URL of your Execution client's HTTP-based RPC API: ![](/static/image/tui-native-ec.0b52fec122.png) Enter `http://127.0.0.1:8545` here if you plan to run an Execution client on the same machine as the Smart Node (in the rest of this guide, we will assume this is what you plan to do). However, if you already have an Execution client set up elsewhere, use its URL here instead. Note that you can always change this by running `rp service config` again later. ### Consensus Client Setup Next, you'll be asked which Consensus client you are using (or plan to use). Because each Consensus client has slightly different behavior, the Smart Node needs to know which one you're using so it can adapt its own behavior accordingly. Choose your client from the list in the following screen: ![](/static/image/tui-native-cc.89794fc8c6.png) Next, you will see a screen prompting you for your client's API URL: ![](/static/image/tui-native-cc-url.65b7077318.png) Enter `http://127.0.0.1:5052` here if you plan to run the Beacon Node of your Consensus client on the same machine as the Smart Node (in the rest of this guide, we will assume this is what you plan to do). However, if you already have a Beacon Node set up elsewhere, use its URL here instead. ### Other Settings The next screen will have a few other miscellaneous settings: ![](/static/image/tui-native-other.467c40560f.png) Leave these as the default options unless you have decided to use a directory other than `/srv/rocketpool` for your Smart Node installation. ### Fallback Clients Starting with 1.5.0 of the Smart Node stack, you can provide a "fallback" Execution client and Consensus client pair that can take over for your primary clients if they ever go offline (such as because you use Geth and need to prune it). In this situation, your primary node machine will still be responsible for attesting and proposing blocks with your minipools' validator keys, but it will connect to an external machine to interact with the Execution layer and Beacon chains. [To learn more about fall back nodes, see this section](/node-staking/fallback.md) and return here when you're done. ### Metrics Rocket Pool has the ability to integrate with Prometheus and Grafana to produce convenient web-based dashboards that let you observe your node's health at a glance: ![](/static/image/nimbus-dashboard.518741bcdb.png) The final question in the Wizard will ask you if you want to enable this: ![](/static/image/tui-native-metrics.b421f31d1f.png) If you choose to enable it, you will learn more about setting it up and how to use it in the [Setting up the Grafana Dashboard](/node-staking/grafana.md) section later in the process. ::: warning NOTE All of the data collected by this system **stays on your machine**. Rocket Pool does not collect any of the telemetry or send it to a separate service. It's purely there for you to use so you can monitor your own node! ::: ### MEV Configuration Since the Merge of the Execution and Consensus layers in September 2022, Ethereum validators now have the ability to earn priority fees and participate in Maximal Extractable Value (or MEV for short). Starting with Smart Node v1.7.0, MEV is now _opt-out_ so a notification about configuring it is presented as part of the initial setup, as you see in the next screen: ![](/static/image/tui-native-mev.985e8fdb99.png) [Please read our MEV guide to learn more about MEV, its configuration, and what to do in this section of the wizard.](/node-staking/mev.md) Return here when you're finished. ### Completion After this question, you've finished setting up the Smart Node configuration. You will see the following dialog: ![](/static/image/tui-native-finished.ba7d7dccb4.png) If you're happy with your setup and are ready to start the Smart Node, click `Save and Exit` here. If you haven't finished installing Rocket Pool yet, return to the Native setup guide now. Otherwise, the next step is to restart your daemon services with: ```shell sudo systemctl restart rp-node rp-watchtower ``` If you would like to review all of the settings and customize many additional settings that weren't included in the Wizard, click `Review All Settings` and go to the [next section](#configuring-via-the-settings-manager). ## Configuring via the Settings Manager If you've already run `rp service config`, instead of being greeted by the Wizard, you will see the **Settings Manager** screen: ![](/static/image/tui-native-settings-home.338ffed65d.png) There are three main features of this screen: 1. The **Category List**, which lets you drill down into the settings for each category of the Smart Node stack that is relevant to Native mode 2. The **Review Changes and Save** button, which you can use when you're ready to see what settings you've changed and save the updated configuration 3. The **Open the Config Wizard** button, which will bring you to the [Setup Wizard](#configuring-via-the-wizard) if you prefer that interface instead ::: tip TIP To use the Settings Manager, **press the `Arrow Keys` (up/down/left/right) to navigate between options in the home page**. Press `Tab` to go **between the category list (1) and the buttons (2 and 3)** at the bottom of the screen. The button that's currently selected will be **highlighted in green**. **Press `Enter` or `Space` to select a button**, analogous to clicking on it with the mouse. **Hold `Ctrl` and press `C` at any time to exit the Settings Manager without saving anything**. ::: As you scroll through the categories list, each option will have a helpful description appear in the **Description Box** to the right of the screen. Feel free to explore them; nothing you do will be saved until you go through the Review dialog via the **Review Changes and Save** button, and you can press **Ctrl+C** at any time to exit without saving, so you won't accidentally mess something up by playing with the settings here. ### Configuring the Settings From the home screen, select any one of the categories with the `Enter` key to view the settings for that category. For example, here is the screen for the **Smart Node and TX Fees** category: ![](/static/image/tui-native-smartnode.1bf7f400fb.png) Use the `Arrow Keys` to move up and down between the settings. The currently selected one will have a white square at the end of it (if it's a text box or a check box), or will be highlighted in white (if it's a drop down). Press `Escape` to go back to the home screen of the Settings Manager when you're done. As you scroll through the settings, each one will show a brief description of what it does in the **Description Box** on the right. It will also show the **default value** there in case you want to revert it to its stock setting. In this example, the **RPL Claim Gas Threshold** setting is currently selected (highlighted with a green box on the left-hand side of the screen). It has been changed to `40`, but you can see that it has a default of `150` in the top-right corner (the top of the **Description Box**). ::: tip TIP As a reminder, nothing will be saved to disk until you go through the Review dialog via the **Review Changes and Save** button. You are encouraged to explore all of the settings to learn about them. ::: ### The Setting Types and How to Use Them The settings manager uses the following setting types and UI elements: #### Text Boxes Text boxes are used to enter arbitrary strings of text or numbers. They look like this: ![](/static/image/tui-textbox.f99e293310.png) Enter your desired values into them, then **press `Enter` or use the `Arrow Keys` to navigate to a different setting in order to preserve your changes.** If you don't, the Settings Manager will assume you're still updating that setting and won't mark it as changed yet. #### Drop Downs Drop downs are used to select an option from a list of choices. They look like this (when they're open): ![](/static/image/tui-dropdown-open.d5dc147082.png) The **green** item is the one that is currently selected. Use the `Arrow Keys` to change options - as you do, the **Description Box** on the right will update to tell you more about the currently selected option. When you're happy with your choice, press `Enter` to choose the selected option and the drop down will close, revealing the option that is currently selected: ![](/static/image/tui-dropdown-closed.c9f39e80ae.png) #### Check Boxes Check boxes are used for simple Yes/No questions. They look like this: ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAPAAAAAgCAIAAACjCWLqAAABg2lDQ1BJQ0MgcHJvZmlsZQAAKJF9kT1Iw0AcxV/TSkUqgnYo4pChOlkQFXHUKhShQqgVWnUwufQLmhiSFBdHwbXg4Mdi1cHFWVcHV0EQ/ABxdHJSdJES/5cUWsR4cNyPd/ced+8AoVFlmhUaAzTdNjOppJjLr4jhVwQRQz9CEGRmGbOSlIbv+LpHgK93CZ7lf+7P0asWLAYEROIZZpg28Trx1KZtcN4njrKyrBKfE4+adEHiR64rHr9xLrks8Myomc3MEUeJxVIHKx3MyqZGPEkcVzWd8oWcxyrnLc5atcZa9+QvjBT05SWu0xxCCgtYhAQRCmqooAobCVp1UixkaD/p4x90/RK5FHJVwMgxjw1okF0/+B/87tYqTox7SZEk0PXiOB/DQHgXaNYd5/vYcZonQPAZuNLb/o0GMP1Jer2txY+Avm3g4rqtKXvA5Q4QezJkU3alIE2hWATez+ib8sDALdCz6vXW2sfpA5ClrtI3wMEhMFKi7DWfd3d39vbvmVZ/P+79cnJWu3nHAAAACXBIWXMAAC4jAAAuIwF4pT92AAAAB3RJTUUH5gMZAzY2IpiKTwAAABl0RVh0Q29tbWVudABDcmVhdGVkIHdpdGggR0lNUFeBDhcAAApFSURBVHja7ZtpVJPXFoZ3JgIBAwQIyCRJRBkEqxigjKFItYq3aCFOF+WCtDUd1NpaahetSm2p1F60igqltQ6I0cqyiq0oQ6CAioBCmASCgLACISGEKQwh9wcUq/2CpEtdbe95/uWsL+c9e3/v2mefsxJcWJgaEIh/CniUAgQyNAKBDI1AIEMjEMjQCGRoBAIZGoFAhkYgniFElALEXxM+H2OQy0UV+p/AiL6R3Eh/5P9S/e/ccliExPD5XD6fy09PZE85CGaX4vnc1OjKPytVsjWdy4+9pv+3eEuEW7zk15N5NwjPN/PPTf0ZGlqXE8/nc7d7q56GaSapfPM4dyJffC6fz01ccx/zuZ6ysKSkKMGDJw8+RzMVfsB/ZPFxy6XPTs17O5fP38vRfdZRDbKWHN19MOp0Wnjqgd0rWM8wyX82ojFh3EIizjzySi8AwIOjARTcjFdSlX+hHloxR1DMGF+QvJ6KneYWt7yWfpJvqr/lEwafN13O10utVQAAIL6v+7zVVd4JXO+nOJ9JQOInUeW6/VYVZZY6s4RMMxi8oTnJT1t9mqV23vv7o5Jf+vaD+C1LYpp37sobdolL+E/Fnqdk6BnOF3gRV50s+3CDtLab6+JTXuwBINsINkRmuDO7QW53K2PTiTyboak8sYifGiJ5+Ll//uqD6/waLI2GRhQza3LCU865yrWN2kC4Pu6bpdYkkSDiwA9smVrDnATpgte+W+NfbUnFy0Repw9G3XpYZHvc39653W+oPHl3wnUrlSahNp8TqYGT5YFge+Hz+HSbxg1bYl+hbdwat7y39PDXXwpo2An5o7oyO/b7Y85F761J9LQJ274/rP/Sx0fT6PvPbLkJAAB3eSe4PCDnfH7y6J0RTsx63sLxLumdtQm+4yskWws2bLrgwZCPShwFp6P55SYqKNmanuDV6PuzquolO1VLNi/+hwW9GoIJXFGup2ac/WTvj61EIEhNDDR2z9jqGGFiqA94Y0Y07ZerF7Bn74ozG/+77a329lMd1tEnt8/Db3xKPXRjCC99oY5z2qF3Uvj+LWqlDgCQhREfH15sRcs/x80Vdy3mxa91nPLcYFqyNjolOjolOvrsIhMAGLCbK+m8teJEctTVVgU7LJHrOqa1nz1zHNq8b3f1Oi47FO4+qGFOtU3Ivg9Db9Nki37ODKhVtTBpkxMMzV4d/67fQNWJ2P1TuBkArAsiJhZ/2ZEMqpZXD59nwdwMbtDltS939JdvTBbQNCRkCvVHt9j6pUlJvGuNAGCTk8JLSno9twUACLWZvKQjQU2/f5RU8++dh4PsKKW/vNxArFy5IyHY8rffADNFur+uvdaitF+eHmCuIRZyA8sKQOSV30oEAFCZSHs09lsY6lO890fVNUSkBebhCR+6jeQeO15n8MrePUF6T+/abpRIBByxh6ZLriv5V0GWDgDgXHP9aFB7MvpCLhVKwOGbH3x9ao/XuGicg1rvE1Q/vs7ea6tvS42u7ku4qCTgSUM68sagF7IYDAlUmGsXcXVowtElCls95lfnXV0b4KYD1pwD/gFNeHnggT1vCEcAQEWYPN2wzm9zGejL2bnv8qwnnOFNql8KqgYAAKf76cE1Q4SWi7wf3T/kbkrDKecfSQ7o1pgQAwx1rJ5F3emc1wkjbklBLFptASdvYjvAiys5YgKJvfkaY/JRp3x/U2g4te3IT3Rc2eiRuEyOb8vFs+OVJzA9yx9Puh4854E5HaADKxbKAAUHoKAqprHv/1FdQ5gY6upKzIi0ATc3MsI7tlRAWRa5enrWeNzQY2N4rJG5l75dZheZHbL5i5VqveZs3ufJHmM0GQnAMXzL9+GTNw8SMoDGrkO07q2Y37UcBIlH+LFQrwa6/ghufO/XGdY2XmUnXQEAHeZigBeoChz2nFITE4C6Wc0TniWoJksxZRQGCDTXEhb5haqhKZXuvrFhb+Ajb0Rlkyew5zJrhio4N6QAAFTshAxpVP+zUEykuoDr6KADgFps0Qkwiyb77cChNwigqyIAjBI03UoMUAYAgKqgAki0V9cQ5ozpqmt3YVjy1cF8NUB/xtdHRaFbmNobelhuNAhgYiIFoBPMJMYAcrkRAHSVRHxasp5qU+u/7lD44rSgXzzOyWijgGvM+Ci9gjTx5T7L0Wkvlex55s2gmr67YYmZTnLLKzERJZMXLUolDvBDZBLAw7KJOQi6pl0GAH1mEjpAn4Kqgz2niVQKMLPVlghVowAwhsfjx8a7mwbuR6e6Ptl1NXJl4I50pnZOMyyMDK1R9uvreJxe77Lw20o9BXZC5Bjqo0QVAI6gwgHo6Q0+Wj5wAIDDTaU8IKMpQU2nSwDMcBZiOoBMRgPonO7Kh1iiNljALPaxCs5oIwCh29jAuLtHY5IfP9tjh9mg8bZiGhFp7HQPbTtUb/jaZ5tbd3+xJ4a/gc/V2tDQ6FI5eN2dG/epva3u3FJjMC0UWgA0hbz/E6XGtalLhwh4AJ3hYVALfQu7C3z9LrkPLewYGTRjlpvVba1qnv5uogaAPjGz6YGBI0f0u/aI0NZmDuyqZRFXdOop0nved9tJGIPjGXf68b3ILol9lhXoFVXOBuJVrDnt8vPsgrnX340dyxFSDefU9fB3na2fqGeK6tD0UsFbK1KX5n2WKcZN2UOLJm45itddEo76bPqOrc9I+2iD2Y7dQW+eKn4vugo7IZjqZpJewM0tDPaWO7zYBfCwre7uNgYQ+ay6Bm267RW+dcpmtnuTPq7eFABMa/w4KnW/3a07fgXSnKBVX2/Wn0fxyKKpGKd/tdXC0GCdfXn+8jfurtmzw0FoSbKr7Dlz/MANrMzL2zHUtXzvj0ckm/YyZed2xBWCx74vP94i7jrrkxjzWdGrAOQn3LI6O+96tMhb191Xz2SIZtu3Uvrtbp3fnFZsOgLD9Pl5izn5Af437fVMyy9EnSk1HR21EFbS9Rl32Z7FbOdmY5V1WaFXrUQHS6VzUUg+o8/lynWHgckdu22WzKxxvtfVZf61Y+1mxnYdyuolWdWGAND9wEJ/dtU8t2IvjxLj1uX5IjLGoPj+4uUVpJtLyyzzAqxJjTnRyZl2vQ+w5+ypW9CE77R3KnebL6L2OebnurUNtnuGFtlI3C7mOzU0g/tSgftMU8GvDIw2D9/qHXrTiiJhsEQslojFEuneX1pm9n1MqKg/++2D2S73+kQvcwpdKE45Ja53sBKCpW4q7m1zWXjHbQ6pshbmzBq9lxNcIQMAkHbMsJhT67SoyMvzDlSsuj2WvT32+GK2yBgAjEVsdgnb1kjwM+dGhSmVVcl2rzLud8o69vaFOn01tHuGFtl0LsooYBJn561Y0N1UsOq2WEONb3IT9iqsGI0O9m0G/cziXM69bsBIcl8BhnpmYBFGmBJN6o9HJJ6mnYdnlq3ckWf4ztmTa23Jtu5WwpTkU6WGNoZeOlPXSfQnWcRfE/RbDgQCGRrxzwK1HAhUoREIZGgEAhkagUCGRiBDIxDI0AgEMjQC8Sz5HzHpqShKad+YAAAAAElFTkSuQmCC) When they are checked, they will have an `X` in the middle as you see above. When they are _unchecked_, they will simply be blank like this: ![](data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAOgAAAAkCAIAAAAM4eHgAAABg2lDQ1BJQ0MgcHJvZmlsZQAAKJF9kT1Iw0AcxV/TSkUqgnYo4pChOlkQFXHUKhShQqgVWnUwufQLmhiSFBdHwbXg4Mdi1cHFWVcHV0EQ/ABxdHJSdJES/5cUWsR4cNyPd/ced+8AoVFlmhUaAzTdNjOppJjLr4jhVwQRQz9CEGRmGbOSlIbv+LpHgK93CZ7lf+7P0asWLAYEROIZZpg28Trx1KZtcN4njrKyrBKfE4+adEHiR64rHr9xLrks8Myomc3MEUeJxVIHKx3MyqZGPEkcVzWd8oWcxyrnLc5atcZa9+QvjBT05SWu0xxCCgtYhAQRCmqooAobCVp1UixkaD/p4x90/RK5FHJVwMgxjw1okF0/+B/87tYqTox7SZEk0PXiOB/DQHgXaNYd5/vYcZonQPAZuNLb/o0GMP1Jer2txY+Avm3g4rqtKXvA5Q4QezJkU3alIE2hWATez+ib8sDALdCz6vXW2sfpA5ClrtI3wMEhMFKi7DWfd3d39vbvmVZ/P+79cnJWu3nHAAAACXBIWXMAAC4jAAAuIwF4pT92AAAAB3RJTUUH5gMZAzk2pQCWgAAAABl0RVh0Q29tbWVudABDcmVhdGVkIHdpdGggR0lNUFeBDhcAAAmjSURBVHja7ZtpVJNnFsdvEsISMEI2kEUSAshSQMUABdkElBHsoANxGyhHpWpqq9UZ63JQW1uHkbFHraJCrYqKGBXHIlr2TUSMgrIjEBSEA4RACFuQhMwHFEXfUOkoPZ4+v295zpv7f+59/+fmPu95gwsJUQIC8aGBRyVAIOMiEMi4CAQyLgIZF4FAxkUgkHERyLgIBDIuAvGuUUMlQPzh8PkYi1wu6rgfPEPauhJd7aE/pfqHYFyDoG18PpfP5/ITD3LGXQR6chSfezKi7PdKCTYlcvmR6dofhG8Jd3mxn8Xy7hAmt/KTpv4ORgVNr6h4XnHRoQsHCghAT446epaeHrk6zu7/Uylbd3rvPNLLzy1J+zclMt+8rrs4JEbSYfvJSU/D31icRNMU/PPCoVfvZc2ZY5Ep1Pek5raFu9HZISZsZ47svWY1wF5wJixAYE57JhOZ//fw7oz3VuT3lNEkzrhSy9xC1sjmJbVk7HI2OuY09hHdx5QPc3Gy6bDNuG+sAACA1seak62ucIvmur3DeFTvg7tWl2j2GZUWG6qblpvRYeCO6iK/a/VJNe4U2yReeKqNYS9ugNJctCIq7uNuAA2T3LBVV53MukDCvHt1TXyOyeB4934O/2SQ6OXnPoelh1d41BnqDg5Jp1VlhcZdspdMdPs65Sv3/uhvTBTmhh86w+lUqohJEM/628/LPCsNyfhOoev5w6vvil82dKcNO7Z4DJbEfhOdYaRQJdQ8N/6kz2jLIExP2heVaFIftjHyL5RPN+0N6Ll/9Id/51KwC/Kmuiwz8tQJ29ublx10MQnZciCkL3nn8QTGgQsbiwAA4CEvnssDjax9Z48/GPLatpI3e2S6+WJ5tPvIDjWMc8PWJDmzJHKRde75CH4JVQGCTYnRrvXuNxUV85iKxkxe1JlZPSqS8VlUoqVkXdz1/ZUmNSCIqToqp1tsdYw0MdT73TAzmtQZtz6Ilzhb3TbhyBdxfM9GpUwdADTKw3ce9TWi5F3iZrd2+PKilluPO7/TBMsj4iIi4iIiLs6hAkA/c4ao/e6i+NjVqU1STshBrv3whH3rkmXV7Havo8d64ZFQpwEVMZUmQfu/Dr5H6ZxzM8W7WtFoRhkNMGi+NOpLj/6K+MgD47gWAIzzw59v/rq1Biga/3r0MhtmXOX6XV8+v62v5NPYXIqKgoyjPobhWv+YGF56PQCYZMXxYmI+y24EAEJ1Ci/mmF/Dq5cSq/6+46gfk3T/1/l1amWLt0YHGr54qdpMqHlreXqjzCIg0VtfRS4adWwjAKFrXpMaAICCKu5WOSdhqI9z38eqq8hoUjuuXE0NcGrdFE2NGsEn+WnqAICzz/agQPXZiKRsMgjA6scz7nOrT1epnobJtXP9agEAQL8nfek9sW7q/uhrMgKeOKguqfebmcZiiaBUf2LbrwyOPr5AOl3L7D+X7e3roMgKK2a/p3cDXuJz6Nu15UMAoCCMnjLYl7+y6+/N2rH/uulvnJmplfP8KgEAwOZxYmDVIKHxGu+K09fcNQk4mcOxWO8ulQXRwVDHmjWU7bY57TDkGOPHplTne72YCPGtZV6tBCJnfTpr9FKbPE8a1J376tgvDFyx/NjeFC/3xmsXRzqMT2KaJ56YEWj5VJ8B0IaVC6mfhAOQkqVv0dfeVFeRJoa6sgwzo/dj3OFhPNbKjOSfFjJXZQat/9dipdaTTN6+WOdhSicRwDp046nQ0ZO+SANA5bQgXPH5tldGBYLIOfREsGsdQ3sIN/Kbrf5soruXtTOkANCm3wowkyzFYccUU6kANaZPnnuToBhtrSQ59BMo9gK2xsyKwXGVHq4N+95nTOUVJjm5FlyzqsFSrztiAAAydkEGVar/XkhUsSbg2toYAKBsNWgHMKV0vjgQaA0AaCoIAHKCqqcA/aR+ACBLyQCiiaurSHPK26q/J+M+k+gOAFCpYgAGgS7SA5BIdAGgQxC+W7CSbFLtueJIqG+C36/OlzopcsDVX92eWEp8/uVeQ/lbC2u4XFjnV9X7MORgio3E8Ma2cMHogw2ZDAf4QQ0iwMs2iLkImrQOHYBeuogB0Cslq2PHpIrFANOapqtBhRwAhvF4/PDIVFLH3X6uY9ee1FWLfbYmmk3MUVMLVgVXyfq01Z3Pr7Sb/VOZlhS7IBIMdbmaAgBHUOAAtLQGxrYJHADgcOMp93dSZKBkMEQAdJxBKwOgs5MC0P62Ox9kC5thllnhXKPAq80EIHTp6eh1dass8utnbOw061Rd/zYZvYtRod6ubCDDibt3t8V0zRn39YBWUG4A0BD0j19IVfYNHepqgAdQf/YMlOXuBV357h7JToOz24YG6GYl9JpNFU/eWhmnBIDeVrOGpzrWXkKtV+aq5mZ94FQsDL+hXksSP3J72ELEWByprM2Vzas6RBZpRqB1u8wc1FKxYjLzcpiB3IwvI4ezyslTLWu6+Xsu1j7vT9LK4MT7uZ8vOumf811KK27cGVf4/KlC4YrkcvncNT9ztFkJ28PoW7/xW3eucHNEBXZBMNXpoh7AzSgIdJNYfdwB8HLs7erSAxDOXZIOzZotpe41siccpwZtXC0NAGhVHl4KZR/z7gOPfHGW35If1mt/RHJOoyhY529Nn4BxwTjzukPA2ofLvt1qVW5IZJZ1Xzh96A5W5SUtGOoTvO+vZ9T5jp5S2truGXuONK55rJzGEppbNJH6mHcvr08opA3BM4ZDjq9XnrdnkYUWrSRp9YX7NLncoLyMoc16yHEp5Ng+0VMYFxe4VovUsVTa5wTlsXrtbmRY9Y/+0jabdtLrHVxTF3pWD7fQ9ZhtssoFaZVTAaDrqYG2ecVHjoWuzgK9poA8oQbGYutj34BSYpF/sWGOtzGxPisiNoXZ8xQ7ZnfNrAZ8u4VNiaODkNxrnZft2DzQ4hJ820TkeC3Ppu4JOPnnOk2j5d5iYYxh+Ca34CIjkojFFrLZQjZbqPnYv5h+aluwsC9zw+FMu0e9wvleBXYkmyyB/QOsgmCp01p7mu1mP3C0JJZVg6Wp/FFWYGknAIC4bYqBZbXNnNuuLg+gdMm94cwtkad9OUI9ANATcjgCznTd3Jted0ppZHYZx6lCr88m7cSGpBptJbS4BN82aZ9zNd9MzTxn0ayuhvwl91pV9OwGx/IeqRGr3sqiWafPrDDb61EXYBS5Nx9DPcXnNkaaIlXqr2eEtaWQEIzFS5fG7XvoX76IPxz0rgLizwIyLuKDBI0KCNRxEQhkXAQCGReBjItAIOMiEMi4CGRcBAIZF4FAxkUgkHERHyz/AwOfWpJv0c3yAAAAAElFTkSuQmCC) To change the setting, simply select it and press `Enter`. ### Saving Changes When you're happy with your changes and you'd like to review them before saving, press the **Review Changes and Save** button on the home screen. As a reminder, to get to it, press the `Tab` key. You will be presented with a view that looks like this: ![](/static/image/tui-native-review.ad95b24182.png) The **Review Box** here will present all of the settings you've changed, showing the old values and the new ones. For example, the first line here shows that the **RPL Claim Gas Threshold** used to be `150`, and it's been changed to `40`. ::: tip NOTE At this point, your changes **still haven't been saved yet**. If you want to go back and modify something, press `Escape` to return to the home screen. ::: When you are satisfied with the changes, press `Enter` to save the new configuration to disk. You will then exit the Terminal UI and be presented with this message: ``` Your changes have been saved! Please restart your daemon service for them to take effect. ``` If you haven't finished installing Rocket Pool yet, return to the Native setup guide now. Otherwise, now you can restart your daemon services with: ```shell sudo systemctl restart rp-node rp-watchtower ``` ## Configuring via the Command Line If you use the Smart Node in a headless environment where you can't interact with the Terminal UI, you can configure your node via the command line instead. The `rocketpool service config` command accepts, as arguments, every setting that can normally be configured via the Terminal UI. Run the following command to see a list of them (note that it's quite long): ``` rocketpool service config --help ``` The output will look like this: ``` NAME: rocketpool service config - Configure the Rocket Pool service USAGE: rocketpool service config OPTIONS: --executionClientMode value Choose which mode to use for your Execution client - locally managed (Docker Mode), or externally managed (Hybrid Mode). Type: choice Options: local, external (default: "local") --executionClient value Select which Execution client you would like to run. Type: choice Options: geth, infura, pocket (default: "geth") --useFallbackExecutionClient Enable this if you would like to specify a fallback Execution client, which will temporarily be used by the Smartnode and your Consensus client if your primary Execution client ever goes offline. Type: bool ... ``` Each option will have its name, its type, its default value, and (if it's a choice parameter) its options. Using this text, you can find the option(s) you want to set and specify them via the appropriate arguments. ::: tip NOTE This command builds on top of your existing configuration, so if you have some settings already saved and just want to modify others, you don't need to repeat them. It will only update settings that you include as arguments to this command. ::: If you haven't finished installing Rocket Pool yet, return to the Native setup guide now. Otherwise, the next step is to restart your daemon services with: ```shell sudo systemctl restart rp-node rp-watchtower ``` --- url: /node-staking/config/overview.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Overview In this section, you'll learn how to configure the Smart Node stack and customize all of the settings to your liking. You will have to configure it prior to running the stack for the first time, but you can always come back once it's running and reconfigure it again whenever you like. ## Prerequisites Before configuring your Smart Node, please make sure you: - Have a node machine (or virtual machine) with the Operating System installed and configured - Have the machine secured (via the [Securing your Node](/node-staking/securing-your-node.md) guide) - Have the Smart Node installed on it ## Guides [Configuring the Smart Node Stack (Docker / Hybrid Mode)](/node-staking/config-docker.md) is the guide to use if you want to run with Docker Mode or Hybrid Mode. [Configuring the Smart Node Stack (Native Mode)](/node-staking/config-native.md) is the guide to use if you want to run with Native Mode. [Advanced Smart Node Configuration for Docker Mode](/node-staking/advanced-config.md) is a supplement to the Docker guide that shows some extra capabilities and features you might be interested in (such as "Reverse Hybrid" Mode or customizing the Docker container flags). --- url: /node-staking/create-validator.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. ::: danger WARNING Minipool deposits are currently disabled in preparation for Saturn 1. ::: # Creating a New Minipool (Validator) As a reminder, a `minipool` in Rocket Pool terms refers to a unique smart contract instance on the Execution Layer that your node manages. The minipool handles a portion of your ETH, known as the **bond amount**, and a portion of ETH from the rETH staking pool, known as the **borrowed amount**. It merges them together to form 32 ETH in total, which is then sent to the Beacon Chain deposit contract to create a new validator. Thus, in order to create a validator using Rocket Pool, you need to **create a minipool**. ::: danger WARNING Minipool creation is governed by two queues. The first is the Rocket Pool deposit queue, which is managed by the Rocket Pool protocol & determines when your minipool will receive its borrowed ETH. There needs to be ETH available in the deposit pool to match your 8 ETH with 24 ETH in the deposit pool & create the minipool. The second is the Beacon Chain queue, which is managed by the Ethereum Beacon Chain & determines when your validator will become active. Please be aware that the time it takes for your minipool to become active can vary greatly depending on your position in each queue & the current state of the network. ::: ::: tip NOTE The Beacon Chain validator queue activation (and exit) times can vary greatly depending on the current state of the network. This is outside Rocket Pool's control and is a function of the Beacon Chain itself. The following tool provides a good estimate of how long you can expect to wait: [https://www.validatorqueue.com/](https://www.validatorqueue.com/) Please review this tool to get an idea of how long you can expect to wait for your validator to become active. ::: ### Staking RPL via the Website The easiest and safest way to stake RPL for your node is to use the protocol's **Stake-on-Behalf** feature, which was reintroduced with the Atlas upgrade. This way, you can stake RPL for your node while the RPL is still in the wallet you used to acquire it. In other words, you **don't need to send RPL to your node's hot wallet** in order to stake it. #### Whitelisting an address to stake on behalf In order to stake on behalf of your node an address must be whitelisted. Your withdrawal address is always whitelisted, and you may skip this step if your RPL is held by your withdrawal address. You only need to whitelist an address once in order to stake from it. You can do this via the following Smart Node command: ```shell rocketpool node add-address-to-stake-rpl-whitelist address-or-ens ``` Where `address-or-ens` is the address or ENS name that resolves to your desired address. You will be asked to confirm the whitelist addition and after the transaction is confirmed, you can then navigate to the relevant page below. #### Staking RPL on behalf of Select which network you're using from the tabs below to be taken to it: **Mainnet** [https://node.rocketpool.net/stake-rpl-on-behalf-of-node](https://node.rocketpool.net/stake-rpl-on-behalf-of-node) **Hoodi Testnet** [https://testnet.node.rocketpool.net/stake-rpl-on-behalf-of-node](https://testnet.node.rocketpool.net/stake-rpl-on-behalf-of-node) Start by connecting your wallet to the website using MetaMask, WalletConnect, or any of the other methods the website supports. You will then be presented with this dialog to look up your node address. Enter your node address & click "Lookup". **Make sure you have the correct node address before doing this!** If you need to confirm your node's address, you can quickly retrieve it via the CLI using the `rocketpool node status` command. This will check that the address is a registered node & that the node has whitelisted the connected wallet. Withdrawal addresses are whitelisted by default, however if you wish to allow other addresses you will need to whitelist them via the following command on your node. ```shell rocketpool node add-address-to-stake-rpl-whitelist address-or-ens ``` This is a two-step process. First, enter the amount of RPL you want to stake and click `Approve` - this will **approve** the staking contract to access that much RPL in your wallet, but **no more than that amount**. ::: tip TIP You can approve more than the amount you intend to stake if you trust the Rocket Pool staking contract, and don't want to perform this extra Approve transaction each time you want to stake more RPL. ::: Once the RPL is approved, you will be able to stake on behalf of a node. Enter the amount of RPL you want to stake in the `Stake RPL` box, and enter your node's address in the `on behalf of Node Address` box. When you've entered that information, press the `Stake` button and approve the transaction. It will be sent to the Ethereum network, and once included in a block, you're all set! If you run `rocketpool node status`, you should see your staked RPL appear under the `=== RPL Stake ===` section. #### Removing an address from the stake whitelist If you ever want to remove an address from your stake-on-behalf whitelist, you may do so with the following Smart Node command: ```shell rocketpool node remove-address-from-stake-rpl-whitelist address-or-ens ``` Where `address-or-ens` is the address or and ENS name resolving to the address you want to remove from the whitelist. ### Staking via the Node CLI If you cannot (or do not want to) use the website to stake your RPL, you can also stake it via the node's CLI directly. First, transfer your RPL from the wallet you acquired it with to your node's address. ::: danger WARNING **Please do this carefully and ensure you are sending the RPL to your node's address - transfers on Ethereum cannot be undone!** **Sending RPL to the wrong address will result in the loss of your RPL.** Use the `rocketpool node status` command to verify your node's address if you aren't sure what it is. ::: Run the following command: ``` rocketpool node stake-rpl ``` Here is the output: ``` Please choose an amount of RPL to stake: 1: Your entire RPL balance (1440.000000 RPL)? 2: A custom amount ``` Select how much you'd like to stake, then confirm the operation. The first time you run this command, it will involve two transactions - one to **approve** the Rocket Pool staking contract to access your RPL, and one to **stake** your RPL with it. Subsequent runs will only require the **stake** transaction, since the token has already been approved. Once both transactions finish, you can check your staked RPL amount with `rocketpool node status`. The following portion of the output is what you want to verify: ``` The node has a total stake of 300.000000 RPL. This is currently 29.76% of its borrowed ETH and 89.29% of its bonded ETH. It can earn max apy on up to 151.209677 RPL (15% of borrowed ETH), and still earn at lower APY with more RPL. ``` This will show you how many minipools you can make of each bond size based on your RPL collateral. ## (Optional) Finding a Custom Vanity Address for your Minipool By default, when you create a new minipool, Rocket Pool will generate a random unique address for it. However, the Smart Node provides the ability to search for a custom **vanity address** for the minipool. A vanity address is one where you personally pick the characters that the address starts with. This is a purely cosmetic exercise and will not have any practical impact on your minipool's operation. As Ethereum addresses are in hexadecimal, any of the following characters are legal: ``` 0 1 2 3 4 5 6 7 8 9 a b c d e f ``` As a few examples, you could make your minipool's address start with a bunch of zeros (`0x000000...`), `0x600d` (hex for "good") or `0xa77e57ed` (hex for "attested", a fitting prefix for a minipool). To find such a vanity address, you will need to **search for it**. This searching process involves picking a number, applying it as a "salt" to the hashing algorithm, and comparing the results against what you're looking for. The results are effectively random (though any given salt always produces the same result), so the only way to find an address with the prefix you want is to try lots and lots of them until you find a salt that works. If you would like a custom vanity address to use for your minipool when you create it, you can use the following command to search for one: ``` rocketpool minipool find-vanity-address ``` This will prompt you for the prefix you want to search for, and ask which type of deposit you will be doing (a 16 ETH or a 32 ETH deposit - see below for more info on these types). Once you enter that information, it will begin trying lots and lots of salts until it finds one that produces your desired prefix! Here is a complete example of the process: ``` $ rocketpool minipool find-vanity-address Please specify the address prefix you would like to search for (must start with 0x): 0xa77e57 Running with 12 threads. Found on thread 3: salt 0x5cd7fb = 0xA77E57c892C9e98B0B81289e4AfdA62fb59c5DDD Finished in 1.91145873s ``` In this case, we searched for `0xa77e57` as the prefix and found the salt `0x5cd7fb` which could generate it. In the next step, when we create a minipool, we can specify this salt as an optional argument to create the new minipool at the address associated with the salt (`0xA77E57c892C9e98B0B81289e4AfdA62fb59c5DDD` as shown above). In general, each additional character you search for will multiply the search time by about 16. Because of this, **we recommend you only look for prefixes of 7 or 8 characters max unless you have a very powerful machine with many CPU cores**. Otherwise, it might take prohibitively long to find a salt that produces the prefix you want. For example, an AMD 5600x with 6 cores (12 threads) at 4.8 GHz can search about 3.2 million salts per second. On average, it will take a few seconds to find a 6-character prefix, a few minutes to find a 7-character prefix, and a few hours to find an 8-character prefix. ::: tip NOTE The salt that gets generated is specific to the following variables: - The network you're using (either the Hoodi Testnet or Mainnet) - The node address - The bond amount - The salt If you change any of those variables, the minipool address for a given salt will change as well. ::: For more advanced usage (such as searching for a different node address or changing how many CPU cores are used for searching), take a look at the help text with `rocketpool minipool find-vanity-address --help`. ## Depositing ETH and Creating a Minipool ::: tip TIP If the market value of rETH is higher than its ETH backing (i.e., rETH is at a premium on the market), there is an opportunity to arbitrage the difference when creating a minipool. The value of the arbitrage is equal to the amount of protocol ETH in the minipool times the premium (minus a small amount of gas). E.g., if making a minipool when there's a 2.5% premium: `16 ETH * .025 = 0.4 ETH`. In other words, you could receive 0.4 ETH back during these conditions just for creating a minipool! If you're interested in taking advantage of this opportunity, consider using the community-developed [rocketarb](https://github.com/xrchz/rocketarb#readme) tool to capture the profit of the MEV rETH arbitrage opportunity that launching your minipool creates. To learn more about rocketarb, feel free to inquire about it on the [RP discord server](https://discord.gg/rocketpool). ::: After everything you've done so far, you are finally ready to deposit your ETH, create a new minipool, and create a Beacon Chain validator. This is done with the following command: ```shell rocketpool node deposit ``` ::: danger WARNING While the CLI does automate a lot of the next steps for you, we **strongly ** recommend monitoring your node & transactions to ensure a successful transition from `prelaunch` to `staking` . Failed transactions (due to adjusted gas settings or insufficient ETH) could make your minipool transition to the `dissolved` state, which you want to avoid. [Learn more about how to confirm a successful stake](/node-staking/create-validator.md#confirming-a-successful-stake) ::: ::: tip NOTE If you want to use a salt for a vanity address that you found using the process above, run the following command instead: ```shell rocketpool node deposit --salt ``` ::: You will first see a note that depositing a new minipool will **automatically distribute** any balance in your node's [fee distributor](/node-staking/fee-distrib-sp.md) contract (used to capture MEV rewards if you're not opted into the [Smoothing Pool](/node-staking/fee-distrib-sp.md#the-smoothing-pool)): ``` Your eth2 client is on the correct network. NOTE: by creating a new minipool, your node will automatically claim and distribute any balance you have in your fee distributor contract. If you don't want to claim your balance at this time, you should not create a new minipool. Would you like to continue? [y/n] ``` If you already have minipools and a balance in your fee distributor, you may decide not to create another minipool if distributing this balance causes a taxable event in your jurisdiction. After that you'll be notified of your commission rate for the new minipool, and a note on whether or not your node's [credit balance](/node-staking/credit.md) can be used to cover the cost of the minipool bond for you: ``` Your minipool will use the current fixed commission rate of 5.00%. If you participate in the smoothing pool, your minipool will receive at least a 5% commission boost, and up to a 9% commission boost based on RPL stake. You currently have 8.00 ETH in your credit balance. This deposit will use 8.000000 ETH from your credit balance and will not require any ETH from your node. ``` You will next be prompted with the network's current gas costs recommendations; confirm your gas price selection and follow the rest of the prompts. ``` Your consensus client is synced, you may safely create a minipool. +============== Suggested Gas Prices ==============+ | Avg Wait Time | Max Fee | Total Gas Cost | | 15 Seconds | 15 gwei | 0.0244 to 0.0366 ETH | | 1 Minute | 10 gwei | 0.0157 to 0.0235 ETH | | 3 Minutes | 7 gwei | 0.0100 to 0.0150 ETH | | >10 Minutes | 6 gwei | 0.0080 to 0.0120 ETH | +==================================================+ These prices include a maximum priority fee of 2.00 gwei. Please enter your max fee (including the priority fee) or leave blank for the default of 10 gwei: Using a max fee of 10.00 gwei and a priority fee of 2.00 gwei. You are about to deposit 8.000000 ETH to create a minipool with a minimum possible commission rate of 14.000000%. ARE YOU SURE YOU WANT TO DO THIS? Exiting this minipool and retrieving your capital cannot be done until: - Your minipool has been *active* on the Beacon Chain for 256 epochs (approx. 27 hours) - The Shapella upgrade of the Ethereum network has been deployed - The Atlas upgrade of the Rocket Pool protocol has been deployed - Your minipool has been upgraded to use the Atlas delegate [y/n] y Creating minipool... Transaction has been submitted with hash . You may follow its progress by visiting: Waiting for the transaction to be included in a block... you may wait here for it, or press CTRL+C to exit and return to the terminal. The node deposit of 8.000000 ETH was made successfully! Your new minipool's address is: The validator pubkey is: Your minipool is now in Initialized status. Once the remaining ETH has been assigned to your minipool from the staking pool, it will move to Prelaunch status. After that, it will move to Staking status once 1h0m0s have passed. You can watch its progress using `rocketpool service logs node`. ``` Note that creating a minipool **is an expensive transaction**! Pay close attention to the total cost and ensure that you accept it. If you accept, your minipool creation will be triggered. Once the transaction completes, you will be given the address of your new minipool contract on the Execution Layer and its corresponding validator public key on the Beacon Chain. You can visit these with any block explorers if you'd like. ## Confirming a Successful Stake Upon creation, your minipool will be put into the `initialized` state. It will remain here until it's your turn in the Rocket Pool queue to be given 24 ETH from the staking pool so you can stake your new validator on the Beacon Chain. Once this happens, your minipool will move into the `prelaunch` state for a certain period of time (currently 12 hours). Your 8 ETH deposit will be transferred to be Beacon Chain, and the Oracle DAO [will verify that it is all correct](https://github.com/rocket-pool/rocketpool-research/blob/master/Reports/withdrawal-creds-exploit.md). During this time, you can observe the validator by looking up its validator pubkey with a Beacon Chain explorer such as [https://beaconcha.in](https://beaconcha.in) (or [https://hoodi.beaconcha.in](https://hoodi.beaconcha.in) for the Hoodi Testnet). You can check on the new minipool's status with the `rocketpool minipool status` command. For example, when it has moved into `prelaunch`, you will likely see something like this: ``` 1 Prelaunch minipool(s): -------------------- Address: Penalties: 0 Status updated: 2024-10-31, 04:51 +0000 UTC Node fee: 5.000000% Node deposit: 8.000000 ETH RP ETH assigned: 2024-10-31, 04:51 +0000 UTC RP deposit: 24.000000 ETH Minipool Balance (EL): 31.000000 ETH Your portion: 7.000000 ETH Available refund: 0.000000 ETH Total EL rewards: 7.000000 ETH Validator pubkey: Validator index: 0 Validator seen: no Use latest delegate: no Delegate address: Rollback delegate: Effective delegate: 0 finalized minipool(s): ``` After this prelaunch period, your minipool will enter `staking` status and send the additional ETH from the staking pool to the deposit contract. This will be done by the `rocketpool_node` Docker container (or the `rp-node` service if you used the Native setup) - if, for some reason, you are taking abnormally long to enter `staking` status, looking at the logs for this container / service will likely tell you what's wrong. You can check these logs with the `rocketpool service logs node` command (or `/srv/rocketpool/node_log.sh` on Native mode setups). Running `rocketpool minipool status` will then show something like this: ``` $ rocketpool minipool status 1 Staking minipool(s): -------------------- Address: Penalties: 0 RP ETH assigned: 2024-10-31, 05:53 +0000 UTC Node fee: 5.000000% Node deposit: 8.000000 ETH RP ETH assigned: 2024-10-31, 04:51 +0000 UTC RP deposit: 24.000000 ETH Minipool Balance (EL): 0.000000 ETH Your portion: 0.000000 ETH Available refund: 0.000000 ETH Total EL rewards: 0.000000 ETH Validator pubkey: Validator index: Validator active: yes Validator balance: 32.018460 ETH Expected rewards: 16.010614 ETH Use latest delegate: no Delegate address: Rollback delegate: Effective delegate: 0 finalized minipool(s): ``` ::: warning NOTE The transaction to migrate from `prelaunch` to `staking` is submitted automatically by your node and is subject to the gas settings in `rocketpool service config`. If the gas settings prevent the node from submitting the transaction, or there is insufficient ETH in the node wallet to pay for the transaction, the minipool will become `dissolved` two weeks after it entered `prelaunch`. If this happens, retrieving the balance is a costly and lengthy process, so make sure to monitor your minipool closely until it reaches `staking` status! ::: Once the Beacon Chain accepts both of the deposits (one from you and one from the staking pool), your validator will enter the Beacon Chain queue where it will wait for its turn to become activated and start staking. At this point, you're done! Congratulations! You have officially created a validator with Rocket Pool! Have a look at the next sections in Monitoring and Maintenance to learn how to watch your validator's performance and health over time. ## Creating Multiple Minipools Conveniently, your Rocket Pool node is capable of hosting as many minipools as you want. You **do not** need to create a new node for each minipool. If you would like to make a second (or third, or fourth...) minipool for your node, all you need to do is run `rocketpool node deposit` again. Also, you won't be able to reuse an old vanity address salt - you'll need to search for another unique one for each of your minipools. ## Next Steps Now that you have a minipool up and running, the next steps will walk you through how to monitor the health of your node, check for and apply updates, and maintain it throughout its life. **Please read through the `Monitoring and Maintenance` section next to learn more about these topics.** --- url: /node-staking/credit.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. ::: danger WARNING Minipool deposits are currently disabled in preparation for Saturn 1. ::: # The Deposit Credit System The deposit credit system is a mechanism to track ETH that was previously bonded by node operators but is no longer required and make it available for use again. The source of this credit comes from two places: - [Migrating an existing 16-ETH bonded minipool down to an 8-ETH bonded minipool](/node-staking/leb-migration.md) (which adds 8 ETH to the node operator's credit balance) - [Migrating an existing solo validator](/node-staking/solo-staker-migration.md) into a minipool (which adds either 16 or 24 ETH to the node operator's credit balance, depending on which type of minipool they create during migration) Every node operator begins with a credit balance of **0 ETH**. Either of these two actions will increase that balance accordingly. This ETH is _not_ made liquid and returned to the node operator; instead, it can be used to **create additional minipools** without requiring any ETH from the node operator. The credit system is **transparent** to the node operator; it will automatically be used (with notifications in the Smart Node CLI explaining that it will be used) during either `rocketpool node deposit` or `rocketpool node create-vacant-minipool` operations if possible. If it _cannot_ be used, the Smart Node will alert the user that it cannot be used and will require a normal ETH bond during either operation. See the [Credit Availability](#credit-availability) section below for more details. ## An Example Say you have a credit balance of 0 ETH, and a single minipool with a 16-ETH bond. You can then [migrate that minipool to an 8-ETH bond](/node-staking/leb-migration.md). This will result in **8 ETH** that is no longer bonded. That 8 ETH will be placed into your **credit balance**. Now, say you want to create a _second_ 8-ETH minipool. You run `rocketpool node deposit` as usual, and select 8-ETH as the bond amount. This normally requires you to provide 8 of your own ETH for the minipool. However, because you have a credit balance of 8 ETH, Rocket Pool will **automatically use that instead**: ``` Please choose an amount of ETH to deposit: 1: 8 ETH 2: 16 ETH 1 Your minipool will use the current fixed commission rate of 14.00%. You currently have 8.00 ETH in your credit balance. This deposit will use 8.000000 ETH from your credit balance and will not require any ETH from your node. Your consensus client is synced, you may safely create a minipool. ``` The second set of lines here is the relevant one: they tell you that you have enough ETH in your credit balance to cover this deposit _and that it is available for use_, so it will use the balance automatically and won't require any supplemental ETH from your node wallet. See [the availability section below](#credit-availability) for details on credit balance availability. ## Viewing your Current Credit Balance To view your current credit balance, simply run the following command: ```shell rocketpool node status ``` This produces a comprehensive list of details about your node, including its credit balance right at the top: ``` Your Smartnode is currently using the Zhejiang Test Network. === Account and Balances === The node 0x9BA1401Eb7D779eC51f910B066e9C4351cD28911 has a balance of 347.796908 ETH and 16799.835547 RPL. The node has 8.000000 ETH in its credit balance, which can be used to make new minipools. ... ``` ## Credit Availability In some situations, your node might have a credit balance available but cannot currently use it to deploy additional minipools. The ETH for your credit balance is taken from the **deposit pool**. Thus, if you want to use 8 ETH in credit to create a new 8-ETH minipool, it will end up taking **all 32 ETH for that minipool** from the deposit pool and require none from you. Because of this, if the deposit pool does not have enough ETH in it to cover the pre-deposit value (currently set to 1 ETH), **the balance will not be available**. In this situation, the Smart Node will alert you during a `rocketpool node deposit` operation that it **cannot** use your credit balance, and must instead use ETH from your node wallet to complete the bond. Doing so will **not** consume your credit balance; it will be left as-is and available for use later once the deposit pool has enough balance to cover it. --- url: /node-staking/docker.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Creating a Standard Rocket Pool Node with Docker In this section, we will walk through the process of installing the Rocket Pool Smart Node stack using the standard [Docker](https://www.docker.com/resources/what-container)-based setup. This will install and configure everything you need to run a complete node, including: - The Rocket Pool **Smart Node** software - An **Execution** (formerly ETH1) client of your choice, or a connection to an existing client you already manage - A **Consensus** (formerly ETH2) client of your choice, or a connection to an existing client you already manage - A **Validator** client that will handle your Beacon Chain validation duties - (Optionally) a **monitoring stack** for capturing performance and health metrics All you need to do is tell it what you want to run! ::: tip NOTE The below instructions require you to use your system's **terminal** to enter and execute commands. If you are connected to the node machine via SSH, you are already doing this. If you are on the node machine and using a Desktop UI, you will need to open a terminal window to execute the following commands. Refer to your OS's instructions to learn how to do this if you are unfamiliar. ::: ## Process Overview At a high level, here's what is involved in installing Rocket Pool: 1. Download the Rocket Pool command-line interface (CLI) 2. Use the CLI to install the Smart Node stack 3. Configure the Smart Node stack with an easy-to-use UI in the terminal 4. Done! ## Before You Start ::: warning If using Ubuntu, it is recommended that before installing Rocket Pool you double check that docker was not installed alongside the operating system. The Ubuntu installer gets docker from the snap package manager, which will conflict with the version of docker installed by Smart Node. Run `snap list`, and make sure `docker` was not installed. For example, this is the output on a machine where docker is not installed: ``` Name Version Rev Tracking Publisher Notes core20 20230308 1852 latest/stable canonical✓ base lxd 5.0.2-838e1b2 24322 5.0/stable/… canonical✓ - snapd 2.59.1 18933 latest/stable canonical✓ snapd ``` And here is the output if it was installed: ``` Name Version Rev Tracking Publisher Notes core20 20230308 1852 latest/stable canonical✓ base docker 20.10.17 2746 latest/stable canonical✓ - lxd 5.0.2-838e1b2 24322 5.0/stable/… canonical✓ - snapd 2.59.1 18933 latest/stable canonical✓ snapd ``` If you see it in the `snap list` output, be sure to remove it with: ```shell sudo systemctl stop snap.docker.dockerd.service sudo snap remove --purge docker ``` After which, it is recommended that you reboot the machine (`sudo systemctl reboot`) ::: ## Downloading the Rocket Pool CLI The instructions for downloading the CLI vary based on your Operating System. ::: warning NOTE You must perform the following instructions **on the machine you will use for your Rocket Pool node.** If you are not using a keyboard and monitor directly connected to your node machine, you will need to access it remotely (e.g. via SSH) and run these commands on it through that remote connection. ::: **Linux** On Linux, start by creating a new folder that will hold the CLI application: ```shell mkdir -p ~/bin ``` Next, download the CLI. This depends on what architecture your system uses.

TIP

If you do not know your CPU architecture, you can run the following command to find it: ```shell uname -m ``` The output of this command will print your architecture. **Note that `x86_64` is the same as `x64` and `amd64`.** **Note that `aarch64` is the same as `arm64`.** For `x64` systems (most normal computers): ```shell wget https://github.com/rocket-pool/smartnode/releases/latest/download/rocketpool-cli-linux-amd64 -O ~/bin/rocketpool ``` For `arm64` systems: ```shell wget https://github.com/rocket-pool/smartnode/releases/latest/download/rocketpool-cli-linux-arm64 -O ~/bin/rocketpool ``` Mark it as executable, so it has permissions to run: ```shell chmod +x ~/bin/rocketpool ``` Next, **log out and log back in** (or close SSH and reconnect), or simply restart. This is because the path that you saved the CLI to (`~/bin`) may not be in your system's `PATH` variable (the list of places your system searches for executables) yet. Logging out and back in will put it there. Now, test running it with the `--version` flag. You should see output like this: ```shell rocketpool --version ``` ```shell rocketpool version 1.24.2 ```

TIP

If you see an error message like this, ```shell -bash: /home/user/rocketpool: cannot execute binary file: Exec format error ``` it means that you downloaded the wrong version above. Please check if your system is **x64** or **arm64** using the command in the tip above, and download the appropriate version. If your system is neither of those, then you will not be able to run Rocket Pool. **MacOS** On macOS, download the CLI for your machine with the following command.

TIP

If you do not know your CPU architecture, you can run the following command to find it: ```shell uname -m ``` The output of this command will print your architecture. **Note that `x86_64` is the same as `x64` and `amd64`.** **Note that `aarch64` is the same as `arm64`.** For `x64` systems (most Macs): ```shell curl -L https://github.com/rocket-pool/smartnode/releases/latest/download/rocketpool-cli-darwin-amd64 > /usr/local/bin/rocketpool ``` For `arm64` systems, such as the Mac mini with M1: ```shell curl -L https://github.com/rocket-pool/smartnode/releases/latest/download/rocketpool-cli-darwin-arm64 > /opt/homebrew/bin/rocketpool ``` For `x64` systems (most Macs): Mark it as executable, so it has permissions to run: ```shell chmod +x /usr/local/bin/rocketpool ``` For `arm64` systems, such as the Mac mini with M1: Mark it as executable, so it has permissions to run: ```shell chmod +x /opt/homebrew/bin/rocketpool ``` Now, test running it with the `--version` flag. You should see output like this: ```shell rocketpool --version ``` ``` rocketpool version 1.24.2 ```

TIP

If you see an error message like this, ```shell /usr/local/bin/rocketpool: Exec format error ``` it means that you downloaded the wrong version above. Please check if your system is x64 or arm64 using the command in the tip above, and download the appropriate version. If your system is neither of those, then you will not be able to run Rocket Pool. ## Installing the Smart Node Stack Now that you have the CLI installed, you can deploy the Smart Node stack. This will prepare your system with Docker, [docker-compose](https://docs.docker.com/compose/), and load the Smart Node files so they're ready to go. It won't actually run anything yet; that comes later. To deploy the Smart Node stack, you will need to run the following command on your node machine (either by logging in locally, or connecting remotely such as through SSH): ```shell rocketpool service install ``` This will grab the latest version of the Smart Node stack and set it up. You should see output like this (_above some release notes for the latest version which will be printed at the end_): ![](/static/image/rp-install-screen.bf1fce7198.png) If there aren't any error messages, then the installation was successful. By default, it will be put into the `~/.rocketpool` directory inside of your user account's home folder. ::: warning NOTE Note that the Smart Node installer cannot install `docker` and `docker-compose` on all platforms automatically. If you receive an error message like this during the installation: ``` Automatic dependency installation for the Mint operating system is not supported. Please install docker and docker-compose manually, then try again with the '-d' flag to skip OS dependency installation. Be sure to add yourself to the docker group with 'sudo usermod -aG docker $USER' after installing docker. Log out and back in, or restart your system after you run this command. ``` Then you simply have to install those two things manually. Docker provides common [install instructions here](https://docs.docker.com/engine/install/). Docker-compose provides common [install instructions here](https://docs.docker.com/compose/install/). Once both are installed, make sure you give your user account permission to use Docker: ```shell sudo usermod -aG docker $USER ``` Finally, re-run the installer with the `-d` flag to skip Docker installation: ```shell rocketpool service install -d ``` ::: After this, **log out and back in or restart your SSH session** for the settings to take effect. Once this is finished, the Smart Node stack will be ready to run. ## Configuring Docker's Storage Location By default, Docker will store all of its container data on your operating system's drive. In some cases, this is not what you want. ::: tip NOTE If you are fine with this default behavior, skip down to the next section. ::: To do this, create a new file called `/etc/docker/daemon.json` as the root user: ```shell sudo nano /etc/docker/daemon.json ``` This will be empty at first, which is fine. Add this as the contents: ```json { "data-root": "/docker" } ``` where `` is the directory that your other drive is mounted to. Press `Ctrl+O, Enter` to save the file, and `Ctrl+X, Enter` to exit the editor. Next, make the folder: ```shell sudo mkdir -p /docker ``` Now, restart the docker daemon so it picks up on the changes: ```shell sudo systemctl restart docker ``` After that, Docker will store its data on your desired disk. ## Configuring the Smart Node Stack The next step in the installation process is to do an initial configuration of your node. Move on to the [Configuring Rocketpool](/node-staking/config/overview.md) section for a walkthrough of this process. --- url: /node-staking/eth-clients.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Choosing your ETH Clients Rocket Pool's Smart Node installer can transform your machine into a full Ethereum node, as it requires both Execution and Consensus clients in order to operate properly. The terms ETH1/ETH2 have been deprecated. The chains will be referred to as the **Execution Layer (ETH1)** and the **Beacon Chain or Consensus Layer (ETH2)** in the rest of these guides. If you already have Execution and Consensus clients up and running on a separate machine (for example, if you're already solo-staking), then skip this section and move onto the [Configuring a Hybrid Rocket Pool Node with External Clients](/node-staking/install-modes.md#the-hybrid-configuration-with-external-clients) section. Otherwise, read on to learn more about your choices for Execution and Consensus clients. ::: warning NOTE As of August 2025, the distribution of clients on the Beacon Chain looks roughly like this: ![](/static/image/ethereum-client-diversity-aug-2025.f6cd5d0bc9.png) _Data obtained from [https://clientdiversity.org](https://clientdiversity.org)_ Obtaining data on which consensus client a validator is running is a relatively difficult problem because clients are not easily identified. The [data methodology](https://clientdiversity.org/methodology/) page on [https://clientdiversity.org](https://clientdiversity.org) goes into how data from different sources are obtained. Feel free to check out [https://ethernodes.org/](https://ethernodes.org/) as an additional source of data. The overwhelming majority of node operators are currently using Geth as an Execution Client and either Lighthouse or Prysm as a Consensus Client. In the interest of supporting the health of the Execution Layer (formerly ETH1) and the Beacon Chain (formerly ETH2), we currently recommend that you consider using different clients. Here are some relevant articles about why an even client diversity is crucial to the health of the network if you would like to learn more: [https://clientdiversity.org/#why](https://clientdiversity.org/#why) [https://blog.ethereum.org/2020/08/21/validated-why-client-diversity-matters/](https://blog.ethereum.org/2020/08/21/validated-why-client-diversity-matters/) [https://our.status.im/the-importance-of-client-diversity/](https://our.status.im/the-importance-of-client-diversity/) [https://medium.com/prysmatic-labs/eth2-mainnet-incident-retrospective-f0338814340c](https://medium.com/prysmatic-labs/eth2-mainnet-incident-retrospective-f0338814340c) [https://dankradfeist.de/ethereum/2022/03/24/run-the-majority-client-at-your-own-peril.html](https://dankradfeist.de/ethereum/2022/03/24/run-the-majority-client-at-your-own-peril.html) [https://eth2book.info/bellatrix/part2/incentives/diversity](https://eth2book.info/bellatrix/part2/incentives/diversity/) ::: For users that would like to get up and running quickly, the Smart Node installer provides a `Random Client` option which may be the best choice. For users that have a specific client they'd like to use in mind, we provide the ability to easily choose one during Rocket Pool's installation. The options below help to describe each client so you can make an informed decision if you'd like to specify which one you want. ## Execution Clients Rocket Pool supports five Execution clients: **Geth**, **Besu**, **Nethermind**, **Reth**, and **Erigon**. Running an Execution client involves storing a copy of the Execution layer blockchain on your machine. It interacts via peer-to-peer communications with other EC nodes to record and verify new blocks and transactions. A full Execution client is **required** to run a validator now that the Execution and Consensus layers have merged. ### Geth [Geth](https://geth.ethereum.org/) (formally named `Go Ethereum`) is one of the three original implementations (along with C++ and Python) of the Ethereum protocol. It is written in Go, fully open source and licensed under the GNU LGPL v3. Geth is the oldest and most widely-used Execution Client around the world. It has a reputation for being very stable and reliable. It is multithreaded, meaning it can take advantage of your entire CPU. Its minimum RAM requirement is 8 GB, but 16 GB is recommended. This makes it viable for low-power systems and high-power systems alike. ::: warning NOTE Geth requires **offline pruning** of its database periodically: its database will grow over time and gradually consume all of your free disk space unless you prune it when your disk runs low on free space. The frequency you need to prune will depend on your SSD's size. For more information on pruning Geth, view the [Pruning the Execution Client](/node-staking/pruning.md) page. ::: ### Besu Hyperledger [Besu](https://besu.hyperledger.org/en/stable/) is an open-source Ethereum client developed under the Apache 2.0 license and written in [Java](https://en.wikipedia.org/wiki/Java_%28programming_language%29). Besu's most exciting features is its use of [Bonsai Tries](https://consensys.net/blog/news/bonsai-tries-a-big-update-for-small-state-storage-in-hyperledger-besu/) for state storage. In addition to their better performance characteristics, Bonsai Tries give Besu two interesting advantages over the other clients: 1. Besu does _not_ need to be pruned at all; it is effectively maintenance-free in that respect 2. Besu is able to revisit any past block in the blockchain, though it does this by rewinding each block so reaching blocks from long ago may take some time. Besu currently recommends at least **16 GB of RAM**, though it is possible to run successfully with 8 GB. ### Nethermind [Nethermind](https://nethermind.io/nethermind-client/) is written in [.NET Core](https://en.wikipedia.org/wiki/.NET). It boasts the fastest sync speed of the Execution clients and has a rich set of configuration options. It is designed with node operators in mind and has many features that they will find helpful. Like Geth, Nethermind requires periodic pruning of its database. Unlike Geth, however, Nethermind's database can [be pruned while it stays online](https://medium.com/nethermind-eth/netherminds-full-pruning-is-here-cutting-the-gordian-knot-5e3450f02de9). This means you do not need to turn your client off and rely on a fallback in order to prune. However, Nethermind's online pruning process is quite resource intensive so users running low-power nodes may see some performance degradation during the process. Nethermind requires **at least 16GB of RAM**, though more is preferable. ::: tip NOTE Nethermind requires periodic pruning of its database periodically: its database will grow over time and gradually consume all of your free disk space unless you prune it when your disk runs low on free space. The frequency you need to prune will depend on your SSD's size. Unlike Geth, however, Nethermind **remains online** while it is pruning. This makes it a compelling choice for nodes because they won't have any down time during pruning. For more information on pruning Nethermind, view the [Pruning the Execution Client](/node-staking/pruning.md) page. ::: ### Reth [Reth](https://reth.rs/) is an Execution layer client written in [Rust](https://www.rust-lang.org/) and uses the [Erigon staged-sync](https://erigon.substack.com/p/erigon-stage-sync-and-control-flows) architecture. Reth is designed from the ground up with efficiency, performance, and modularity in mind. It's licenced under the Apache/MIT permissive license and built with small, well-abstracted, well-tested, and benchmarked packages. This makes for a great open source developer experience and allows Reth's components to be used in other projects. As the newest client in the ecosystem, Reth is rapidly evolving and gaining adoption. While RAM and CPU requirements are flexible, the most important requirement is by far the disk. We suggest using a good [TLC disk](https://gist.github.com/yorickdowne/f3a3e79a573bf35767cd002cc977b038). Reth requires **at least 8 GB of RAM** for a full node or **16 GB of RAM** for an archive node. ### Erigon [Erigon](https://erigon.tech/) is an Execution client written in [Go](https://go.dev/). It uses a staged-sync architecture and can pull snapshots over BitTorrent on first start, which makes initial sync comparatively fast if the torrent port is reachable. In the Settings Manager, Erigon exposes a **Torrent Port** (default `42069`, TCP and UDP) in addition to the usual P2P port (`30303`). Forward both if you want snapshot sync and peering to work well from outside your LAN. Erigon supports **Rolling History Expiry** (drop bodies and receipts older than about one year). It does **not** support pre-merge-only History Expiry; if you pick that mode, it keeps remaining block history with full-mode state pruning. If you run it as a **full node**, it keeps receipts. Like the other clients, RAM needs are flexible and disk quality matters. Open the torrent and P2P ports in your router (and host firewall) the same way you would for Geth's `30303`. ### Client Comparison Table | Client | Type | RAM Usage | | ---------- | ---- | --------- | | Geth | Full | \~8 GB | | Besu | Full | \~10 GB | | Nethermind | Full | \~7-15 GB | | Reth | Full | \~14 GB | | Erigon | Full | \~10 GB | _RAM usage data sourced from [eth-docker](https://ethdocker.com/Usage/ResourceUsage/). Actual usage may vary based on configuration and network conditions._ ## Consensus Clients Rocket Pool's installer is proud to support five currently available Consensus clients: **Lighthouse**, **Lodestar**, **Nimbus**, **Prysm**, and **Teku**. Each of these is a **full client**, meaning you will contribute to the decentralization of the Consensus network regardless of which client you choose. All five clients are quite low-risk, low-maintenance, and will generate practically identical total rewards from validation. They differ slightly in terms of resource requirements and features, but you cannot go wrong with any of them. By default, the Rocket Pool installer will offer to select a random consensus client for you. This will help contribute to the overall **diversity of the network**. This is important from a security perspective: if one client is used by a majority of nodes and suffers from a severe bug or attack, it might cause all of those nodes to fail and thus threaten the entire Beacon Chain's stability. ### Lighthouse [Lighthouse](https://lighthouse.sigmaprime.io/) is an open-source Ethereum 2.0 maintained by [Sigma Prime](https://sigmaprime.io/). It implements the [Ethereum 2.0 specification](https://github.com/ethereum/consensus-specs) as defined by the Ethereum Foundation Research team. Lighthouse is a cutting-edge distributed systems project implementing technologies at the forefront of blockchain research; including proof-of-stake consensus, parallel transaction execution and state separation (sharding). Lighthouse has no official affiliation with the Ethereum Foundation and will continue to follow its guidance as long it is remains in the best interest of the Ethereum protocol and community surrounding it. Lighthouse is implemented in [Rust](https://www.rust-lang.org/) and will maintain a focus on security and efficiency. ### Lodestar [Lodestar](https://lodestar.chainsafe.io/) is the fifth open-source Ethereum consensus client maintained by [ChainSafe Systems](https://chainsafe.io/). Our flagship product is our production-capable beacon chain and validator client for Ethereum consensus. Our software and tooling is uniquely situated as the go-to for researchers and developers for rapid prototyping and browser usage. Millions of developers around the world are familiar with Typescript, and Lodestar's high-quality codebases are excellent introductions to the Ethereum world. Lodestar has also been a leader in light client research, standardization, and implementation of Ethereum light clients. We strive to work with other client implementers, researchers and developers to demonstrate the importance of having browsers utilize trustless data directly from the blockchain. Lodestar's niche is in its implementation language, [Typescript](https://www.typescriptlang.org/). ### Nimbus [Nimbus](https://nimbus.team/) is a client implementation for both Ethereum 2.0 and Ethereum 1.0 that strives to be as lightweight as possible in terms of resources used. This allows it to perform well on embedded systems and resource-restricted devices. If you're planning to run an Execution and Consensus client pair with 16GB total RAM on your node, nimbus is recommended. However, resource-restricted hardware is not the only thing Nimbus is good for. Its low resource consumption makes it easy to run Nimbus together with other workloads on your server (this is especially valuable for stakers looking to lower the cost of their server instances). Nimbus is written in [Nim](https://nim-lang.org/) and maintained by the [Status.im team](https://status.im/about/). ### Prysm The [Prysm](https://docs.prylabs.network/docs/getting-started/#what-is-prysm) project is a full-featured implementation for the Ethereum 2.0 network written entirely in the [Go programming language](https://golang.org/). Created by [Prysmatic Labs](https://prysmaticlabs.com/), Prysm implements the official [Ethereum 2.0 specification](https://github.com/ethereum/consensus-specs), which is the product of an ongoing collective research and development effort by various teams across the Ethereum ecosystem including the [Ethereum Foundation](https://ethereum.org/). ### Teku [Teku](https://docs.teku.consensys.net/en/stable/) (formerly known as Artemis) is a [Java](https://en.wikipedia.org/wiki/Java_%28programming_language%29)-based Ethereum consensus client designed & built to meet institutional needs and security requirements. PegaSys is an arm of [ConsenSys](https://consensys.net/) dedicated to building enterprise-ready clients and tools for interacting with the core Ethereum platform. Teku is Apache 2.0 licensed and written in Java, a language notable for its maturity & ubiquity. ### Client Comparison Table | Client | RAM Usage | Sync Time | | ---------- | --------- | ---------------------------- | | Lighthouse | \~14 GB | Instant with checkpoint sync | | Lodestar | \~12 GB | Instant with checkpoint sync | | Nimbus | \~5 GB | Instant with checkpoint sync | | Prysm | \~9 GB | Instant with checkpoint sync | | Teku | \~10 GB | Instant with checkpoint sync | _RAM usage data sourced from [eth-docker](https://ethdocker.com/Usage/ResourceUsage/). Actual usage may vary based on configuration and network conditions._ --- url: /node-staking/fallback.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Specifying a Fallback Node Starting with **1.5.0** of the Smart Node stack, you can provide a "fallback" Execution client and Consensus client pair that can take over for your primary clients if they ever go offline (such as because [you use Geth and need to prune it](/node-staking/pruning.md)). In this situation, your primary node machine will still be responsible for attesting and proposing blocks with your megapool's validator keys, but it will connect to an external machine to interact with the Execution layer and Beacon chains. Essentially, it allows you to _temporarily_ use another pair of clients for things like querying the chains, sending transactions, and receiving blocks to attest to. This pair can be externally managed (like Hybrid mode), or it can be another Rocket Pool node (another Docker mode machine that has the API ports exposed, which we'll cover below). Once your node's primary clients are back online, the Smart Node and your Validator client will switch back to them automatically. ::: warning NOTE A fallback node is **not** the same as a "backup" node. Fallback nodes have an Execution and Consensus client pair synced to the chain and running, but they **do not** have your node's wallet or its validator keys loaded. If your main node ever goes offline, **your fallback will not start validating for you.** ::: ## Supported Clients As of v1.9.0, all our supported validator clients have added Fallback support with only a few limitations: | Name | Supports Fallback | Valid Fallback Clients | | ---------- | ----------------- | ------------------------------------------------------------------------------ | | Lighthouse | Yes | Any (doppelganger protection off)
Lighthouse (doppelganger protection on) | | Nimbus | Yes | Any | | Prysm | Yes | Prysm | | Teku | Yes | Any | | Lodestar | Yes | Any | ## Setting up a New Node (Docker Mode) You can use a 2nd machine that you own locally, a remote node hosted on a VPS, or a cloud-based node as a fallback node. This example shows you how to create a 2nd Smart Node on a different machine using Docker mode, which can serve as a fallback node. ::: tip TIP If you already have a 2nd node ready and have its RPC ports exposed, feel free to skip this section. ::: 1. Follow the steps in the guide on setting up a node ([local](/node-staking/local/hardware.md) or [remote](/node-staking/vps/providers.md)). 2. Once the machine is ready, [install the Smart Node stack](/node-staking/docker.md). 3. Run `rocketpool service config` to specify which clients you'd like to use. 1. When you get to the end of the wizard and it asks if you'd like to review your settings, select **Yes**. 2. Enter the `Execution Client` settings. 3. Check the `Expose RPC Ports` box: 4. Go back and enter the `Consensus Client` settings. 5. Check the `Expose API Port` box (and, if you're using **Prysm**, the `Expose RPC Port` box as well): 6. Save the settings and start the Smart Node. 4. Skip to the [Securing your Node](/node-staking/securing-your-node.md) guide to set up SSH and the proper security posture on it. 1. If you have `ufw` installed, you will need to add rules to allow incoming traffic to the API ports (`8545`, `8546`, and `5052` by default; also `5053` if you're using **Prysm**). 5. That's it! You can stop here. ::: danger NOTE **Do not** create a wallet with `rocketpool wallet init` or recover your old wallet. Leave this node without a wallet and without validator keys. Its only job is to have a synced Execution client and Consensus client. ::: ## Connecting your Main Node to the Fallback Node Once you have a fallback node prepared, you can connect it to your main node. 1. Enter the `rocketpool service config` TUI and enter the `Fallback Clients` settings. 2. Check the `Use Fallback Clients` box. 3. Enter the RPC URL for your Execution client in the `Execution Client URL` box. For example, if your fallback node's IP address is `192.168.1.45` and you have its Execution client on the default port of `8545`, you would enter `http://192.168.1.45:8545` here. 4. Do the same for the RPC URL of your fallback Consensus client. Following the same example, if you have it on the default port of `5052`, you would enter `http://192.168.1.45:5052` here. 5. Optionally check **Prefer Fallback Clients** (default off). If enabled, the Smart Node will send API, node, and watchtower requests to your fallback Execution and Consensus clients first, and only use the primary pair if the fallback is unavailable. This keeps Smart Node load off the primary clients so they can focus on validator duties. Your Validator Client is not affected and still uses the primary pair first. The final page should look like this: ![](/static/image/tui-fallback-clients.e0a556975d.png) ::: tip NOTE **Native mode** users can follow the same steps, though the TUI will look slightly different from the above screenshot. Note that this will only provide the **Smart Node itself** (the daemon service) with fallback support; **you will have to update your Validator client service's arguments manually to give it access to the fallback clients.** ::: Press `enter` on the final box to ensure that it's confirmed, then save the settings and apply the changes. Once they've been applied, you can confirm the availability of your fallback node using the `rocketpool node sync` command: ``` Your Smartnode is currently using the Ethereum Mainnet. Your eth2 client is on the correct network. Your primary execution client is fully synced. Your fallback execution client is fully synced. Your primary consensus client is fully synced. Your fallback consensus client is fully synced. ``` If it shows that both the fallback Execution and Consensus client are synced, then you're all set! ## Testing the Fallback Clients If you'd like to be absolutely sure that your configuration is going to work by testing the fallback clients, simply stop the Execution and Consensus clients on your main node: ```shell docker stop rocketpool_eth1 rocketpool_eth2 ``` Then run any command that queries the chain, such as `rocketpool network stats`. You will see a warning message at the top indicating that one (or both) of your primary clients are offline, and that it's reverting to the fallback clients: ``` NOTE: primary clients are not ready, using fallback clients... Primary EC status: unavailable (Sync progress check failed with [Post "http://eth1:8545": dial tcp: lookup eth1 on 127.0.0.11:53: no such host]) Primary CC status: unavailable (Sync progress check failed with [Could not get node sync status: Get "http://eth2:5052/eth/v1/node/syncing": dial tcp: lookup eth2 on 127.0.0.11:53: no such host]) ========== General Stats ========== Total Value Locked: 1196.926316 ETH Deposit Pool Balance: 23.586761 ETH Minipool Queue Demand: 0.000000 ETH Deposit Pool ETH Used: 6.809609% ============== Nodes ============== Current Commission Rate: 5.000000% Node Count: 16 Active Minipools: 36 Initialized: 0 Prelaunch: 0 Staking: 36 Withdrawable: 0 Dissolved: 0 Finalized Minipools: 30 =========== Megapools ============ Megapool contracts deployed: 10 Total megapool validators: 86 Staking: 51 In Prestake: 6 In Queue: 10 Exited: 14 Locked: 1 Exiting: 2 Dissolved: 2 ========== Smoothing Pool ========= Contract Address: 0xE8D1136ac49DBe6ac8f299130253004DC63841a1 Nodes Opted in: 3 Pending Balance: 0.000000 ============== Tokens ============= rETH Price (ETH / rETH): 1.185477 ETH RPL Price (ETH / RPL): 0.000639 ETH Total RPL staked: 33406.127068 RPL Total Megapool RPL staked: 11406.127068 RPL Total Legacy RPL staked: 22000.000000 RPL ``` Finally, start your primary clients again: ```shell docker start rocketpool_eth1 rocketpool_eth2 ``` And you're done! Your fallback setup is working. ## Next Steps Whether or not you've opted into creating and/or running a fallback node for your setup, the next step is to learn about **priority fees**. Click on the next section of the guide when you're ready to proceed. --- url: /node-staking/faq.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # FAQ (WIP) ### What are the benefits of running minipools with Rocket Pool compared to a 32 ETH solo validator? By running a single solo validator, you would receive 100% rewards on your 32 ETH. By running two 16 ETH minipools, you would receive 100% rewards on your 32 ETH **plus** 14% of the rewards on 32 ETH provided by the Rocket Pool protocol. By running four 8 ETH minipools, you would receive 100% rewards on your 32 ETH **plus** 14% of the rewards on 96 ETH provided by the Rocket Pool protocol. You would also have the option to use Rocket Pool's [Smoothing Pool](/node-staking/fee-distrib-sp.md#the-smoothing-pool) feature. ### How do I know how much my rETH is worth? Does it rebase? The rETH token will not rebase. The number of tokens on your wallet will remain constant but they appreciate in value over time. ### I have a technical issue running my node, how do I get help? You can start by checking the [Rocket Pool Support](https://rocketpool.support) page. If that doesn't help, you can ask your question on the Rocket Pool **#support** channel in [the Discord server](https://discord.gg/rocketpool). ### How can I get test ETH to experiment with creating and running a minipool? I can't post messages on the faucet channel. See [Getting test ETH on Hoodi](/node-staking/testnet/overview.md#getting-test-eth-on-hoodi). ### How do I recover my node if my machine breaks? Short answer: your mnemonic is all that you need to fully recover your node. Always make sure to keep it safe. To recover your node on a new machine, start by making sure **your previous machine is not going to be online again** with the keys available, as two nodes running with the same keys **will get you slashed**. Follow the [steps](/node-staking/install-modes.md) to install the Smart Node on a new machine. Then, recover your node wallet and validator keys by running the command `rocketpool wallet recover` and insert your 24-word mnemonic. ### Why aren't my clients syncing? I have a low amount of peers. Clients need to have a healthy number of peers to be able to properly sync. You can start by running the test [here](https://www.yougetsignal.com/tools/open-ports/), checking if ports 30303 and 9001 are opened. Your Consensus client also uses UDP port 8001 for QUIC, so forward that one too (this tool only tests TCP). If they're closed, you'll need to setup port forwarding on your router. Also, make sure your node has a static local IP address so the port forwarding does not break due to your node getting a new address. ### My consensus client is taking too long to sync. What should I do? Consensus clients can take a long time to sync if you didn't start the sync process using [Checkpoint Sync](/node-staking/config-docker.md#beacon-chain-checkpoint-syncing). Even if you're running it for a long time, it's usually faster to configure the checkpoint sync URL, clear the current sync data with `rocketpool service resync-eth2` and start over. Your client should be synced in less than a minute. ### I've already rebooted. Why does Grafana say I still need to reboot? The reboot information is cached and only updates every few hours. Running `sudo apt update` will force an update. ### I changed my Execution Layer and/or my Beacon Chain or Consensus Layer. How do I clean out the old data? If you change clients, Rocketpool does not delete the old volumes. This data could be wasting significant disk space and you may want to remove it. To do so, you need to find the volumes. If you are using the default Rocketpool settings, the docker volumes are stored at `/var/lib/docker/volumes/`. The execution layer is in `rocketpool_eth1clientdata/_data/*` and the consensus layer is in `rocketpool_eth2clientdata/_data/*`. To access these directories, you may need to sudo as root using `sudo -i`. Then you can delete a directory by calling `rm -rf `. For example, if you wanted to delete all the geth data, you would call `rm -rf /var/lib/docker/volumes/rocketpool_eth1clientdata/_data/geth/`. To exit as root, type `exit`. --- url: /node-staking/fee-distrib-sp.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Fee Distributors and the Smoothing Pool Node operators receive **priority fees** (**tips**) from the transactions they include in any blocks that they propose to the Ethereum chain. These fees come from and stay on the Execution layer. Unlike most validation rewards which are generated on the Consensus layer and automatically withdrawn periodically, these fees are _immediately liquid_. In general, priority fees provide almost as much ETH to you as Beacon Chain rewards do, so they are a very nice benefit of the Merge. ::: tip NOTE As a quick reminder here's a breakdown of the different types of rewards and which layer they're provided on: - Consensus Layer: attestations, block proposals, sync committees, slashing reports - Execution Layer: priority fees and MEV (discussed in the next section) from block proposals ::: ## Fee Recipients When you propose a block on the Ethereum chain, the protocol needs to know where to send the tips from each transaction included in your block. It can't send them to your validator's address, because that's on the Consensus layer - not the Execution layer. It can't send them to your minipool address, because it has to work for solo stakers too and solo stakers don't have an address on the Execution layer attached to their validators the way Rocket Pool does. Instead, the way it works is fairly straightforward: when Rocket Pool starts up your Validator Client, it passes in an argument called the **fee recipient**. The fee recipient is simply an address on the Execution layer where you want the tips to go. Your node's `fee recipient` can be one of the following special contracts: - Your node's own personal **Fee Distributor** - Your node's megapool contract - The **Smoothing Pool** (opt-in) The Smart Node will automatically set the correct fee recipient based on your configuration: | Smoothing Pool Status | Has Megapool Validators | Has Minipools | Fee Recipient | | --------------------- | ----------------------- | ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Opted In | No | Yes | Smoothing Pool address | | Opted In | Yes | No | Smoothing Pool address | | Opted In | Yes | Yes | Smoothing Pool address (all validators) | | Opted Out | No | Yes | Fee Distributor contract address | | Opted Out | Yes | No | Megapool contract address | | Opted Out | Yes | Yes | Megapool validators → Megapool address
Minipool validators → Fee Distributor address
(Set per validator via [keymanager API](https://ethereum.github.io/keymanager-APIs/#/Fee%20Recipient/setFeeRecipient)) | Rocket Pool is designed to fairly distribute these rewards between you and the rETH pool stakers, the same way it fairly distributes your Beacon chain rewards: your portion of any priority fees your minipool validators earn will go to you (plus the average commission of all of your minipools), and the remaining portion will go to the pool stakers (minus your average commission). The exact portion depends on the number of 8 ETH-bonded, 16 ETH-bonded minipools, and 4 ETH-bonded megapool validators you have. In brief, the **Fee Distributor** is a unique contract attached to your node that collects and fairly splits your priority fees between you and the rETH stakers. It's like your own personal vault for priority fees. Anyone (including you) can distribute its balance at any time to ensure that the rewards are always available to rETH stakers. The **Smoothing Pool** is a special opt-in contract that allows all participating node operators to aggregate and pool their priority fees together, and distributes them evenly among the participants during each Rocket Pool rewards interval (currently every 28 days) and the rETH pool stakers. This is a very compelling feature for node operators that don't want to worry about the luck factor involved in getting block proposals with high priority fees, and would rather have a nice, regular, consistent set of monthly earnings. We'll cover both of these below so you understand the difference and whether or not you want to join the Smoothing Pool. ::: tip NOTE Minipools created after 2024-10-28 used to earn bonus commission (up to 14% in total) through the Smoothing Pool. As defined in [RPIP-62](https://rpips.rocketpool.net/RPIPs/RPIP-62), the bonus ended four rewards intervals after Saturn 1 (the last one was paid in June 2026). These minipools now earn their 5% contract commission, whether or not you are in the Smoothing Pool. ::: ## Your Fee Distributor Your Fee Distributor is a unique contract on the Execution Layer that's **specific to your node**. It will hold all of the priority fees you've earned over time, and it contains the logic required to fairly split and distribute them to the rETH pool stakers and your withdrawal address. This distribution process **can be called by anyone** (including rETH stakers), and can be done **at any time**. If someone other than you distributes it, your share is held as [unclaimed rewards](#claiming-unclaimed-rewards) until you claim it. It does not have a time limit before rewards expire. The address for your node's Fee Distributor is **deterministically based on your node address**. That means it is known ahead of time, before the Fee Distributor is even created. New Rocket Pool nodes will automatically create (initialize) their node's Fee Distributor contract upon registration. This only needs to be run once. One interesting ramification of this is that your Distributor's address may start accruing a balance **before** you've initialized your Fee Distributor contract. This is okay, because your Distributor will gain access to all of this existing balance as soon as you initialize it. ### Viewing its Address and Balance You can view your fee distributor's address and balance as part of: ```shell rocketpool node status ``` The output will look like this: ![](/static/image/status-fee-distributor.ec05f77ee4.png) ### Claiming fees from your Fee Distributor You can claim and distribute the entire balance of your fee distributor using the following command: ```shell rocketpool node distribute-fees ``` This will send your share of the rewards to your **withdrawal address**. ::: warning NOTE ON TAXABLE EVENTS Anyone can distribute your fee distributor (to prevent you from holding rETH rewards hostage). Rocket Pool also distributes it automatically whenever one of your minipools is closed, so that the fees you had accumulated are split using your node's average commission before it changes. You may have a taxable event whenever your fee distributor is distributed. Please keep these conditions in mind when deciding whether or not to use the Smoothing Pool (discussed below). ::: ### Claiming Unclaimed Rewards Your share goes straight to your withdrawal address only when the fee distributor is distributed by your node address or your withdrawal address, for example with `rocketpool node distribute-fees`. Since the Saturn 1 upgrade, when anyone else distributes it (including Rocket Pool itself when you close a minipool), your share is set aside as **unclaimed rewards** instead. Unclaimed rewards do not expire, and only your node address or withdrawal address can claim them. To check for unclaimed rewards and claim them, run: ```shell rocketpool node claim-unclaimed-rewards ``` If you have any, it will show the amount before asking you to confirm the claim: ``` The node's withdrawal address is 0x4ACb4E5E5A9a5EfB1f4D3eE2f6E5A13bB0E8f0a7 You have 0.012345 ETH in unclaimed rewards. Your node 0xE8325F5f4486c2FF2AC7B522Fbc9eB249d46C936 has rewards that were distributed to its unclaimed rewards balance instead of its withdrawal address. This happens whenever your fee distributor is distributed by anyone other than your node or withdrawal address. Claiming will send them to your current withdrawal address. ``` The rewards are sent to your **current** withdrawal address. ### The Penalty System To ensure that node operators don't "cheat" by manually modifying the fee recipient used in their Validator Client, Rocket Pool employs a penalty system. The Oracle DAO are able to penalise node operators that do not follow the protocol rules. If a node is _opted out_ of the Smoothing Pool, the following addresses are considered valid fee recipients: - The rETH address - The Smoothing Pool address - The node's fee distributor contract - The node's megapool contract If a node is _opted in_ to the Smoothing Pool, the following address is considered a valid fee recipient: - The Smoothing Pool address A fee recipient other than one of the valid addresses above is considered to be **invalid**. The Smart Node software automatically sets the correct fee recipient based on your configuration (whether you're opted into the Smoothing Pool, and whether you have megapool validators, minipools, or both). For nodes with both megapool validators and minipools while opted out, the fee recipient is set per validator using the keymanager API. The full list of conditions are summarized [here](/node-staking/fee-distrib-sp.md#fee-recipients). The Smart Node software is designed to ensure honest users will never get penalized, even if it must take the Validator Client offline to do so. If this happens, you will stop attesting and will see error messages in your log files about why the Smart Node can't correctly set your fee recipient. ## The Smoothing Pool The **Smoothing Pool** is a unique opt-in feature of the Rocket Pool network that is available to our node operators. Essentially, it becomes the fee recipient for every node operator that opts into it and collectively accumulates the priority fees from blocks proposed by those node operators into one large pool. During a Rocket Pool rewards checkpoint (the same ones used to distribute RPL rewards), the total ETH balance of the pool is distributed fairly to the pool stakers and the node operators that opted into it. In essence, the Smoothing Pool is a way to effectively eliminate the randomness associated with being selected for block proposals. If you've ever had a streak of bad luck and gone months without a proposal, or if your block proposals only have low priority fees, you may find the Smoothing Pool quite exciting. To make the math easy to understand, community member Ken Smith has put together a [massive analysis](https://raw.githubusercontent.com/htimsk/SPanalysis/main/report/Analysis%20of%20the%20Smoothing%20Pool.pdf) comparing the profitability of the Smoothing Pool and the Fee Distributor, which is summarized nicely with this chart: ![](/static/image/sp-chart.dc5aab244f.png) In short, as long as the Smoothing Pool has more minipools than you do, it's more likely that you'll come out ahead by joining it. ### The Rules The Smoothing Pool uses the following rules: - During a Rocket Pool rewards checkpoint when the Smoothing Pool's balance is distributed between node operators (factoring in their commission), RPL staking node operators, rETH stakers, and potentially the Rocket Pool DAO. The exact percentages are determined by Rocket Pool [Protocol Dao (pDAO) governance](/pdao/overview.md) - Opting into the Smoothing Pool is done on a **node level**. If you opt in, all of your minipools and megapool validators are opted in. - Anyone can opt in at any time. They must wait a full rewards interval (3 days on Hoodi, 28 days on Mainnet) before opting out to prevent gaming the system (e.g. leaving the SP right after being selected to propose a block). - Once opted out, they must wait another full interval to opt back in. - The Smoothing Pool calculates the "share" of each validator (portion of the pool's ETH for the interval) owned by each node opted in. - The share is a function of your validator's performance during the interval (calculated by looking at how many attestations you sent on the Beacon Chain, and how many you missed), and your commission rate. - Your node's total share is the sum of your validator shares. - Your node's total share is scaled by the amount of time you were opted in. - If you were opted in for the full interval, you receive your full share. - If you were opted in for 30% of an interval, you receive 30% of your full share. If you are interested in the complete technical details of Smoothing Pool rewards calculation, please review the [full specification here](https://github.com/rocket-pool/rocketpool-research/blob/master/Merkle%20Rewards%20System/rewards-calculation-spec.md#smoothing-pool-rewards). ### Joining and Leaving the Smoothing Pool To opt into the Smoothing Pool, run the following command: ```shell rocketpool node join-smoothing-pool ``` This will record you as opted-in in the Rocket Pool contracts and automatically change your Validator Client's `fee recipient` from your node's distributor contract to the Smoothing Pool contract. To leave the pool, run this command: ```shell rocketpool node leave-smoothing-pool ``` This will record you as opted-out in the Rocket Pool contracts, and once a small delay has passed, will automatically change your Validator Client's `fee recipient` from the Smoothing Pool contract back to your node's Fee Distributor contract. ### Claiming Rewards from the Smoothing Pool Rewards from the Smoothing Pool are bundled together with RPL at the end of each rewards interval using the Redstone rewards system. Claiming them is as simple as running: ```shell rocketpool node claim-rewards ``` If opted into the Smoothing Pool, you will notice that the amount of ETH you receive for each interval is more than zero: ``` Welcome to the new rewards system! You no longer need to claim rewards at each interval - you can simply let them accumulate and claim them whenever you want. Here you can see which intervals you haven't claimed yet, and how many rewards you earned during each one. Rewards for Interval 0 (2022-08-04 01:35:39 -0400 EDT to 2022-09-01 01:35:39 -0400 EDT): Staking: 50.820133 RPL Smoothing Pool: 0.000000 ETH Rewards for Interval 1 (2022-09-01 01:35:39 -0400 EDT to 2022-09-29 01:35:39 -0400 EDT): Staking: 40.668885 RPL Smoothing Pool: 0.096200 ETH Total Pending Rewards: 91.489018 RPL 0.096200 ETH Which intervals would you like to claim? Use a comma separated list (such as '1,2,3') or leave it blank to claim all intervals at once. ``` Note that the Smoothing Pool rewards in Interval 1 here indicate that the node was opted in during that interval and received rewards accordingly. We'll cover more about claiming RPL and Smoothing Pool rewards later in the guide, in the [Claiming Rewards](/node-staking/rewards.md) section. ## Next Steps Once you've decided on whether or not you want to join the Smoothing Pool, take a look at the next section on MEV and MEV rewards. --- url: /node-staking/grafana.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Setting up the Grafana Dashboard Now that you have your node up and running, you'll probably want to have a convenient way to monitor everything about it at a glance to make sure it's functioning correctly (and what kind of earnings it's generating for you). There are many tools out there that do this job. One of the most popular is called [Grafana](https://grafana.com/) - an easy-to-use, general-purpose dashboard system that you can access with a browser. Rocket Pool comes out-of-the-box with support for Grafana and its dependencies; it even comes with a pre-built dashboard for each of the Consensus clients. For example, here is a snapshot of what the dashboard looks like on the Hoodi test network: ![](/static/image/grafana-1.3.b0fda448f5.jpg) The standard dashboard includes the following information all in a convenient format: - **Top left:** some important statistics about your machine's health and performance, and any pending system updates - **Top right:** the activity and performance of your validators on the Beacon Chain, along with some Execution and Consensus client stats - **Bottom left:** details about the entire Rocket Pool network, for reference - **Bottom right:** details about your staking rewards, both ETH and RPL In this guide, we'll show you how to enable Rocket Pool's metrics system so you can use this dashboard - or even build your own! ## Overview of the Rocket Pool Metrics Stack If you choose to enable metrics during the Smart Node configuration process, your node will add the following processes: - [Prometheus](https://prometheus.io/) - a data collection, storage, and reporting system that captures all of the metrics you see above (any many more) and stores them, so they can be looked at over time - The Prometheus [Node Exporter](https://github.com/prometheus/node_exporter) - a service that collects information about your machine's health (such as CPU usage, RAM usage, free disk space and swap space, etc.) and reports it to Prometheus - Grafana, the tool that exposes Prometheus's data through a convenient website hosted on your node - An optional custom set of scripts that will report any available Operating System updates to Prometheus, so you know if your system needs to be patched The default configuration will create Docker containers with all of these services that live alongside the rest of the Smart Node's Docker containers. It will open up a port on your node machine for Grafana, so you can access its dashboard from any machine on your local network with a browser. ## Enabling the Metrics Server **Docker** Enabling metrics in Docker mode is the easiest of all. Start by running the Smart Node configuration command again: ```shell rocketpool service config ``` Go to the `Monitoring / Metrics` section and check the `Enable Metrics` checkbox. For those who prefer to fine-tune their port settings, you may do so here. Note that all of these ports are restricted to Docker's internal network with the exception of the Grafana port - that will be opened on your machine (so you can access it via a browser from other machines, such as your desktop or phone) so you may want to change that if the default port conflicts with something you already have. Save and exit, and smartnode will start the Prometheus, Node Exporter, and Grafana Docker containers for you. It will also modify your Consensus and Validator clients so they expose their own metrics to Prometheus. The Operating System and Rocket Pool update tracker is **not installed by default** for maximum flexibility, but the process is simple. If you would like to install it so your dashboard shows you how many updates are available for your system, you can do it with this command: ```shell rocketpool service install-update-tracker ``` Under the hood, this will install a service that hooks into your Operating System's package manager, periodically checks for updates, and sends that information to Prometheus. This service is different for every Operating System, but it has been confirmed to work on the following: - Ubuntu 20.04+ - Debian 9 and 10 - CentOS 7 and 8 - Fedora 34

NOTE

Enabling the service automatically is incompatible with SELinux. If your system has SELinux enabled by default (as is the case with CentOS and Fedora), the installation command will get you _most of the way there_ but will also give you instructions on how to finish the process manually at the end. During this check, it will also compare your installed Rocket Pool Smart Node version with the latest release, and inform you if there's a new release available. If you enabled the update tracker, then the last step is to restart the Node Exporter with the following command: ```shell docker restart rocketpool_exporter ``` After that, you should be all set. **Hybrid** Hybrid Mode works similar to Docker Mode; the only difference is that you must manually add the proper command-line flags for enabling metrics to your Execution and Consensus Client service definition. First, we will update your Execution Client. Open the `systemd` unit file you created when you installed your Execution Client and make sure it has the correct flags, based on which client you are running: **Geth** ``` --metrics --metrics.addr 0.0.0.0 --metrics.port 9105 ``` **Nethermind** ``` --Metrics.Enabled true --Metrics.ExposePort 9105 ``` **Besu** ``` --metrics-enabled --metrics-host=0.0.0.0 --metrics-port=9105 ``` Next, we will update your Consensus Client. Open the `systemd` unit file you created when you installed your Consensus Client and make sure it has the correct flags, based on which client you are running: **Lighthouse** ``` --metrics --metrics-address 0.0.0.0 --metrics-port 9100 --validator-monitor-auto ``` **Lodestar** ``` --metrics --metrics.address 0.0.0.0 --metrics.port 9100 ``` **Nimbus** ``` --metrics --metrics-address=0.0.0.0 --metrics-port=9100 ``` **Prysm** ``` --monitoring-host 0.0.0.0 --monitoring-port 9100 ``` If you see the flag `--disable-monitoring`, remove it. **Teku** ``` --metrics-enabled=true --metrics-interface=0.0.0.0 --metrics-port=9100 --metrics-host-allowlist=* ``` If you already have these flags set and are using different ports for your solo validator monitoring, leave them as-is and make note of which ports you're using. Now, scroll up and follow the directions in the `Docker` tab of this section to finish the process - keeping in mind that you must replace the ports listed there with any custom ports you use when you run `rocketpool service config`. **Native** Native installation of Grafana and Prometheus is recommended for advanced users only. It requires Linux administration skills like `systemd`, file permissions, users and network management. First, make sure your Execution Client and Consensus Client have metrics enabled. Refer to 'Hybrid' tab for details. Next, check prebuilt prometheus and node_exporter packages on [the official download page](https://prometheus.io/download/). Choose packages with proper architecture for your platform (amd64 or arm64). Most recent LTS (Long Time Support) version of Prometheus is recommended. For example to download prometheus v2.45.3 LTS and node_exporter v1.7.0 for Linux amd64 with `wget` do: ```shell wget https://github.com/prometheus/prometheus/releases/download/v2.45.3/prometheus-2.45.3.linux-amd64.tar.gz wget https://github.com/prometheus/node_exporter/releases/download/v1.7.0/node_exporter-1.7.0.linux-amd64.tar.gz wget https://github.com/prometheus/alertmanager/releases/download/v0.26.0/alertmanager-0.26.0.linux-amd64.tar.gz ``` Extract prometheus and node_exporter executables from downloaded archives. ```shell sudo tar -zxvf prometheus-2.45.3.linux-amd64.tar.gz -C /usr/local/bin --wildcards '*/prometheus' --strip-components=1 sudo tar -zxvf node_exporter-1.7.0.linux-amd64.tar.gz -C /usr/local/bin --wildcards '*/node_exporter' --strip-components=1 sudo tar -zxvf alertmanager-0.26.0.linux-amd64.tar.gz -C /usr/local/bin --wildcards '*/alertmanager' --strip-components=1 ``` Create directories for prometheus & alertmanager configs. ```shell sudo mkdir /etc/prometheus sudo mkdir /etc/alertmanager sudo mkdir /var/lib/prometheus sudo mkdir /var/lib/alertmanager ``` Create file `/etc/prometheus/prometheus.yml` with following content: ```yaml global: scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute. scrape_timeout: 12s # Timeout must be shorter than the interval evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute. scrape_configs: - job_name: "prometheus" static_configs: - targets: ["localhost:9091"] - job_name: "node" static_configs: - targets: ["localhost:9103"] # - targets: ['localhost:9103', 'node_hostname:9103'] - job_name: "eth1" static_configs: - targets: ["localhost:9105"] # Uncomment the line below if you are using geth as Execution Client #metrics_path: /debug/metrics/prometheus - job_name: "eth2" static_configs: - targets: ["localhost:9100"] - job_name: "validator" static_configs: - targets: ["validator:9101"] - job_name: "rocketpool" scrape_interval: 5m scrape_timeout: 5m static_configs: - targets: ["node:9102"] - job_name: "watchtower" scrape_interval: 5m scrape_timeout: 5m static_configs: - targets: ["watchtower:9104"] alerting: alertmanagers: - static_configs: - targets: ["localhost:9093"] ```

NOTE

Change the port numbers for the Execution Client and Consensus Client if required. You may be running your node on a different host than the host running prometheus change. In that case install node_exporter on your rocketpool node host and update `targets` of the `node` job to include all machines you want to monitor. Also adjust `metrics_path` if your Execution Client is geth - it exposes non-standard endpoint for metrics. Create the `/etc/alertmanager/alertmanager.yml` with the following content. Replace both `webhook_url` values with your own [Discord webhook URL](https://support.discord.com/hc/en-us/articles/228383668-Intro-to-Webhooks): ```yaml global: # ResolveTimeout is the default value used by alertmanager if the alert does # not include EndsAt, after this time passes it can declare the alert as resolved if it has not been updated. # This has no impact on alerts from Prometheus, as they always include EndsAt. # default = 5m resolve_timeout: 5m route: # The labels by which incoming alerts are grouped together. group_by: ["alertname"] # How long to initially wait to send a notification for a group # of alerts. Allows to wait for an inhibiting alert to arrive or collect # more initial alerts for the same group. group_wait: 30s # How long to wait before sending a notification about new alerts that # are added to a group of alerts for which an initial notification has # already been sent. (Usually ~5m or more.) group_interval: 5m # How long to wait before sending a notification again if it has already been sent successfully for an alert. repeat_interval: 4h routes: # severity=info: Don't send the follow-up resolved notification. - match: severity: info continue: false # The notification destination receiver: "node_operator_no_resolved" # all other alerts get sent notifications for the initial firing _and_ resolved notifications. - receiver: "node_operator_default" #match: We want this to match all alerts (severity=info is first though so it will stop) # The notification destination receiver: "node_operator_default" receivers: - name: "node_operator_default" discord_configs: - webhook_url: "https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN" - name: "node_operator_no_resolved" discord_configs: - webhook_url: "https://discord.com/api/webhooks/YOUR_WEBHOOK_ID/YOUR_WEBHOOK_TOKEN" send_resolved: false inhibit_rules: # Inhibit rules mute a new alert (target) that matches an existing alert (source). - source_match: # if the existing alert (source) is severity=critical severity: "critical" target_match: # and the new alert (target) is severity=warning severity: "warning" # and the alertname, job, and instance labels have the same value equal: ["alertname", "job", "instance"] ``` Create system user for prometheus and alertmanager. ```shell sudo useradd -r -s /sbin/nologin prometheus sudo useradd -r -s /sbin/nologin alertmanager ``` Change prometheus/alertmanager files ownership and permissions. ```shell sudo chown prometheus:prometheus /usr/local/bin/prometheus sudo chown alertmanager:alertmanager /usr/local/bin/alertmanager sudo chown prometheus:prometheus /usr/local/bin/node_exporter sudo chown -R prometheus:prometheus /etc/prometheus sudo chown -R alertmanager:alertmanager /etc/alertmanager sudo chown -R prometheus:prometheus /var/lib/prometheus sudo chown -R alertmanager:alertmanager /var/lib/alertmanager sudo chmod u+sx,g+sx,o-wx /usr/local/bin/prometheus sudo chmod u+sx,g+sx,o-wx /usr/local/bin/alertmanager sudo chmod u+sx,g+sx,o-wx /usr/local/bin/node_exporter ``` Create file `/lib/systemd/system/node-exporter.service` for node_exporter service configuration. ``` [Unit] Description=Node metrics exporter for Prometheus Documentation=https://prometheus.io/docs/introduction/overview Wants=network-online.target After=network-online.target [Service] User=prometheus Group=prometheus Type=simple Restart=on-failure WorkingDirectory=/var/lib/prometheus RuntimeDirectory=node-exporter RuntimeDirectoryMode=0750 ExecStart=/usr/local/bin/node_exporter --web.listen-address=:9103 [Install] WantedBy=multi-user.target ```

NOTE

If you want to change the port on which node_exporter is running, modify command at `ExecStart` parameter. Default port is 9100. Create file `/lib/systemd/system/prometheus.service` for prometheus service configuration. ``` [Unit] Description=Prometheus instance Documentation=https://prometheus.io/docs/introduction/overview Wants=network-online.target After=network-online.target [Service] User=prometheus Group=prometheus Type=simple Restart=on-failure WorkingDirectory=/var/lib/prometheus RuntimeDirectory=prometheus RuntimeDirectoryMode=0750 ExecStart=/usr/local/bin/prometheus --config.file /etc/prometheus/prometheus.yml --web.listen-address=:9091 [Install] WantedBy=multi-user.target ```

NOTE

If you want to change the port on which prometheus is running, modify command at `ExecStart` parameter. Default port is 9090. Create file `/lib/systemd/system/alertmanager.service` for the alertmanager service configuration. ``` [Unit] Description=Alertmanager instance Documentation=https://prometheus.io/docs/alerting/latest/alertmanager/ Wants=network-online.target After=network-online.target [Service] User=alertmanager Group=alertmanager Type=simple Restart=on-failure WorkingDirectory=/var/lib/alertmanager RuntimeDirectory=alertmanager RuntimeDirectoryMode=0750 ExecStart=/usr/local/bin/alertmanager --config.file /etc/alertmanager/alertmanager.yml --web.listen-address=:9093 [Install] WantedBy=multi-user.target ```

NOTE

If you want to change the port on which alertmanager is running, modify command at `ExecStart` parameter. Default port is 9093. Let `systemd` know about new services. ```shell sudo systemctl daemon-reload ``` Enable and start node-exporter service. ```shell sudo systemctl enable node-exporter sudo systemctl start node-exporter ``` Check the service status to make sure it's running. ```shell sudo systemctl status node-exporter ``` Enable and start prometheus service. ```shell sudo systemctl enable prometheus sudo systemctl start prometheus ``` Enable and start alertmanager service. ```shell sudo systemctl enable alertmanager sudo systemctl start alertmanager ``` Check the service status to make sure it's running. ```shell sudo systemctl status prometheus sudo systemctl status alertmanager ``` Setup package repository for Grafana. ```shell sudo apt-get update sudo apt-get install -y apt-transport-https software-properties-common sudo mkdir -p /etc/apt/keyrings/ wget -q -O - https://apt.grafana.com/gpg.key | gpg --dearmor | sudo tee /etc/apt/keyrings/grafana.gpg > /dev/null echo "deb [signed-by=/etc/apt/keyrings/grafana.gpg] https://apt.grafana.com stable main" | sudo tee -a /etc/apt/sources.list.d/grafana.list ``` Install Grafana. ```shell sudo apt-get update sudo apt-get install grafana ``` Verify settings in `/etc/grafana/grafana.ini`. Change the `http_port` to 3100 to be in line with the other sections provided in this document. Configure datasource to visualise metrics from Prometheus in Grafana. Create file `/etc/grafana/provisioning/datasources/prometheus.yml`. ```yaml apiVersion: 1 deleteDatasources: - name: Prometheus orgId: 1 datasources: - name: Prometheus type: prometheus access: proxy orgId: 1 url: http://localhost:9091 basicAuth: false isDefault: true version: 1 editable: true ```

NOTE

Edit `url` if you have changed Prometheus listening port. Enable and start service for Grafana. ```shell sudo systemctl daemon-reload sudo systemctl enable grafana-server sudo systemctl start grafana-server ``` Check if Grafana is up and running. ```shell sudo systemctl status grafana-server ``` This is pretty much it. ## Configure firewall to allow connections for monitoring ::: warning NOTE If you have UFW enabled as referenced in the [Securing your Node](/node-staking/securing-your-node.md) section, you will need to open a few ports in order to allow local connections between the Prometheus and your Execution/Consensus Clients. Follow the steps below. ::: **Docker** Run the following, and replace the ports as needed: ```shell RP_NET=$(docker inspect rocketpool_net | grep -Po "(?<=\"Subnet\": \")[0-9./]+") sudo ufw allow from $RP_NET to any port 9105 comment "Allow Prometheus access to Execution Client" sudo ufw allow from $RP_NET to any port 9100 comment "Allow Prometheus access to Consensus Client" sudo ufw allow from $RP_NET to any port 9103 comment "Allow Prometheus access to Exporter" ``` **Native** If your RocketPool node and Prometheus resides on different hosts you need to configure firewall on your node host to allow incoming traffic from Prometheus host IP to the node monitoring ports. You also need to configure UFW on the Prometheus machine to allow for outgoing traffic from the Prometheus host to the RocketPool node host. Having node host IP `192.168.1.5` and Prometheus host IP `192.168.1.6` the UFW rules for the node will be: ```shell sudo ufw allow from 192.168.1.6 to any port 9100:9105 proto tcp comment 'Allow Prometheus host to scrape metrics of this host' ``` And for Prometheus host: ```shell sudo ufw allow out from any to 192.168.1.5 port 9100:9105 proto tcp comment 'Allow this host to scrape node metrics' ``` Assuming your Grafana listening port is 3100, continue reading to find out how to expose Grafana in your network. You can then open the firewall to allow external devices access to your Grafana dashboard. **Network** Use this if you want to access Grafana from any machine inside your local network, but deny access everywhere else. This will be the most common use case. Please check whether your local network uses the `192.168.1.xxx` structure first. You may have to change the command below to match your local network's configuration if it uses a different address structure (e.g. `192.168.99.xxx`). ```shell # This assumes your local IP structure is 192.168.1.xxx sudo ufw allow from 192.168.1.0/24 proto tcp to any port 3100 comment 'Allow grafana from local network' ``` **Subnet** Use this if your Rocket Pool node is not connected to the same subnet as the device from which you are viewing Grafana. This may happen when your node is connected directly to your ISP's modem and the device you use to view Grafana is connected to a secondary router. Please check whether your local network uses the `192.168.1.xxx` structure first. You may have to change the command below to match your local network's configuration if it uses a different address structure (e.g. `192.168.99.xxx`). ```shell # To allow any devices in the broader subnet # for example allowing 192.168.2.20 to access # grafana on 192.168.1.20 sudo ufw allow from 192.168.1.0/16 proto tcp to any port 3100 comment 'Allow grafana from local subnets' ``` **Anywhere** This will let you access Grafana from anywhere. If you want to access it from outside your local network, you will still need to forward the Grafana port (default 3100) in your router settings. ```shell # Allow any IP to connect to Grafana sudo ufw allow 3100/tcp comment 'Allow grafana from anywhere' ``` ## Setting up Grafana Now that the metrics server is ready, you can access it with any browser on your local network. Refer to the tabs below for your Smart Node installation mode. Navigate to the following URL, substituting the variables with your setup as necessary: ``` http://: ``` For example, if you node's IP was `192.168.1.5` and you used the default Grafana port of `3100`, then you would go to this URL in your browser: ``` http://192.168.1.5:3100 ``` You will see a login screen like this: ![](/static/image/grafana-login.a147466227.png) The default Grafana information is: ``` Username: admin Password: admin ``` You will then be prompted to change the default password for the `admin` account. Pick something strong and don't forget it! ::: tip Tip If you lose the admin password, you can reset it using the following command on your node: **Docker and Hybrid Mode** ```shell docker exec -it rocketpool_grafana grafana-cli admin reset-admin-password admin ``` **Native** ```shell sudo grafana-cli admin reset-admin-password admin ``` You will be able to log into Grafana using the default `admin` credentials once again, and then you will be prompted to change the password for the `admin` account. ::: Thanks to community member **tedsteen**'s work, Grafana will automatically connect to your Prometheus instance so it has access to the metrics that it collects. All you need to do is grab the dashboard! ## Importing the Rocket Pool Dashboard Now that you have Grafana attached to Prometheus, you can import the standard dashboard (or build your own using the metrics that it provides, if you are familiar with that process). Start by going to the **Create** menu (the plus icon on the right-side bar) and click on **Import**: ![](/static/image/grafana-import.510b12f441.png) When prompted for the dashboard ID in the **Import via grafana.com** box, enter `24900` or use the full URL ([https://grafana.com/grafana/dashboards/24900-rocket-pool-dashboard-v1-4-0/](https://grafana.com/grafana/dashboards/24900-rocket-pool-dashboard-v1-4-0/)) and press the **Load** button. You will be prompted with some information about the dashboard here, such as its name and where you'd like to store it (the default **General** folder is fine unless you use a lot of dashboards and want to organize them). Under the **Prometheus** drop-down at the bottom, you should only have a single option labeled **Prometheus (default)**. Select this option. Your screen should look like this: ![](/static/image/grafana-import2.178729ca7e.png) If yours matches, click the **Import** button and you will be immediately taken to your new dashboard. ::: tip NOTE Smart Node v1.23.0 ships **Rocket Pool Dashboard v1.4.2** with its metrics stack. That revision adds node-scoped minipool and megapool validator counts by status and drops network-wide megapool status panels that depended on removed supply-collector metrics. If your Grafana already imported an older dashboard, re-import (or load the JSON provisioned with Smart Node) so those panels match the metrics your node exports. ::: At first glance, you should see lots of information about your node and your validators. Each box comes with a handy tooltip on the top left corner (the `i` icon) that you can hover over to learn more about it. For example, here is the tooltip for the **Your Validator Share** box: ![](/static/image/tooltip.73fa921575.png) However, we aren't done setting things up yet - there is still a little more configuration to do. ::: warning NOTE Some of the boxes (notably the APR ones) have been temporarily disabled due to the way Shapella provides skimmed rewards. They will be enabled again in a future version of the Smart Node that can track historical rewards properly. ::: ## Tailoring the Hardware Monitor to your System Now that the dashboard is up, you might notice that a few boxes are empty such as **SSD Latency** and **Network Usage**. We have to tailor the dashboard to your specific hardware so it knows how to capture these things. ### CPU Temp To update your CPU temperature gauge, click the title of the **CPU Temp** box and select **Edit** from the drop down. Your screen will now look something like this: ![](/static/image/cpu-temp.21ed27d7a2.png) This is Grafana's edit mode, where you can change what is displayed and how it looks. We're interested in the query box highlighted in red, to the right of the **Metrics browser** button. By default, that box has this in it: ``` node_hwmon_temp_celsius{job="node", chip="", sensor=""} ``` There are two fields in this text that are currently blank: `chip` and `sensor`. These are unique to each machine, so you'll have to fill them in based on what your machine provides. To do this, follow these steps: 1. Remove the `, sensor=""` portion so it ends with `chip=""}`. For clarity, the whole thing should now be `node_hwmon_temp_celsius{job="node", chip=""}`. 2. Put your cursor in-between the quote marks of `chip=""` and press `Ctrl+Spacebar`. This will bring up an auto-complete box with the available options, which looks like this: ![](/static/image/grafana-autocomplete.f020d2bd2b.png) 3. Select the option that corresponds to your system's CPU. 4. Once that's selected, add `, sensor=""` back into the string. Place your cursor in-between the quote marks of `sensor=""` and press `Ctrl+Spacebar` to get another auto-complete menu. Select the sensor you want to monitor. ::: tip Tip If you don't know which `chip` or `sensor` is correct, you'll have to try all of them until you find the one that looks right. To help with this, install the `lm-sensors` package (for example, `sudo apt install lm-sensors` on Debian / Ubuntu) and run the `sensors -u` command to provide what sensors your computer has. You can try to correlate a chip ID from Grafana's list with what you see here based on their names and IDs. For example, this is one of the outputs of our `sensors -u` command: ``` k10temp-pci-00c3 Tctl: temp1_input: 33.500 Tdie: temp2_input: 33.500 ``` In our case, the corresponding chip in Grafana is `pci0000:00_0000:00:18_3` and the corresponding sensor is `temp1`. ::: Once you're happy with your selections, click the blue **Apply** button in the top right corner of the screen to save the settings. ::: warning NOTE Not all system expose CPU temperature info - notably virtual machines or cloud-based systems. If yours doesn't have anything in the auto-complete field for `chip`, this is probably the case and you won't be able to monitor your CPU temperature. ::: ### SSD Latency The **SSD Latency** chart tracks how long it takes for read/write operations to take. This is helpful in gauging how fast your SSD is, so you know if it becomes a bottleneck if your validator suffers from poor performance. To update the SSD you want to track in the chart, click on the **SSD Latency** title and select **Edit**. This chart has four query fields (four textboxes) with eight `device=""` portions in total. You'll need to update the first four of these portions with the device you want to track. Simply place your cursor in-between the quote marks and press `Ctrl+Spacebar` to get Grafana's auto-complete list, and select the correct option from there for each of the `device=""` portions. **You want to start from the leftmost empty setting first, or the auto-complete list may not appear.** ::: tip Tip If you don't know which device to track, run the following command: ``` lsblk ``` This will output a tree showing your device and partition list, for example: ``` NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT ... loop25 7:25 0 132K 1 loop /snap/gtk2-common-themes/9 loop26 7:26 0 65,1M 1 loop /snap/gtk-common-themes/1515 nvme0n1 259:0 0 238,5G 0 disk ├─nvme0n1p1 259:1 0 512M 0 part /boot/efi ├─nvme0n1p2 259:2 0 150,1G 0 part / ├─nvme0n1p3 259:3 0 87,4G 0 part └─nvme0n1p4 259:4 0 527M 0 part ``` If you didn't change Docker's default location to a different drive during your Smart Node installation, then the disk you want to track will be the one that your Operating System is installed on. Look in the `MOUNTPOINT` column for an entry simply labeled `/`, then follow that back up to its parent device (the one with `disk` in the `TYPE` column). Typically this will be `sda` for SATA drives or `nvme0n1` for NVMe drives. If you _did_ change Docker's default location to a different drive, or if you're running a hybrid / native setup, you should be able to use the same technique of "following the mount point" to determine which device your chain data resides on. ::: Optionally, you can also track latency of a second disk on your system. This is aimed at people that keep their Operating System and chain data on separate drives. To set this up, simply follow the instructions above for the last two query fields, substituting `device=""` portion values with those of the disk you want to track. Once you're happy with your selections, click the blue **Apply** button in the top right corner of the screen to save the settings. ### Network Usage This chart tracks how much data you're sending and receiving over a particular network connection. As you might expect, the dashboard needs to know which network you want it to track. To change it, click on the **Network Usage** title and select **Edit**. This chart has two query fields with two `device=""` portions in total. You'll need to update these with the network you want to track. Place your cursor in-between the quote marks and press `Ctrl+Spacebar` to get Grafana's auto-complete list, and select the correct option from there for each of the `device=""` portions. ::: tip Tip If you don't know which device to track, run the following command: ```shell sudo route ``` The output will look something like this: ``` Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.1.1 0.0.0.0 255.255.255.255 UH 100 0 0 eth0 ``` Look at the `Destination` column for the row with the value if `default`. Follow that row all the way to the `Iface` column. The device listed there is the one you want to use - in this example, `eth0`. ::: Once you're happy with your selections, click the blue **Apply** button in the top right corner of the screen to save the settings. ### Total Net I/O This tracks the total amount of data you've sent and received. You might find it useful to watch if, for example, your ISP limits you to a certain amount of data per month. The setup is identical to the **Network Usage** box above, so simply follow those instructions for this box too. ### Disk Space Used This keeps tabs on how full your Operating System disk is getting, so you know when it's time to clean up (and if your chain data lives on the same drive, time to [prune Geth or Nethermind](/node-staking/pruning.md)). The steps are the same as the **SSD Latency** box above, so simply follow those instructions for this box too. As a reminder, you want the drive that houses the partition which has `/` in the `MOUNTPOINT` column for this one because that will be your Operating System drive. Fill this into the first query field. Optionally, you can also track the free space of a second disk on your system. This is aimed at people that keep their Operating System and chain data on separate drives. Set this up by following the same process, but instead of looking at which partition has `/` in the `MOUNTPOINT` column, you want to look for the one that has whatever your second drive's mount point is. Update the second query field with the disk associated with that partition. ### Disk Temp This tracks the current temperature of your Operating System disk. The steps are the same as the **CPU Temp** box above, so simply follow those instructions for this box too, substituting CPU chip and sensor values with those of your Operating System disk. Fill these values into the first query field. Optionally, you can also track the current temperature of a second disk on your system. Set this up by following the same process, substituting the chip and sensor values with those of your second drive. Fill these values into the second query field. ## Customizing the Dashboard While the standard dashboard tries to do a good job capturing everything you'd want to see at a glance, it's quite easy to customize a Grafana dashboard however you want. You can add new graphs, change the way graphs look, move things around, and much more! Take a look at [Grafana's Tutorials](https://grafana.com/tutorials/) page to learn how to play with it and set it up to your liking. ## Customizing the Metrics Stack The tools used in the Rocket Pool Metrics Stack offer a wide array of configuration options beyond what is included in the default Rocket Pool installation. This section includes configuration examples for different use cases. In general, [Grafana configuration options](https://grafana.com/docs/grafana/latest/administration/configuration/) should be passed through using environment variables in `override/grafana.yml`. Any config option can be converted to an environment variable using the following syntax: ``` GF__ ``` ### Grafana SMTP Settings for Sending Emails To send emails from Grafana, e.g. for alerts or to invite other users, SMTP settings need to be configured in the Rocket Pool Metrics Stack. See the [Grafana SMTP configuration](https://grafana.com/docs/grafana/latest/administration/configuration/#smtp) page for reference. **Docker and Hybrid Mode** Open `~/.rocketpool/override/grafana.yml` in a text editor. Add an `environment` section below the `x-rp-comment: Add your customizations below this line` line, replacing the values below with those for your SMTP provider. ```yaml version: "3.7" services: grafana: x-rp-comment: Add your customizations below this line environment: ## SMTP settings start, replace values with those of your SMTP provider - GF_SMTP_ENABLED=true - GF_SMTP_HOST=mail.example.com:`port` # Gmail users should use smtp.gmail.com:587 - GF_SMTP_USER=admin@example.com - GF_SMTP_PASSWORD=password - GF_SMTP_FROM_ADDRESS=admin@example.com - GF_SMTP_FROM_NAME="Rocketpool Grafana Admin" ## SMTP server settings end ``` **Native** Open `/etc/grafana/grafana.ini` in a text editor. Look for `[smtp]` section and update it, replacing the values below with those for your SMTP provider. ``` [smtp] enabled = true host = mail.example.com:`port` # Gmail users should use smtp.gmail.com:587 user = admin@example.com # If the password contains # or ; you have to wrap it with triple quotes. Ex """#password;""" password = """passw0rd""" from_address = admin@example.com from_name = "Rocketpool Grafana Admin" ``` ::: tip Tip If using Gmail and [2-Step Verification](https://support.google.com/accounts/answer/185839) is enabled, create an [App Password](https://support.google.com/mail/answer/185833?hl=en) for this service. ::: After making these modifications, **run the following to apply the changes**: **Docker and Hybrid Mode** ```shell docker stop rocketpool_grafana rocketpool service start ``` **Native** ```shell sudo systemctl restart grafana-server ``` To test the SMTP settings, go to the **Alerting** menu and click **Contact points**. ![](/static/image/grafana-contact-points.44edb2444b.png) Click **New contact point** and select **Email** as the Contact point type. Enter an email address in the **Addresses** section and click **Test**. ![](/static/image/grafana-new-contact-point.76b7b4e494.png) Check to see that the test email was received. Click **Save contact point\*** when finished. --- url: /node-staking/install-modes.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Selecting a Rocket Pool Mode Rocket Pool's Smart Node stack is quite flexible; there are several different ways to run it. It can stand up an entire full node from scratch, it can integrate with existing Execution or Consensus client deployments, and it can even run natively as a set of system services. In this section, we will cover the typical ways of configuring and using the Smart Node stack. ## The Default Docker-Based Configuration The default mode, and the most common way to run a Smart Node, is to have it create an entire full node instance on your local machine that Rocket Pool manages. To accomplish this, the Smart Node uses [Docker containers](https://www.docker.com/resources/what-container). In essence, a Docker container is a small sandbox that comes pre-configured with a program, all of its dependencies, and all of the configuration needed to run correctly. When it's no longer needed, it can simply be thrown away. It's a nice little self-contained bundle that lets things work without making a mess of your actual filesystem or other programs. This mode is what the Smart Node Installer will deploy for you. It uses the following Docker containers: - `rocketpool_node` - This is a background process that will periodically check for and claim RPL rewards after a reward checkpoint (if you have auto-claim enabled, more on this later), and is responsible for actually staking new validators when you create a minipool. - `rocketpool_watchtower` - This is used by Oracle Nodes to perform oracle-related duties. For regular node operators, this will simply stay idle. - `rocketpool_eth1` - This will be your Execution client. - `rocketpool_eth2` - This will be your Consensus beacon node client. - `rocketpool_validator` - This will be your Validator client, which is responsible for your validator duties (such as attesting to blocks or proposing new blocks). In most situations, this is a good option to choose when creating a new node from scratch. It's the fastest, most hands-off procedure. It will also handle updates to the Execution and Consensus clients with every new Smart Node release, so you don't have to worry about them (though you can manually upgrade them at any time if you desire). ::: warning NOTE Currently, some of the Docker containers need to run as the `root` user to function correctly. While Docker containers are generally quite good at preventing a user from escaping into your main Operating System, you may not be comfortable with this requirement for security reasons. In this case, we suggest you use the Native configuration mode listed below. ::: If you would like to use this mode, proceed to the [Configuring a Standard Rocket Pool Node with Docker](/node-staking/docker.md) section. ## The Hybrid Configuration with External Clients The hybrid configuration is well-suited for users that are interested in running a Rocket Pool node, but already have their own Execution and/or Consensus clients running for other purposes (for example, because they're already solo-staking). In this mode, Rocket Pool will deploy Docker containers for its own processes and for a Validator client it manages, but will ignore the Execution client and Beacon Node containers for whichever external clients you already run and maintain. **As Rocket Pool will be creating and maintaining new validator keys for each of your node's minipools, it is important that it runs its own Validator client.** When using this configuration, the Smart Node will use the following Docker containers (which were described above): - `rocketpool_node` - `rocketpool_watchtower` - `rocketpool_validator` The `rocketpool_eth1` and `rocketpool_eth2` containers will either be included or excluded, depending on which clients you already have running externally. If you would like to use this mode, proceed to the [Configuring a Standard Rocket Pool Node with Docker](/node-staking/docker.md) section. When prompted to choose a management mode for your Execution and/or Consensus clients, choose the **Externally Managed** option which is described in detail within that section. ## The Native Configuration without Docker This configuration bypasses Docker entirely. Instead of running the Smart Node stack via Docker, each process will be installed as a local system service (e.g. via `systemd`). This includes the `node`, `watchtower`, `eth1`, `eth2`, and `validator` processes. This configuration offers the most flexibility because it allows you to fine-tune Rocket Pool's parameters (such as its security posture, where the Execution and Consensus clients live, where the chain data lives, where your keys live, and so on). It is also the most difficult to set up and maintain. In this mode, the Smart Node Installer is no longer relevant. You are responsible for manually instantiating, maintaining, and upgrading the Smart Node infrastructure, the ETH clients, and the validator clients. ::: danger WARNING While we provide some example documentation on how to do this, we suggest that this mode should only be used by **experienced system administrators**. ::: If you would like to use this mode, proceed to the [Configuring a Native Rocket Pool Node without Docker](/node-staking/native.md) section. --- url: /node-staking/installing/overview.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Overview In this section, you'll learn how to install the Rocket Pool Smart Node stack onto your node machine. There are several different flavors of installation; you'll learn which one is right for you and walk through the installation process for it. ## Prerequisites Before diving into this section, please make sure you've: - Picked a node machine (local hardware or virtual server) - Set up the Operating System on it - Configured a remote control system such as [SSH](/node-staking/ssh.md) - Secured it by following the [Securing your Node](/node-staking/securing-your-node.md) guide ## Guides [Choosing your ETH Clients](/node-staking/eth-clients.md) presents the various options for Ethereum clients - both on the Execution Layer (formerly ETH1) and the Consensus Layer (formerly ETH2). You'll need one of each in order to run your node, and this section will help you choose which ones you'd like to run. [Selecting a Rocket Pool Mode](/node-staking/install-modes.md) will show you the different modes the Rocket Pool Smart Node can be installed with and will help you pick the mode that's best for you. [Creating a Standard Rocket Pool Node with Docker](/node-staking/docker.md) will walk you through the installation process for **Docker Mode** and **Hybrid Mode**. [Creating a Native Rocket Pool Node without Docker](/node-staking/native.md) will walk you through the installation process for **Native Mode**. --- url: /node-staking/leb-migration.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. ::: danger WARNING Minipool deposits are currently disabled in preparation for Saturn 1. ::: # Migrating a 16-ETH Minipool to 8-ETH Node operators have the ability to **directly migrate** their existing 16-ETH minipools into 8-ETH minipools. Doing so will add 8 ETH to their [deposit credit balances](/node-staking/credit.md) which can be used to **create additional minipools without requiring any ETH from the node operators**. In effect, this process allows a node operator to **convert one 16-ETH minipool into two 8-ETH minipools for free** (_though it will still require ETH for gas and require enough RPL collateral to handle both minipools_). Migrating an existing 16-ETH minipool to an 8-ETH one is formally known as **bond reduction**. It is a two-step process and involves validation by the Oracle DAO. We'll walk you through the whole process in the sections below. ### Bond Reduction Rules A bond reduction involves the following steps: 1. Starting the bond reduction, done by the node operator. 2. A waiting period (the "bond reduction scrub check"), allowing the Oracle DAO time to verify the bond reduction is legal and cancel any bond reductions that violate the rules. 3. Completing the bond reduction, done by the node operator. To perform a successful bond reduction without being scrubbed, the minipool must follow these rules: 1. The minipool must be upgraded to the [Atlas delegate](/node-staking/minipools/delegates.md); the old Redstone delegate cannot be used. 2. The minipool's validator on the Beacon Chain must be **pending or actively staking**. It cannot be slashed, exiting / exited, or withdrawable / withdrawn. 3. The minipool's validator balance on the Beacon Chain must be **at least 31.99 ETH** (32 ETH with a small buffer for poorly-timed complications resulting in missed attestations after a rewards skim). The minipool must obey these conditions for the **entire duration** of the scrub check, during which time the Oracle DAO will be watching it to ensure compliance with the conditions above. If, at any time during the scrub check, a minipool is found to be in violation of these conditions, the bond reduction will be **scrubbed**. The minipool itself will not be affected; it will still happily live on as a 16 ETH minipool, validating and acting as though the whole bond-reduction process never happened. However, **it will no longer be eligible for bond reductions**. Once a minipool's bond reduction is scrubbed, it can never be attempted again. ::: warning NOTE Upon a successful bond reduction, the minipool's bond amount will be reduced from 16 ETH to 8 ETH and **the minipool's commission will be reset to whatever the current network value is**. If you reduce a 16-ETH minipool with a 20% commission, **you will not keep that 20% commission**. It will be reduced to the network value (**currently set to a flat 14%**). Note that as demonstrated by the [example math](/node-staking/create-validator.md) section, an 8-ETH minipool at 14% is _still more profitable_ than a 16-ETH minipool at 20% so holding onto a high commission rate is not a compelling reason to retain a 16 ETH bond. ::: ### Step 1: Beginning Bond Reduction To begin the bond reduction process, enter the following command: ```shell rocketpool minipool begin-bond-reduction ``` This will start by providing a brief blurb on the process (though, if you have read through this guide, it should all be familiar to you already). Once you acknowledge that you understand the process, it will show you which minipools currently have a bond that can be reduced, along with their current bond and commission: ``` Please select a minipool to begin the ETH bond reduction for: 1: All available minipools 2: 0x7E5703fdA638CD86c316B9EbAF76927fF695ADC5 (Current bond: 16 ETH, commission: 15.00%) 3: 0x7E5704aD2a63eb90880426Dcd4a3811246dF3cB0 (Current bond: 16 ETH, commission: 15.00%) 4: 0x7E5705c149D11efc951fFc20349D7A96bc6b819C (Current bond: 16 ETH, commission: 15.00%) 5: 0x7E570625cE8F586c90ACa7fe8792EeAA79751778 (Current bond: 16 ETH, commission: 15.00%) ``` Once you've selected one or more minipools to reduce, the Smart Node will check if those minipools are eligible for bond reduction. To be eligible, these conditions must be satisfied: - The minipool has been upgraded to use the [Atlas minipool delegate contract](/node-staking/minipools/delegates.md). - The minipool's validator must have a Beacon Chain balance of at least 32 ETH. - The minipool's validator must be pending or active. - You have enough RPL staked to support the minimum RPL collateral level that would be required _after_ the bond reduction. If not, it will print a warning error explaining what needs to be done first; for example: ``` Please select a minipool to begin the ETH bond reduction for: 1: All available minipools 2: 0x7E5703fdA638CD86c316B9EbAF76927fF695ADC5 (Current bond: 16 ETH, commission: 15.00%) 3: 0x7E5704aD2a63eb90880426Dcd4a3811246dF3cB0 (Current bond: 16 ETH, commission: 15.00%) 4: 0x7E5705c149D11efc951fFc20349D7A96bc6b819C (Current bond: 16 ETH, commission: 15.00%) 5: 0x7E570625cE8F586c90ACa7fe8792EeAA79751778 (Current bond: 16 ETH, commission: 15.00%) 2 Cannot reduce bond for minipool 0x7E5703fdA638CD86c316B9EbAF76927fF695ADC5: The minipool version is too low. It must be upgraded first using `rocketpool minipool delegate-upgrade`. You do not have enough RPL staked to support this bond reduction; it would bring you below the minimum RPL staking requirement. You will have to stake more RPL first. ``` This shows that the selected minipool requires a delegate upgrade and the node needs more RPL staked in order to reduce that minipool's bond. When you have satisfied the preconditions, selecting a minipool in this command will simply prompt you to choose your gas price for the transaction and confirmation of the action. Upon accepting the confirmation, the minipool's bond reduction will begin. ### Monitoring the Scrub Check Timer Once you've started a bond reduction, you can view how long until it's able to be completed in your `node` daemon logs: **Docker and Hybrid Mode** For **Docker Mode** and **Hybrid Mode** users, this can be done with the following command: ```shell rocketpool service logs node ``` **Native Mode** Consult the script you use to review your node daemon's system logs. You will see a new entry noting how much time is left until the scrub check for your bond reduction is complete: ``` rocketpool_node | 2023/02/25 09:04:21 Checking for minipool bonds to reduce... rocketpool_node | 2023/02/25 09:04:21 Minipool 0x7E5703fdA638CD86c316B9EbAF76927fF695ADC5 has 12m0s left until it can have its bond reduced. ``` Once this timer reaches zero and no longer appears in these logs, you can complete the bond reduction. ### Step 2: Completing Bond Reduction When the scrub timer has successfully ended, there are two ways to complete your minipool's bond reduction: 1. Let the `node` daemon handle it for you; it does this during the routine check it performs every five minutes (the same one that prints the time-remaining line in the log above). If it notices you have an eligible bond reduction, **it will complete the reduction automatically** - just as it does with staking pending minipools and checking your fee recipient. You will see output in the `node` log showing when it has detected, and completed, a bond reduction. 2. Complete the bond reduction manually using the following command: ```shell rocketpool minipool reduce-bond ``` The command is simple; follow the prompts to complete the process once your minipool is eligible for bond reduction. During the bond reduction, Rocket Pool **distributes your minipool's existing balance** using the minipool's pre-bond-reduction bond and commission to ensure both you and the rETH stakers get your fair share of the existing balance, and the bond reduction doesn't change the rewards either party _would_ have gotten on that balance. ### The Results of a Reduced Bond You can verify the successful bond reduction using `rocketpool minipool status`. **Before** the bond reduction, for the example minipool we've been following, that command would produce the following output: ``` Address: 0x7E5703fdA638CD86c316B9EbAF76927fF695ADC5 ... Node fee: 15.000000% Node deposit: 16.000000 ETH RP ETH assigned: 2023-02-08, 06:13 +0000 UTC RP deposit: 16.000000 ETH Minipool Balance (EL): 0.150713 ETH Your portion: 0.086660 ETH Available refund: 0.000000 ETH Total EL rewards: 0.086660 ETH ... Beacon balance (CL): 32.000152 ETH Your portion: 16.000087 ETH ... ``` **After** the bond reduction, the command would return this output: ``` Address: 0x7E5703fdA638CD86c316B9EbAF76927fF695ADC5 ... Node fee: 14.000000% Node deposit: 8.000000 ETH RP ETH assigned: 2023-02-08, 06:13 +0000 UTC RP deposit: 24.000000 ETH Minipool Balance (EL): 0.086769 ETH Your portion: 0.000000 ETH Available refund: 0.086769 ETH Total EL rewards: 0.086769 ETH ... Beacon balance (CL): 32.000037 ETH Your portion: 8.000013 ETH ... ``` Note how things have changed: - `Node fee` (commission) went from 15% to 14% - `Node deposit` (your bond) went from 16 ETH to 8 ETH - `RP deposit` (the amount you borrowed) went from 16 ETH to 24 ETH - `Minipool Balance (EL)` went from 0.150713 ETH to 0.086769 ETH - `Your portion (EL)` went from 0.086660 ETH to 0 ETH - `Available refund` went from 0 ETH to 0.086769 ETH - `Your portion (CL)` went from 16.000087 ETH to 8.000013 ETH The changes to `Node fee`, `Node deposit`, `RP deposit`, and `Your portion (CL)` indicate that the bond was successfully reduced. The changes to `Minipool Balance (EL)`, `Your portion (EL)`, and `Available refund` indicate the results of the **minipool balance distribution** that occurred as part of the bond reduction process. To clarify how to interpret these results: - If you look at [the transaction](https://zhejiang.beaconcha.in/tx/0xf02f6b1a4ea68f356909e6f1974dc3c24d301ba115b97f3013c3c829ba2ca57c), you will also see that it sent 0.06413383 ETH from the minipool to the staking pool. - In the "before" example, the staking pool's share is the minipool's balance minus the node operator's portion, or `0.150713 - 0.086660 = 0.064053` which is the amount transferred to the staking pool during the bond reduction (plus a small amount from a rewards skim that occurred during the scrub check). - The _node operator's_ share, on the other hand, doesn't get sent to the node operator's withdrawal address. It is instead bookmarked as an **available refund**, which is why the refund amount increased from 0 ETH to what was previously the "your portion" amount of the minipool's balance on the EL. - You can claim this refund at any time using the following command: ```shell rocketpool minipool refund ``` There is one more important result of the bond reduction, which can be observed using `rocketpool node status`: ``` Your Smartnode is currently using the Zhejiang Test Network. === Account and Balances === The node 0x9BA1401Eb7D779eC51f910B066e9C4351cD28911 has a balance of 347.796908 ETH and 16799.835547 RPL. The node has 8.000000 ETH in its credit balance, which can be used to make new minipools. ``` The bond reduction process has **increased the node's** [deposit credit balance](/node-staking/credit.md) by 8 ETH. This credit can be used to [make another 8-ETH minipool](/node-staking/create-validator.md#depositing-eth-and-creating-a-minipool) for free (no ETH required from the node wallet, except for gas)! --- url: /node-staking/local/hardware.md --- > For AI agents: the complete documentation index is available at /llms.txt, the full documentation bundle is available at /llms-full.txt. # Selecting Staking Hardware There are no official specifications for running a Rocket Pool node. This page offers some guidelines and examples that you can use to select staking hardware. The minimum hardware requirements of your node will depend on the Consensus and Execution clients that you choose. If, for example, you intend to run your node on a low powered device, you may be limited to using `Geth` as your Execution client and `Nimbus` as your Consensus client. If you're using a more powerful NUC with 32+ GB of RAM, all client combinations are open to you. The guidelines below assume you want a **comfortable** level of hardware, meaning you have excess capacity. If you keep these guidelines in mind, your node will have plenty of resources to run any of the Rocket Pool supported client combinations. This will allow you to choose a `random` client pair, which is very important for client diversity on the Ethereum network. ::: tip NOTE Ethereum staking is very forgiving. If your house is flooded and your staking device is fried, there is no big penalty for taking a week to get back up and running (unless you happen to be in a sync committee, which is a very rare event). Component failure might happen at some point, but don't stress about it. Downtime does not get you slashed unless you are offline during a major outage of the entire Ethereum network. ::: ## Hardware Requirements Ethereum validators are not very computationally expensive, which is to say that once your Execution and Consensus clients are running, any additional validator will use **a very small amount of additional resources**. This grows up to 64 validators, at which point the resources required for adding a 65th validator and beyond are negligible. In our experience, most setups, including mini-PCs and NUCs, are capable of running an effectively unlimited number of validators. ### CPU Requirements **Guideline: any modern CPU with at least 4 threads.** Running a Rocket Pool node is not very computationally intensive. The biggest impact of the CPU is how fast your node can initially sync the state of the blockchain when you first create it (or if you ever change clients later). After the initial sync, the CPU is not used as heavily. CPU naming can be deceptive; an Intel Core i5 from 2010 is usually **less powerful** than a core i3 from 2022. Many community members use Intel NUC devices because of their small form factor, but an old i5 NUC may be a worse choice than a new i3. For this reason, we recommend using a "modern" CPU that is, at most, a few years old. More specifically, **for x64-based CPUs**, we recommend a CPU that supports the [BMI2](https://en.wikipedia.org/wiki/X86_Bit_manipulation_instruction_set#BMI2_\(Bit_Manipulation_Instruction_Set_2\)) extension - check the manufacturer's specs for your CPU to see if it is supported. Not all modern CPUs support this; for example, Celeron CPUs tend not to include it. ARM-based CPUs (such as the Mac M1 or M2, or the Rock 5B) do not apply to the BMI2 extension above. ::: tip NOTE If you are interested in using a NUC, you can tell how modern the NUC is by its model number. They are formatted as `NUC` + `generation number` + `model` + `CPU type` + `suffix`. For example, a `NUC11PAHi50Z` unit is a 11th generation i5 unit. You can see a list of NUCs [here](https://www.intel.com/content/www/us/en/products/details/nuc/kits/products.html) on the Intel website. Other mini-PCs, such as the Asus PN50 or PN51, do not follow this convention but information about which CPU is used by them should be included in their product pages. ::: The amount of cores on a CPU is less relevant than its **number of threads**. We recommend a **minimum of 4 threads** for Rocket Pool node operation. A 2 core CPU with 4 threads will work without issue. It is rare to find a CPU with only 2 threads. ### RAM Requirements **Guideline: at least 16 GB of RAM, 32 GB preferred, DDR4 preferred** Rocket Pool nodes can operate with as little as 16 GB of RAM. We generally recommend having slightly more to offer some headroom and full support for RAM-heavy clients such as Teku. An added benefit of more RAM is that you can provide a larger cache size to Execution client, which tends to slow the rate of your disk space usage. ### SSD Requirements **Guideline: a 2+ TB SSD that has TLC or better, with a DRAM cache. NVMe preferred.** This element is more important than most people expect. The Execution client relies heavily on IOPS, or "operations per second"; we recommend 15k Read IOPS, and 5k Write IOPS In practice, this means that: - HDD (spinning platter) drives will not work - SATA or external USB 3.0+ SSDs _can_ work - NVMe SSD drives are preferred If you already have an SSD you want to use and want to be sure it has sufficient performance for node operation. _\* If you are unsure if your disk meets these performance requirements, `fio` is a good way to test them. See [here](https://arstech.net/how-to-measure-disk-performance-iops-with-fio-in-linux/) for Linux instructions, and [here](https://www.nivas.hr/blog/2017/09/19/measuring-disk-io-performance-macos/) for MacOS instructions._ :::tip NOTE SSD selection can be a complex choice! The method SSDs use to store data on their flash chips has a noticeable impact on speed and longevity. When shopping for an SSD you might notice labels like `QLC`, `TLC` or `SLC`. These stand for the amount of data contained within a single cell of the flash chip: `Q` for "quad" means 4, `T` for "triple" means 3, `M` for "multi" means 2, and `S` for "single" means 1. We recommend **TLC, MLC, or SLC** drives. We **do not recommend QLC drives** due to their slower performance and lower total reliability. SSDs come with or without DRAM, which is a hardware element that makes accessing data on the SSD more efficient. Those with DRAM are faster but those without DRAM are cheaper. However, DRAM is quite important for providing smooth node operation. We recommend a drive with a **DRAM** cache. We **do not recommend DRAM-less drives**. ::: The final consideration is drive size. As of 4/2026, the `geth` execution client database size requires about 1.2TB of space after it finishes its initial sync (or after you just finished pruning it). This will grow steadily over time, and while pruning can regain some of that space, the freshly pruned state _does_ grow over time. You will have peace of mind with a larger drive. The size of this database can be reduced if you [decide to not to store history before the merge](/node-staking/maintenance/history-expiry.md). ### Common Accessories Many node operators improve their setups beyond the minimum requirements. Some common additions include: - SSD heatsinks to extend the drive lifespan - Uninterruptable power supplies (UPS) in case of power outages - A fallback node to have a backup in case something fails These are all convenient to have, but not required to run a Rocket Pool node. ## Example Setups In this section, we'll showcase a few of the varied builds that Rocket Pool's community has created for themselves. They are examples of what people are using, not recommendations for how you should run your setup. Note that many are somewhat outdated and, eg, use SSDs that are now too small. ### Xer0's Server ![](/static/image/Xer0.d2ed387786.jpg) Discord user **Xer0** is among the many stakers that opted to go with a conventional PC form factor for their staking machine. They wanted to build a rig that would last for years and years to come with minimal maintenance and upgrading required, while still offering complete customization of every component. To that end, Xer0 devised and built a full ATX server - much like a traditional desktop PC, but targeted exclusively at staking on Ethereum. Their setup includes a six-core Xeon Bronze 3204 (1.9 GHz), 8 DDR4 slots, and an M.2 slot... though since this is essentially a home server build, the exact components are completely up to the end user. Xer0's setup: - Motherboard: [Supermicro X11SPI-TF](https://www.newegg.com/supermicro-mbd-x11spi-tf-o-intel-xeon-scalable-processors-single-socket-p-supported-cpu-tdp-suppor/p/1B4-005W-00153) ($440) - CPU: [Xeon Bronze 3204](https://www.amazon.com/Intel-BX806954216-Bronze-1-9GHz-FC-LGA14B/dp/B07RTBMWVJ) ($248) - RAM: [NEMIX 2x32GB DDR4 ECC 2933MHz](https://www.amazon.com/2x32GB-DDR4-2933-PC4-23400-Registered-Memory/dp/B07V1YG2VV) ($359) - SSD: [Sabrent 2TB Rocket M.2 2280 SSD](https://www.newegg.com/sabrent-rocket-2tb/p/14R-00X6-00007) ($250) - Case: [SilverStone HTPC ATX GD07B](https://www.amazon.com/dp/B007X8TQW0) ($172) - PSU: [EVGA SuperNova 650 G3, 80+ Gold](https://www.newegg.com/evga-supernova-g3-series-220-g3-0650-y1-650w/p/N82E16817438094) ($111) - Cooler: [Noctua NH-D9 DX-3647 4U](https://www.amazon.com/Noctua-NH-D9-DX-3647-4U-Premium/dp/B07DPQJH5J) ($100) - **Total: $1680** Here are Xer0's comments on why they chose this setup: _Obviously there is no need to build a monstrosity for simply staking on the Ethereum network, but I do have a few reasons why I built something like this._ 1. _Now I believe that 1 or more validators in the future will be worth much more than what we are seeing right now, so I wanted to buy something that will be able to support the network for at least the next 10-20 years without a hiccup._ 2. _By creating a machine that has at this many cores I've also given myself a lot more headroom to the point of I could run an L2 aggregator on top of this without any problems (regarding hardware) and anything else that I'd want to run on a server._ :) 3. _I like building computers, and so I built it…_ 4. _With a server build, It gives me a lot more flexibility with hardware and features that most computers don't have natively._ 5. _A bit of future proof (just in-case)_ :wink: ### Darcius's Shelf Rig ![](/static/image/Darcius.55ffafa2f5.jpg) Rocket Pool's founder David Rugendyke (known on Discord as **darcius**) spent a long time perfecting his node. After some debate, he built a Mini-ITX that's small and portable, but still packs an enormous amount of processing power. His rig includes an 8-core Ryzen 7 5800x (3.8 GHz), two DDR4 slots, and two M.2 slots for NVMe SSDs. It is truly one of the most high-performance rigs of the Rocket Pool nodes, but with good reason: darcius runs a special type of Rocket Pool node called an Oracle Node, which relays information from the Beacon chain back to the Execution chain about all of the Rocket Pool validators. With thousands of Rocket Pool minipools active to watch, that job takes a lot of horsepower... but his shelf rig is easily up to the task. Darcius's setup: - Motherboard: [MSI MPG B550I Mini-ITX AMD](https://www.newegg.com/msi-mpg-b550i-gaming-edge-wifi/p/N82E16813144323) ($200) - CPU: [AMD Ryzen 7 5800x](https://www.newegg.com/amd-ryzen-7-5800x/p/N82E16819113665) ($490) - RAM: [Corsair Vengeance RGB Pro 2x16GB DDR4 3600MHz](https://www.newegg.com/p/0RN-00P8-000A5) ($390) - SSD: [Samsung 970 EVO Plus 2TB M.2 2280 NVMe SSD](https://www.newegg.com/samsung-970-evo-plus-2tb/p/N82E16820147744) ($315) - Case: [SilverStone SST-SG13B Mini-ITX](https://www.amazon.com/SilverStone-Technology-Mini-ITX-Computer-SST-SG13WB-USA/dp/B07MNC3JCB) ($52) - PSU: [SilverStone Strider Platinum 550W](https://www.newegg.com/silverstone-strider-platinum-series-ps-st55f-pt-550w/p/N82E16817256154) ($140) - **Total: $1587** ### Yorick's microATX Build ![](/static/image/Yorick-stock.900c0ac9f0.jpg) Veteran hardware enthusiast **YorickDowne** has a lot of experience building and maintaining servers. Using that knowledge, he has settled on a flexible microATX setup. His machine is considerably smaller than a typical PC, but still manages to fit in server-grade technology that maximizes resilience and uptime - key metrics when running a Rocket Pool node. He has recommendations for both Intel and AMD setups, which you can find [on his website](https://eth-docker.net/docs/Usage/Hardware). The Intel version uses a quad core i3-9100F (3.6 GHz) or a Xeon CPU, and the AMD version suggests any Ryzen CPU that supports ECC memory. For both configurations, he suggests 16 GB of ECC RAM, and a 1 TB NVMe SSD. Yorick's Setup: - Motherboard: [SuperMicro X11SCL-F-O](https://www.newegg.com/supermicro-mbd-x11scl-f-o-8th-generation-intel-core-i3-pentium-celeron-processor-intel-xeon-pro/p/N82E16813183671) ($200) - CPU: [Intel i3-9100F](https://www.newegg.com/intel-core-i3-9th-gen-core-i3-9100f/p/N82E16819118072) ($150) - RAM: [Samsung 1x16GB DDR4 ECC UDIMM 2400MHz](https://www.newegg.com/samsung-16gb-288-pin-ddr4-sdram/p/1WK-002G-00080) ($100) - SSD: [Samsung 970 EVO Plus 1TB M.2 2280 NVMe SSD](https://www.newegg.com/samsung-970-evo-plus-1tb/p/N82E16820147743?Item=N82E16820147743) ($165) - Case: [SilverStone Micro ATX HTPC Case ML04B-USA](https://www.amazon.com/Silverstone-Technology-Aluminum-Center-ML04B-USA/dp/B07PD8CL7P/) ($110) - PSU: Any (example: [Seasonic PRIME Fanless PX-500 Platinum 500W](https://www.newegg.com/seasonic-prime-fanless-px-500-500w/p/N82E16817151234)) ($161) - Case fans: Any - **Total: About $886** Here are Yorick's comments on why he chose this setup: - _It is at the same or lower cost as some NUCs_ - _It has ECC RAM, which means that if memory fails - which it does now and then - I will know, because the system will tell me. I do not have to run memtest87 for 4-5 days to figure out whether my problem with instability is even memory-related. I protect my time fiercely so I can spend it bloviating on Discord instead of troubleshooting hardware_ - _It has IPMI, which is remote management via Ethernet/browser of the entire machine, including UEFI and power-cycle. I should be allowed to go on an extended vacation and still have full remote access._ - _If I want redundant storage so eventual SSD failure is a non-event, I can do that_ - _It allows for great flexibility in build choices. I can choose however much RAM and compute I want; I can choose to run a NAS with virtualization tech like TrueNAS Scale and run the node on there alongside some other home-servery stuff._ ### Drez's Laptop ![](/static/image/Drez.a1b0b8dc8b.jpg) Sometimes, shelling out for new hardware just doesn't make sense. In Discord user **Drez**'s case, running a Rocket Pool node is one of those times. Drez happened to have a spare laptop lying around, and they turned it into a node with ease. Their machine comes with a quad core i7-4710HQ (2.5 GHz), two DDR3 slots, and a 2.5" SATA slot. Being a laptop, it also comes with its own battery (which offsets the need for a UPS). They added some additional upgrades over time, giving the laptop even more power for extra peace of mind. Drez's setup: - Laptop: [MSI GE70 2PE Apache Pro](https://www.msi.com/Laptop/GE70-2PE-Apache-Pro/Specification) ($1800) - RAM: 2x8GB DDR3 1333Mhz (Included) - SSD: [Samsung 860 EVO 1TB 2.5" SATA](https://www.amazon.com/Samsung-Inch-Internal-MZ-76E1T0B-AM/dp/B078DPCY3T) ($110) - **Total: $1910** Here are Drez's comments on why they chose this setup: _Main reason i am gonna stake on this laptop is because i already had spare one and dont need to spend extra money on a new server. I like its mobility, compactness, built-in screen for easy monitoring. In case of overheating i bought a laptop cooling pad and spare CPU cooler just in case, i also recommend to change thermal compound paste especially if you're gonna run on an older machine_ ## NUCs (Next Unit of Computing) and Mini-PCs Running a Rocket Pool node doesn't necessarily require a complete build-it-yourself desktop. In fact, one of the most popular setups among stakers is the illustrious NUC. A NUC (Next Unit of Computing) is essentially a small, self-contained computer that is designed around very low power usage and maximum efficiency. NUCs are great for most stakers that only run a few validators because of their low maintenance, low monthly running costs, and ease of setup. Unlike PCs, NUCs come preassembled in a case; all you need to do is add some RAM, add an SSD, and you're up and running! Below are a few examples of NUC setups that some Rocket Pool veterans use and recommend. ::: tip NOTE **Ethernet Adaptor Compatibility** If you're planning to buy an Intel® NUC 11th or 12th Generation you can encounter connectivity issues with the ethernet adaptor, specifically if the adaptor is identified as **I225-LM** (Check intel especifications before buying). If you already have one, there are steps you can take to address this concern. The I225-LM adaptor has been associated with certain compatibility challenges that may lead to **system freezes** and unexpected kernel behavior, particularly when using Linux kernels. To determine if your NUC employs the problematic I225-LM ethernet adaptor, you can use the following command in the terminal: ```shell sudo lshw -class network | grep 225 ``` If the output confirms the presence of the I225-LM adaptor, you might experience the mentioned issues. However, there are _remedies_ you can apply to mitigate these problems: **USB-C to Ethernet Adaptor**: A viable solution involves acquiring a USB-C to Ethernet adaptor and connecting your internet cable through this external adaptor. While this approach requires additional hardware and configuration, it has proven effective in resolving the compatibility conflicts. This allows you to utilize the latest available Linux kernels without encountering the freezing or kernel-related anomalies associated with the I225-LM adaptor.**This is the recommended solution (for now) if you already have one NUC with the I225-LM** _Keep in mind that opting for an adaptor may introduce a trade-off in terms of potential latency or reduced internet velocity. To mitigate this impact, it's advisable to select an adaptor with at least 1GB/s portability, thereby helping maintain optimal data transfer rates._ **Driver and Software Updates**: Consider updating your drivers, firmware, and BIOS by referring to the official Intel® support page for your NUC model [here](https://www.intel.com/content/www/us/en/search.html?ws=text#sort=relevancy\&f:@tabfilter=\[Downloads). This might include using the latest available support driver from Intel's website or applying BIOS updates that address compatibility concerns. **Intel's Patch (Windows)**: Intel has released a patch to address a similar issue on Windows systems. While the patch itself **may not directly apply to Linux environments**, it highlights the recognition of the problem by Intel and their efforts to provide solutions. You can find more details about the patch in this [link](https://www.intel.com/content/www/us/en/download/705968/patch-for-a-modern-standby-lan-issue-on-intel-nuc-11th-12th-generation-products.html?wapkw=nuc11tnhi3). Keep in mind that technology evolves, and solutions might change over time. Always stay updated with the latest resources provided by Intel for your specific NUC model on their official Downloads [page](https://www.intel.com/content/www/us/en/search.html?ws=text#sort=relevancy\&f:@tabfilter=\[Downloads]). By following these steps, you can address the compatibility challenges associated with the I225-LM ethernet adaptor on Intel® NUC 11th and 12th Generation Products, ensuring a smoother and more reliable experience with your server deployment. _While a subset of NUC users with this adaptor have reported experiencing no issues, it's important to note that the **majority of users**, particularly after a kernel upgrade, have encountered problems. Notably, the 5.15.+ kernels have proven to be the most stable option for those using the I225-LM adaptor. If the idea of using a USB-C adaptor isn't appealing and you're willing to take the risk of potential random freezes, it's advisable to **remain on a kernel version that has demonstrated greater stability**._ ::: ### Ken's NUC8i5BEK ![](/static/image/Ken.e2a6dbb2cd.jpg) The NUC8i5BEK is one of Intel's own NUCs with an 8th-generation processor. Released in 2018, this model comes with a quad-core i5-8259U CPU (2.30 GHz), two DDR4 slots, an M.2 slot for SSDs, and USB 3.1 ports. It normally draws about 20 watts, but Discord user **Ken** has been able to optimize it down to 9 watts during normal validation. It is more than capable of handling any Execution and any Consensus client, making it an excellent choice for a lightweight, efficient node machine. Ken's Setup: - Base: [Intel NUC8i5BEK](https://www.amazon.com/Intel-NUC-Mainstream-Kit-NUC8i5BEK/dp/B07GX67SBM) ($349) - RAM: [Dell Memory Upgrade - 1x16GB DDR4 SODIMM 3200MHz](https://www.dell.com/en-us/shop/dell-memory-upgrade-16gb-1rx8-ddr4-sodimm-3200mhz/apd/ab371022/memory) ($112) - SSD: [ADATA XPG S7 Series 2TB M.2 2280 NVMe SSD](https://www.amazon.com/XPG-S7-Gen3x4-Solid-State/dp/B08BDZQJP5) ($230) - Fanless Case (optional): [AKASA Turing Fanless case](https://www.amazon.com/Akasa-Compact-fanless-Generation-NUC45-M1B/dp/B07RTBF1SY) ($134) - **Total: $691 to $825** Here are Ken's comments on why he chose this setup: - _Small size and footprint, the power supply is a brick on the power cord (like a laptop), single-board computer, x86 architecture, low purchase price point, low power consumption (\~10W), 3-year warranty, and an active manufacture product line (Intel)._ - _8th generations are plenty fast and at a lower price point than the latest generation chips._ - _I upgraded to a fan-less (passively cooled) case, so the NUC is absolutely silent (0 dB) as I’m leaving it my home office (a stock NUC is near silent already)._ - _Plus no mechanical wear on the fan bearings._ - _Resale or re-purpose value if I decide to retire this hardware platform as my RP node - NUC’s make a great workstation computer._ ### GreyWizard's NUC10i7FNH ![](/static/image/GreyWizard.8c7c47b713.jpg) The NUC10i7FNH is another one of Intel's own NUCs. This one sports a 10th-generation processor, and was released in 2019. It comes with a six core i7-10710U CPU (1.10 GHz, boosts to 4.7 GHz), two DDR4 slots, an M.2 slot and a 2.5" slot for SSDs, and USB 3.1 ports. It draws about 20 watts of power. It is an incredibly powerful machine, given its power consumption and size. Discord user **GreyWizard** uses this NUC for his node - the extra power gives him peace of mind knowing that no matter what the future of the Ethereum 2.0 chain holds, his machine will be able to handle it. GreyWizard's Setup: - Base: [Intel BXNUC10I7FNH1](https://www.newegg.com/intel-bxnuc10i7fnh1/p/N82E16856102227) ($445) - RAM: 2x [Samsung M471A4G43MB1 32GB DDR4 SODIMM 2666 MHz](https://www.newegg.com/samsung-32gb-260-pin-ddr4-so-dimm/p/0RM-002H-00156) ($154 ea.) - SSD: [Samsung 970 EVO Plus 2TB M.2 2280 NVMe SSD](https://www.newegg.com/samsung-970-evo-plus-2tb/p/N82E16820147744) ($315) - **Total: $1068** Here are GreyWizard's comments on why he chose this setup: _I went with the i7 NUC mostly because it felt like the best combination of outstanding performance relative to overall size and overhead. I also looked at other options like building a Micro ATX-sized machine. After pricing one with the specs I was looking for, this Intel NUC ended up being about the same price, and the form factor is really tough to beat. I like having the extra headroom for performance/peace of mind, and I acknowledge that this is almost certainly way overkill. I consider staking as a serious investment and I don't want to worry if my hardware will be sufficient._ _Tips for other people considering this as an option..._ - _The NUC does run pretty warm, similar temps to a laptop. If you worry about CPU temp and you want something powerful, then you should look at small desktop setups like Micro ATX._ - _You will want to make sure there is plenty of room around your NUC for airflow. Plan to clean the area regularly to prevent dust buildup._ - _Make sure to check compatibility for your RAM cards. The different NUCs support varying degrees of total RAM, RAM speeds, etc._ - _If you go with the NUC, I'd suggest you give yourself room to grow when selecting RAM... For example, spend a bit extra and get a single 32gb RAM card rather than 2x16 so you can expand later if you want (assuming your NUC will support 64gb in this example)_ - _Feel free to reach out to me on Discord if you would like to discuss._ ### ArtDemocrat's NUC10i5FNHN Build Process Video To complement Greywizard's setup descriptions and tips, ArtDemocrat created this build process video as an additional help resource to set up a NUC10 (in this case a NUC10i5FNHN, but the build process should be similar for a NUC10i7FNH):