From 23fb596779247c56391084a32293a140ee4dcec3 Mon Sep 17 00:00:00 2001 From: Jacek Sieka Date: Thu, 15 Sep 2022 13:01:20 +0200 Subject: [PATCH] add link to eth-clients checkpoint sync sources --- docs/the_nimbus_book/src/trusted-node-sync.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/the_nimbus_book/src/trusted-node-sync.md b/docs/the_nimbus_book/src/trusted-node-sync.md index ff75b1337..bc3983383 100644 --- a/docs/the_nimbus_book/src/trusted-node-sync.md +++ b/docs/the_nimbus_book/src/trusted-node-sync.md @@ -13,6 +13,9 @@ Should this node, or your connection to it, be compromised, your node will not b It is possibly to use trusted node sync with a third-party API provider -- see [here](trusted-node-sync.md#verify-you-synced-the-correct-chain) for how to verify that the chain you are given corresponds to the canonical chain at the time. +!!! tip + A list of community-operated checkpoint sync nodes can be found [here](https://eth-clients.github.io/checkpoint-sync-endpoints/) - always verify after after a checkpoint sync that the right chain was provided by the node. + ## Perform a trusted node sync !!! tip