Proposed block with null fee recipient

Hello,

I proposed a block with a null fee recipient. I’ve sent the block reward equivalent as compensation.

Slot: https://beaconcha.in/slot/12015278
Compensation tx: Ethereum Transaction Hash: 0xaae0556dd3... | Etherscan

This was a misconfig on my side when migrating between node setups and has since been fixed.

Cheers,
Sam

7 Likes

Thanks for the quick response and resolution @samcm, misconfiguration can be hard to catch in advance. Hopefully it’s all fixed now, so you’re ready to propose your next CSM block :partying_face:

4 Likes

Since this was clearly a misconfiguration, and @samcm was proactive in addressing it and in reimbursing the protocol for the lost value, I believe that no additional EL-stealing penalty should be reported. Thank you!

5 Likes

As a CSM Commitee Member, I can assure everyone that any issue can be resolved by a general vote. This is the beauty of decentralization. Even if we have any mistakes or misunderstandings, we can always correct them!
Also, you can be sure that our committee is always ready to consider any issues and resolve them as soon as possible!
Just imagine how long it would take to resolve this issue in a centralized structure? For example, if your taxes were calculated incorrectly, then it could take half a year of bureaucracy, nerves and queues to correct such an error. In our case, everything happens with a minimum amount of bureaucracy in the shortest possible time!

5 Likes

I agree with @remus. Happy to see the proactiveness!

6 Likes