T'used to be the day earlier than genesis, when all used to be ready, geth used to be in sync, my beacon node paired. Firewalls configured, VLANs galore, hours of preparation supposed not anything neglected.
Then suddenly the whole thing went awry, the SSD in my gadget determined to die. My configs had been long gone, chain information used to be historical past, not anything to do however believe in subsequent day supply.
I discovered myself designing backups and redundancies. Sophisticated techniques ate up my fantasies. Considering additional I got here to understand: being worried about a lot of these disasters used to be rather unwise.
Occasions
The beacon chain has a number of mechanisms to incentivise validator behaviour, all of that are dependant at the present standing of the community, so it’s important to imagine those failure circumstances within the better context of the way different validators may fail when deciding what are, and what are not, profitable tactics of securing your node(s).
As an lively validator, your stability both will increase or decreases, it by no means is going sideways*. Subsequently a beautiful affordable method of maximising your income, is to minimise your downsides. There are three ways your stability can also be decreased by way of the beacon chain:
- Consequences are issued when your validator misses certainly one of their tasks (e.g. as a result of they’re offline)
- State of being inactive Leaks are passed out to validators that pass over their tasks whilst the community is failing to finalise (i.e. when your validator being offline is very correlated with different validators being offline)
- Slashings are given to validators who produce blocks or attestations which can be contradictory and due to this fact may well be utilized in an assault
* On reasonable, a validator’s stability might keep the similar, however for any given responsibility, they’re both rewarded or punished.
Correlation
The impact of a unmarried validator being offline or acting slashable behaviour is small with regards to the whole well being of the beacon chain. It’s due to this fact now not punished closely. By contrast, if many validators are offline, the stability of offline validators can lower a lot more swiftly.
In a similar fashion, if many validators carry out slashable movements on the identical time, from the beacon chain’s viewpoint, that is indistinguishable from an assault. It’s due to this fact handled as such, and 100% of the offending validators’ stake is burned.
As a result of those “anti-correlation” incentives, validators will have to concern extra about disasters that may have an effect on others on the identical time moderately than remoted, particular person problems.
Reasons and their likelihood.
So let’s suppose via some failure circumstances and read about them in the course of the lens of what number of others could be affected on the identical time, and the way badly your validators could be punished.
I disagree with @econoar right here that those are worst case problems. Those are extra average degree problems. House UPS and Twin WAN deal with disasters are not correlated with different customers and so will have to be a ways down your listing of considerations.
🌍 Web/energy failure
In case you are validating from house, then it is extremely most probably you can come across the sort of disasters one day sooner or later. Residential web and tool connections do not need assured uptime. Alternatively, when the web does pass down, or your energy is out, the outage is typically restricted on your house or even then just for a couple of hours.
Until you’ve got very spotty web/energy, it may not be profitable paying for fall-over connections. You can obtain a couple of hours of consequences, however as the remainder of the community is working usually, your consequences will probably be kind of equivalent to what your rewards would were over the similar duration. In different phrases, a ok hour-long failure units your validator’s stability again to kind of the place it used to be ok hours earlier than the failure, and in ok further hours your validator’s stability will probably be again to its pre-failure quantity.
[Validator #12661 regaining ETH as quickly as it was lost – Beaconcha.in
🛠 Hardware failure
Like internet failure, hardware failure strikes randomly, and when it does, your node might be down for a few days. It is valuable to consider the expected rewards over the lifetime of the validator versus the cost of redundant hardware. Is the expected value of the failure (the offline penalties times the chance of it happening) greater than the cost of the redundant hardware?
Personally, the chance of failure is low enough and the cost of fully redundant hardware high enough, that it almost certainly isn’t worth it. But then again, I am not a whale 🐳 ; as with any failure scenario, you need to evaluate how this applies to your particular situation.
☁️ Cloud services failure
Maybe, to avoid the risks of hardware or internet failure altogether, you decide to go with a cloud provider. With a cloud provider, you have introduced the risk of correlated failures. The question that matters is, how many other validators are using the same cloud provider as you?
A week before genesis, Amazon AWS had a prolonged outage which affected a large portion of the web. If something similar were to happen now, enough validators would go offline at the same time that the inactivity penalties would kick in.
Even worse, if a cloud provider were to duplicate the VM running your node and accidentally leave the old and the new node running at the same time, you could be slashed (the penalties incurred would be especially bad if this accidental duplication affected many other nodes too).
If you are insistent on relying on a cloud provider, consider switching to a smaller provider. It may end up saving you a lot of ETH.
🥩 Staking Services
There are several staking services on mainnet today with varying degrees of decentralisation, but they all contain an increased risk of correlated failures if you trust them with your ETH. These services are necessary components of the eth2 ecosystem, especially for those with less than 32 ETH or without the technical know-how to stake, but they are architected by humans and therefore imperfect.
If staking pools eventually grow to be as large as eth1 mining pools, then it is conceivable that a bug could cause mass slashings or inactivity penalties for their members.
🔗 Infura Failure
Last month Infura went down for 6 hours causing outages across the Ethereum ecosystem; it is easy to see how this is likely to result in correlated failures for eth2 validators.
In addition, 3rd party eth1 API providers necessarily rate-limit calls to their service: In the past this has caused validators to be unable to produce valid blocks (on the Medalla testnet).
The best solution is to run your own eth1 node: you won’t encounter rate-limiting, it will reduce the likelihood of your failures being correlated, and it will improve the decentralisation of the network as a whole.
Eth2 clients have also started adding the possibility of specifying multiple eth1 nodes. This makes it easy to switch to a backup endpoint, in the event your primary endpoint fails (Lighthouse: –eth1-endpoints, Prysm: PR#8062, Nimbus & Teku will likely add support somewhere in the future).
I highly recommend adding backup API options as cheap/free insurance (EthereumNodes.com shows the free and paid API endpoints and their current status). This is useful whether you are running your own eth1 node or not.
🦏 Failure of a particular eth2 client
Despite all the code review, audits, and rockstar work, all of the eth2 clients have bugs hiding somewhere. Most of them are minor and will be caught before they present a major problem in production, but there is always the chance that the client you choose will go offline or cause you to be slashed. If this were to happen, you would not want to be running a client with > 1/3 of the nodes on the network.
You must strike a tradeoff between what you deem to be the best client vs how popular that client is. Consider reading through the documentation of another client so that if something happens to your node, you know what to expect in terms of installing and configuring a different client.
If you have lots of ETH at stake, it is probably worth running multiple clients each with some of your ETH to avoid putting all your eggs in one basket. Otherwise, Vouch is an interesting offering for multi-node staking infrastructure, and Secret Shared Validators are seeing rapid development.
🦢 Black swans
There are of course many unlikely, unpredictable, yet dangerous scenarios that will always present a risk. Scenarios that lie outside the obvious decisions about your staking set-up. Examples such as Spectre and Meltdown at the hardware level, or kernel bugs such as BleedingTooth hint at some of the hazards that exist across the entire hardware stack. By definition, it is not possible to entirely predict and avoid these problems, instead you generally must react after the fact.
What to worry about
Ultimately this comes down to calculating the expected value E(X) of a given failure: how likely an event is to happen, and what the penalties would be if it did. It is vital to consider these failures in the context of the rest of the eth2 network since the correlation greatly affects the penalties at hand. Comparing the expected cost of a failure to the cost of mitigating it will give you the rational answer as to whether it is worth getting in front of.
No one knows all the ways a node can fail, nor how likely each failure is, but by making individual estimates of the chances of each failure type and mitigating the biggest risks, the “wisdom of the crowd” will prevail and on average the network as a whole will make a good estimate. Furthermore, because of the different risks each validator faces, and the differing estimates of those risks, the failures you did not account for will be caught by others and therefore the degree of correlation will be reduced. Yay decentralisation!
📕 DON’T PANIC
Finally, if something does happen to your node, don’t panic! Even during inactivity leaks, penalties are small on short time scales. Take a few moments to think through what happened and why. Then make a plan of action to fix the problem. Then take a deep breath before you proceed. An extra 5 minutes of penalties is preferable to being slashed because you did something ill-advised in a rush.
Most of all: 🚨 Do not run 2 nodes with the same validator keys! 🚨
Thanks Danny Ryan, Joseph Schweitzer, and Sacha Yves Saint-Leger for review
[Slashings because validators ran >1 node – Beaconcha.in]
