Under the Surface 020#

Date: 25.11.2022
Under the Surface 020#

Contribution Program​

Under the Surface 020#

With our Custom GitPOAPs being now officially enabled, our contribution program is now finally entering its next phase. OpenSource lives of small contributions. We know your time & input is valuable and your contribution should be worth a reward - so as a start, for your help you can earn multiple exclusive GitPOAPs! To earn them, just use Stereum and find a bug or let us know of annoyances you run across. Use the bug template to write an issue & earn some nice rewards.

Custom installation - Showcase Client Switch​

As we told you in the last post, the custom installation is implemented and working. One scenario that the custom installation already enables, is for you to change your client on an existing Ethereum node. To do this, you currently would have to: 

  • Click on "Edit Node"

  • Add the new client  

  • Connect everything and set it up the way you need it 

  • Start the client 

  • When the new Client is synced, simply remove the old one from your node 

  • Add the validator key


Honestly, this is hella convuluted. But we are already working on a simpler solution. You might already have noticed that there is button on top, that will cut this process down to a few clicks. It will join with the next version.  

Multiservice RPC Endpoint Connection & DataAPI Widget​

Under the Surface 020#Under the Surface 020#

With our current update we also extended the RPC Endpoint Connection and the DataAPI widget to be multiservice compatible. This means that if you have multiple clients running on your node, you can see and use all of them in the dashboard at the same time. 

Alerts & Notifications​

We have also recently started working on a feature that we personally are very excited about to build onto in the future - alerts and notifications. With this feature you should have your node even better under control and need to worry even less about your ETH. The alerts & notifications basically refine the already existing Stereum featureset into a powerhouse. We will talk more about this feature in the next posts. But to say as much in advance: It will be a central piece on how Stereum will support you in the future.  

Port Widget ​

Under the Surface 020#Under the Surface 020#

As you also might have noticed already, we have a new feature joining us in the Stereum 2.0 dashboard soon - the “Open Ports” Widget. The list is located here and should allow the user to see the “Public Container Ports” in use. This component will show you ports of a container bound to a network interface, which are used to make p2p connections to Execution Clients or Consensus Clients easier for services to target. Or make services available to the host and forward them via ssh tunnel ports – for example using them you could access Prometheus for widgets. We hope this will make it that much easier for you to find them.  

Network Switch​

Also an important feature we worked on in the last 2 weeks is the - Network Switch. With this you can now easily switch the network of your node with a few clicks. To access go to the Edit Node page, where you can also find the custom installation feature. Here go to the top to change your network by simply clicking the dropdown menu. After you selected the network you want to change to, you will have to click the “confirm” button.

Gnosis Chain Preview​

We are happy to say that 2.0 is so close that we are able to look beyond it. A huge entry barrier for people to get into staking in the first place remains - 32 ETH. A huge number for the average person. We want to set a new treshhold to get into staking. The new staking treshhold will enable you to stake for 1 GNO on the Gnosis Chain. This means that many more people will have the chance to participate in staking, and with Stereum we are lowering the barrier to entry even further. You can look forward to a working One Execution Client - One Consensus Client Combination, you can use to stake on the Gnosis chain at the latest in February of 2023. You can follow our development by keeping an eye on our issue page on GitHub.