Merge branch 'unstable' into vc-fallback

This commit is contained in:
Mac L
2024-07-16 21:39:40 +10:00
116 changed files with 3449 additions and 3100 deletions

View File

@@ -16,21 +16,19 @@ validator client or the slasher**.
| Lighthouse version | Release date | Schema version | Downgrade available? |
|--------------------|--------------|----------------|----------------------|
| v5.2.0 | Jun 2024 | v19 | yes before Deneb |
| v5.1.0 | Mar 2024 | v19 | yes before Deneb |
| v5.0.0 | Feb 2024 | v19 | yes before Deneb |
| v4.6.0 | Dec 2023 | v19 | yes before Deneb |
| v4.6.0-rc.0 | Dec 2023 | v18 | yes before Deneb |
| v4.5.0 | Sep 2023 | v17 | yes |
| v4.4.0 | Aug 2023 | v17 | yes |
| v4.3.0 | Jul 2023 | v17 | yes |
| v4.2.0 | May 2023 | v17 | yes |
| v4.1.0 | Apr 2023 | v16 | no |
| v4.0.1 | Mar 2023 | v16 | no |
| v5.3.0 | Aug 2024 TBD | v22 TBD | no (TBD) |
| v5.2.0 | Jun 2024 | v19 | no |
| v5.1.0 | Mar 2024 | v19 | no |
| v5.0.0 | Feb 2024 | v19 | no |
| v4.6.0 | Dec 2023 | v19 | no |
> **Note**: All point releases (e.g. v4.4.1) are schema-compatible with the prior minor release
> (e.g. v4.4.0).
> **Note**: Even if no schema downgrade is available, it is still possible to move between versions
> that use the same schema. E.g. you can downgrade from v5.2.0 to v5.0.0 because both use schema
> v19.
> **Note**: Support for old schemas is gradually removed from newer versions of Lighthouse. We
usually do this after a major version has been out for a while and everyone has upgraded. Deprecated
schema versions for previous releases are archived under
@@ -210,12 +208,15 @@ Here are the steps to prune historic states:
| Lighthouse version | Release date | Schema version | Downgrade available? |
|--------------------|--------------|----------------|-------------------------------------|
| v4.6.0 | Dec 2023 | v19 | yes before Deneb |
| v4.6.0-rc.0 | Dec 2023 | v18 | yes before Deneb |
| v4.5.0 | Sep 2023 | v17 | yes |
| v4.4.0 | Aug 2023 | v17 | yes |
| v4.3.0 | Jul 2023 | v17 | yes |
| v4.2.0 | May 2023 | v17 | yes |
| v5.2.0 | Jun 2024 | v19 | yes before Deneb using <= v5.2.1 |
| v5.1.0 | Mar 2024 | v19 | yes before Deneb using <= v5.2.1 |
| v5.0.0 | Feb 2024 | v19 | yes before Deneb using <= v5.2.1 |
| v4.6.0 | Dec 2023 | v19 | yes before Deneb using <= v5.2.1 |
| v4.6.0-rc.0 | Dec 2023 | v18 | yes before Deneb using <= v5.2.1 |
| v4.5.0 | Sep 2023 | v17 | yes using <= v5.2.1 |
| v4.4.0 | Aug 2023 | v17 | yes using <= v5.2.1 |
| v4.3.0 | Jul 2023 | v17 | yes using <= v5.2.1 |
| v4.2.0 | May 2023 | v17 | yes using <= v5.2.1 |
| v4.1.0 | Apr 2023 | v16 | yes before Capella using <= v4.5.0 |
| v4.0.1 | Mar 2023 | v16 | yes before Capella using <= v4.5.0 |
| v3.5.0 | Feb 2023 | v15 | yes before Capella using <= v4.5.0 |

View File

@@ -241,7 +241,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]
@@ -505,6 +505,8 @@ Flags:
--disable-quic
Disables the quic transport. The node will rely solely on the TCP
transport for libp2p connections.
--disable-self-limiter
Disables the outbound rate limiter (requests sent by this node).
--disable-upnp
Disables UPnP support. Setting this will prevent Lighthouse from
attempting to automatically establish external port mappings.
@@ -575,12 +577,6 @@ Flags:
When present, Lighthouse will forget the payload statuses of any
already-imported blocks. This can assist in the recovery from a
consensus failure caused by the execution layer.
--self-limiter
Enables the outbound rate limiter (requests made by this node). Use
the self-limiter-protocol flag to set per protocol configurations. If
the self rate limiter is enabled and a protocol is not present in the
configuration, the quotas used for the inbound rate limiter will be
used.
--shutdown-after-sync
Shutdown beacon node as soon as sync is completed. Backfill sync will
not be performed before shutdown.

View File

@@ -23,7 +23,7 @@ Commands:
is the recommended way to provide a network boot-node since it has a
reduced attack surface compared to a full beacon node.
database_manager
Manage a beacon node database [aliases: db]
Manage a beacon node database. [aliases: db]
validator_client
When connected to a beacon node, performs the duties of a staked
validator (e.g., proposing blocks and attestations). [aliases: v, vc,
@@ -70,7 +70,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]

View File

@@ -86,7 +86,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]

View File

@@ -62,7 +62,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]

View File

@@ -74,7 +74,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]

View File

@@ -43,7 +43,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]

View File

@@ -63,7 +63,7 @@ Options:
[possible values: DEFAULT, JSON]
--logfile-max-number <COUNT>
The maximum number of log files that will be stored. If set to 0,
background file logging is disabled. [default: 5]
background file logging is disabled. [default: 10]
--logfile-max-size <SIZE>
The maximum size (in MB) each log file can grow to before rotating. If
set to 0, background file logging is disabled. [default: 200]