Fallback fee recipient address value

Open Beginner friendly
#777 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 6 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
backend, cli

Research direction

Start by reading the beacon node CLI argument definitions and the local block production path that chooses a fee recipient when prepare_beacon_proposer has supplied none. Trace how the selected value reaches block production, then check the relevant tests or add coverage for the configured fallback and the existing zero address default. Done means --fallback-fee-recipient configures the address used when the proposer has not supplied one.

Written by the indexing model from the issue text.

Description

Currently, when a validator client has not supplied a fee recipient through prepare_beacon_proposer, local block production falls back to the zero address. Operators cannot configure an alternative resulting in validator rewards being lost.

Please add a --fallback-fee-recipient CLI argument for the beacon node, used when no fee recipient has been supplied for the proposer. This is a flag supported by all other CL clients.

Dominant language
Rust
Stars
86
Forks
34
Avg merge
9d 20h
Merged PRs (30d)
77

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lambdaclass/ethlambda

All issues in lambdaclass/ethlambda

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.