# Slot proposed with incorrect fee recipient

**URL:** <https://research.lido.fi/t/slot-proposed-with-incorrect-fee-recipient/9587>\
**Category:** CSM Support\
**Created:** [February 22, 2025, 1:42pm UTC](https://research.lido.fi/t/slot-proposed-with-incorrect-fee-recipient/9587 "2025-02-22T13:42:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![enti](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/enti/32/5380_2.png) [@enti](https://research.lido.fi/u/enti)\
**Post date:** [February 22, 2025, 1:42pm UTC](https://research.lido.fi/t/slot-proposed-with-incorrect-fee-recipient/9587/1 "2025-02-22T13:42:12Z")

</div>

Hello all, earlier today, operator #325 which belongs to me proposed a block on slot [11,116,657](https://beaconcha.in/slot/11116657) with an incorrect fee recipient.

After reviewing my setup, my error is similar to that of [Proposed blocks with wrong fee recipient due to Dappnode-Nimbus bug](https://research.lido.fi/t/proposed-blocks-with-wrong-fee-recipient-due-to-dappnode-nimbus-bug/9057). For some reason the fee recipient in web3signer on dappnode was bypassed, so the fee went to the one set up in the client (my personal address). I reached out to the dappnode guys already to have a look at the issue.

Funds were sent back to the EL Rewards Vault as soon as I noticed in [this transaction](https://etherscan.io/tx/0xfa095a4ba4cfc4cb7331685fd6f0322893677241927d9a225477187164140e89).

FWIW I’m part of the CSM committee, and I will abstain from any votes or comments regarding my situation.