You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When charon's broadcaster component broadcasts any duty it logs the Submitted successfully log for all the duties which includes delay duration. Here's the log when validator registrations are broadcasted:
12:32:23.134 INFO bcast Successfully submitted validator registration to beacon node {"delay": "25416h32m0.13494757s", "pubkey": "858_9bf", "duty": "0/builder_registration"}
As we can see in the above log the delay time is incorrect as it takes slot number into account and calculates delay from the genesis time. This should take the delay from the start of current epoch as validator registrations are broadcasted at the start of each epoch.
Has this worked before in a previous version?
No
🔬 Minimal Reproduction
Run v0.17.0 with v1.7.0 cluster-lock with --builder-api-enabled=true.
🔥 Error
12:32:23.134 INFO bcast Successfully submitted validator registration to beacon node {"delay": "25416h32m0.13494757s", "pubkey": "858_9bf", "duty": "0/builder_registration"}
🌍 Your Environment
What version of Charon are you running? (Which release)
v0.17.0
The text was updated successfully, but these errors were encountered:
🐞 Bug Report
Description
When charon's broadcaster component broadcasts any duty it logs the Submitted successfully log for all the duties which includes delay duration. Here's the log when validator registrations are broadcasted:
As we can see in the above log the delay time is incorrect as it takes slot number into account and calculates delay from the genesis time. This should take the delay from the start of current epoch as validator registrations are broadcasted at the start of each epoch.
Has this worked before in a previous version?
No
🔬 Minimal Reproduction
Run v0.17.0 with v1.7.0 cluster-lock with
--builder-api-enabled=true
.🔥 Error
🌍 Your Environment
What version of Charon are you running? (Which release)
The text was updated successfully, but these errors were encountered: