Chain inclusion for builder_proposer is not working as expected
#2661
Comments
obol-bulldozer bot
pushed a commit
that referenced
this issue
Nov 1, 2023
Fixes inclusion checker bug which was reporting false negatives about the inclusion blinded blocks. This happened because of misconfiguration between deadline of a duty and inclusion checker lag. Duty deadline of `builder_proposer` is 5 slots while inclusion lag is 4 slots. Inclusion checker should start checking after duty deadline is hit to avoid getting any submissions after that. Which is why even the blinded block was _actually_ proposed successfully, inclusion checker marked it failed as duty was still active and retryer was busy retrying `blinded_block` submission request. category: bug ticket: #2661
|
Closed by #2670 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐞 Bug Report
Description
Recently as part of tracking successes of blinded blocks using tracker we found out that some peers in the cluster were reporting failures due to chain inclusion error but the block was proposed successfully.
Has this worked before in a previous version?
No.
🔬 Minimal Reproduction
Check the logs of the cluster:
DSRV-3cluster🔥 Error
But this block was actually proposed successfully: https://goerli.beaconcha.in/slot/6817827
🌍 Your Environment
What version of Charon are you running? (Which release)
Anything else relevant (validator index / public key)?
Public key: 0xa09953ebb5f425910fed77ef08fbe091a816cb3756f1a4423e58fa1a8d0e9a7730ebbb98a64804b6354a221e3813ed62
Validator Index: 586718
The text was updated successfully, but these errors were encountered: