add note about not invalidating valid and available blocks

[djrtwo]

This came up on the call today as a path that is not entirely clear in the spec.

I think that this note is either appropriate here (before is_data_available()) or embedded as a comment in on_block() around the call to is_data_available(). Open to thoughts on how to make sure we are abundantly clear here.

[terencechain]

LGTM. Might consider adding an extra mention for ‘with KZG referenced blobs’ to clarify that it’s the block that should be valid, rather than suggesting a valid block could contain an invalid blob

[tbenr]

I think that this note is either appropriate here (before is_data_available()) or embedded as a comment in on_block() around the call to is_data_available(). Open to thoughts on how to make sure we are abundantly clear here.

I think that is good to have a mention on on_block(). The concept that is important to highlight is that if is_data_available fails the block MUST not be considered invalid per se.

While over is_data_available definition is important to highlight that must not fail if sees extraneous blob_sidecars, and MUST return true as long as a valid blob_sidecar has been seen\received for each block's commitment.

[djrtwo]

okay, the warning is now in both places and makes a note about these being in addition to the expected/referenced blobs

[tbenr]

LGTM