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
Seems like there is a bug in the way we calculated attestation inclusion in recent refactor of inclusion checker. Some of the attestation that are marked as never included on-chain were actually included in a block. Here are the logs from core team cluster node outrageous-taxi:
Fix inclusion tracker to handle duplicate attestations per block. That means attestations with identical attestation data, but different aggregation bits.
category: bug
ticket: #2130
🐞 Bug Report
Description
Seems like there is a bug in the way we calculated attestation inclusion in recent refactor of inclusion checker. Some of the attestation that are marked as never included on-chain were actually included in a block. Here are the logs from core team cluster node
outrageous-taxi
:For example, check for first log slot number
5492676
, here's our validator https://goerli.beaconcha.in/validator/0xafd55095b1390d6f075aaac8673bde501d9ec0459cc32b96ba311b4f36d47cf3b2dd846be3833260c92703c26f8c6423#attestations. It says our attestation was included in5492677
.🔬 Minimal Reproduction
Run charon with tag
96af658
.The text was updated successfully, but these errors were encountered: