Document migrating to Besu (#1115)

* (WIP) Document migrating to Besu

Signed-off-by: Roland Tyler <roland.tyler@consensys.net>

* Navigation edit

Signed-off-by: Roland Tyler <roland.tyler@consensys.net>

* Additional content

Signed-off-by: Roland Tyler <roland.tyler@consensys.net>

* Feedback

Signed-off-by: Roland Tyler <roland.tyler@consensys.net>
pull/1119/head
rolandtyler 2 years ago committed by GitHub
parent daf25602e8
commit 01a150cd90
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
  1. 17
      docs/HowTo/Get-Started/migrate-to-besu.md
  2. 1
      mkdocs.navigation.yml

@ -0,0 +1,17 @@
---
description: Migrate to Besu guide
---
# Migrate to Besu
Migrate from a different Ethereum [execution client](../../Concepts/Merge.md#execution-and-consensus-clients)
to Besu to contribute to [client diversity](https://clientdiversity.org/).
When migrating from a different client, you are [configuring Besu as an execution client](../Upgrade/Prepare-for-The-Merge.md#configure-besu-as-an-execution-client)
and connecting your [consensus client](../../Concepts/Merge.md#consensus-clients) to Besu instead of your original execution client.
To minimize downtime while [Besu syncs](../../Concepts/Node-Types.md) and avoid downtime penalties,
you can sync Besu with a new consensus layer instance.
Once Besu has fully synced you can connect it to your existing consensus client.
Find guides to switch from specific clients on the [client diversity website](https://clientdiversity.org/#switch).

@ -21,6 +21,7 @@ nav:
- Install binary distribution: HowTo/Get-Started/Installation-Options/Install-Binaries.md
- Build from source: HowTo/Get-Started/Installation-Options/Build-from-source.md
- Start Besu: HowTo/Get-Started/Starting-node.md
- Migrate to Besu: HowTo/Get-Started/migrate-to-besu.md
- Configure Besu:
- Consensus protocols:
- QBFT: HowTo/Configure/Consensus-Protocols/QBFT.md

Loading…
Cancel
Save