danielSanchezQ
commented
6 months ago Is there a possibility of this happening? I mean, why should the previously attested blob come back for verification again?
As the protocol is trustless we do not know why or who may request it, but we need to know how to react to that situations anyway.
Verifiers should know what was already attested, and if it was already attested just skip next same blobs verification attempts.