# Starting Rocket Pool and Setting Up a Node Wallet

At this point, you should have the complete Rocket Pool infrastructure running, including the Smartnode stack, an Execution (ETH1) and an Consensus (ETH2) client. You should also have hardened your operating system from outside attackers. If you've completed both of these steps, you're ready to create a Rocket Pool node and begin staking. If not, please review the previous sections and return here once you've completed those steps.

# Starting and Stopping the Rocket Pool Services

# Confirming the Correct Version and Network

Once the containers or services are up, a good first step is to confirm that you have the correct versions of the clients and are on the network that you expect. You can do this with the following command:

rocketpool service version

The output will look like this (note that you may have a newer version than what is displayed here, this is just an example):

Your Smartnode is currently using the Ethereum Mainnet.

Rocket Pool client version: 1.6.4
Rocket Pool service version: 1.6.4
Selected Eth 1.0 client: Geth (Locally managed)
        Image: ethereum/client-go:v1.10.25
Selected Eth 2.0 client: Lighthouse (Locally managed)
        Image: sigp/lighthouse:v3.1.0

The first line will tell you if your Smartnode is configured for the Ethereum mainnet or for the Prater testnet.


For Docker / Hybrid users: If you are not on the network you expect to be on, go back to the Installing Rocket Pool section and review the installation instructions - you may have missed the portion that has different instructions depending on which network you want to use.

For Native users: If you accepted the default settings when you first ran rp service config, then it's possible that the network reported here is incorrect. Simply switch it in the rp service config TUI, in the Smartnode section, to the proper network and restart your node and watchtower services.

The second set of lines will tell you which clients you're using, and which versions of them are defined in Rocket Pool's configuration.

# Checking the Service Status and Logs

Now that the Smartnode services have been started, it's a good idea to check that they're running correctly without errors.


When you're done looking at the logs, you can exit and return to the command prompt using Ctrl + C.

# Setting up a Wallet

If the Smartnode services are up and running, the next step is to set up an ETH1 wallet for your node. This is simply an ETH1 address that will hold your node's funds - it will use this to send ETH to your minipool when you begin staking, pay for gas during various transactions, and other various operations.

You have the option of either creating a brand new wallet from scratch, or importing / recovering an existing wallet or address. Please choose which option you'd like from the tabs below.


As of the current build, Rocket Pool needs to have access to your wallet's private key in order to perform its automatic duties. This means that the private key will exist in a file on your machine. If an attacker manages to gain access to your machine, they could gain access to your node wallet and steal all of the tokens that it contains! Please ensure that you have followed the security guide in the Securing your Node section before you continue, and are comfortable with your security posture.

# Waiting for Your ETH Clients to Sync

Now that you have a wallet set up, you're going to want to wait until your Execution (ETH1) and Consensus (ETH2) clients have finished syncing with the network before proceeding.

One easy way to check on their status is with the following command:

rocketpool node sync

This command will show how far along your Execution (ETH1) & Consensus (ETH2) clients are in the syncing process, similar to this:

$ rocketpool node sync

Your Smartnode is currently using the Prater Test Network.

Your eth2 client is on the correct network.

Your primary execution client is fully synced.
You do not have a fallback execution client enabled.
Your consensus client is still syncing (99.69%).

You can call this occasionally to keep tabs on your clients' progress.

To get an actual ETA of the sync time, it's easiest to look at the logs for your clients with rocketpool service logs eth1 and rocketpool service logs eth2 respectively (or the equivalent log script commands if you're using the hybrid / native modes.) Each client typically provides an ETA on its sync status in its log output.


It can take days to fully sync both ETH1 and ETH2 depending on your client selection and your machine's hardware profile. This is expected. Sit back, relax, and wait for both of them to finish.

# Next Steps

Once you've imported or recovered your node wallet and your clients are done syncing, follow the next steps in the Intro to the Command Line Interface guide.