From b92a0d631df7a153c4b2d8fd55ff3bc819cd6e97 Mon Sep 17 00:00:00 2001 From: Miran Date: Mon, 27 Nov 2023 18:48:48 +0100 Subject: [PATCH] fix #4065, explicitly mention trusted node sync (#5611) * fix #4065, explicitly mention trusted node sync * Update docs/the_nimbus_book/src/migration.md Co-authored-by: tersec --------- Co-authored-by: tersec --- docs/the_nimbus_book/src/migration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/the_nimbus_book/src/migration.md b/docs/the_nimbus_book/src/migration.md index 74d78afb7..1f13b0cd1 100644 --- a/docs/the_nimbus_book/src/migration.md +++ b/docs/the_nimbus_book/src/migration.md @@ -22,7 +22,7 @@ Given what's at stake, there is no such thing as a stupid question. No matter which client you are migrating over from, the first step is to sync the Nimbus beacon node. -The easiest way to do this is to follow the [beacon node quick start guide](./quick-start.md). +The easiest and fastest way to do this is to follow the [beacon node quick start guide](./quick-start.md) and perform a [trusted node sync](./trusted-node-sync.md) from the source client. Once your Nimbus beacon node has synced and you're satisfied that it's working, move to **Step 2**.