tersec
GitHub
parent
3f90fe8a7d
commit
b8e9240ee0
|
|
@ -38,7 +38,6 @@ markdown_extensions:
|
|||
nav:
|
||||
- About:
|
||||
- 'index.md'
|
||||
- 'merge.md'
|
||||
- 'philosophy.md'
|
||||
- 'preparation.md'
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@
|
|||
|
||||
The Nimbus Light Client is a light-weight alternative to running a full beacon node, when setting up an Ethereum execution client for read-only use cases after the merge.
|
||||
|
||||
Execution layer (EL) clients provide the [web3 API](https://ethereum.github.io/execution-apis/api-documentation/) to expose information stored on the Ethereum blockchain. With [the merge 🐼](./merge.md), EL clients can no longer run standalone and require an external component to determine the latest state to sync to.
|
||||
Execution layer (EL) clients provide the [web3 API](https://ethereum.github.io/execution-apis/api-documentation/) to expose information stored on the Ethereum blockchain. Post-merge 🐼, EL clients can no longer run standalone and require an external component to determine the latest state to sync to.
|
||||
|
||||
## Comparison
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ In order to run a beacon node, you need to also be running an execution client -
|
|||
Nimbus has been tested all major execution clients - see the [execution client comparison](https://ethereum.org/en/developers/docs/nodes-and-clients/#execution-clients) for more information.
|
||||
|
||||
!!! warning
|
||||
You need to run your own execution client after [the merge](./merge.md) - relying on third-party services such as Infura, Alchemy and Pocket will not be possible.
|
||||
You need to run your own execution client - relying on third-party services such as Infura, Alchemy and Pocket will not be possible.
|
||||
|
||||
!!! info
|
||||
Syncing an execution client may take hours or even days, depending on your hardware! The backup providers will be synced only when the primary becomes unavailable, which may lead to a small gap in validation duties - this limitation may be lifted in future versions.
|
||||
|
|
@ -78,7 +78,7 @@ Select an execution client and install it, configuring it such that that WebSock
|
|||
|
||||
### 2. Leave the execution client running
|
||||
|
||||
The execution client will be syncing the chain, up to [the merge](./merge.md). Once it reaches this point, it will wait for the beacon node to provide further sync instructions.
|
||||
The execution client will be syncing the chain through the merge transition block. Once it reaches this point, it will wait for the beacon node to provide further sync instructions.
|
||||
|
||||
It is safe to start the beacon node even if the execution client is not yet fully synced and vice versa.
|
||||
|
||||
|
|
|
|||
|
|
@ -19,9 +19,6 @@ Its efficiency and low resource consumption allows it to perform well on all kin
|
|||
|
||||
This book explains the ways in which you can use Nimbus to either monitor the beacon chain or become a fully-fledged validator.
|
||||
|
||||
!!! tip
|
||||
[The Merge 🐼](https://ethereum.org/en/upgrades/merge/) is happening soon! Bookmark our [merge readiness](./merge.md) page to stay on top of how you need to prepare.
|
||||
|
||||
!!! note
|
||||
Staking and becoming a validator on Ethereum requires 32 ETH, a stable high-speed internet connection and an always-on server. Before staking, make sure that you understand the requirements and practice setting up a validator on a testnet. [Pooled staking](https://ethereum.org/en/staking/pools/) and [Staking as a service](https://ethereum.org/en/staking/saas/) are alternative ways to stake in the network. You can also run a Nimbus node without staking.
|
||||
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
This page has been removed - following [the merge](./merge.md) it is no longer possible to use Infura for validation duties.
|
||||
This page has been removed - following the merge it is no longer possible to use Infura for validation duties.
|
||||
|
|
|
|||
|
|
@ -1,35 +1 @@
|
|||
# The Merge
|
||||
|
||||
The Ethereum network is preparing for a major upgrade to merge the beacon chain with the existing proof-of-work execution network, thus transitioning to proof-of-stake.
|
||||
|
||||
Read more about it [here](https://ethereum.org/en/upgrades/merge/).
|
||||
|
||||
## Preparing for the merge
|
||||
|
||||
The merge happens in two phases, the first of which is the Bellatrix upgrade on the Beacon Chain 2022-09-06 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!
|
||||
|
||||
As the merge draws near, we will continue to update this page with the latest information and instructions.
|
||||
|
||||
### Keep Nimbus up to date
|
||||
|
||||
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).
|
||||
|
||||
If you were running an execution client before, make sure to update its configuration to include an option for [JWT secrets](./eth1.md#3-pass-the-jwt-secret-to-nimbus) and engine API.
|
||||
|
||||
Please note that once the Bellatrix fork epoch is reached on 6th of September 2022, Nimbus will refuse to start unless connected to a properly configured execution client. If you need more time to complete the transition, you can temporarily run the beacon node with the command-line option `--require-engine-api-in-bellatrix=no`, but please note that such a setup will stop working once the network TTD is reached (currently estimated to happen on 13th of September, see https://wenmerge.com/ for more up-to-date information).
|
||||
|
||||
### Prepare a suggested fee recipient
|
||||
|
||||
After the merge, validators that propose blocks are eligible to receive transaction fees - read more about fee recipients [here](https://launchpad.ethereum.org/en/merge-readiness#fee-recipient).
|
||||
|
||||
See the [suggested fee recipent page](./suggested-fee-recipient.md) for information about the changes needed to Nimbus.
|
||||
This page has been removed; all Ethereum Foundation-affiliated Ethereum networks have merged.
|
||||
|
|
|
|||
Loading…
Reference in New Issue