Development Update — 6th Feb, 2020 – Rocket Pool
To begin, let’s recap what is to be a smart node operator in Rocket Pool during Ethereum 2.0. Users who wish to stake their own ETH in Rocket Pool, but not run a node, will need node operators to do their staking for them. These stakings users may be customers of a business, exchange or any other service which has registered a group in the Rocket Pool network and been on-boarded through it. Or they might be just regular users who do not have the time, skills or minimum amount of ETH required to run a node themselves.
Thee node operators who receive these deposits for staking, might be staking as a service companies or just about anyone and they’ll be spread far and wide in the Rocket Pool network. Currently we have a command line interface (CLI) package which we used in our last beta. Command lines aren’t for everyone though and one thing that a lot of Web3 Dapps really need is a good user interface (GUI) to make interacting with the Dapp a smooth experience and we’re no exception to this.
Above you can see an early work in progress design and flow for the GUI. Each screen is aiming to be simple and easy to follow. This should hopefully allow future node operators run their smart nodes even easier than it is now with the CLI.
Besides a simple user interface, the GUI has some extra features that the CLI doesn’t, this mostly relates to easier monitoring and the ability to install the Rocket Pool Smart Node Stack on remote servers.
Connection Manager and Remote Installs
Not only will you be able to install locally on your current computer, but you’ll also be able to deploy smart nodes on single or multiple remote servers at once using SSH in the background. Simply add a new remote connection, then install to it and monitor it all from another computer, neat!
Configure Your Node
Once installed on a local or remote server, the Rocket Pool smart node stack will need to be configured. This will entail selecting which ETH1 client you’d like to use (Geth/Parity/Infura — Light client) and which ETH2 client you’d like to use that is supported Rocket Pool (Prysmatic Labs, Lighthouse etc).
As briefly mentioned above, we’re providing Infura support in the way of an ETH1 light client. This greatly reduces the resources required for a node as the ETH1 clients are dealing with the current main chain and its long history. But it does mean you’d be entrusting Infura with your ETH1 connection, so that might be a trade off for those of you who want total control.
Once installed on a local or remote server and configured, the Rocket Pool smart node stack will begin and the first thing it will do, is to sync the current ETH1 and ETH2 chains. This can take a while depending on your connection, but it can be easily monitored via the GUI and once it’s completed, you’ll be greeted with the main server dashboard. The blockie shown below is your nodes main ETH1 account that is created for it upon install.
Server – Dashboard
Once the Ethereum chains are synced, you’ll be able to see the server dashboard which gives an overview of your current node. From the top you’ll see your current nodes ETH and token balances, a graph of your current servers resources (HDD, CPU and MEM) and a graph of the resources that the Rocket Pool smart node stack is using + all the validators currently running on it (see M1, M2, M3 etc — these are our minipool validators). The menu at the bottom provides access to other main areas with more detailed information on the server, the stack and help in using the GUI.
Server — Details
It’s important to know how your server is running if you want to be a good smart node operator, so if you click on the server icon on the main menu, you’ll get more detailed information into just what’s happening. You’ll also be able to run custom commands from the GUI and view the output for those more advanced users.
Server — Rocket Pool Stack Details
Like above, you can view extra details on the current Rocket Pool stack that is running. This most importantly includes seeing what minipool validators are running on the node and their status. If any of those minipool boxes are clicked, you’ll be taken to the minipool manager screen which is also shown below.
The main graph on this screen shows the capacity of the Rocket Pool network and below that a sub-menu which allows you to cast votes for what you think node operators should charge for users who stake on their node, view the logs from the stack and the ability to stop the stack service running.
Release and Platform Support
The initial release of the Smart Node GUI is planned for our next beta which we’re targeting for early Q2. This initial release will be aiming to support Linux (Ubuntu + possible other flavours) and MacOSX. Windows 10 that has WSL2 installed might see an experimental release shortly after, depending on how testing goes with WSL2 once it is released.
Published at Thu, 06 Feb 2020 10:37:44 +0000
{flickr|100|campaign}
