Closed stefa2k closed 3 years ago
Thank you for reporting this. It's a pretty odd one, in that the only way this could occur is if the beacon node that gave us the attestation then fails to return the block for which the attestation has been made! Do you know which beacon node this was, out of curiosity?
I'll make a fix for this ASAP.
Hey, thanks for the fast reply! Don't know which beacon, I was in the process of updating a node with multiple clients (lighthouse, prysm, teku) as well as rebooting the host. Running multiple vouch instances and having this on each vouch when rebooting the host on which the beacon-node-address
client is residing on.