gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-05-07 08:52:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Lighthouse Book API and Advanced Usage section (#4300)

Browse Source 
## Issue Addressed

Update Information in Lighthouse Book

## Proposed Changes

- move Validator Graffiti from Advanced Usage to Validator Management
- update API response and command
- some items that aren't too sure I put it in comment, which can be seen in raw/review format but not live


## Additional Info

Please provide any additional information. For example, future considerations
or information useful for reviewers.


Co-authored-by: chonghe <44791194+chong-he@users.noreply.github.com>
This commit is contained in:
chonghe
2023-06-02 03:17:36 +00:00
parent 749a242b0f
commit 6c769ed86c
20 changed files with 706 additions and 278 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
book/src/slasher.md
View File

@@ -8,10 +8,9 @@ extra income for your validators. However it is currently only recommended for e
of the immaturity of the slasher UX and the extra resources required.
## Minimum System Requirements
* Quad-core CPU
* 16 GB RAM
* 256 GB solid state storage (in addition to space for the beacon node DB)
* 256 GB solid state storage (in addition to the space requirement for the beacon node DB)
## How to Run
@@ -28,7 +27,7 @@ messages are filtered for relevancy, and all relevant messages are checked for s
to the slasher database.
You **should** run with debug logs, so that you can see the slasher's internal machinations, and
provide logs to the devs should you encounter any bugs.
provide logs to the developers should you encounter any bugs.
## Configuration
@@ -97,7 +96,7 @@ Both database backends LMDB and MDBX place a hard limit on the size of the datab
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 accommodate the default history length and around 300K validators but
By default the limit is set to accommodate the default history length and around 600K validators (with about 30% headroom) 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.
@@ -108,7 +107,7 @@ If you want an estimate of the database size you can use this formula:
4.56 GB * (N / 256) * (V / 250000)
```
where `V` is the validator count and `N` is the history length.
where `N` is the history length and `V` is the validator count.
You should set the maximum size higher than the estimate to allow room for growth in the validator
count.