This repository has been archived by the owner on Jun 8, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 6
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #52 from dappnode/pablo/implement-fee-recipient-ad…
…dress Implement-fee-recipient-address
- Loading branch information
Showing
2 changed files
with
12 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -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...) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters