status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

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 <tersec@users.noreply.github.com>

---------

Co-authored-by: tersec <tersec@users.noreply.github.com>
This commit is contained in:
Miran 2023-11-27 18:48:48 +01:00 committed by GitHub
parent 6dee4d59fe
commit b92a0d631d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/the_nimbus_book/src/migration.md
View File

@ -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. 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**. Once your Nimbus beacon node has synced and you're satisfied that it's working, move to **Step 2**.