Skip to content

Commit afe145b

Browse files
authored
Merge pull request #43 from dappnode/mateu/update-setup-wizard
Update setup-wizard
2 parents 7edd60a + 34cae80 commit afe145b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

setup-wizard.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,17 +17,17 @@ fields:
1717
title: Checkpoint for fast sync
1818
description: >-
1919
To get Lighthouse up and running in only a few minutes, you can start Lighthouse from a recent finalized checkpoint state rather than syncing from genesis. This is substantially **faster** and consumes **less resources** than syncing from genesis, while still providing all the same features. Be sure you are using a trusted node for the fast sync. Check the Check the [Lighthouse docs](https://lighthouse-book.sigmaprime.io/checkpoint-sync.html) for more information.
20-
Use the Dappnode Official endpoint for your network (`https://checkpoint-sync.dappnode.io`, `https://checkpoint-sync-hoodi.dappnode.io`, `https://checkpoint-sync-gnosis.dappnode.io`) or get your checkpoint sync from [Infura](https://infura.io/) (i.e https://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@eth2-beacon.infura.io)
20+
Use the Dappnode Official endpoint for your network (`https://checkpoint-sync.dappnode.net`, `https://checkpoint-sync-hoodi.dappnode.net`, `https://checkpoint-sync-gnosis.dappnode.net`) or get your checkpoint sync from [Infura](https://infura.io/) (i.e https://XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX@eth2-beacon.infura.io)
2121
*Note - If you are going to provide your own checkpoint sync endpoint, make sure you do not use a slash `/` at the end of the URL.*
2222
required: false
2323
- id: feeRecipientAddress
2424
target:
2525
type: environment
2626
name: FEE_RECIPIENT_ADDRESS
2727
service: [beacon-chain, validator]
28-
title: Fee Recipient Address
28+
title: Fee Recipient Address (only fallback)
2929
description: >-
30-
Fee Recipient is a feature that lets you specify a priority fee recipient address on your validator client instance and beacon node. Make sure this is an address you control. After The Merge, Execution Clients will begin depositing priority fees into this address whenever your validator proposes a new block.
30+
This fee recipient address would be only used in case of error of your primary fee recipient. Your primary fee recipient is defined when you import your keys in the staking brain. By default the fallback fee recipient address is `0x0000000000000000000000000000000000000000`.
3131
required: true
3232
pattern: "^0x[a-fA-F0-9]{40}$"
3333
patternErrorMessage: Must be a valid address (0x1fd16a...)

0 commit comments

Comments
 (0)