RPC nodes, Layer 2 solutions and Staking made easier and more resilient at a lower cost
Launchnodes pre-synced Geth node makes staking ETH easier and cheaper. It can be used by all consensus layer clients running on cloud or bare metal. Synching a Geth node usually takes up to 3 days, but a Launchnodes pre-synced Geth takes just 2- 4 hours.
Launchnodes takes no staking commission from clients. Instead, it provides software and professional services so clients can become Solo Stakers and keep all the returns from their Ethereum staking operations.
All Ethereum Layer 2 solutions also require Geth, an easy-to-run Pre-synced node running on AWS supports building in the Layer 2 ecosystem.
Our focus on Ethereum Solo Staking and our desire for mass participation means we provide all the ‘LEGO bricks’ involved in ETH staking for clients to build their own solutions, using Launchnodes as a fully managed service or Level 3 technical support.
Geth connects computing infrastructure to the Ethereum network. It is a software client that serves as a node for the Ethereum blockchain. It is referred to as the execution layer client now that Ethereum is a Proof of Stake network.
Geth is used for creating software which runs on the EVM (Ethereum Virtual Machine) and is used by the Ethereum Beacon Chain. The beacon nodes that form the chain do the work of attesting and producing blocks.
Today solo staking is done by running one of 4 major node clients to which 32 ETH is attached through the Ethereum launchpad.
To stake ETH on any consensus layer client requires an execution layer client. Today the most useful execution layer client is Geth, due to how extensively it is used, the developer community that supports it and the documentation around it.
Using Launchnodes’ pre-synced Geth client on AWS allows customers to solo stake ETH using any consensus layer client. It also makes it much easier to do so, as our Geth for staking node allows you to sync your staking infrastructure much more quickly, reducing the time from days to a few hours.
Customers use Launchnodes’ Geth nodes to build highly resilient staking architectures using public cloud and their own data centre infrastructure.
A pre-synced node saves you the syncing time, which varies but can be more than 2 days. Using Launchnodes’ pre-synced nodes, it will take you a few hours at most.
As Geth is mission critical in your staking operation, having a high availability instance that is synchronised in a short period of time to the network, empowers your technical teams to keep your staking validator nodes 100% effective.
Using a Launchnodes pre-synced Geth node allows you to stake ETH more easily and at a lower cost on your own infrastructure or using AWS, Azure or GCP.
It also enables clients to choose their consensus layer client or run a mix of different clients easily and with higher levels of resilience.
After the Merge, running your own execution layer client becomes essential in order to earn your Maximal Extractable Value (MEV). So if you are running validators pre-Merge using a shared execution layer client then you need to start running your own.
Providing a pre-synced Geth node is most useful today. However, Launchnodes will look at all clients and make them available when we think the clients are robust and do not constitute a risk to those staking ETH at scale or hyperscale.
Post Merge a pre-synced Geth node allows you to get nodes up and running faster irrespective of the consensus layer client you are using, also irrespective of what or where your infrastructure is running.
Geth is used by all Ethereum Layer 2 solutions and so providing a high availability pre-synced node helps all people and organisations building in the Ethereum ecosystem.
Using APIs as a substitute for running your own Geth client has risks. The frequency of the calls that you need to make to ensure optimal Ethereum staking returns can be expensive and potential latency problems mean you might experience performance issues on your validator nodes. This is why the Ethereum Foundation does not recommend it, and Infura also states that their super useful set of APIs are not suitable for staking.