From dd0a14aa2e6d2a51101366eb380440343d27c32e Mon Sep 17 00:00:00 2001 From: Jacek Sieka Date: Tue, 6 Sep 2022 07:50:20 +0200 Subject: [PATCH] merge docs update Note the date and time --- docs/the_nimbus_book/src/merge.md | 6 +++++- docs/the_nimbus_book/src/suggested-fee-recipient.md | 2 ++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/docs/the_nimbus_book/src/merge.md b/docs/the_nimbus_book/src/merge.md index c5272f5a6..45d7b3768 100644 --- a/docs/the_nimbus_book/src/merge.md +++ b/docs/the_nimbus_book/src/merge.md @@ -6,7 +6,9 @@ Read more about it [here](https://ethereum.org/en/upgrades/merge/). ## Preparing for the merge -The merge is in its final phase of testing on testnets and is expected to happen later during the year. +The merge happens in two phases, the first of which is the Bellatrix upgrade on the Beacon Chain 2022-09-22 11:34:47 UTC. + +The second phase happens when total difficulty on the execution chain reaches `58750000000000000000000` - it is expected this happens around 2022-09-15, but may come days early or late. ### Bookmark this page! @@ -16,6 +18,8 @@ As the merge draws near, we will continue to update this page with the latest in Leading up to the merge, it is important to [keep Nimbus up to date](./keep-updated.md). Before the merge, the exact version of Nimbus required to participate will be announced, but stakers should be prepared to upgrade their nodes on short notice. +You must be running Nimbus **22.8.0** or later. + ### Set up your Execution Client As a node operator, you will need to run both an execution client and a consensus client after the merge. If you were previously using a third-party web3 provider (such as Infura or Pocket), you will need to [set up an execution client](./eth1.md). diff --git a/docs/the_nimbus_book/src/suggested-fee-recipient.md b/docs/the_nimbus_book/src/suggested-fee-recipient.md index 9b27e0970..dd8042ffe 100644 --- a/docs/the_nimbus_book/src/suggested-fee-recipient.md +++ b/docs/the_nimbus_book/src/suggested-fee-recipient.md @@ -1,5 +1,7 @@ # Set up suggested fee recipient +The fee recipient is an Ethereum address that receives the transaction fees from block production, separately from the proposer reward that accrues on the beacon chain. + A suggested fee recipient offers an execution client, in a merged Ethereum network, a coinbase it might use, based on the validator that is proposing the block. !!! warning