gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-07-01 20:04:41 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix some typos (#3376)

Browse Source 
## Proposed Changes

This PR fixes various minor typos in the project.
This commit is contained in:
Justin Traglia
2022-07-27 00:51:06 +00:00
parent 44fae52cd7
commit 0f62d900fe
16 changed files with 25 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
book/src/slasher.md
View File

@@ -1,6 +1,6 @@
# Running a Slasher
Lighthouse includes a slasher for identifying slashable offences comitted by other validators and
Lighthouse includes a slasher for identifying slashable offences committed by other validators and
including proof of those offences in blocks.
Running a slasher is a good way to contribute to the health of the network, and doing so can earn
@@ -69,7 +69,7 @@ The slasher uses MDBX as its backing store, which places a hard limit on the siz
file. You can use the `--slasher-max-db-size` flag to set this limit. It can be adjusted after
initialization if the limit is reached.
By default the limit is set to accomodate the default history length and around 300K validators but
By default the limit is set to accommodate the default history length and around 300K validators but
you can set it lower if running with a reduced history length. The space required scales
approximately linearly in validator count and history length, i.e. if you halve either you can halve
the space required.
@@ -134,7 +134,7 @@ the slot duration.
### Chunk Size and Validator Chunk Size
* Flags: `--slasher-chunk-size EPOCHS`, `--slasher-validator-chunk-size NUM_VALIDATORS`
* Arguments: number of ecochs, number of validators
* Arguments: number of epochs, number of validators
* Defaults: 16, 256
Adjusting these parameter should only be done in conjunction with reading in detail