cerc-io/lighthouse
16
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Correct table formatting in Lighthouse book (#4407)

Browse Source 
This is only a minor correction to the table not properly showing up in Lighthouse book. The changes solves the formatting issue. Another change is on the link to do port-forwarding.
This commit is contained in:
chonghe 2023-06-16 06:44:32 +00:00
parent affea585f4
commit 2bb62b7f7d
2 changed files with 12 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
book/src/faq.md
View File

@ -386,7 +386,7 @@ For these reasons, we recommend that you make your node publicly accessible.
Lighthouse supports UPnP. If you are behind a NAT with a router that supports Lighthouse supports UPnP. If you are behind a NAT with a router that supports
UPnP, you can simply ensure UPnP is enabled (Lighthouse will inform you in its UPnP, you can simply ensure UPnP is enabled (Lighthouse will inform you in its
initial logs if a route has been established). You can also manually [set up port mappings](./advanced_networking.md) in your router to your local Lighthouse instance. By default, initial logs if a route has been established). You can also manually [set up port mappings/port forwarding](./advanced_networking.md/#how-to-open-ports) in your router to your local Lighthouse instance. By default,
Lighthouse uses port 9000 for both TCP and UDP. Opening both these ports will Lighthouse uses port 9000 for both TCP and UDP. Opening both these ports will
make your Lighthouse node maximally contactable. make your Lighthouse node maximally contactable.

21
book/src/voluntary-exit.md
View File

@ -101,16 +101,17 @@ There are two types of withdrawal credentials, `0x00` and `0x01`. To check which
<div align="center"> <div align="center">
| Number of eligible validators | Ideal scenario *n* | Practical scenario *n* | | Number of eligible validators | Ideal scenario *n* | Practical scenario *n* |
|-------------------------------|--------------------| ---------------------- | |:----------------:|:---------------------:|:----:|
| 300000 | 2.60 | 2.63 | | 300000 | 2.60 | 2.63 |
| 400000 | 3.47 | 3.51 | | 400000 | 3.47 | 3.51 |
| 500000 | 4.34 | 4.38 | | 500000 | 4.34 | 4.38 |
| 600000 | 5.21 | 5.26 | | 600000 | 5.21 | 5.26 |
| 700000 | 6.08 | 6.14 | | 700000 | 6.08 | 6.14 |
| 800000 | 6.94 | 7.01 | | 800000 | 6.94 | 7.01 |
| 900000 | 7.81 | 7.89 | | 900000 | 7.81 | 7.89 |
| 1000000 | 8.68 | 8.77 | | 1000000 | 8.68 | 8.77 |
</div> </div>
> Note: Ideal scenario assumes no block proposals are missed. This means a total of withdrawals of 7200 blocks/day * 16 withdrawals/block = 115200 withdrawals/day. Practical scenario assumes 1% of blocks are missed per day. As an example, if there are 700000 eligible validators, one would expect a waiting time of slightly more than 6 days. > Note: Ideal scenario assumes no block proposals are missed. This means a total of withdrawals of 7200 blocks/day * 16 withdrawals/block = 115200 withdrawals/day. Practical scenario assumes 1% of blocks are missed per day. As an example, if there are 700000 eligible validators, one would expect a waiting time of slightly more than 6 days.