Skip to content
This repository has been archived by the owner on Jun 8, 2024. It is now read-only.

Commit

Permalink
Merge pull request #52 from dappnode/pablo/implement-fee-recipient-ad…
Browse files Browse the repository at this point in the history
…dress

Implement-fee-recipient-address
  • Loading branch information
pablomendezroyo authored Jun 14, 2022
2 parents a954eea + e8aed58 commit 7c10c3c
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 0 deletions.
11 changes: 11 additions & 0 deletions setup-wizard.yml
Original file line number Diff line number Diff line change
Expand Up @@ -27,3 +27,14 @@ fields:
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 [Lighthouse docs](https://lighthouse-book.sigmaprime.io/checkpoint-sync.html).
Get your checkpoint sync from [infura](https://infura.io/) (i.e https://[email protected])
required: false
- id: feeRecipientAddress
target:
type: environment
name: FEE_RECIPIENT_ADDRESS
service: validator
title: Fee Recipient Address
description: >-
Fee Recipient is a feature that lets you specify a priority fee recipient address on your validator client instance and beacon node. After The Merge, execution clients will begin depositing priority fees into this address whenever your validator client proposes a new block.
required: true
pattern: "^0x[a-fA-F0-9]{40}$"
patternErrorMessage: Must be a valid address (0x1fd16a...)
1 change: 1 addition & 0 deletions validator/entrypoint.sh
Original file line number Diff line number Diff line change
Expand Up @@ -63,4 +63,5 @@ exec -c lighthouse \
--metrics-address 0.0.0.0 \
--metrics-port 8008 \
--metrics-allow-origin "*" \
--suggested-fee-recipient="${FEE_RECIPIENT_ADDRESS}" \
$EXTRA_OPTS

0 comments on commit 7c10c3c

Please sign in to comment.