You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: beacon_chain/nimbus_beacon_node.nim
+4-2Lines changed: 4 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -538,7 +538,8 @@ proc init*(T: type BeaconNode,
538
538
getDepositContractSnapshot(),
539
539
eth1Network,
540
540
config.web3ForcePolling,
541
-
optJwtSecret)
541
+
optJwtSecret,
542
+
config.requireEngineAPI)
542
543
543
544
eth1Monitor.loadPersistedDeposits()
544
545
@@ -639,7 +640,8 @@ proc init*(T: type BeaconNode,
639
640
getDepositContractSnapshot(),
640
641
eth1Network,
641
642
config.web3ForcePolling,
642
-
optJwtSecret)
643
+
optJwtSecret,
644
+
config.requireEngineAPI)
643
645
644
646
if config.rpcEnabled:
645
647
warn"Nimbus's JSON-RPC server has been removed. This includes the --rpc, --rpc-port, and --rpc-address configuration options. https://nimbus.guide/rest-api.html shows how to enable and configure the REST Beacon API server which replaces it."
Copy file name to clipboardExpand all lines: docs/the_nimbus_book/src/merge.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,6 +22,8 @@ As a node operator, you will need to run both an execution client and a consensu
22
22
23
23
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.
24
24
25
+
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).
26
+
25
27
### Prepare a suggested fee recipient
26
28
27
29
After the merge, validators that propose blocks are eligible to recieve transaction fees - read more about fee recipients [here](https://launchpad.ethereum.org/en/merge-readiness#fee-recipient).
0 commit comments