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 #20 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 b483b8d + 6dea41a commit 49d3943
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 0 deletions.
1 change: 1 addition & 0 deletions build/entrypoint.sh
Original file line number Diff line number Diff line change
Expand Up @@ -67,4 +67,5 @@ exec -c /home/user/nimbus-eth2/build/nimbus_beacon_node \
--keymanager-address=0.0.0.0 \
--keymanager-token-file=${TOKEN_FILE} \
--graffiti=\"$GRAFFITI\" \
--suggested-fee-recipient="${FEE_RECIPIENT_ADDRESS}" \
$EXTRA_OPTS
11 changes: 11 additions & 0 deletions setup-wizard.yml
Original file line number Diff line number Diff line change
Expand Up @@ -38,4 +38,15 @@ fields:
It's a good idea to add a backup web3 provider in case your main one goes down. For example, if your primary EL client is a local Geth, but you want to use Infura as a backup.
Get your web3 backup from [infura](https://infura.io/) (i.e https://[email protected])
required: false
- id: feeRecipientAddress
target:
type: environment
name: FEE_RECIPIENT_ADDRESS
service: beacon-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...)

0 comments on commit 49d3943

Please sign in to comment.