sigp · mergify · Apr 17, 2025 · Apr 2, 2025 · Apr 2, 2025 · Apr 3, 2025
diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml
@@ -221,7 +221,7 @@ jobs:
                   |Non-Staking Users| <TODO>|---|
 
                   *See [Update
-                  Priorities](https://lighthouse-book.sigmaprime.io/installation-priorities.html)
+                  Priorities](https://lighthouse-book.sigmaprime.io/installation_priorities.html)
                   more information about this table.*
 
                   ## All Changes
@@ -230,7 +230,7 @@ jobs:
 
                   ## Binaries
 
-                  [See pre-built binaries documentation.](https://lighthouse-book.sigmaprime.io/installation-binaries.html)
+                  [See pre-built binaries documentation.](https://lighthouse-book.sigmaprime.io/installation_binaries.html)
 
                   The binaries are signed with Sigma Prime's PGP key: `15E66D941F697E28F49381F426416DC3F30674B0`
 

diff --git a/account_manager/src/validator/exit.rs b/account_manager/src/validator/exit.rs
@@ -27,7 +27,7 @@ pub const PASSWORD_PROMPT: &str = "Enter the keystore password";
 
 pub const DEFAULT_BEACON_NODE: &str = "http://localhost:5052/";
 pub const CONFIRMATION_PHRASE: &str = "Exit my validator";
-pub const WEBSITE_URL: &str = "https://lighthouse-book.sigmaprime.io/voluntary-exit.html";
+pub const WEBSITE_URL: &str = "https://lighthouse-book.sigmaprime.io/validator_voluntary_exit.html";
 
 pub fn cli_app() -> Command {
     Command::new("exit")

diff --git a/beacon_node/client/src/notifier.rs b/beacon_node/client/src/notifier.rs
@@ -353,7 +353,7 @@ async fn bellatrix_readiness_logging<T: BeaconChainTypes>(
         if !beacon_chain.is_time_to_prepare_for_capella(current_slot) {
             error!(
                 info = "you need an execution engine to validate blocks, see: \
-                https://lighthouse-book.sigmaprime.io/merge-migration.html",
+                https://lighthouse-book.sigmaprime.io/archived_merge_migration.html",
                 "Execution endpoint required"
             );
         }
@@ -433,7 +433,7 @@ async fn capella_readiness_logging<T: BeaconChainTypes>(
         if !beacon_chain.is_time_to_prepare_for_deneb(current_slot) {
             error!(
                 info = "you need a Capella enabled execution engine to validate blocks, see: \
-                           https://lighthouse-book.sigmaprime.io/merge-migration.html",
+                           https://lighthouse-book.sigmaprime.io/archived_merge_migration.html",
                 "Execution endpoint required"
             );
         }

diff --git a/book/src/SUMMARY.md b/book/src/SUMMARY.md
@@ -22,6 +22,7 @@
   * [Doppelganger Protection](./validator_doppelganger.md)
   * [Suggested Fee Recipient](./validator_fee_recipient.md)
   * [Validator Graffiti](./validator_graffiti.md)
+  * [Consolidation](./validator_consolidation.md)
 * [APIs](./api.md)
   * [Beacon Node API](./api_bn.md)
     * [Lighthouse API](./api_lighthouse.md)
@@ -61,6 +62,7 @@
   * [Development Environment](./contributing_setup.md)
 * [FAQs](./faq.md)
 * [Protocol Developers](./developers.md)
+  * [Lighthouse Architecture](./developers_architecture.md)
 * [Security Researchers](./security.md)
 * [Archived](./archived.md)
   * [Merge Migration](./archived_merge_migration.md)

diff --git a/book/src/advanced_blobs.md b/book/src/advanced_blobs.md
@@ -6,7 +6,7 @@ In the Deneb network upgrade, one of the changes is the implementation of EIP-48
 
 1. What is the storage requirement for blobs?
 
-   We expect an additional increase of ~50 GB of storage requirement for blobs (on top of what is required by the consensus and execution clients database). The calculation is as below:
+   After Deneb, we expect an additional increase of ~50 GB of storage requirement for blobs (on top of what is required by the consensus and execution clients database). The calculation is as below:
 
    One blob is 128 KB in size. Each block can carry a maximum of 6 blobs. Blobs will be kept for 4096 epochs and pruned afterwards. This means that the maximum increase in storage requirement will be:
 
@@ -16,6 +16,8 @@ In the Deneb network upgrade, one of the changes is the implementation of EIP-48
 
    However, the blob base fee targets 3 blobs per block and it works similarly to how EIP-1559 operates in the Ethereum gas fee. Therefore, practically it is very likely to average to 3 blobs per blocks, which translates to a storage requirement of 48 GB.
 
+   After Electra, the target blobs is increased to 6 blobs per block. This means blobs storage is expected to use ~100GB of disk space.
+
 1. Do I have to add any flags for blobs?
 
    No, you can use the default values for blob-related flags, which means you do not need add or remove any flags.
@@ -25,7 +27,7 @@ In the Deneb network upgrade, one of the changes is the implementation of EIP-48
    Use the flag `--prune-blobs false` in the beacon node. The storage requirement will be:
 
    ```text
-   2**17 bytes * 3 blobs / block * 7200 blocks / day * 30 days = 79GB / month or 948GB / year
+   2**17 bytes * 6 blobs / block * 7200 blocks / day * 30 days = 158GB / month or 1896GB / year
    ```
 
    To keep blobs for a custom period, you may use the flag `--blob-prune-margin-epochs <EPOCHS>` which keeps blobs for 4096+EPOCHS specified in the flag.

diff --git a/book/src/advanced_database_migrations.md b/book/src/advanced_database_migrations.md
@@ -7,7 +7,8 @@ been applied automatically and in a _backwards compatible_ way.
 
 However, backwards compatibility does not imply the ability to _downgrade_ to a prior version of
 Lighthouse after upgrading. To facilitate smooth downgrades, Lighthouse v2.3.0 and above includes a
-command for applying database downgrades.
+command for applying database downgrades. If a downgrade is available _from_ a schema version,
+it is listed in the table below under the "Downgrade available?" header.
 
 **Everything on this page applies to the Lighthouse _beacon node_, not to the
 validator client or the slasher**.
@@ -16,12 +17,8 @@ validator client or the slasher**.
 
 | Lighthouse version | Release date | Schema version | Downgrade available? |
 |--------------------|--------------|----------------|----------------------|
+| v7.0.0             | Apr 2025     | v22            | no                   |
 | v6.0.0             | Nov 2024     | v22            | no                   |
-| v5.3.0             | Aug 2024     | v21            | yes                  |
-| 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).
@@ -209,8 +206,9 @@ Here are the steps to prune historic states:
 
 | Lighthouse version | Release date | Schema version | Downgrade available?                |
 |--------------------|--------------|----------------|-------------------------------------|
+| v7.0.0             | Apr 2025     | v22            | no                                  |
 | v6.0.0             | Nov 2024     | v22            | no                                  |
-| v5.3.0             | Aug 2024     | v21            | yes                                 |
+| v5.3.0             | Aug 2024     | v21            | yes before Electra using <= v7.0.0  |
 | 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    |

diff --git a/book/src/archived.md b/book/src/archived.md
@@ -1,3 +1,3 @@
 # Archived
 
-This section keeps the topics that are deprecated or less applicable for archived purposes.
+This section keeps the topics that are deprecated. Documentation in this section is for informational purposes only and will not be maintained.
diff --git a/book/src/archived-key-management.md → book/src/archived_key_management.md b/book/src/archived-key-management.md → book/src/archived_key_management.md
diff --git a/book/src/archived-merge-migration.md → book/src/archived_merge_migration.md b/book/src/archived-merge-migration.md → book/src/archived_merge_migration.md
diff --git a/book/src/developers_architecture.md b/book/src/developers_architecture.md
@@ -0,0 +1,5 @@
+# Lighthouse architecture
+
+A technical walkthrough of Lighthouse's architecture can be found at: [Lighthouse technical walkthrough](https://www.youtube.com/watch?v=pLHhTh_vGZ0)
+
+![Lighthouse architecture](imgs/developers_architecture.svg)