From 3f9fdec35da6e250ddd020f12272d0ef4502fc6a Mon Sep 17 00:00:00 2001
From: GlacierWalrus <114941647+GlacierWalrus@users.noreply.github.com>
Date: Fri, 12 Jan 2024 18:35:37 +0000
Subject: [PATCH 1/3] Remove reference to PL mainnet lightweight snapshot
---
networks/mainnet/README.md | 1 -
1 file changed, 1 deletion(-)
diff --git a/networks/mainnet/README.md b/networks/mainnet/README.md
index d3eb7477b..bdd74f750 100644
--- a/networks/mainnet/README.md
+++ b/networks/mainnet/README.md
@@ -52,7 +52,6 @@ Also see [Mainnet RPCs](./rpcs.md) and [Mainnet Explorers](./explorers.md).
## Resources
-* [Latest lightweight snapshot](https://snapshots.mainnet.filops.net/minimal/latest) generated with [Lotus](https://lotus.filecoin.io/) by [Protocol Labs](https://protocol.ai/)
* [Latest lightweight snapshot](https://forest-archive.chainsafe.dev/latest/mainnet/) generated with [Forest](http://github.com/ChainSafe/forest) by [ChainSafe](https://chainsafe.io/)
* [Complete Filecoin blockchain archival data](https://forest-archive.chainsafe.dev/list/) generated with [Forest](http://github.com/ChainSafe/forest) by [ChainSafe](https://chainsafe.io/)
* [Status page and incidents](https://filecoin.statuspage.io/)
From 9fb31ab065c8640d836cd69a3da3187b58d6ac30 Mon Sep 17 00:00:00 2001
From: GlacierWalrus <114941647+GlacierWalrus@users.noreply.github.com>
Date: Fri, 12 Jan 2024 18:36:36 +0000
Subject: [PATCH 2/3] Remove reference to calibnet snapshots
---
networks/calibration/README.md | 4 ----
1 file changed, 4 deletions(-)
diff --git a/networks/calibration/README.md b/networks/calibration/README.md
index e42f1fca1..2cd531567 100644
--- a/networks/calibration/README.md
+++ b/networks/calibration/README.md
@@ -43,10 +43,6 @@ Developers can reference pre-existing deals that are already available on the ne
/dns4/bootstrap-3.calibration.fildev.network/tcp/1347/p2p/12D3KooWFWUqE9jgXvcKHWieYs9nhyp6NF4ftwLGAHm4sCv73jjK
```
-## Snapshots
-
-* [Latest minimal snapshot](https://snapshots.calibrationnet.filops.net/minimal/latest.zst)
-
## Active storage providers
The following storage providers are running on the Calibration testnet.
From fafcf8c50a7bdf6fdcf9bf8d80af3e711e572dfd Mon Sep 17 00:00:00 2001
From: GlacierWalrus <114941647+GlacierWalrus@users.noreply.github.com>
Date: Fri, 12 Jan 2024 18:54:15 +0000
Subject: [PATCH 3/3] Replace dead link to lotus-docs
The page linked to was removed in filecoin-project/lotus-docs#698
---
storage-providers/architecture/lotus-components.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/storage-providers/architecture/lotus-components.md b/storage-providers/architecture/lotus-components.md
index 0252ebeb4..1109a66a0 100644
--- a/storage-providers/architecture/lotus-components.md
+++ b/storage-providers/architecture/lotus-components.md
@@ -33,7 +33,7 @@ The machine running the Lotus daemon must be connected to the public internet fo
Syncing the chain is a key role of the daemon. It communicates with the other nodes on the network by sending messages, which are, in turn, collected into [blocks](https://docs.filecoin.io/reference/general/glossary/#block). These blocks are then collected into [tipsets](https://docs.filecoin.io/reference/general/glossary/#tipset). Your Lotus daemon receives the messages on-chain, enabling you to maintain consensus about the state of the Filecoin network with all the other participants.
-Due to the growth in the size of the chain since its genesis, it is not advised for storage providers to sync the entire history of the network. Instead, providers should use the available [lightweight snapshots](https://lotus.filecoin.io/kb/chain-snapshots/) to import the most recent messages. One exception in which a provider would need to sync the entire chain would be to run a blockchain explorer.
+Due to the growth in the size of the chain since its genesis, it is not advised for storage providers to sync the entire history of the network. Instead, providers should use the available [lightweight snapshots](https://docs.filecoin.io/networks/mainnet#resources) to import the most recent messages. One exception in which a provider would need to sync the entire chain would be to run a blockchain explorer.
Synced chain data should be stored on an SSD; however, faster NVMe drives are strongly recommended. A slow chain sync can lead to delays in critical messages being sent on-chain from your Lotus miner, resulting in the faulting of sectors and the slashing of collateral.