hyperledger · macfarla · Nov 22, 2024
@@ -53,7 +53,7 @@ The following is an overview of the public network sync modes:
 |-------------------------------------------|-------------|--------------|-------------|
 | [Snap](#snap-synchronization)             | Efficient sync from genesis block, downloading as many trie leaves as possible and reconstructing locally. Faster than fast sync. | Besu version 22.4.0 or later | Cannot switch from fast sync to snap sync mid-process. |
 | [Checkpoint](#checkpoint-synchronization) | Syncs from a specific checkpoint block configured in the genesis file. Fastest sync mode with lowest storage requirements. | Besu version 22.4.3 or later | |
-| [Fast](#fast-synchronization)             | Downloads block headers and transaction receipts, verifies chain from genesis block. | None | Might become impossible to fast sync Ethereum Mainnet in the future. |
+| [Fast](#fast-synchronization)             | Downloads block headers and transaction receipts, verifies chain from genesis block. | None | Deprecated in Besu version 24.11.0 and later. |
 | [Full](#full-synchronization)             | Downloads and verifies the entire blockchain and state from genesis block, building an archive node with full state history. | None | Slowest sync mode, requires the most disk space. |
 
 :::info Private network syncing
@@ -136,12 +136,13 @@ You can restart Besu during a checkpoint sync in case of hardware or software pr
 resumes from the last valid world state and continues to download blocks starting from the last
 downloaded block.
 
-### Fast synchronization
+### Fast synchronization (Deprecated)
 
 :::caution
 
-It might become impossible to sync Ethereum Mainnet using fast sync in the future. If you sync for
-the first time or ever need to re-sync, update Besu to a version that supports newer sync methods.
+Fast sync is deprecated in Besu version 24.11.0 and later. Please read this [blog post](https://www.lfdecentralizedtrust.org/blog/sunsetting-tessera-and-simplifying-hyperledger-besu) for more context on the rationale behind this decision as well as alternative options.
+
+If you sync for the first time or need to re-sync, update Besu to a version that supports newer sync methods.
 
 :::
 

@@ -40,14 +40,14 @@ To define a genesis configuration, create a genesis file (for example, `genesis.
 
 ## Syncing and storage
 
-By default, Besu syncs to the current state of the blockchain using [fast sync](../concepts/node-sync.md#fast-synchronization) in:
+By default, Besu syncs to the current state of the blockchain using [snap sync](../concepts/node-sync.md#snap-synchronization) in:
 
 - Networks specified using [`--network`](../reference/cli/options.md#network) except for the `dev` development network.
 - Ethereum Mainnet.
 
 We recommend using [snap sync](../concepts/node-sync.md#snap-synchronization) for a faster sync, by starting Besu with [`--sync-mode=SNAP`](../reference/cli/options.md#sync-mode).
 
-By default, Besu stores data in the [Forest of Tries](../concepts/data-storage-formats.md#forest-of-tries) format. We recommend using [Bonsai Tries](../concepts/data-storage-formats.md#bonsai-tries) for lower storage requirements, by starting Besu with [`--data-storage-format=BONSAI`](../reference/cli/options.md#data-storage-format).
+By default, Besu stores data in the [Bonsai Tries format](../concepts/data-storage-formats.md#bonsai-tries).
 
 ## Run a node for testing
 

@@ -5582,6 +5582,7 @@ The synchronization mode. Use `SNAP` for [snap sync](../../concepts/node-sync.md
 :::note Notes
 
 - We recommend using snap sync over fast sync because snap sync can be faster by several days.
+- Fast sync is deprecated in Besu version 24.11.0 and later. 
 - It might become impossible to sync Mainnet using fast sync in the future, as clients drop support for fast sync.
   We recommend updating Besu to a version that supports other sync methods.
 - When using a mode other than `FULL`, most historical world state data is unavailable.