Block proposal resulted in no rewards received

[patrtech77]

Steps to Reproduce

1. [Step 1] NA
2. [Step 2] NA
3. [Step ...] NA

Expected behavior: [What you expect to happen] Reward to be received for block proposal. Block was proposed on Jan 4. Block proposal submitted: 1 validator, Reward: 0.000 ETH

Actual behavior: [What actually happens]

Frequency: [What percentage of the time does it occur?] This is the first time since POS genesis that a block was proposed and no reward received.

Logs

Please post relevant logs from Besu (and the consensus client, if running proof of stake) from before and after the issue.

Versions (Add all that apply)

• Software version: [`besu/v24.12.2/linux-x86_64]
• Java version: openjdk-java-21`]
• OS Name & Version: [Ubuntu 20.04.6 LTS]
• Kernel Version: [Linux NUC 5.15.0-130-generic External mining #140~20.04.1-Ubuntu SMP Wed Dec 18 21:35:34 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux]
• Virtual Machine software & version: [NA]
• Docker Version: [NA]
• Cloud VM, type, size: [Amazon Web Services I3-large]
• Consensus Client & Version if using Proof of Stake: [Lighthouse v6.0.1-0d90135
  BLS library: blst-portable
  BLS hardware acceleration: true
  SHA256 hardware acceleration: false
  Allocator: jemalloc
  Profile: maxperf

besu_logs_EST.log

Specs: mainnet (true), minimal (false), gnosis (true) ]

Smart contract information (If you're reporting an issue arising from deploying or calling a smart contract, please supply related information)

• Solidity version [solc --version]
• Repo with minimal set of deployable/reproducible contract code - please provide a link
• Please include specifics on how you are deploying/calling the contract
• Have you reproduced the issue on other eth clients

Additional Information (Add any of the following or anything else that may be relevant)

• Besu setup info - genesis file, config options
• System info - memory, CPU

[daniellehrner]

The block in question seems to be this one: https://etherscan.io/block/21549714

[patrtech77]

Yes, that's correct. Just wanted to know what happened and if there is anything to do avoid this scenario again in the future?

[fab-10]

@patrtech77 please share the logs around the event for your Consensus Client

[patrtech77]

@fab-10 Attached are the logs from Lighthouse:

Beacon Logs Missed Block Reward 1-4-2025.txt

[fab-10]

@fab-10 Attached are the logs from Lighthouse:

Beacon Logs Missed Block Reward 1-4-2025.txt

I am not able to download this log, maybe a GH issue?

[patrtech77]

Beacon Logs Missed Block Reward 1-4-2025.txt 2nd attempt.

[patrtech77]

@fab-10 Attached are the logs from Lighthouse:
Beacon Logs Missed Block Reward 1-4-2025.txt

I am not able to download this log, maybe a GH issue?

Can you try the above, 2nd attempt seems to work.

[fab-10]

@patrtech77 the download works now, but we need the validator log too for the info about the block proposal, could you share it?

[patrtech77]

@patrtech77 the download works now, but we need the validator log too for the info about the block proposal, could you share it?

@fab-10 Would you be able to help with the command line for the validator logs? I have not looked at these logs before? Thank you

[fab-10]

@patrtech77 unfortunately IDK how Lighthouse works, but in our test instance on Sepolia, we have in the log dir beacon.log and validator.log files, and in the latter, there are the info about the produced block, for example

{"msg":"Requesting unsigned block","level":"INFO","ts":"2025-01-16T13:22:12.002262512Z","service":"block","slot":6775011}
{"msg":"Requesting unsigned block","level":"INFO","ts":"2025-01-16T13:22:12.002344369Z","service":"block","module":"validator_services::block_service:464","slot":6775011}
{"msg":"Received unsigned block","level":"INFO","ts":"2025-01-16T13:22:12.06749179Z","service":"block","slot":6775011}
{"msg":"Received unsigned block","level":"INFO","ts":"2025-01-16T13:22:12.06750291Z","service":"block","module":"validator_services::block_service:573","slot":6775011}
{"msg":"Publishing signed block","level":"INFO","ts":"2025-01-16T13:22:12.093663911Z","service":"block","signing_time_ms":26,"slot":6775011}
{"msg":"Publishing signed block","level":"INFO","ts":"2025-01-16T13:22:12.093668148Z","service":"block","module":"validator_services::block_service:379","signing_time_ms":26,"slot":6775011}
{"msg":"Successfully published block","level":"INFO","ts":"2025-01-16T13:22:12.554860496Z","service":"block","slot":6775011,"graffiti":"Some(\"Besu 🐐 Lighthouse\")","attestations":1,"deposits":0,"block_type":"Full"}
{"msg":"Successfully published block","level":"INFO","ts":"2025-01-16T13:22:12.554894154Z","service":"block","module":"validator_services::block_service:398","slot":6775011,"graffiti":"Some(\"Besu 🐐 Lighthouse\")","attestations":1,"deposits":0,"block_type":"Full"}