Skip to content

Typo Update validator-offline.md #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
voronor wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Typo Update validator-offline.md #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion help/validator-offline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ The penalty for missing attestations is exactly the same as the reward for a suc

[Proposing a block is rare](../rewards/proposal-frequency.md). Depending on the size of the [validator pool](../staking-glossary.md#validator-pool), a single validator will on average only propose a block every few months. If you are unlucky enough to be offline at the time that your validator is asked to propose a block, that's also ok.

The Ethereum network is robust and designed to handle these situations. If you miss your block proposal, the [slot](../staking-glossary.md#slot) that should have contained your block will be empty. Other than the lost [rewards](broken-reference) from missing the block proposal, there are **no penalties or slashing** that occurs from a missed block proposal.
The Ethereum network is robust and designed to handle these situations. If you miss your block proposal, the [slot](../staking-glossary.md#slot) that should have contained your block will be empty. Other than the lost [rewards](broken-reference) from missing the block proposal, there are **no penalties or slashing** that occur from a missed block proposal.

If you have a large number of validators or want to minimize your downtime, [consider running a second consensus and execution client pair and adding this endpoint to your already running validator client. ](https://docs.ethstaker.cc/ethstaker-knowledge-base/tutorials/methods-to-minimize-downtime#running-multiple-consensus-execution-client-pairs)This will ensure that if one of your client pairs goes down, your validator client will automatically fallback to the other one.

Expand Down