merge docs update

Note the date and time
This commit is contained in:
Jacek Sieka 2022-09-06 07:50:20 +02:00
parent e183dccc7f
commit dd0a14aa2e
No known key found for this signature in database
GPG Key ID: A1B09461ABB656B8
2 changed files with 7 additions and 1 deletions

View File

@ -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).

View File

@ -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